From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell 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 Message-ID: <1422889943.4801.14.camel@citrix.com> References: <1422546694-22797-1-git-send-email-julien.grall@linaro.org> <1422546694-22797-3-git-send-email-julien.grall@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YIIft-0003ns-B5 for xen-devel@lists.xenproject.org; Mon, 02 Feb 2015 15:12:29 +0000 In-Reply-To: <1422546694-22797-3-git-send-email-julien.grall@linaro.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Julien Grall Cc: christoffer.dall@linaro.org, xen-devel@lists.xenproject.org, tim@xen.org, parth.dixit@linaro.org, stefano.stabellini@citrix.com List-Id: xen-devel@lists.xenproject.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 Acked-by: Ian Campbell