[PATCH v5 08/10] x86/hyper-v: use hypercall for remote TLB flush

Jork Loeser Jork.Loeser at microsoft.com
Tue May 30 19:17:46 UTC 2017


> -----Original Message-----
> From: Andy Shevchenko [mailto:andy.shevchenko at gmail.com]
> Sent: Tuesday, May 30, 2017 09:53
> To: Vitaly Kuznetsov <vkuznets at redhat.com>
> Cc: x86 at kernel.org; devel at linuxdriverproject.org; linux-
> kernel at vger.kernel.org; KY Srinivasan <kys at microsoft.com>; Haiyang Zhang
> <haiyangz at microsoft.com>; Stephen Hemminger <sthemmin at microsoft.com>;
> Thomas Gleixner <tglx at linutronix.de>; Ingo Molnar <mingo at redhat.com>; H.
> Peter Anvin <hpa at zytor.com>; Steven Rostedt <rostedt at goodmis.org>; Jork
> Loeser <Jork.Loeser at microsoft.com>; Simon Xiao <sixiao at microsoft.com>;
> Andy Lutomirski <luto at kernel.org>
> Subject: Re: [PATCH v5 08/10] x86/hyper-v: use hypercall for remote TLB flush
> 
> On Tue, May 30, 2017 at 2:34 PM, Vitaly Kuznetsov <vkuznets at redhat.com>
> wrote:
> > +#define HV_FLUSH_ALL_PROCESSORS                        0x00000001
> > +#define HV_FLUSH_ALL_VIRTUAL_ADDRESS_SPACES    0x00000002
> > +#define HV_FLUSH_NON_GLOBAL_MAPPINGS_ONLY      0x00000004
> > +#define HV_FLUSH_USE_EXTENDED_RANGE_FORMAT     0x00000008
> 
> BIT() ?

Certainly a matter of taste. Given that the Hyper-V spec lists these as hex numbers, I find the explicit numbers appropriate.

Regards,
Jork



More information about the devel mailing list