From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
Hu Tao <hutao@cn.fujitsu.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Anton Blanchard <anton@samba.org>,
David Rientjes <rientjes@google.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v4] numa: enable sparse node numbering on ppc
Date: Tue, 1 Jul 2014 08:37:14 -0700 [thread overview]
Message-ID: <20140701153713.GC15697@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140701152448.GR3222@otherpad.lan.raisama.net>
On 01.07.2014 [12:24:48 -0300], Eduardo Habkost wrote:
> On Mon, Jun 30, 2014 at 02:34:56PM -0700, Nishanth Aravamudan wrote:
> [...]
> > }
> > + assert(numa_info[i].present);
> > numa_info[i].node_mem = ram_size - usedmem;
> > }
>
> Tab here.
>
> >
> [...]
> > + for (i = 0, j = 0; i < max_cpus; i++) {
> > + do {
> > + j = (j + 1) % (max_numa_nodeid);
> > + } while (!numa_info[j].present);
>
> Ditto.
>
> (Those can be detected using checkpatch.pl).
Grr, sorry, I had been using checkpatch, but rushed this one. My
apologies!
> Other than that, the PC changes look good to me (I haven't reviewed the
> spapr.c changes). But I have an additional request: can you submit the
> nb_numa_nodes/num_numa_nodes rename as a separate patch, to make the
> other changes more visible and easier to review?
Yep, that makes sense.
Thanks,
Nish
prev parent reply other threads:[~2014-07-01 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 21:34 [Qemu-devel] [RFC PATCH v4] numa: enable sparse node numbering on ppc Nishanth Aravamudan
2014-07-01 15:24 ` Eduardo Habkost
2014-07-01 15:37 ` Nishanth Aravamudan [this message]
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=20140701153713.GC15697@linux.vnet.ibm.com \
--to=nacc@linux.vnet.ibm.com \
--cc=aik@ozlabs.ru \
--cc=anton@samba.org \
--cc=ehabkost@redhat.com \
--cc=hutao@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rientjes@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).