[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <956163a3-9a9f-ac12-b429-eb592bce815b@wdc.com>
Date: Mon, 29 Apr 2019 12:52:18 -0700
From: Atish Patra <atish.patra@....com>
To: Borislav Petkov <bp@...en8.de>
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 4/14/19 7:29 AM, Borislav Petkov wrote:
> 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.
>
Not sure I am following you.
tlb_flushall_shift knob was removed by
commit e9f4e0a9fe27 ("x86/mm: Rip out complicated, out-of-date, buggy
TLB flushing")
Regards,
Atish
Powered by blists - more mailing lists