From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xenproject.org
Cc: stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH v4 1/4] xen/arm: vgic-v2: Report the correct GICC size to the guest
Date: Fri, 23 Oct 2015 14:43:16 +0100 [thread overview]
Message-ID: <562A3974.2080601@citrix.com> (raw)
In-Reply-To: <1445607584.2374.172.camel@citrix.com>
On 23/10/15 14:39, Ian Campbell wrote:
> On Fri, 2015-10-23 at 14:34 +0100, Julien Grall wrote:
>> Hi Ian,
>>
>> On 23/10/15 14:28, Ian Campbell wrote:
>>> On Thu, 2015-10-08 at 19:23 +0100, Julien Grall wrote:
>>>> The GICv2 DT node is usually used by the guest to know the
>>>> address/size
>>>> of the regions (GICD, GICC...) to map into their virtual memory.
>>>>
>>>> While the GICv2 spec requires the size of the GICC to be 8KB, we
>>>> correctly do an 8KB stage-2 mapping but errornously report 256 in the
>>>> device tree (based on GUEST_GICC_SIZE).
>>>
>>> "erroneously"
>>>
>>>>
>>>> I bet we didn't see any issue so far because all the registers except
>>>> GICC_DIR lives in the first 256 bytes of the GICC region and all the
>>>> guest
>>>
>>> "guests"
>>>
>>>> I have seen so far are driving the GIC with GICC_CTLR.EIOmode =
>>>> 0.
>>>>
>>>> Signed-off-by: Julien Grall <julien.grall@citrix.com>
>>>
>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>>
>>> (typo's fixable on commit).
>>
>> Thank you!
>>
>>>> ---
>>>> This patch is a good candidate to backport for Xen 4.6 - 4.4.
>>>> Without it a guest relying on the DT can't use GICC_DIR.
>>>
>>> Noted, but just to check: This patch (and none of the other fixes in
>>> this
>>> series) are all which are required for a guest to be able to use
>>> GICC_DIR,
>>> right?
>>
>> Correct. BTW, I forgot to mention that this patch may not apply cleanly
>> on Xen 4.4 as rearranged the guest memory address space in Xen 4.5.
>
> I'd be inclined not to bother with it for 4.4 at this juncture then.
I'm fine with that.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-10-23 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 18:23 [PATCH v4 0/4] xen/arm: gic-v2: Detect automatically aliased GIC 400 Julien Grall
2015-10-08 18:23 ` [PATCH v4 1/4] xen/arm: vgic-v2: Report the correct GICC size to the guest Julien Grall
2015-10-23 13:28 ` Ian Campbell
2015-10-23 13:34 ` Julien Grall
2015-10-23 13:39 ` Ian Campbell
2015-10-23 13:43 ` Julien Grall [this message]
2015-10-08 18:23 ` [PATCH v4 2/4] xen/arm: gic: Check the size of the CPU and vCPU interface retrieved from DT Julien Grall
2015-10-23 13:21 ` Ian Campbell
2015-10-08 18:23 ` [PATCH v4 3/4] xen/arm: gic-v2: Automatically detect aliased GIC400 Julien Grall
2015-10-23 13:23 ` Ian Campbell
2015-10-08 18:23 ` [PATCH v4 4/4] xen/arm: platform: Drop the quirks callback Julien Grall
2015-10-23 13:23 ` Ian Campbell
2015-10-23 13:52 ` [PATCH v4 0/4] xen/arm: gic-v2: Detect automatically aliased GIC 400 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=562A3974.2080601@citrix.com \
--to=julien.grall@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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).