[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170605083038.753a27e5@xeon-e3>
Date: Mon, 5 Jun 2017 08:30:38 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Jork Loeser <Jork.Loeser@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Andy Lutomirski <luto@...nel.org>,
"H. Peter Anvin" <hpa@...or.com>, devel@...uxdriverproject.org,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v4 02/10] x86/hyper-v: stash the max number of
virtual/logical processor
On Mon, 5 Jun 2017 11:24:27 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Sat, 27 May 2017 20:43:58 +0300
> Andy Shevchenko <andy.shevchenko@...il.com> wrote:
>
> > On Wed, May 24, 2017 at 3:03 PM, Vitaly Kuznetsov <vkuznets@...hat.com> wrote:
> > > Max virtual processor will be needed for 'extended' hypercalls supporting
> > > more than 64 vCPUs. While on it, unify on 'Hyper-V' in mshyperv.c as we
> > > currently have a mix, report acquired misc features as well.
> > >
> > > Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
> > > Acked-by: K. Y. Srinivasan <kys@...rosoft.com>
> > > Tested-by: Simon Xiao <sixiao@...rosoft.com>
> > > Tested-by: Srikanth Myakam <v-srm@...rosoft.com>
> >
> > > + u32 max_vp_index;
> > > + u32 max_lp_index;
> >
> > > + pr_info("Hyper-V: max %d virtual processors, %d logical processors\n",
> > > + ms_hyperv.max_vp_index, ms_hyperv.max_lp_index);
> >
> > And surprisingly no-one from the above list did not get a warning?!
Gcc 6.3 does not warn when %d is used on unsigned values.
> Begs to question how many other warnings are they ignoring?
None.
Powered by blists - more mailing lists