All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Julien Grall <julien.grall@arm.com>,
	Vijay Kilari <vijay.kilari@gmail.com>
Cc: Andre Przywara <andre.przywara@arm.com>,
	"prasun.kapoor" <prasun.kapoor@cavium.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: arm64: Approach for DT based NUMA and issues
Date: Fri, 16 Dec 2016 11:18:28 +0100	[thread overview]
Message-ID: <1481883508.3445.441.camel@citrix.com> (raw)
In-Reply-To: <d8178818-bb57-735c-1bec-4b4722071199@arm.com>


[-- Attachment #1.1: Type: text/plain, Size: 1835 bytes --]

On Fri, 2016-12-16 at 09:40 +0000, Julien Grall wrote:
> Hi Vijay,
> On 16/12/2016 07:39, Vijay Kilari wrote:
> > If we drop numa-node-id from memory node generated to dom0, then
> > dom0 will
> > assume all the memory is from node0. So eventually node1 device
> > intialization fails.
> 
> I suggested to drop the property numa-node-id from every node (not
> only 
> memory one). So DOM0 will think it is running a non-NUMA platform.
> 
>  From my knowledge this is working on x86, and I don't understand
> why 
> this would be an issue on ARM. If you think the device may not work, 
> please explain why.
> 
Yes, I confirm that what you said works and any x86 NUMA system I've
seen.

AFAIUI, since Vijay is talking about "devices", the x86 equivalent of
what would be an "IONUMA system", i.e. a platform where I/O devices are
physically attached to more than just one I/O hub, which in turn are
attached to different nodes.
I don't have first hand experience with these systems on the x86 world,
but I'm quite sure they also function with the configuration Julien is
suggesting to use.

Boris did some work to _improve_ the situation (namely, to make it
possible for *Xen* to report to the toolstack, to which NUMA node a
specific device is attached to). But:
 - things were working already before this
 - that does involve Xen and toolstack, while Dom0 remains totally 
   NUMA _unaware_.

And I indeed think that doing what Julien says (i.e., keep dom0 NUMA-
ignorant) is, if possible, best as a first step.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2016-12-16 10:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  6:59 arm64: Approach for DT based NUMA and issues Vijay Kilari
2016-11-27  1:01 ` Dario Faggioli
2016-11-27 12:23   ` Julien Grall
2016-11-27 20:51     ` Dario Faggioli
2016-11-28 11:02       ` Vijay Kilari
2016-11-28 12:30         ` Dario Faggioli
2016-11-28 17:49           ` Julien Grall
2016-11-28 13:50 ` Andre Przywara
2016-11-28 15:05   ` Vijay Kilari
2016-11-28 17:48     ` Julien Grall
2016-11-28 18:59 ` Julien Grall
2016-12-16  7:39   ` Vijay Kilari
2016-12-16  9:40     ` Julien Grall
2016-12-16 10:18       ` Dario Faggioli [this message]
2017-03-02 12:39         ` Vijay Kilari
2017-03-02 12:52           ` Julien Grall
2017-03-02 14:10             ` Vijay Kilari

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=1481883508.3445.441.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=andre.przywara@arm.com \
    --cc=julien.grall@arm.com \
    --cc=prasun.kapoor@cavium.com \
    --cc=sstabellini@kernel.org \
    --cc=vijay.kilari@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    /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.