From: Andre Przywara <andre.przywara@amd.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 1/4] hvm: NUMA guest: extend memops hypercall
Date: Fri, 4 Jul 2008 17:28:55 +0200 [thread overview]
Message-ID: <486E41B7.8080707@amd.com> (raw)
In-Reply-To: <C493F829.238DF%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 4/7/08 13:48, "Andre Przywara" <andre.przywara@amd.com> wrote:
>
>>> Looking some more, I still don't see that this patch can work. Don't the
>>> subfunctions in memory.c go and OR in MEMF_node() values on top of what the
>>> caller may have specified??
>> Maybe I don't get your question right, but the only part where the
>> caller specified node number is used is the line I handled in the last
>> patch. Later they only use the member memflags of struct memop_args, not
>> struct xen_memory_reservation. If the node number is not specified (or
>> blocked), it will be later determined by looking at the current
>> scheduled pCPU (and thus node), but this is the current behavior anyway.
>
> Take common/memory.c:populate_physmap() as a specific example. It
> unconditionally specifies MEMF_node() in its invocation of
> alloc_domheap_pages(), regardless of whether its caller has already
> specified a node in the memop_args structure that is passed into it.
Have you applied the patches correctly? From 02_numa_guest.patch:
@@ -115,7 +113,7 @@
goto out;
page = alloc_domheap_pages(
- d, a->extent_order, a->memflags | MEMF_node(node));
+ d, a->extent_order, a->memflags);
if ( unlikely(page == NULL) )
{
gdprintk(XENLOG_INFO, "Could not allocate order=%d extent:"
The other use of MEMF_node is in exchange_memory, which is not given any
NUMA node info from the caller, so this is correct.
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 277-84917
----to satisfy European Law for business letters:
AMD Saxony Limited Liability Company & Co. KG,
Wilschdorfer Landstr. 101, 01109 Dresden, Germany
Register Court Dresden: HRA 4896, General Partner authorized
to represent: AMD Saxony LLC (Wilmington, Delaware, US)
General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-07-04 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 7:57 [PATCH 1/4] hvm: NUMA guest: extend memops hypercall Andre Przywara
2008-07-04 9:52 ` Keir Fraser
2008-07-04 11:14 ` Andre Przywara
2008-07-04 11:59 ` Keir Fraser
2008-07-04 12:48 ` Andre Przywara
2008-07-04 14:54 ` Keir Fraser
2008-07-04 15:28 ` Andre Przywara [this message]
2008-07-04 15:34 ` Keir Fraser
2008-07-04 23:12 ` Andre Przywara
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=486E41B7.8080707@amd.com \
--to=andre.przywara@amd.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.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.