>>> On 20.11.14 at 15:40, <kevin.t...@intel.com> wrote: >> From: Tian, Kevin >> Sent: Thursday, November 20, 2014 4:51 PM >> > From: Jan Beulich [mailto:jbeul...@suse.com] >> > Sent: Thursday, November 20, 2014 4:04 PM >> > >>> On 20.11.14 at 08:45, <kevin.t...@intel.com> wrote: >> > > Current option sounds a reasonable one, i.e. passing a list of BDFs >> > > assigned to this VM before populating p2m, and then having >> > > hypervisor to filter out reserved regions associated with those >> > > BDFs. This way libxc teaches Xen to create reserved regions once, >> > > and then later the filtered info is returned upon query. >> > >> > Reasonable, but partly redundant. The positive aspect being that >> > it permits this list and the list of actually being assigned devices to >> > be different, i.e. allowing holes to be set up for devices that only >> > _may_ get assigned at some point. >> >> redundant if we think the list only exactly matching the statically >> assigned devices. but that's just current point. >> >> reasonable if we think there may be other policies impacting the list >> (e.g. if hotplugable device may have a config option and then we have >> a potential list larger than static assigned devices). From this angle >> I think the new interface actually makes sense for this very purpose. > > Jan are you OK with this?
I can live with it, yes. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
