From: Julien Grall <julien.grall@citrix.com>
To: "Chen, Tiejun" <tiejun.chen@intel.com>,
Julien Grall <julien.grall@citrix.com>,
JBeulich@suse.com, tim@xen.org, konrad.wilk@oracle.com,
andrew.cooper3@citrix.com, kevin.tian@intel.com,
yang.z.zhang@intel.com, ian.campbell@citrix.com,
wei.liu2@citrix.com, Ian.Jackson@eu.citrix.com,
stefano.stabellini@citrix.com
Cc: xen-devel@lists.xen.org
Subject: Re: [RFC][v2][PATCH 07/14] xen/passthrough: extend hypercall to support rdm reservation policy
Date: Mon, 25 May 2015 13:42:32 +0200 [thread overview]
Message-ID: <55630AA8.8070905@citrix.com> (raw)
In-Reply-To: <5562FE88.9050107@intel.com>
Hi,
On 25/05/2015 12:50, Chen, Tiejun wrote:
>
> On 2015/5/25 18:02, Julien Grall wrote:
>>
>>
>> On 25/05/2015 04:09, Chen, Tiejun wrote:
>>> On 2015/5/22 18:33, Julien Grall wrote:
>>>> Hi,
>>>>
>>>> On 22/05/2015 10:35, Tiejun Chen wrote:
>>>>> diff --git a/xen/include/public/domctl.h b/xen/include/public/domctl.h
>>>>> index 0c0ea4a..203c80e 100644
>>>>> --- a/xen/include/public/domctl.h
>>>>> +++ b/xen/include/public/domctl.h
>>>>> @@ -499,6 +499,11 @@ struct xen_domctl_assign_device {
>>>>> XEN_GUEST_HANDLE_64(char) path; /* path to the device
>>>>> tree node */
>>>>> } dt;
>>>>> } u;
>>>>> + /* IN */
>>>>> +#define XEN_DOMCTL_DEV_NO_RDM 0
>>>>> +#define XEN_DOMCTL_DEV_RDM_RELAXED 1
>>>>> +#define XEN_DOMCTL_DEV_RDM_STRICT 2
>>>>> + uint32_t flag; /* flag of assigned device */
>>>>
>>>> You don't plumb this value for DT neither in the toolstack (see
>>>> xc_assign_dt_device) and Xen. Please add a comment saying it's only
>>>> used
>>>
>>> I think we should do this,
>>>
>>> @@ -1801,6 +1801,8 @@ int xc_assign_dt_device(
>>>
>>> domctl.u.assign_device.dev = XEN_DOMCTL_DEV_DT;
>>> domctl.u.assign_device.u.dt.size = size;
>>> + /* DT doesn't own any RDM. */
>>> + domctl.u.assign_device.flag = XEN_DOMCTL_DEV_NO_RDM;
>>> set_xen_guest_handle(domctl.u.assign_device.u.dt.path, path);
>>>
>>> rc = do_domctl(xch, &domctl);
>>
>> I would be fine with plumbing in drivers/passthrough/device_tree.c and a
>> check that the value is not different.
>>
>
> Are you saying something like this?
>
> @@ -149,6 +149,14 @@ int iommu_do_dt_domctl(struct xen_domctl *domctl,
> struct domain *d,
> if ( domctl->u.assign_device.dev != XEN_DOMCTL_DEV_DT )
> break;
>
> + if ( domctl->u.assign_device.dev == XEN_DOMCTL_DEV_NO_RDM )
wrong field here. Other than that it looks good to me.
> + {
> + printk(XENLOG_G_ERR "XEN_DOMCTL_assign_device: assign \"%s\""
> + " to dom%u failed (%d) since we don't support RDM.\n",
> + dt_node_full_name(dev), d->domain_id, ret);
> + break;
> + }
> +
> if ( unlikely(d->is_dying) )
> {
> ret = -EINVAL;
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-05-25 11:42 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 9:35 [RFC][v2][PATCH 00/14] Fix RMRR Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 01/14] tools: introduce some new parameters to set rdm policy Tiejun Chen
2015-06-02 15:57 ` Wei Liu
2015-06-03 1:35 ` Chen, Tiejun
2015-06-07 11:06 ` Wei Liu
2015-06-08 1:42 ` Chen, Tiejun
2015-05-22 9:35 ` [RFC][v2][PATCH 02/14] introduce XENMEM_reserved_device_memory_map Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 03/14] tools/libxc: Expose new hypercall xc_reserved_device_memory_map Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 04/14] tools/libxl: detect and avoid conflicts with RDM Tiejun Chen
2015-06-02 16:29 ` Wei Liu
2015-06-03 2:25 ` Chen, Tiejun
2015-06-07 11:20 ` Wei Liu
2015-06-08 2:16 ` Chen, Tiejun
2015-05-22 9:35 ` [RFC][v2][PATCH 05/14] xen/x86/p2m: introduce set_identity_p2m_entry Tiejun Chen
2015-05-28 12:27 ` Jan Beulich
2015-05-29 1:19 ` Chen, Tiejun
2015-05-22 9:35 ` [RFC][v2][PATCH 06/14] xen:vtd: create RMRR mapping Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 07/14] xen/passthrough: extend hypercall to support rdm reservation policy Tiejun Chen
2015-05-22 10:33 ` Julien Grall
2015-05-25 2:09 ` Chen, Tiejun
2015-05-25 10:02 ` Julien Grall
2015-05-25 10:50 ` Chen, Tiejun
2015-05-25 11:42 ` Julien Grall [this message]
2015-05-26 0:42 ` Chen, Tiejun
2015-05-22 9:35 ` [RFC][v2][PATCH 08/14] tools: extend xc_assign_device() " Tiejun Chen
2015-06-02 16:36 ` Wei Liu
2015-06-03 2:58 ` Chen, Tiejun
2015-06-07 11:27 ` Wei Liu
2015-06-09 5:42 ` Chen, Tiejun
2015-05-22 9:35 ` [RFC][v2][PATCH 09/14] xen: enable XENMEM_memory_map in hvm Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 10/14] tools: extend XENMEM_set_memory_map Tiejun Chen
2015-05-22 10:25 ` Julien Grall
2015-05-25 2:00 ` Chen, Tiejun
2015-06-02 16:42 ` Wei Liu
2015-06-03 3:06 ` Chen, Tiejun
2015-05-22 9:35 ` [RFC][v2][PATCH 11/14] hvmloader: get guest memory map into memory_map[] Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 12/14] hvmloader/pci: skip reserved ranges Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 13/14] hvmloader/e820: construct guest e820 table Tiejun Chen
2015-05-22 9:35 ` [RFC][v2][PATCH 14/14] xen/vtd: enable USB device assignment Tiejun Chen
2015-05-22 9:46 ` [RFC][v2][PATCH 00/14] Fix RMRR Jan Beulich
2015-05-28 5:48 ` Chen, Tiejun
2015-05-28 7:55 ` Jan Beulich
2015-05-29 7:58 ` Chen, Tiejun
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=55630AA8.8070905@citrix.com \
--to=julien.grall@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=kevin.tian@intel.com \
--cc=konrad.wilk@oracle.com \
--cc=stefano.stabellini@citrix.com \
--cc=tiejun.chen@intel.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=yang.z.zhang@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).