All of lore.kernel.org
 help / color / mirror / Atom feed
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=v3 1/8] xen: arm: map memory as inner shareable.
Date: Mon, 17 Mar 2014 15:17:11 +0000	[thread overview]
Message-ID: <532711F7.1070403@linaro.org> (raw)
In-Reply-To: <1395069109.18221.39.camel@kazak.uk.xensource.com>

On 03/17/2014 03:11 PM, Ian Campbell wrote:
> On Mon, 2014-03-17 at 15:06 +0000, Julien Grall wrote:
>> Hi Ian,
>>
>> On 03/17/2014 02:53 PM, Ian Campbell wrote:
>>> The inner shareable domain contains all SMP processors, including different
>>> clusters (e.g. big.LITTLE). Therefore this is the correct thing to use for Xen
>>> memory mappings. The outer shareable domain is for devices on busses which are
>>> coherent and barrier-aware (e.g. AMBA4 AXI with ACE). While the system domain
>>> is for things behind bridges which are not.
>>>
>>> One wrinkle is that Normal memory with attributes Inner Non-cacheable, Outer
>>> Non-cacheable (which we call BUFFERABLE) must be mapped Outer Shareable on ARM
>>> v7. Therefore change the prototype of mfn_to_xen_entry to take the attribute
>>> index so we can DTRT. On ARMv8 the sharability is ignored and considered to
>>> always be Outer Shareable.
>>>
>>> Don't adjust the barriers, flushes etc, those remain as they were (which is
>>> more than is now required).  I'll change those in a later patch.
>>>
>>> Many thanks to Leif for explaining the difference between Inner- and
>>> Outer-Shareable in words of two or less syllables, I hope I've replicated that
>>> explanation properly above!
>>
>> Is there any reason to not modify VTCR_EL2?
> 
> Could do as a future cleanup but I wanted to get Xen's own mappings
> sorted first.

AFAIU, you are also modifying P2M attributes. In any case:

Acked-by: Julien Grall <julien.grall@linaro.org>

-- 
Julien Grall

  reply	other threads:[~2014-03-17 15:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17 14:53 [PATCH v3 0/8] xen: arm: map normal memory as inner shareable, reduce scope of various barriers Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 1/8] xen: arm: map memory as inner shareable Ian Campbell
2014-03-17 15:06   ` Julien Grall
2014-03-17 15:11     ` Ian Campbell
2014-03-17 15:17       ` Julien Grall [this message]
2014-03-17 17:36         ` Ian Campbell
2014-03-18 13:47           ` Julien Grall
2014-03-18 14:04             ` Ian Campbell
2014-03-18 16:12             ` Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 2/8] xen: arm: Only upgrade guest barriers to " Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 3/8] xen: arm: consolidate barrier definitions Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 4/8] xen: arm: Use SMP barriers when that is all which is required Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 5/8] xen: arm: Use dmb for smp barriers Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 6/8] xen: arm: add scope to dsb and dmb macros Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 7/8] xen: arm: weaken SMP barriers to inner shareable Ian Campbell
2014-03-17 14:53 ` [PATCH=v3 8/8] xen: arm: use more specific barriers for read and write barriers 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=532711F7.1070403@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 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.