[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190414142709.GA569@zn.tnic>
Date: Sun, 14 Apr 2019 16:27:09 +0200
From: Borislav Petkov <bp@...en8.de>
To: Atish Patra <atish.patra@....com>
Cc: Christoph Hellwig <hch@...radead.org>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@...nel.org>,
Albert Ou <aou@...s.berkeley.edu>,
Anup Patel <anup@...infault.org>,
Palmer Dabbelt <palmer@...ive.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>, Gary Guo <gary@...yguo.net>,
"H. Peter Anvin" <hpa@...or.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Luc Van Oostenryck <luc.vanoostenryck@...il.com>
Subject: Re: [1/3] x86: Update DEBUG_TLBFLUSH options description.
On Fri, Apr 12, 2019 at 01:14:54PM -0700, Atish Patra wrote:
> On 4/10/19 11:56 PM, Christoph Hellwig wrote:
> > Given that this option enables generic code (which you reuse for RISC-V
> > later in this series) please also move the config option to
> > mm/Kconfig, proabbly keyed off another ARCH_HAVE_DEBUG_TLBFLUSH
> > symbol that the architecture can select.
> >
>
> Sure.
And when you do that, instead of deleting the help text, make it
generic. Otherwise, there's no explanation anymore, how that option is
supposed to be used through tlb_flushall_shift.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
Powered by blists - more mailing lists