From: "Michal Prívozník" <mprivozn@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: tao3.xu@intel.com, qemu-devel@nongnu.org, ehabkost@redhat.com
Subject: Re: [PATCH 2/2] numa: Parse initiator= attribute before cpus= attribute
Date: Fri, 9 Jul 2021 11:44:33 +0200 [thread overview]
Message-ID: <165737d8-c23f-033e-adf3-86046be13965@redhat.com> (raw)
In-Reply-To: <20210709112659.5a03a52d@redhat.com>
On 7/9/21 11:26 AM, Igor Mammedov wrote:
> On Wed, 7 Jul 2021 15:40:30 +0200
> Michal Privoznik <mprivozn@redhat.com> wrote:
>
>> When parsing cpus= attribute of -numa object couple of checks
>> is performed, such as correct initiator setting (see the if()
>> statement at the end of for() loop in
>> machine_set_cpu_numa_node()).
>>
>> However, with the current code cpus= attribute is parsed before
>> initiator= attribute and thus the check may fail even though it
>> is not obvious why. But since parsing the initiator= attribute
>> does not depend on the cpus= attribute we can swap the order of
>> the two.
>
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
>
> FYI:
> I'm planning to deprecate '-numa node,cpus=' in favor of '-numa cpu'.
Yes, I'm aware of that and I remember I posted some patches for libvirt
that you reviewed. I need to return to them rather sooner than later.
Meanwhile, this patch helps.
Thanks,
Michal
next prev parent reply other threads:[~2021-07-09 9:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:40 [PATCH 0/2] numa: Parse initiator= attribute before cpus= attribute Michal Privoznik
2021-07-07 13:40 ` [PATCH 1/2] numa: Report expected initiator Michal Privoznik
2021-07-09 9:27 ` Igor Mammedov
2021-07-09 19:33 ` Pankaj Gupta
2021-07-07 13:40 ` [PATCH 2/2] numa: Parse initiator= attribute before cpus= attribute Michal Privoznik
2021-07-09 9:26 ` Igor Mammedov
2021-07-09 9:44 ` Michal Prívozník [this message]
2021-07-08 0:06 ` [PATCH 0/2] " Connor Kuehl
2021-07-09 20:49 ` Eduardo Habkost
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=165737d8-c23f-033e-adf3-86046be13965@redhat.com \
--to=mprivozn@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tao3.xu@intel.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).