From: Dario Faggioli <dario.faggioli@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: <ian.campbell@citrix.com>, <wency@cn.fujitsu.com>,
<stefano.stabellini@eu.citrix.com>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>, <tangchen@cn.fujitsu.com>,
<mingo@redhat.com>, <tglx@linutronix.de>,
Elena Ufimtseva <ufimtseva@gmail.com>, <hpa@zytor.com>,
<xen-devel@lists.xenproject.org>, <akpm@linux-foundation.org>,
<boris.ostrovsky@oracle.com>
Subject: Re: [Xen-devel] [PATCH 1/2] xen: vnuma support for PV guests running as domU.
Date: Thu, 14 Nov 2013 12:48:50 +0100 [thread overview]
Message-ID: <1384429730.29902.129.camel@Abyss> (raw)
In-Reply-To: <5284B238.6020601@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 2158 bytes --]
On gio, 2013-11-14 at 11:21 +0000, David Vrabel wrote:
> On 14/11/13 07:26, Dario Faggioli wrote:
> > IIRC, it's more something that was already happening (the breakage, I
> > mean), than a "safety net" for the unforeseeable future. Might be worth
> > giving some context about it, perhaps referencing the email thread or
> > the git commit hash in the comment.
>
> Yes, a comment like:
>
> /*
> * Set a dummy node and return success. This prevents calling any
> * hardware-specific initializers which do not work in a PV guest.
> */
>
> is better. No need to refer to any specific threads. It's pretty clear
> that any hardware-specific init isn't appropriate for a PV guest.
>
Ok.
> >> + if (rc != 0) {
> >> + for (i = 0; i < MAX_LOCAL_APIC; i++)
> >> + set_apicid_to_node(i, NUMA_NO_NODE);
> >> + nodes_clear(numa_nodes_parsed);
> >> + nodes_clear(node_possible_map);
> >> + nodes_clear(node_online_map);
> >> + node_set(0, numa_nodes_parsed);
> >> + numa_add_memblk(0, 0, PFN_PHYS(max_pfn));
> >> + }
> >> + return 0;
> >>
> > Ok, so, we always return 'success', as we were saying during last round.
> > However, we do not call dummy_numa_init() directly, and instead we do
> > all these stuff, with the last two statements being exactly what
> > dummy_numa_init() does. Reason is linking, i.e., the fact that
> > dummy_numa_init() is not exported and you can't reach it from here,
> > right?
>
> I think this bit is fine as-is.
>
Ok, cool. :-) Shouldn't we then kill or reformulate the comments where
dummy_numa_init is explicitly referenced then?
E.g., this one: /* will pass to dummy_numa_init */
It might be me, but I find it rather confusing. After seeing that, I'd
expect to see that, at some point, either the function returns failure
(which of course we don't want), or a direct call dummy_numa_init().
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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-14 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 3:36 [PATCH 0/2] xen: vnuma introduction for pv guest Elena Ufimtseva
2013-11-14 3:36 ` [PATCH 1/2] xen: vnuma support for PV guests running as domU Elena Ufimtseva
2013-11-14 7:26 ` [Xen-devel] " Dario Faggioli
2013-11-14 11:21 ` David Vrabel
2013-11-14 11:48 ` Dario Faggioli [this message]
2013-11-14 14:11 ` Elena Ufimtseva
2013-11-14 11:18 ` David Vrabel
2013-11-14 14:11 ` [Xen-devel] " Stefano Stabellini
2013-11-14 3:36 ` [PATCH 2/2] xen: enable vnuma for PV guest Elena Ufimtseva
2013-11-14 6:53 ` [Xen-devel] [PATCH 0/2] xen: vnuma introduction for pv guest 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=1384429730.29902.129.camel@Abyss \
--to=dario.faggioli@citrix.com \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=ian.campbell@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tangchen@cn.fujitsu.com \
--cc=tglx@linutronix.de \
--cc=ufimtseva@gmail.com \
--cc=wency@cn.fujitsu.com \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox