All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Tiejun" <tiejun.chen@intel.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	"jbeulich@suse.com" <jbeulich@suse.com>,
	"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
	"stefano.stabellini@eu.citrix.com"
	<stefano.stabellini@eu.citrix.com>,
	"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	"tim@xen.org" <tim@xen.org>,
	"Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [v8][PATCH 02/17] introduce XEN_DOMCTL_set_rdm
Date: Mon, 08 Dec 2014 09:30:38 +0800	[thread overview]
Message-ID: <5484FF3E.5080604@intel.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D12610AB18@SHSMSX101.ccr.corp.intel.com>

On 2014/12/2 16:33, Tian, Kevin wrote:
>> From: Chen, Tiejun
>> Sent: Monday, December 01, 2014 5:24 PM
>>
>> This should be based on a new parameter globally, 'pci_rdmforce'.
>>
>> pci_rdmforce = 1 => Of course this should be 0 by default.
>>
>> '1' means we should force check to reserve all ranges. If failed
>> VM wouldn't be created successfully. This also can give user a
>> chance to work well with later hotplug, even if not a device
>> assignment while creating VM.
>>
>> But we can override that by one specific pci device:
>>
>> pci = ['AA:BB.CC,rdmforce=0/1]
>>
>> But this 'rdmforce' should be 1 by default since obviously any
>> passthrough device always need to do this. Actually no one really
>> want to set as '0' so it may be unnecessary but I'd like to leave
>> this as a potential approach.
>
> since no one requires it, why bother adding it? better to just
> keep global option.

This originates from my preliminary thought. Here I hope we can extend 
this approach to enable this feature just for any specific device in 
hotplug case.

But yes, this definitely isn't mandatory now since we can take this in 
next step so I can remove this right now, and of course I assume there's 
no any objection from other guys.

>
>>
>> So this domctl provides an approach to control how to populate
>> reserved device memory by tools.
>>
>> Note we always post a message to user about this once we owns
>> RMRR.
>>
>> Signed-off-by: Tiejun Chen <tiejun.chen@intel.com>
>> ---

[snip]

>> --- a/tools/libxl/libxl_dm.c
>> +++ b/tools/libxl/libxl_dm.c
>> @@ -90,6 +90,53 @@ const char *libxl__domain_device_model(libxl__gc *gc,
>>       return dm;
>>   }
>>
>> +int libxl__domain_device_setrdm(libxl__gc *gc,
>> +                                libxl_domain_config *d_config,
>> +                                uint32_t dm_domid)
>> +{
>> +    int i, ret;
>> +    libxl_ctx *ctx = libxl__gc_owner(gc);
>> +    struct xen_guest_pcidev_info *pcidevs = NULL;
>> +    uint32_t rdmforce = 0;
>> +
>> +    if ( d_config->num_pcidevs )
>> +    {
>> +        pcidevs =
>> malloc(d_config->num_pcidevs*sizeof(xen_guest_pcidev_info_t));
>> +        if ( pcidevs )
>> +        {
>> +            for (i = 0; i < d_config->num_pcidevs; i++)
>> +            {
>> +                pcidevs[i].devfn = PCI_DEVFN(d_config->pcidevs[i].dev,
>> +
>> d_config->pcidevs[i].func);
>> +                pcidevs[i].bus = d_config->pcidevs[i].bus;
>> +                pcidevs[i].seg = d_config->pcidevs[i].domain;
>> +                pcidevs[i].flags = d_config->pcidevs[i].rdmforce &
>> +                                   PCI_DEV_RDM_CHECK;
>> +            }
>> +        }
>> +        else
>> +        {
>> +            LIBXL__LOG(CTX, LIBXL__LOG_ERROR,
>> +                               "Can't allocate for pcidevs.");
>> +            return -1;
>> +        }
>> +    }
>> +    rdmforce = libxl_defbool_val(d_config->b_info.rdmforce) ? 1 : 0;
>> +
>> +    /* Nothing to do. */
>> +    if ( !rdmforce && !d_config->num_pcidevs )
>> +        return 0;
>
> move check before creating pcidevs.
>

Okay,

@@ -99,40 +99,33 @@ int libxl__domain_device_setrdm(libxl__gc *gc,
      struct xen_guest_pcidev_info *pcidevs = NULL;
      uint32_t rdmforce = 0;

-    if ( d_config->num_pcidevs )
-    {
-        pcidevs = 
malloc(d_config->num_pcidevs*sizeof(xen_guest_pcidev_info_t));
-        if ( pcidevs )
-        {
-            for (i = 0; i < d_config->num_pcidevs; i++)
-            {
-                pcidevs[i].devfn = PCI_DEVFN(d_config->pcidevs[i].dev,
-                                             d_config->pcidevs[i].func);
-                pcidevs[i].bus = d_config->pcidevs[i].bus;
-                pcidevs[i].seg = d_config->pcidevs[i].domain;
-                pcidevs[i].flags = d_config->pcidevs[i].rdmforce &
-                                   PCI_DEV_RDM_CHECK;
-            }
-        }
-        else
-        {
-            LIBXL__LOG(CTX, LIBXL__LOG_ERROR,
-                               "Can't allocate for pcidevs.");
-            return -1;
-        }
-    }
      rdmforce = libxl_defbool_val(d_config->b_info.rdmforce) ? 1 : 0;
-
      /* Nothing to do. */
      if ( !rdmforce && !d_config->num_pcidevs )
          return 0;

+    pcidevs = 
malloc(d_config->num_pcidevs*sizeof(xen_guest_pcidev_info_t));
+    if ( pcidevs )
+    {
+        for (i = 0; i < d_config->num_pcidevs; i++)
+        {
+            pcidevs[i].devfn = PCI_DEVFN(d_config->pcidevs[i].dev,
+                                         d_config->pcidevs[i].func);
+            pcidevs[i].bus = d_config->pcidevs[i].bus;
+            pcidevs[i].seg = d_config->pcidevs[i].domain;
+        }
+    }
+    else
+    {
+        LIBXL__LOG(CTX, LIBXL__LOG_ERROR, "Can't allocate for pcidevs.");
+        return -1;
+    }
+
      ret = xc_domain_device_setrdm(ctx->xch, dm_domid,
                                    (uint32_t)d_config->num_pcidevs,
-                                  rdmforce,
+                                  rdmforce & PCI_DEV_RDM_CHECK,
                                    pcidevs);
-    if ( d_config->num_pcidevs )
-        free(pcidevs);
+    free(pcidevs);

      return ret;
  }


Thanks
Tiejun

  reply	other threads:[~2014-12-08  1:30 UTC|newest]

Thread overview: 106+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-01  9:24 [v8][PATCH 00/17] xen: RMRR fix Tiejun Chen
2014-12-01  9:24 ` [v8][PATCH 01/17] tools/hvmloader: link errno.h from xen internal Tiejun Chen
2014-12-01  9:24 ` [v8][PATCH 02/17] introduce XEN_DOMCTL_set_rdm Tiejun Chen
2014-12-02  8:33   ` Tian, Kevin
2014-12-08  1:30     ` Chen, Tiejun [this message]
2014-12-02 19:39   ` Konrad Rzeszutek Wilk
2014-12-08  3:16     ` Chen, Tiejun
2014-12-08 15:57       ` Konrad Rzeszutek Wilk
2014-12-09  1:06         ` Chen, Tiejun
2014-12-09  8:33           ` Jan Beulich
2014-12-09 16:36             ` Konrad Rzeszutek Wilk
2014-12-04 15:33   ` Jan Beulich
2014-12-05  6:13     ` Tian, Kevin
2014-12-08  6:06     ` Chen, Tiejun
2014-12-08  8:43       ` Jan Beulich
2014-12-09  2:38         ` Chen, Tiejun
2014-12-09  7:29           ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 03/17] introduce XENMEM_reserved_device_memory_map Tiejun Chen
2014-12-02 19:47   ` Konrad Rzeszutek Wilk
2014-12-08  6:17     ` Chen, Tiejun
2014-12-08 10:00       ` Jan Beulich
2014-12-08 16:45         ` Daniel De Graaf
2014-12-08 16:54           ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 04/17] update the existing hypercall to support XEN_DOMCTL_set_rdm Tiejun Chen
2014-12-02  8:46   ` Tian, Kevin
2014-12-08  6:22     ` Chen, Tiejun
2014-12-04 15:50   ` Jan Beulich
2014-12-08  7:11     ` Chen, Tiejun
2014-12-08  8:51       ` Jan Beulich
2014-12-09  7:47         ` Chen, Tiejun
2014-12-09  8:19           ` Jan Beulich
2014-12-09  9:12             ` Chen, Tiejun
2014-12-09  9:21               ` Jan Beulich
2014-12-09  9:35                 ` Chen, Tiejun
2014-12-09 10:11             ` Tim Deegan
2014-12-09 10:22               ` Jan Beulich
2014-12-10  1:59                 ` Chen, Tiejun
2014-12-10 20:21                   ` Konrad Rzeszutek Wilk
2014-12-10  3:39               ` Tian, Kevin
2014-12-10  9:01                 ` Jan Beulich
2014-12-10  9:57                   ` Tian, Kevin
2014-12-10 11:12                 ` Tim Deegan
2014-12-11  2:03                   ` Tian, Kevin
2014-12-11 13:09                     ` Tim Deegan
2014-12-18 16:13                       ` Tim Deegan
2014-12-19  1:03                         ` Chen, Tiejun
2014-12-01  9:24 ` [v8][PATCH 05/17] tools/libxc: introduce hypercall for xc_reserved_device_memory_map Tiejun Chen
2014-12-02  8:46   ` Tian, Kevin
2014-12-02 19:50   ` Konrad Rzeszutek Wilk
2014-12-08  7:25     ` Chen, Tiejun
2014-12-08 15:52       ` Konrad Rzeszutek Wilk
2014-12-01  9:24 ` [v8][PATCH 06/17] tools/libxc: check if modules space is overlapping with reserved device memory Tiejun Chen
2014-12-02  8:54   ` Tian, Kevin
2014-12-02 19:55   ` Konrad Rzeszutek Wilk
2014-12-08  7:49     ` Chen, Tiejun
2014-12-01  9:24 ` [v8][PATCH 07/17] hvmloader/util: get reserved device memory maps Tiejun Chen
2014-12-02  8:59   ` Tian, Kevin
2014-12-08  7:55     ` Chen, Tiejun
2014-12-02 20:01   ` Konrad Rzeszutek Wilk
2014-12-08  8:09     ` Chen, Tiejun
2014-12-08  8:45       ` Chen, Tiejun
2014-12-04 15:52   ` Jan Beulich
2014-12-08  8:52     ` Chen, Tiejun
2014-12-08  9:18       ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 08/17] hvmloader/mmio: reconcile guest mmio with reserved device memory Tiejun Chen
2014-12-02  9:11   ` Tian, Kevin
2014-12-08  9:04     ` Chen, Tiejun
2014-12-04 16:04   ` Jan Beulich
2014-12-08  9:10     ` Chen, Tiejun
2014-12-01  9:24 ` [v8][PATCH 09/17] hvmloader/ram: check if guest memory is out of reserved device memory maps Tiejun Chen
2014-12-02  9:42   ` Tian, Kevin
2014-12-02 20:17   ` Konrad Rzeszutek Wilk
2014-12-04 16:20   ` Jan Beulich
2014-12-05  6:23     ` Tian, Kevin
2014-12-05  7:43       ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 10/17] hvmloader/mem_hole_alloc: skip any overlap with reserved device memory Tiejun Chen
2014-12-02  9:48   ` Tian, Kevin
2014-12-02 20:23   ` Konrad Rzeszutek Wilk
2014-12-04 16:28   ` Jan Beulich
2014-12-05  6:24     ` Tian, Kevin
2014-12-05  7:46       ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 11/17] xen/x86/p2m: reject populating for reserved device memory mapping Tiejun Chen
2014-12-02  9:57   ` Tian, Kevin
2014-12-04 16:42   ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 12/17] xen/x86/ept: handle reserved device memory in ept_handle_violation Tiejun Chen
2014-12-02  9:59   ` Tian, Kevin
2014-12-02 20:26   ` Konrad Rzeszutek Wilk
2014-12-04 16:46   ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 13/17] xen/mem_access: don't allow accessing reserved device memory Tiejun Chen
2014-12-02 14:54   ` Julien Grall
2014-12-18 22:56     ` Tamas K Lengyel
2014-12-02 20:27   ` Konrad Rzeszutek Wilk
2014-12-04 16:51   ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 14/17] xen/x86/p2m: introduce set_identity_p2m_entry Tiejun Chen
2014-12-02 10:00   ` Tian, Kevin
2014-12-02 20:29   ` Konrad Rzeszutek Wilk
2014-12-01  9:24 ` [v8][PATCH 15/17] xen:vtd: create RMRR mapping Tiejun Chen
2014-12-02 10:02   ` Tian, Kevin
2014-12-02 20:30   ` Konrad Rzeszutek Wilk
2014-12-01  9:24 ` [v8][PATCH 16/17] xen/vtd: group assigned device with RMRR Tiejun Chen
2014-12-02 10:11   ` Tian, Kevin
2014-12-02 20:40   ` Konrad Rzeszutek Wilk
2014-12-04 17:05   ` Jan Beulich
2014-12-01  9:24 ` [v8][PATCH 17/17] xen/vtd: re-enable USB device assignment if enable pci_force Tiejun Chen
2014-12-05 16:12   ` Konrad Rzeszutek Wilk
2014-12-02 19:17 ` [v8][PATCH 00/17] xen: RMRR fix Konrad Rzeszutek Wilk

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=5484FF3E.5080604@intel.com \
    --to=tiejun.chen@intel.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=kevin.tian@intel.com \
    --cc=stefano.stabellini@eu.citrix.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 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.