From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: christoffer.dall@linaro.org, xen-devel@lists.xenproject.org,
tim@xen.org, parth.dixit@linaro.org,
stefano.stabellini@citrix.com
Subject: Re: [PATCH v3 2/2] xen/arm: Automatically find a PPI for the DOM0 event channel interrupt
Date: Mon, 2 Feb 2015 15:12:23 +0000 [thread overview]
Message-ID: <1422889943.4801.14.camel@citrix.com> (raw)
In-Reply-To: <1422546694-22797-3-git-send-email-julien.grall@linaro.org>
On Thu, 2015-01-29 at 15:51 +0000, Julien Grall wrote:
> Use the new vgic interface to know which virtual PPI is free and use it
> for the event channel code.
>
> At the DOM0 creation time, Xen doesn't know which vIRQ will be free.
> All the vIRQ will be reserved when we parse the device tree. So we can
> allocate the vIRQ just after the device tree has been parsed.
>
> It's safe to defer the allocation because no vIRQ can be injected as
> long as the vCPU is not online.
>
> As the device tree node "hypervisor" containing the description of the
> event channel interrupt is created earlier, add a placeholder which will
> be fix up once Xen has allocated the PPI.
>
> Also correct the check in arch_domain_create to use is_hardware_domain.
>
> Signed-off-by: Julien Grall <julien.grall@linaro.org>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
prev parent reply other threads:[~2015-02-02 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 15:51 [PATCH v3 0/2] xen/arm: Automatically find a PPI for the DOM0 event IRQ Julien Grall
2015-01-29 15:51 ` [PATCH v3 1/2] xen/arm: vgic: Keep track of vIRQ used by a domain Julien Grall
2015-02-02 15:09 ` Ian Campbell
2015-02-18 17:36 ` Julien Grall
2015-02-19 17:15 ` Ian Campbell
2015-02-19 17:19 ` Julien Grall
2015-01-29 15:51 ` [PATCH v3 2/2] xen/arm: Automatically find a PPI for the DOM0 event channel interrupt Julien Grall
2015-02-02 15:12 ` Ian Campbell [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=1422889943.4801.14.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=christoffer.dall@linaro.org \
--cc=julien.grall@linaro.org \
--cc=parth.dixit@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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 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.