[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170609150707.322c3b9f@gandalf.local.home>
Date: Fri, 9 Jun 2017 15:07:07 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
devel@...uxdriverproject.org, "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
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>,
Jork Loeser <Jork.Loeser@...rosoft.com>,
Simon Xiao <sixiao@...rosoft.com>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH v8 10/10] tracing/hyper-v: trace
hyperv_mmu_flush_tlb_others()
On Fri, 09 Jun 2017 20:53:53 +0200
Paul Bolle <pebolle@...cali.nl> wrote:
> On Fri, 2017-06-09 at 14:32 -0400, Steven Rostedt wrote:
> > I'm sure it works, but it just adds one more way of doing the same
> > thing. I thought that was what perl was always criticized for, and why
> > people usually prefer python. Don't get me wrong, I prefer oysters over
> > snakes. But I just wanted to point out the lack of consistency here.
>
> A major benefit is that
> #if IS_ENABLED(CONFIG_HYPERV)
>
> is shorter than
> #if defined(CONFIG_HYPERV) || defined(CONFIG_HYPERV_MODULE)
>
> and less prone to typos.
>
I don't believe the module version is needed here. Otherwise I would
question the #if altogether. Which now I'm looking at it, why is it
needed?
What includes this header file that wouldn't have that set anyway? The
only place it is included is in:
arch/x86/hyperv/mmu.c
Is that compiled without CONFIG_HYPERV?
-- Steve
Powered by blists - more mailing lists