All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Mj Embd <mj.embd@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARM GIC Security Extensions and Xen
Date: Mon, 28 Oct 2013 08:00:40 -0700	[thread overview]
Message-ID: <526E7C18.5040208@linaro.org> (raw)
In-Reply-To: <CAPUj1OOpbp76Hhx=Q+pg7xgLjMArgyL72fLdW8CHqjsCtRM=Qg@mail.gmail.com>



On 10/28/2013 04:29 AM, Mj Embd wrote:
> Slight modification GICC_AIAR (%s/GICV/GICC/g)
>
> On Mon, Oct 28, 2013 at 4:57 PM, Mj Embd <mj.embd@gmail.com> wrote:
>> Does Xen GIC implementation use Grp0 as secure and Grp 1 as NS as
>> mentioned  in GIC 400 manual
>> --
>> When a GIC that implements the GIC Security Extensions is connected to
>> a processor that implements the ARM Security Extensions:
>>
>> Group 0 interrupts are Secure interrupts, and Group 1 interrupts are
>> Non-secure interrupts.
>>
>>
>> ARM IHI 0048B.b Non-Confidential ID072613 Pg 1-16
>> ---
>>
>> The manual also states
>>
>> In GICv2, ARM recommends that separate registers are used to manage
>> Group 0 and Group 1 interrupts:
>>
>> GICV_IAR, GICV_EOIR, and GICV_HPPIR for Group 0 interrupts GICV_AIAR,
>> GICV_AEOIR, and GICV_AHPPIR for Group 1 interrupts.
>>
>> pg 5-162
>>
>>
>> I was not able to find GICV_AIAR being used in code.

Xen is running in non-secure mode. The register GICC_AIAR is only used 
for secure mode. Actually in secure mode, it's an alias to GICC_IAR.

-- 
Julien Grall

  reply	other threads:[~2013-10-28 15:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 11:27 ARM GIC Security Extensions and Xen Mj Embd
2013-10-28 11:29 ` Mj Embd
2013-10-28 15:00   ` Julien Grall [this message]
2013-10-29 14:14     ` Mj Embd
2013-10-30 18:51       ` Julien Grall
2013-10-30 18:53         ` Mj Embd
2013-10-31 16:14           ` Ian Campbell
2013-10-31 16:49             ` Mj Embd

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=526E7C18.5040208@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=mj.embd@gmail.com \
    --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.