From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "Keir (Xen.org)" <keir@xen.org>,
Andrew Cooper <Andrew.Cooper3@citrix.com>,
Julien Grall <julien.grall@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@citrix.com>,
"JBeulich@suse.com" <JBeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 3/5] x86: widen NUMA nodes to be allocated from
Date: Fri, 27 Feb 2015 14:00:21 +0000 [thread overview]
Message-ID: <1425045618.10194.81.camel@citrix.com> (raw)
In-Reply-To: <1425044785.14641.202.camel@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 914 bytes --]
On Fri, 2015-02-27 at 13:46 +0000, Ian Campbell wrote:
> On Fri, 2015-02-27 at 13:27 +0000, Dario Faggioli wrote:
> > After this series, vcpu_to_node() (defined in xen/include/xen/numa.h) is
> > left with only one use, in xen/arch/arm/domain.c, besides of course
> > being used to implement domain_to_node() (still in
> > xen/include/xen/numa.h).
> >
> > So, provided ARM people (and I'm Cc-ing them) can get rid of that,
>
> Happy to do so if you have advise on what to replace it with, just 0?
>
As Julien says, with the MEMF_no_owner feature Jan is introducing in the
series.
> We don't do NUMA yet on ARM so that would be fine, but eventually we'd
> want the vcpu stack to be allocated in some sort of "sensible relative
> to vcpu affinity" location...
>
Yes, and Jan's MEMF_no_owner, if it works on your arch too, as it seems
it could, will provide exactly that.
Regards,
Dario
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-02-27 14:00 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-26 13:44 [PATCH 0/5] (not just)x86/Dom0: NUMA related adjustments Jan Beulich
2015-02-26 13:52 ` [PATCH 1/5] x86: allow specifying the NUMA nodes Dom0 should run on Jan Beulich
2015-02-26 17:14 ` Dario Faggioli
2015-02-27 8:46 ` Jan Beulich
2015-02-27 10:04 ` Dario Faggioli
2015-02-27 10:50 ` Jan Beulich
2015-02-27 14:54 ` Dario Faggioli
2015-02-27 15:04 ` Jan Beulich
2015-03-03 10:51 ` Jan Beulich
2015-03-04 10:18 ` Dario Faggioli
2015-03-06 9:11 ` Jan Beulich
2015-03-06 10:46 ` Dario Faggioli
2015-03-06 11:33 ` Dario Faggioli
2015-03-06 13:26 ` Jan Beulich
2015-03-06 11:49 ` Jan Beulich
2015-03-03 9:59 ` Ian Campbell
2015-03-05 16:11 ` Andrew Cooper
2015-03-05 16:43 ` Jan Beulich
2015-03-05 17:27 ` Andrew Cooper
2015-03-06 9:19 ` [PATCH 1/5 v2] " Jan Beulich
2015-03-06 10:41 ` Dario Faggioli
2015-03-06 16:05 ` Andrew Cooper
2015-02-26 13:53 ` [PATCH 2/5] allow domain heap allocations to specify more than one NUMA node Jan Beulich
2015-02-27 11:34 ` Dario Faggioli
2015-03-02 17:12 ` Ian Campbell
2015-03-03 7:59 ` Jan Beulich
2015-03-05 16:18 ` Andrew Cooper
2015-02-26 13:54 ` [PATCH 3/5] x86: widen NUMA nodes to be allocated from Jan Beulich
2015-02-27 13:27 ` Dario Faggioli
2015-02-27 13:36 ` Jan Beulich
2015-02-27 14:11 ` Dario Faggioli
2015-02-27 13:38 ` Julien Grall
2015-02-27 13:55 ` Dario Faggioli
2015-02-27 13:58 ` Jan Beulich
2015-02-27 13:46 ` Ian Campbell
2015-02-27 14:00 ` Dario Faggioli [this message]
2015-02-27 14:03 ` Jan Beulich
2015-03-05 16:39 ` Andrew Cooper
2015-02-26 13:55 ` [PATCH 4/5] VT-d: " Jan Beulich
2015-03-05 17:08 ` Andrew Cooper
2015-03-09 3:07 ` Tian, Kevin
2015-02-26 13:56 ` [PATCH 5/5] AMD IOMMU: " Jan Beulich
2015-03-05 17:30 ` Andrew Cooper
2015-03-06 7:50 ` Jan Beulich
2015-03-06 12:15 ` Andrew Cooper
2015-03-09 15:42 ` Suravee Suthikulanit
2015-03-09 17:26 ` Andrew Cooper
2015-03-09 19:02 ` Suravee Suthikulanit
2015-03-10 7:35 ` Jan Beulich
2015-03-10 13:55 ` Boris Ostrovsky
2015-02-27 10:04 ` [PATCH 0/5] (not just)x86/Dom0: NUMA related adjustments Dario Faggioli
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=1425045618.10194.81.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Andrew.Cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=Stefano.Stabellini@citrix.com \
--cc=julien.grall@citrix.com \
--cc=keir@xen.org \
--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.