From: "wangyanan (Y)" <wangyanan55@huawei.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Andrew Jones" <drjones@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
wanghaibin.wang@huawei.com
Subject: Re: [PATCH v3 0/2] hw/core/machine: Add an unit test for smp_parse
Date: Fri, 29 Oct 2021 14:28:57 +0800 [thread overview]
Message-ID: <aff7ec09-ec31-bf4f-b36c-67329f1fa02d@huawei.com> (raw)
In-Reply-To: <91def190-d563-e463-7915-525d67631194@redhat.com>
On 2021/10/28 22:44, Philippe Mathieu-Daudé wrote:
> On 10/26/21 05:46, Yanan Wang wrote:
>> Hi,
>>
>> This is v3 which introduces an unit test for generic smp_parse.
>>
>> We have had enough discussions about what kind of SMP configurations
>> by the user should be considered valid and what should be invalid.
>> Since we have finished optimizing the SMP parsing code, then this
>> test normatively listed all the possible valid/invalid configurations
>> that the user can provide. This can be a testing tool when we
>> introduce new topology members and need to touch the parsing code.
>>
>> For your reference, some related discussion is here:
>> https://lore.kernel.org/qemu-devel/YOxf+sxzUSJdbY+j@redhat.com/
>>
>> Changelog:
>> v2->v3:
>> - add Andrew's R-b for PATCH #1
>> - drop an unused macro definition in PATCH #2
>> - v2: https://lore.kernel.org/qemu-devel/20211013074119.23028-1-wangyanan55@huawei.com/
>>
>> v1->v2:
>> - split smp_parse out into a separate .c file instead of a header (patch #1)
>> - dropped an unnecessary function and add Andrew's R-b (patch #2)
>> - v1: https://lore.kernel.org/qemu-devel/20211010103954.20644-1-wangyanan55@huawei.com/
>>
>> Yanan Wang (2):
>> hw/core/machine: Split out the smp parsing code
>> tests/unit: Add an unit test for smp parsing
> Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
Thank you for the testing/review and the help of v4 respin.
Thanks,
Yanan
.
prev parent reply other threads:[~2021-10-29 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 3:46 [PATCH v3 0/2] hw/core/machine: Add an unit test for smp_parse Yanan Wang
2021-10-26 3:46 ` [PATCH v3 1/2] hw/core/machine: Split out the smp parsing code Yanan Wang
2021-10-26 3:46 ` [PATCH v3 2/2] tests/unit: Add an unit test for smp parsing Yanan Wang
2021-10-28 11:50 ` [PATCH v3 0/2] hw/core/machine: Add an unit test for smp_parse wangyanan (Y)
2021-10-28 14:44 ` Philippe Mathieu-Daudé
2021-10-29 6:28 ` wangyanan (Y) [this message]
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=aff7ec09-ec31-bf4f-b36c-67329f1fa02d@huawei.com \
--to=wangyanan55@huawei.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.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).