From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Tiejun" Subject: Re: [v6][PATCH 2/2] xen:vtd: missing RMRR mapping while share EPT Date: Mon, 22 Sep 2014 13:46:43 +0800 Message-ID: <541FB7C3.9080608@intel.com> References: <541FB087.4080008@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <541FB087.4080008@intel.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: Jan Beulich Cc: "Zhang, Yang Z" , Kevin , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org > >> It should suffice to give 3 Gb (or event slightly less) of memory to > >> the DomU (if your Dom0 can hopefully tolerate running with just 1Gb). > > > > Yes. So I can't produce that real case of conflict with those existing > > RMRR in my platform. > > When you pass 3Gb to the guest, its memory map should extend to > about 0xC0000000, well beyond the range the RMRRs reference. So Yes. So I set memory size as 2816M which also cover all RMRR ranges in my platform. > you ought to be able to see the collision (or if you don't you ought to > have ways to find out why they're not happening, as that would be a > sign of something else being bogus). > Then I can see that work as we expect: # xl cr hvm.cfg Parsing config from hvm.cfg libxl: error: libxl_pci.c:949:do_pci_add: xc_assign_device failed: Operation not permitted libxl: error: libxl_create.c:1329:domcreate_attach_pci: libxl_device_pci_add failed: -3 And # xl dmesg ... (XEN) [VT-D]iommu.c:1589: d0:PCI: unmap 0000:00:02.0 (XEN) [VT-D]iommu.c:1452: d1:PCI: map 0000:00:02.0 (XEN) Cannot identity map d1:ad000, already mapped to 115d51. (XEN) [VT-D]iommu.c:2296: IOMMU: mapping reserved region failed (XEN) XEN_DOMCTL_assign_device: assign 0000:00:02.0 to dom1 failed (-1) (XEN) [VT-D]iommu.c:1589: d1:PCI: unmap 0000:00:02.0 (XEN) [VT-D]iommu.c:1452: d0:PCI: map 0000:00:02.0 ... Thanks Tiejun