From: Atish Patra <Atish.Patra@wdc.com>
To: "paul.walmsley@sifive.com" <paul.walmsley@sifive.com>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
Anup Patel <Anup.Patel@wdc.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"palmer@sifive.com" <palmer@sifive.com>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v4 0/3] Optimize tlbflush path
Date: Thu, 31 Oct 2019 15:13:16 +0000 [thread overview]
Message-ID: <ad18523fdf51b426808a6ff115ca3decc8e80aeb.camel@wdc.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1910242001550.28076@viisi.sifive.com>
On Thu, 2019-10-24 at 20:09 -0700, Paul Walmsley wrote:
> On Fri, 30 Aug 2019, Paul Walmsley wrote:
>
> > On Thu, 22 Aug 2019, Atish Patra wrote:
> >
> > > This series adds few optimizations to reduce the trap cost in the
> > > tlb
> > > flush path. We should only make SBI calls to remote tlb flush
> > > only if
> > > absolutely required.
> >
> > The patches look great. My understanding is that these
> > optimization
> > patches may actually be a partial workaround for the TLB flushing
> > bug that
> > we've been looking at for the last month or so, which can corrupt
> > memory
> > or crash the system.
>
> I don't think we're any closer to root-causing this
> issue. Meanwhile,
> OpenSBI has merged patches to work around it. So since many of us
> have
> looked at Atish's TLB optimization patches, and we all think they
> are
> useful optimizations, let's plan to merge it for v5.5-rc1.
>
>
Thanks. These patches still applies cleanly on 5.4-rc5.
Let me know if you need something from myside.
> - Paul
--
Regards,
Atish
prev parent reply other threads:[~2019-10-31 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 7:51 [PATCH v4 0/3] Optimize tlbflush path Atish Patra
2019-08-22 7:51 ` [PATCH v4 1/3] RISC-V: Do not invoke SBI call if cpumask is empty Atish Patra
2019-08-22 8:10 ` Christoph Hellwig
2019-08-22 7:51 ` [PATCH v4 2/3] RISC-V: Issue a local tlbflush if possible Atish Patra
2019-08-22 8:10 ` Christoph Hellwig
2019-08-22 7:51 ` [PATCH v4 3/3] RISC-V: Issue a tlb page flush " Atish Patra
2019-08-22 8:11 ` Christoph Hellwig
2019-08-22 18:31 ` Atish Patra
2019-08-31 2:50 ` [PATCH v4 0/3] Optimize tlbflush path Paul Walmsley
2019-09-28 4:23 ` Atish Patra
2019-10-25 3:09 ` Paul Walmsley
2019-10-31 15:13 ` Atish Patra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad18523fdf51b426808a6ff115ca3decc8e80aeb.camel@wdc.com \
--to=atish.patra@wdc.com \
--cc=Anup.Patel@wdc.com \
--cc=aou@eecs.berkeley.edu \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).