Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@infradead.org (Christoph Hellwig)
To: linux-riscv@lists.infradead.org
Subject: [RFC] Cache flush via SBI
Date: Mon, 2 Jul 2018 06:32:33 -0700	[thread overview]
Message-ID: <20180702133233.GA25558@infradead.org> (raw)
In-Reply-To: <CAAhSdy3=k52BYjiC+2S0RHk-hnPQXP0da-04aL-tb_O_XuvUEg@mail.gmail.com>

On Mon, Jul 02, 2018 at 05:42:01PM +0530, Anup Patel wrote:
> Hi All,
> 
> I have gone through various discussions around cache flush/invalidate
> operation not being part of RISC-V spec. Although, CPU designers can
> still provide these operations in an implementation specific way.
> Right?
> 
> My suggestion is to have SBI calls for cache flush/invalidate so that
> platform specific firmware can
> provide cache flush/invalidate in a more generic way. Thoughts??

No, we need to add them to the spec.  In fact Jacob just sent out
anothet proposal to isa-dev, but I haven't had the time to go back
and review it yet.

      reply	other threads:[~2018-07-02 13:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02 12:12 [RFC] Cache flush via SBI Anup Patel
2018-07-02 13:32 ` Christoph Hellwig [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=20180702133233.GA25558@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-riscv@lists.infradead.org \
    /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