From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gavin Shan <gshan@redhat.com>, qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
peter.maydell@linaro.org, b.galvani@gmail.com,
strahinja.p.jankovic@gmail.com, imammedo@redhat.com,
kfting@nuvoton.com, wuhaotsh@google.com,
nieklinnenbank@gmail.com, rad@semihalf.com,
quic_llindhol@quicinc.com, marcin.juszkiewicz@linaro.org,
eduardo@habkost.net, marcel.apfelbaum@gmail.com,
armbru@redhat.com, wangyanan55@huawei.com, vijai@behindbytes.com,
palmer@dabbelt.com, alistair.francis@wdc.com,
bin.meng@windriver.com, liwei1518@gmail.com,
dbarboza@ventanamicro.com, zhiwei_liu@linux.alibaba.com,
shan.gavin@gmail.com
Subject: Re: [PATCH v9 0/9] Unified CPU type check
Date: Wed, 13 Dec 2023 11:08:32 +0100 [thread overview]
Message-ID: <ff0237a8-9e1c-46bf-ae69-99c3f33112f6@linaro.org> (raw)
In-Reply-To: <0b2aaedf-7a4c-49f4-b4af-71f9ab693207@redhat.com>
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.
next prev parent reply other threads:[~2023-12-13 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 0:47 [PATCH v9 0/9] Unified CPU type check Gavin Shan
2023-12-04 0:47 ` [PATCH v9 1/9] machine: Use error handling when CPU type is checked Gavin Shan
2024-01-05 11:00 ` Philippe Mathieu-Daudé
2024-01-08 1:11 ` Gavin Shan
2023-12-04 0:47 ` [PATCH v9 2/9] machine: Introduce helper is_cpu_type_supported() Gavin Shan
2023-12-04 0:47 ` [PATCH v9 3/9] machine: Improve is_cpu_type_supported() Gavin Shan
2024-01-05 22:09 ` Philippe Mathieu-Daudé
2024-01-08 1:21 ` Gavin Shan
2023-12-04 0:47 ` [PATCH v9 4/9] machine: Print CPU model name instead of CPU type Gavin Shan
2023-12-04 0:47 ` [PATCH v9 5/9] hw/arm/virt: Hide host CPU model for tcg Gavin Shan
2023-12-04 0:47 ` [PATCH v9 6/9] hw/arm/virt: Check CPU type in machine_run_board_init() Gavin Shan
2023-12-04 0:47 ` [PATCH v9 7/9] hw/arm/sbsa-ref: " Gavin Shan
2023-12-04 0:47 ` [PATCH v9 8/9] hw/arm: " Gavin Shan
2023-12-04 0:47 ` [PATCH v9 9/9] hw/riscv/shakti_c: " Gavin Shan
2023-12-12 4:55 ` [PATCH v9 0/9] Unified CPU type check Gavin Shan
2023-12-13 10:08 ` Philippe Mathieu-Daudé [this message]
2023-12-13 10:54 ` Gavin Shan
2024-01-05 22:12 ` Philippe Mathieu-Daudé
2024-01-08 1:24 ` Gavin Shan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff0237a8-9e1c-46bf-ae69-99c3f33112f6@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=armbru@redhat.com \
--cc=b.galvani@gmail.com \
--cc=bin.meng@windriver.com \
--cc=dbarboza@ventanamicro.com \
--cc=eduardo@habkost.net \
--cc=gshan@redhat.com \
--cc=imammedo@redhat.com \
--cc=kfting@nuvoton.com \
--cc=liwei1518@gmail.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=nieklinnenbank@gmail.com \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=quic_llindhol@quicinc.com \
--cc=rad@semihalf.com \
--cc=shan.gavin@gmail.com \
--cc=strahinja.p.jankovic@gmail.com \
--cc=vijai@behindbytes.com \
--cc=wangyanan55@huawei.com \
--cc=wuhaotsh@google.com \
--cc=zhiwei_liu@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).