Message ID | 20231204004726.483558-1-gshan@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | Unified CPU type check | expand |
Hi Phil, On 12/4/23 10:47, Gavin Shan wrote: > This series bases on Phil's repository because the prepatory commits > have been queued to the branch. > > https://gitlab.com/philmd/qemu.git (branch: cpus-next) > > There are two places where the user specified CPU type is checked to see > if it's supported or allowed by the board: machine_run_board_init() and > mc->init(). We don't have to maintain two duplicate sets of logic. This > series intends to move the check to machine_run_board_init() so that we > have unified CPU type check. > > This series can be checked out from: > > git@github.com:gwshan/qemu.git (branch: kvm/cpu-type) > > PATCH[1-4] refactors and improves the logic to validate CPU type in > machine_run_board_init() > PATCH[5-9] validates the CPU type in machine_run_board_init() for the > individual boards > > v6: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg00768.html > v7: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01045.html > v8: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01168.html > Ping to see if there is a chance to queue it up before the Chrismas? :) Thanks, Gavin
On 12/12/23 05:55, Gavin Shan wrote: > Hi Phil, > > On 12/4/23 10:47, Gavin Shan wrote: >> This series bases on Phil's repository because the prepatory commits >> have been queued to the branch. >> >> https://gitlab.com/philmd/qemu.git (branch: cpus-next) >> >> There are two places where the user specified CPU type is checked to see >> if it's supported or allowed by the board: machine_run_board_init() and >> mc->init(). We don't have to maintain two duplicate sets of logic. This >> series intends to move the check to machine_run_board_init() so that we >> have unified CPU type check. >> >> This series can be checked out from: >> >> git@github.com:gwshan/qemu.git (branch: kvm/cpu-type) >> >> PATCH[1-4] refactors and improves the logic to validate CPU type in >> machine_run_board_init() >> PATCH[5-9] validates the CPU type in machine_run_board_init() for the >> individual boards >> >> v6: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg00768.html >> v7: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01045.html >> v8: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01168.html >> > > Ping to see if there is a chance to queue it up before the Chrismas? :) Series queued. "Before" Christmas will depend on the final release tag. Thanks for the various iterations, Phil.
On 12/13/23 20:08, Philippe Mathieu-Daudé wrote: > On 12/12/23 05:55, Gavin Shan wrote: >> On 12/4/23 10:47, Gavin Shan wrote: >>> This series bases on Phil's repository because the prepatory commits >>> have been queued to the branch. >>> >>> https://gitlab.com/philmd/qemu.git (branch: cpus-next) >>> >>> There are two places where the user specified CPU type is checked to see >>> if it's supported or allowed by the board: machine_run_board_init() and >>> mc->init(). We don't have to maintain two duplicate sets of logic. This >>> series intends to move the check to machine_run_board_init() so that we >>> have unified CPU type check. >>> >>> This series can be checked out from: >>> >>> git@github.com:gwshan/qemu.git (branch: kvm/cpu-type) >>> >>> PATCH[1-4] refactors and improves the logic to validate CPU type in >>> machine_run_board_init() >>> PATCH[5-9] validates the CPU type in machine_run_board_init() for the >>> individual boards >>> >>> v6: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg00768.html >>> v7: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01045.html >>> v8: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01168.html >>> >> >> Ping to see if there is a chance to queue it up before the Chrismas? :) > > Series queued. "Before" Christmas will depend on the final release tag. > > Thanks for the various iterations, > Phil, thank you for you continuous reviews and valuable comments. Yes, the final merge to master branch depends on the release plan. 'queue' meant to merge the series to your 'cpus-next' branch ;-) Thanks, Gavin
Hi Gavin, On 13/12/23 11:54, Gavin Shan wrote: > On 12/13/23 20:08, Philippe Mathieu-Daudé wrote: >> On 12/12/23 05:55, Gavin Shan wrote: >>> On 12/4/23 10:47, Gavin Shan wrote: >>>> This series bases on Phil's repository because the prepatory commits >>>> have been queued to the branch. >>>> >>>> https://gitlab.com/philmd/qemu.git (branch: cpus-next) >>>> >>>> There are two places where the user specified CPU type is checked to >>>> see >>>> if it's supported or allowed by the board: machine_run_board_init() and >>>> mc->init(). We don't have to maintain two duplicate sets of logic. This >>>> series intends to move the check to machine_run_board_init() so that we >>>> have unified CPU type check. >>>> >>>> This series can be checked out from: >>>> >>>> git@github.com:gwshan/qemu.git (branch: kvm/cpu-type) >>>> >>>> PATCH[1-4] refactors and improves the logic to validate CPU type in >>>> machine_run_board_init() >>>> PATCH[5-9] validates the CPU type in machine_run_board_init() for the >>>> individual boards >>>> >>>> v6: >>>> https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg00768.html >>>> v7: >>>> https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01045.html >>>> v8: >>>> https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01168.html >>>> >>> >>> Ping to see if there is a chance to queue it up before the Chrismas? :) >> >> Series queued. "Before" Christmas will depend on the final release tag. >> >> Thanks for the various iterations, >> > > Phil, thank you for you continuous reviews and valuable comments. > > Yes, the final merge to master branch depends on the release plan. > 'queue' meant to merge the series to your 'cpus-next' branch ;-) I had to fix 3 different issues caught by our CI. Next time please run your series on GitLab CI, you just have to push your branch and wait for the result :) Now merged as 445946f4dd..cd75cc6337. Happy new year!
Hi Phil, On 1/6/24 08:12, Philippe Mathieu-Daudé wrote: > On 13/12/23 11:54, Gavin Shan wrote: >> On 12/13/23 20:08, Philippe Mathieu-Daudé wrote: >>> On 12/12/23 05:55, Gavin Shan wrote: >>>> On 12/4/23 10:47, Gavin Shan wrote: >>>>> This series bases on Phil's repository because the prepatory commits >>>>> have been queued to the branch. >>>>> >>>>> https://gitlab.com/philmd/qemu.git (branch: cpus-next) >>>>> >>>>> There are two places where the user specified CPU type is checked to see >>>>> if it's supported or allowed by the board: machine_run_board_init() and >>>>> mc->init(). We don't have to maintain two duplicate sets of logic. This >>>>> series intends to move the check to machine_run_board_init() so that we >>>>> have unified CPU type check. >>>>> >>>>> This series can be checked out from: >>>>> >>>>> git@github.com:gwshan/qemu.git (branch: kvm/cpu-type) >>>>> >>>>> PATCH[1-4] refactors and improves the logic to validate CPU type in >>>>> machine_run_board_init() >>>>> PATCH[5-9] validates the CPU type in machine_run_board_init() for the >>>>> individual boards >>>>> >>>>> v6: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg00768.html >>>>> v7: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01045.html >>>>> v8: https://lists.nongnu.org/archive/html/qemu-arm/2023-11/msg01168.html >>>>> >>>> >>>> Ping to see if there is a chance to queue it up before the Chrismas? :) >>> >>> Series queued. "Before" Christmas will depend on the final release tag. >>> >>> Thanks for the various iterations, >>> >> >> Phil, thank you for you continuous reviews and valuable comments. >> >> Yes, the final merge to master branch depends on the release plan. >> 'queue' meant to merge the series to your 'cpus-next' branch ;-) > > I had to fix 3 different issues caught by our CI. Next time please > run your series on GitLab CI, you just have to push your branch and > wait for the result :) > > Now merged as 445946f4dd..cd75cc6337. > > Happy new year! > Happy new year. I just came back from holiday. Thanks for the reminder for GitLab CI, which I don't know how to run yet. I will learn how to run it from gitlab :) Thanks, Gavin