From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: stefano.stabellini@eu.citrix.com, tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v2 4/4] Revert "xen: arm: force guest memory accesses to cacheable when MMU is disabled"
Date: Tue, 04 Feb 2014 15:37:36 +0000 [thread overview]
Message-ID: <52F10940.9000109@linaro.org> (raw)
In-Reply-To: <1391523745-21139-4-git-send-email-ian.campbell@citrix.com>
On 02/04/2014 02:22 PM, Ian Campbell wrote:
> This reverts commit 89eb02c2204a0b42a0aa169f107bc346a3fef802.
>
> This approach has a short coming in that it breaks when a guest enables its
> MMU (SCTLR.M, disabling HCR.DC) without enabling caches (SCTLR.C) first/at the
> same time. It turns out that FreeBSD does this.
>
> This has now been fixed (yet) another way (third time is the charm!) so remove
> this support. The original commit contained some fixes which are still
> relevant even with the revert of the bulk of the patch:
> - Correction to HSR_SYSREG_CRN_MASK
> - Rename of HSR_SYSCTL macros to avoid naming clash
> - Definition of some additional cp reg specifications
>
> Since these are still useful they are not reverted.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
Except the spurious line toward the end of the patch:
Acked-by: Julien Grall <julien.grall@linaro.org>
> diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c
> index b8f2e82..ec51d1b 100644
> --- a/xen/arch/arm/traps.c
> +++ b/xen/arch/arm/traps.c
[..]
> default:
> printk("%s %d, %d, c%d, c%d, %d %s x%d @ 0x%"PRIregister"\n",
> sysreg.read ? "mrs" : "msr",
> @@ -1635,6 +1477,7 @@ done:
> if (first) unmap_domain_page(first);
> }
>
> +
Spurious change?
> static void do_trap_instr_abort_guest(struct cpu_user_regs *regs,
> union hsr hsr)
--
Julien Grall
next prev parent reply other threads:[~2014-02-04 15:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 14:21 [PATCH 0/4 v2] xen/arm: fix guest builder cache cohenrency (again, again) Ian Campbell
2014-02-04 14:22 ` [PATCH v2 1/4] xen: arm: rename create_p2m_entries to apply_p2m_changes Ian Campbell
2014-02-04 14:22 ` [PATCH v2 2/4] xen: arm: rename p2m next_gfn_to_relinquish to lowest_mapped_gfn Ian Campbell
2014-02-04 14:22 ` [PATCH v2 3/4] xen/arm: clean and invalidate all guest caches by VMID after domain build Ian Campbell
2014-02-04 15:00 ` Jan Beulich
2014-02-04 15:43 ` Ian Campbell
2014-02-04 15:48 ` Jan Beulich
2014-02-04 16:07 ` Ian Campbell
2014-02-04 16:42 ` Jan Beulich
2014-02-04 15:32 ` Ian Jackson
2014-02-04 15:37 ` Ian Campbell
2014-02-04 15:55 ` Ian Jackson
2014-02-04 16:09 ` Ian Campbell
2014-02-04 16:16 ` Ian Jackson
2014-02-04 14:22 ` [PATCH v2 4/4] Revert "xen: arm: force guest memory accesses to cacheable when MMU is disabled" Ian Campbell
2014-02-04 15:37 ` Julien Grall [this message]
2014-02-04 16:07 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2014-02-05 16:03 [PATCH 0/4 v3] xen/arm: fix guest builder cache cohenrency (again, again) Ian Campbell
2014-02-05 16:03 ` [PATCH v2 4/4] Revert "xen: arm: force guest memory accesses to cacheable when MMU is disabled" Ian Campbell
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=52F10940.9000109@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.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 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).