From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [PATCH v3 13/24] xen/arm: Implement hypercall PHYSDEVOP_{, un}map_pirq Date: Mon, 23 Feb 2015 09:33:05 +0000 Message-ID: <54EB01E102000078000625CB@mail.emea.novell.com> References: <1421159133-31526-1-git-send-email-julien.grall@linaro.org> <1421159133-31526-14-git-send-email-julien.grall@linaro.org> <54C932BF.5070009@linaro.org> <54CA2709.9080409@linaro.org> <1424451224.30924.357.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YPpO2-0003yF-Ji for xen-devel@lists.xenproject.org; Mon, 23 Feb 2015 09:33:10 +0000 In-Reply-To: <1424451224.30924.357.camel@citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , Stefano Stabellini Cc: xen-devel@lists.xenproject.org, Julien Grall , stefano.stabellini@citrix.com, tim@xen.org List-Id: xen-devel@lists.xenproject.org >>> On 20.02.15 at 17:53, wrote: > Jan, do you have any feeling for how this is going to play out on x86 > with the vapic stuff? The vapic logic shouldn't require any physdevop involvement, so if I read right what you propose (not having such a requirement / connection on ARM) either, I agree that a new domctl should be all that's needed (if XEN_DOMCTL_{,un}bind_pt_irq can't be re-used). Jan