From: Eric Blake <eblake@redhat.com>
To: He Chen <he.chen@linux.intel.com>, Andrew Jones <drjones@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
qemu-arm@nongnu.org, Shannon Zhao <zhaoshenglong@huawei.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3] Allow setting NUMA distance for different NUMA nodes
Date: Thu, 23 Mar 2017 08:52:40 -0500 [thread overview]
Message-ID: <4c620bdf-5979-38f5-8dc2-74641c627151@redhat.com> (raw)
In-Reply-To: <20170323072335.GC10166@he>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On 03/23/2017 02:23 AM, He Chen wrote:
>>> -numa dist,src=1,dst=0,val=21 \
>>
>> And maybe should also point out how to set an unreachable node with 255.
>>
> Thanks for your careful review. Regarding setting unreachable node,
> which way is good? Set exact 255 as distance or distance that is larger
> than 255 is regarded as unreachable?
Given that you spec'd val as 'uint8', you can't pass a value for
distance that is larger than 255.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2017-03-23 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 9:32 [Qemu-devel] [PATCH v3] Allow setting NUMA distance for different NUMA nodes He Chen
2017-03-22 10:34 ` Andrew Jones
2017-03-23 7:23 ` He Chen
2017-03-23 7:44 ` Andrew Jones
2017-03-23 13:52 ` Eric Blake [this message]
2017-03-23 9:29 ` Igor Mammedov
2017-03-29 8:50 ` He Chen
2017-03-29 11:44 ` Igor Mammedov
2017-03-29 12:30 ` Andrew Jones
2017-03-30 15:00 ` Eduardo Habkost
2017-03-30 15:26 ` Andrew Jones
2017-03-30 20:56 ` 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=4c620bdf-5979-38f5-8dc2-74641c627151@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=he.chen@linux.intel.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=zhaoshenglong@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).