From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: [PATCH v3 20/24] xen/passthrough: Extend XEN_DOMCTL_assign_device to support DT device Date: Tue, 10 Mar 2015 16:33:58 +0000 Message-ID: <54FF1CF6.5030702@linaro.org> References: <1421159133-31526-1-git-send-email-julien.grall@linaro.org> <1421159133-31526-21-git-send-email-julien.grall@linaro.org> <1424452643.30924.368.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1YVN6y-0008GK-7N for xen-devel@lists.xenproject.org; Tue, 10 Mar 2015 16:34:28 +0000 Received: by wesx3 with SMTP id x3so3109245wes.4 for ; Tue, 10 Mar 2015 09:34:26 -0700 (PDT) In-Reply-To: <1424452643.30924.368.camel@citrix.com> 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 , Daniel De Graaf Cc: Wei Liu , Ian Jackson , tim@xen.org, stefano.stabellini@citrix.com, Jan Beulich , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org Hi Ian, On 20/02/15 17:17, Ian Campbell wrote: >> + /* TODO: Do we need to check is_dying? Mostly to protect against >> + * hypercall trying to passthrough a device while we are >> + * dying. > > FWIW the PCI case appears not to care... There is one place in XEN_DOMCTL_assign_device... Although I don't understand much the usage of is_dying. >> + */ >> + >> + switch ( domctl->cmd ) >> + { >> + case XEN_DOMCTL_assign_device: >> + ret = -ENOSYS; >> + if ( domctl->u.assign_device.dev != XEN_DOMCTL_DEV_DT ) >> + break; > > You added something similar to iommu_do_pci_domctl, would it not be > preferable for the caller to switch on domctl->u.assign_device.dev and > call the correct iommu_do_*_domctl? I though about it. It would require to stub iommu_do_*_domctl. So I preferred to chose the current solution. Regards, -- Julien Grall