From: Julien Grall <julien.grall@linaro.org>
To: Christoffer Dall <christoffer.dall@linaro.org>
Cc: Andre Przywara <andre.przywara@calxeda.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [ARM] Bash often segfaults in Dom0 with the latest Xen
Date: Tue, 11 Jun 2013 12:48:38 +0100 [thread overview]
Message-ID: <51B70E96.1030306@linaro.org> (raw)
In-Reply-To: <CAMJs5B_4A2cgybq_xERKgLF+yibtUqJFz2G8rDAZhko61hNq6g@mail.gmail.com>
On 06/05/2013 02:38 AM, Christoffer Dall wrote:
> - All other cache accesses should be coherent across cores and are
> physically indexed/physically tagged so I don't see how this could be
> your issue.
I was looking on KVM code and I noticed that it traps all data cache
instruction. Is there any reason to trap it?
I wonder if it could be the issue on Xen because we don't trap cache
instruction and the manual is not clear on that.
Thanks,
--
Julien
next prev parent reply other threads:[~2013-06-11 11:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 22:45 [ARM] Bash often segfaults in Dom0 with the latest Xen Julien Grall
2013-06-05 1:38 ` Christoffer Dall
2013-06-05 9:52 ` Ian Campbell
2013-06-05 11:48 ` Julien Grall
2013-06-05 14:30 ` Christoffer Dall
2013-06-05 15:18 ` Ian Campbell
2013-06-05 16:12 ` Julien Grall
2013-06-05 16:46 ` Stefano Stabellini
2013-06-05 17:36 ` Christoffer Dall
2013-06-05 17:53 ` Julien Grall
2013-06-05 17:57 ` Christoffer Dall
2013-06-05 18:01 ` Stefano Stabellini
2013-06-05 18:17 ` Christoffer Dall
2013-06-05 18:36 ` Julien Grall
2013-06-11 11:48 ` Julien Grall [this message]
2013-06-11 14:25 ` Christoffer Dall
2013-06-05 9:38 ` Ian Campbell
2013-06-05 10:39 ` 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=51B70E96.1030306@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=andre.przywara@calxeda.com \
--cc=christoffer.dall@linaro.org \
--cc=xen-devel@lists.xen.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).