This is about v13 of the RDM series.  Compared to v11, I have:
 - imported it into git (dropping change notices for all previous version)
 - brought in new versions of 01 (aka "v12a") and 06 from Jan
 - made adjustments as needed by the new 01 from Jan
 - double-checked the acks etc., dropping unjustified acks

git branch here:
  http://xenbits.xen.org/gitweb/?p=people/iwj/xen.git;a=summary
  git://xenbits.xen.org/people/iwj/xen.git
  base.rdm-v13..wip.rdm-v13

*a   01   introduce XENMEM_reserved_device_memory_map
 a   02   xen/vtd: create RMRR mapping
 a   03   xen/passthrough: extend hypercall to support rdm reservation policy
 a   04   xen: enable XENMEM_memory_map in hvm
 a   05   hvmloader: get guest memory map into memory_map[]
*a   06   hvmloader/pci: try to avoid placing BARs in RMRRs
 a   07   hvmloader/e820: construct guest e820 table
* T  08   tools/libxc: Expose new hypercall xc_reserved_device_memory_map
 a   09   tools: extend xc_assign_device() to support rdm reservation policy
 a   10   tools: introduce some new parameters to set rdm policy
* T  11   tools/libxl: detect and avoid conflicts with RDM
 a   12   tools: introduce a new parameter to set a predefined rdm boundary
 a   13   libxl: construct e820 map with RDM information for HVM guest
 a   14   xen/vtd: enable USB device assignment
 a   15   xen/vtd: prevent from assign the device with shared rmrr
 a   16   tools: parse to enable new rdm policy parameters

* = changed in v13, since v11
a = acked enough to commit
T = tools maintainer ack required

Wei, can you please give your formal ack for the two changed patches ?

Tiejun, can you please test this series ?  Hopefully if you say it
still works after this, we can commit it tomorrow.

Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Reply via email to