From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751032AbdE3XEy (ORCPT ); Tue, 30 May 2017 19:04:54 -0400 Received: from mail-pf0-f172.google.com ([209.85.192.172]:34123 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750821AbdE3XEw (ORCPT ); Tue, 30 May 2017 19:04:52 -0400 Date: Tue, 30 May 2017 16:04:45 -0700 From: Stephen Hemminger To: Jork Loeser Cc: Andy Shevchenko , Vitaly Kuznetsov , Stephen Hemminger , Haiyang Zhang , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , Steven Rostedt , Ingo Molnar , Andy Lutomirski , "H. Peter Anvin" , "devel@linuxdriverproject.org" , Thomas Gleixner Subject: Re: [PATCH v5 08/10] x86/hyper-v: use hypercall for remote TLB flush Message-ID: <20170530160445.54b29cb8@xeon-e3> In-Reply-To: References: <20170530113424.15687-1-vkuznets@redhat.com> <20170530113424.15687-9-vkuznets@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 May 2017 19:17:46 +0000 Jork Loeser wrote: > > -----Original Message----- > > From: Andy Shevchenko [mailto:andy.shevchenko@gmail.com] > > Sent: Tuesday, May 30, 2017 09:53 > > To: Vitaly Kuznetsov > > Cc: x86@kernel.org; devel@linuxdriverproject.org; linux- > > kernel@vger.kernel.org; KY Srinivasan ; Haiyang Zhang > > ; Stephen Hemminger ; > > Thomas Gleixner ; Ingo Molnar ; H. > > Peter Anvin ; Steven Rostedt ; Jork > > Loeser ; Simon Xiao ; > > Andy Lutomirski > > 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 > > 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 Keep the hex numbers, it makes more sense not to change it since rest of arch/x86/hyperv uses hex values.