From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
nd@arm.com, xen-devel@lists.xenproject.org
Subject: Re: xen/arm and swiotlb-xen: possible data corruption
Date: Thu, 2 Mar 2017 19:32:41 +0000 [thread overview]
Message-ID: <b4655bfd-080f-5a56-d307-7a06bcd93854@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1703021106100.2888@sstabellini-ThinkPad-X260>
Hi Stefano,
On 02/03/17 19:12, Stefano Stabellini wrote:
> On Thu, 2 Mar 2017, Julien Grall wrote:
>> On 02/03/17 08:53, Edgar E. Iglesias wrote:
>>> On Thu, Mar 02, 2017 at 09:38:37AM +0100, Edgar E. Iglesias wrote:
>>>> On Wed, Mar 01, 2017 at 05:05:21PM -0800, Stefano Stabellini wrote:
> Julien, from looking at the two diffs, this is simpler and nicer, but if
> you look at xen/include/asm-arm/page.h, my patch made
> clean_dcache_va_range consistent with invalidate_dcache_va_range. For
> consistency, I would prefer to deal with the two functions the same way.
> Although it is not a spec requirement, I also think that it is a good
> idea to issue cache flushes from cacheline aligned addresses, like
> invalidate_dcache_va_range does and Linux does, to make more obvious
> what is going on.
invalid_dcache_va_range is split because the cache instruction differs
for the start and end if unaligned. For them you want to use clean &
invalidate rather than invalidate.
If you look at the implementation of other cache helpers in Linux (see
dcache_by_line_op in arch/arm64/include/asm/assembler.h), they will only
align start & end.
Also, the invalid_dcache_va_range is using modulo which I would rather
avoid. The modulo in this case will not be optimized by the compiler
because cacheline_bytes is not a constant.
So I still prefer to keep this function really simple.
BTW, you would also need to fix clean_and_invalidate_dcache_va_range.
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-02 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 1:05 xen/arm and swiotlb-xen: possible data corruption Stefano Stabellini
2017-03-02 8:38 ` Edgar E. Iglesias
2017-03-02 8:53 ` Edgar E. Iglesias
2017-03-02 17:56 ` Julien Grall
2017-03-02 19:12 ` Stefano Stabellini
2017-03-02 19:32 ` Julien Grall [this message]
2017-03-02 22:39 ` Stefano Stabellini
2017-03-02 22:55 ` Edgar E. Iglesias
2017-03-02 23:07 ` Stefano Stabellini
2017-03-02 23:24 ` Julien Grall
2017-03-02 23:19 ` Julien Grall
2017-03-03 0:53 ` Stefano Stabellini
2017-03-03 16:20 ` Julien Grall
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=b4655bfd-080f-5a56-d307-7a06bcd93854@arm.com \
--to=julien.grall@arm.com \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.com \
--cc=nd@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).