From: Alan Kao <alankao@andestech.com>
To: <paul.walmsley@sifive.com>, <palmer@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Does sfence.vma implicitly cover what fence.i does?
Date: Wed, 9 Oct 2019 16:53:14 +0800 [thread overview]
Message-ID: <20191009085313.GA14021@andestech.com> (raw)
Hi Paul, Palmer,
In arch/riscv/include/asm/tlbflush.h, the comment says
> Flush entire local TLB. 'sfence.vma' implicitly fences with the instruction
> cache as well, so a 'fence.i' is not necessary.
and in the privileged spec, it is stated that
> Executing an SFENCE.VMA instruction guarantees that any previous stores
> already visible to the current RISC-V hart are ordered before all subsequent
> implicit references from that hart to the memory-management data structures.
So my question is straightforward. Is I-cache a kind of memory-management data
structure? am I missing something here?
Thanks for any clarification.
Alan
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2019-10-09 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 8:53 Alan Kao [this message]
2019-10-16 18:55 ` Does sfence.vma implicitly cover what fence.i does? Paul Walmsley
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=20191009085313.GA14021@andestech.com \
--to=alankao@andestech.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.