From: "Jan Beulich" <JBeulich@suse.com>
To: Elena Ufimtseva <ufimtseva@gmail.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com, lccycc123@gmail.com,
george.dunlap@eu.citrix.com, msw@linux.com,
dario.faggioli@citrix.com, stefano.stabellini@eu.citrix.com,
ian.jackson@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH RESEND v7 3/9] vnuma hook to debug-keys u
Date: Fri, 22 Aug 2014 10:13:51 +0100 [thread overview]
Message-ID: <53F725EF020000780002C92D@mail.emea.novell.com> (raw)
In-Reply-To: <20140821161907.GC18265@laptop.dumpdata.com>
>>> On 21.08.14 at 18:19, <konrad.wilk@oracle.com> wrote:
> On Thu, Aug 21, 2014 at 01:10:23AM -0400, Elena Ufimtseva wrote:
>> @@ -389,6 +389,34 @@ static void dump_numa(unsigned char key)
>>
>> for_each_online_node(i)
>> printk(" Node %u: %u\n", i, page_num_node[i]);
>> +
>> + if ( d->vnuma ) {
>> + printk(" Domain has %u vnodes, %u vcpus\n", d->vnuma->nr_vnodes, d->max_vcpus);
Long line.
>> + for ( i = 0; i < d->vnuma->nr_vnodes; i++ ) {
>
> That '{'
> needs to be on another line.
>
>> +
>> + err = snprintf(keyhandler_scratch, 12, "%u", d->vnuma->vnode_to_pnode[i]);
>> + if ( err < 0 || d->vnuma->vnode_to_pnode[i] == NUMA_NO_NODE)
>
> You need a space at the end, so 'NUMA_NO_NODE )'
>
>> + snprintf(keyhandler_scratch, 3, "???");
>> + printk(" vnode %3u - pnode %s,", i, keyhandler_scratch);
>> +
>> + printk(" %"PRIu64" MB, ",
>> + (d->vnuma->vmemrange[i].end - d->vnuma->vmemrange[i].start) >> 20);
>> +
>> + printk("vcpu nrs: ");
>> + for ( j = 0, n = 0; j < d->max_vcpus; j++ ) {
>
> { on its own line.
>> + if ( d->vnuma->vcpu_to_vnode[j] == i ) {
>
> Ditto
And, Elena, I have been pointing out these coding style issues
on previous iterations.
Jan
prev parent reply other threads:[~2014-08-22 9:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 5:10 [PATCH RESEND v7 3/9] vnuma hook to debug-keys u Elena Ufimtseva
2014-08-21 5:10 ` [PATCH RESEND v7 4/9] libxc: Introduce xc_domain_setvnuma to set vNUMA Elena Ufimtseva
2014-08-22 1:40 ` Konrad Rzeszutek Wilk
2014-08-21 5:10 ` [PATCH RESEND v7 5/9] libxl: vnuma types declararion Elena Ufimtseva
2014-08-25 14:15 ` Wei Liu
2014-08-21 5:10 ` [PATCH RESEND v7 6/9] libxl: build numa nodes memory blocks Elena Ufimtseva
2014-08-22 2:18 ` Konrad Rzeszutek Wilk
2014-08-25 14:15 ` Wei Liu
2014-08-21 5:10 ` [PATCH RESEND v7 7/9] libxc: allocate domain memory for vnuma enabled Elena Ufimtseva
2014-08-22 2:10 ` Konrad Rzeszutek Wilk
2014-08-25 0:40 ` Elena Ufimtseva
2014-08-21 5:10 ` [PATCH RESEND v7 8/9] libxl: vnuma nodes placement bits Elena Ufimtseva
2014-08-21 5:10 ` [PATCH RESEND v7] libxl: vnuma topology configuration parser and doc Elena Ufimtseva
2014-08-22 2:06 ` Konrad Rzeszutek Wilk
2014-08-22 17:40 ` Elena Ufimtseva
2014-08-21 16:19 ` [PATCH RESEND v7 3/9] vnuma hook to debug-keys u Konrad Rzeszutek Wilk
2014-08-22 9:13 ` Jan Beulich [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=53F725EF020000780002C92D@mail.emea.novell.com \
--to=jbeulich@suse.com \
--cc=Ian.Campbell@citrix.com \
--cc=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=lccycc123@gmail.com \
--cc=msw@linux.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=ufimtseva@gmail.com \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).