All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Shivaprasad G Bhat <sbhat@linux.vnet.ibm.com>,
	Greg Kurz <groug@kaod.org>,
	David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org, libvir-list@redhat.com
Subject: Re: [Qemu-devel] [PATCH] spapr: make default PHB optionnal
Date: Tue, 18 Jul 2017 10:02:41 +0200	[thread overview]
Message-ID: <1500364961.11997.10.camel@redhat.com> (raw)
In-Reply-To: <68cfb52b-d4cc-1980-e6f5-a454baf4e2e5@linux.vnet.ibm.com>

On Wed, 2017-07-12 at 17:09 +0530, Shivaprasad G Bhat wrote:
> Setting numa_node for emulated devices is the benefit for now. On x86, I
> figured there is
> no way to set the numa_node for the root controller and the emulated
> devices sitting there
> all have numa_node set to -1. Only the devices on the pxb can have a
> sensible value specified.
> Does it mean, the emulated devices/drivers don't care about the
> numa_node they are on?
> 
> Would it be fine on PPC to disallow setting the NUMA node for the
> default PHB because that is where
> all the emulated devices sit ?

I was not aware of that limitation for x86 guests.

If that's the case, then I would say it's perfectly okay to
just disallow setting the NUMA node for the default PHB, at
least for the time being.

-- 
Andrea Bolognani / Red Hat / Virtualization

  reply	other threads:[~2017-07-18  8:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 16:48 [Qemu-devel] [PATCH] spapr: make default PHB optionnal Greg Kurz
2017-07-04  7:29 ` David Gibson
2017-07-04  8:47   ` Greg Kurz
2017-07-12 10:55     ` Andrea Bolognani
2017-07-12 11:39       ` Shivaprasad G Bhat
2017-07-18  8:02         ` Andrea Bolognani [this message]
2017-07-19  4:38         ` David Gibson
2017-07-12 12:25       ` Greg Kurz
2017-07-19  4:34     ` David Gibson
2017-07-24 18:59       ` Greg Kurz

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=1500364961.11997.10.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=libvir-list@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=sbhat@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.