From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel <xen-devel@lists.xen.org>
Cc: Keir Fraser <keir@xen.org>,
George Dunlap <george.dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Jackson <Ian.Jackson@eu.citrix.com>,
Julien Grall <julien.grall@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH 0/4] xen/arm: fix guest builder cache cohenrency (again, again)
Date: Wed, 29 Jan 2014 13:26:34 +0000 [thread overview]
Message-ID: <52E9018A.5090908@linaro.org> (raw)
In-Reply-To: <1390997452.31814.90.camel@kazak.uk.xensource.com>
Hi Ian,
Thanks for the patch series.
On 29/01/14 12:10, Ian Campbell wrote:
> Jan/Ian/Keir -- the final patch involves tools changes and a new domctl,
> which is why you are copied (although the domctl is marked as arm
> specific you might have opinions on it).
>
> On ARM we need to take care of cache coherency for guests which we have
> just built because they start with their caches disabled.
>
> Our current strategy for dealing with this, which is to make guest
> memory default to cacheable regardless of the in guest configuration
> (the HCR.DC bit), is flawed because it doesn't handle guests which
> enable their MMU before enabling their caches, which at least FreeBSD
> does. (NB: Setting HCR.DC while the guest MMU is enabled is
> UNPREDICTABLE, hence we must disable it when the guest turns its MMU
> one).
Enabling the cache earlier wouldn't change the issue :). The main
problem is the page table attributes. Using Write-Through (with cached
enabled/disabled) can randomly crash guest.
--
Julien Grall
prev parent reply other threads:[~2014-01-29 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 12:10 [PATCH 0/4] xen/arm: fix guest builder cache cohenrency (again, again) Ian Campbell
2014-01-29 12:11 ` [PATCH 1/4] Revert "xen: arm: force guest memory accesses to cacheable when MMU is disabled" Ian Campbell
2014-01-29 13:22 ` Julien Grall
2014-01-29 14:18 ` Ian Campbell
2014-01-29 12:11 ` [PATCH 2/4] xen: arm: rename create_p2m_entries to apply_p2m_changes Ian Campbell
2014-01-29 13:18 ` Julien Grall
2014-01-29 12:11 ` [PATCH 3/4] xen: arm: rename p2m next_gfn_to_relinquish to lowest_mapped_gfn Ian Campbell
2014-01-29 13:19 ` Julien Grall
2014-01-29 12:11 ` [PATCH 4/4] xen/arm: clean and invalidate all guest caches by VMID after domain build Ian Campbell
2014-01-29 13:00 ` Jan Beulich
2014-01-29 13:28 ` Stefano Stabellini
2014-01-29 14:15 ` Ian Campbell
2014-01-29 15:01 ` Jan Beulich
2014-01-29 16:35 ` Ian Campbell
2014-01-29 16:50 ` Jan Beulich
2014-01-30 11:26 ` Ian Jackson
2014-01-30 12:24 ` Ian Campbell
2014-01-30 12:32 ` Ian Campbell
2014-01-29 13:26 ` Julien Grall [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=52E9018A.5090908@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=george.dunlap@eu.citrix.com \
--cc=julien.grall@citrix.com \
--cc=keir@xen.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.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 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.