[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190819144627.GA27061@infradead.org>
Date: Mon, 19 Aug 2019 07:46:27 -0700
From: "hch@...radead.org" <hch@...radead.org>
To: Atish Patra <Atish.Patra@....com>
Cc: "hch@...radead.org" <hch@...radead.org>,
"aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
Anup Patel <Anup.Patel@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"alexios.zavras@...el.com" <alexios.zavras@...el.com>,
"palmer@...ive.com" <palmer@...ive.com>,
"paul.walmsley@...ive.com" <paul.walmsley@...ive.com>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"allison@...utok.net" <allison@...utok.net>
Subject: Re: [PATCH] RISC-V: Issue a local tlb flush if possible.
On Thu, Aug 15, 2019 at 08:37:04PM +0000, Atish Patra wrote:
> We get ton of them. Here is the stack dump.
Looks like we might not need to flush anything at all here as the
mm_struct was never scheduled to run on any cpu?
Powered by blists - more mailing lists