From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Zhang, Yang Z" Subject: Re: [v6][PATCH 2/2] xen:vtd: missing RMRR mapping while share EPT Date: Thu, 25 Sep 2014 02:30:34 +0000 Message-ID: References: <541FB087.4080008@intel.com> <541FB7C3.9080608@intel.com> <541FFFC50200007800036C28@mail.emea.novell.com> <541FE65A.8070803@intel.com> <542017E80200007800036D1E@mail.emea.novell.com> <5420D357.1060202@intel.com> <5422823B.1090109@intel.com> <5422A1250200007800038152@mail.emea.novell.com> <54228683.1090103@intel.com> <5422A74C02000078000381B0@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5422A74C02000078000381B0@mail.emea.novell.com> Content-Language: en-US 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 , "Chen, Tiejun" Cc: "Tian, Kevin" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org Jan Beulich wrote on 2014-09-24: >>>> On 24.09.14 at 10:53, wrote: >> On 2014/9/24 16:47, Jan Beulich wrote: >>>>>> On 24.09.14 at 10:35, wrote: >>>> In tools stack, how can we get ultimate e820 table built by hvmloader? >>> >>> What is this needed for? >> >> I mean in case of a hotplug after the migration, we should check any >> overlap with current existing RAM/MMIO, right? So we need to know >> current existing guest RAM/MMIO layout since this ultimate e820 >> table is just built by hvmloader, not in xen internal. > > Actually I think we'd be better off not complicating the tool stack > for this - with proper checking for collisions in the P2M updates, the > assignment ought to fail without the tool stack doing anything. How do the checking in P2M updates? Only hvmloader knows whether the RMRR region is reserved. If we want do the check in hypervisor, we need to report those info to hypervisor. > > Jan Best regards, Yang