[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY4PR21MB063181014B7F3945D56A2B22F1010@CY4PR21MB0631.namprd21.prod.outlook.com>
Date: Mon, 10 Apr 2017 17:34:55 +0000
From: Jork Loeser <Jork.Loeser@...rosoft.com>
To: Vitaly Kuznetsov <vkuznets@...hat.com>,
KY Srinivasan <kys@...rosoft.com>
CC: "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Steven Rostedt <rostedt@...dmis.org>
Subject: RE: [PATCH 6/7] x86/hyper-v: use hypercall for remove TLB flush
> -----Original Message-----
> From: Vitaly Kuznetsov [mailto:vkuznets@...hat.com]
> > We may be supporting more than 64 CPUs in this hypercall. I am going
> > to inquire with the Windows folks and get back to you.
>
> Thanks! It is even specified in the specification:
> "Future versions of the hypervisor may support more than 64 virtual
> processors per partition. In that case, a new field will be added to the flags
> value that allows the caller to define the “processor bank” to which the
> processor mask applies."
>
> We, however, need to know where to put this in flags.
Would the HvFlushVirtualAddressListEx hypercall do? Is there a doc update/clarification needed?
Regards,
Jork
Powered by blists - more mailing lists