From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: [v7][RFC][PATCH 06/13] hvmloader/ram: check if guest memory is out of reserved device memory maps Date: Wed, 05 Nov 2014 17:00:29 +0000 Message-ID: <545A57AD02000078000C1037@mail.emea.novell.com> References: <1414136077-18599-1-git-send-email-tiejun.chen@intel.com> <544A84B10200007800042016@mail.emea.novell.com> <544DFDB2.2010508@intel.com> <544E29C70200007800042595@mail.emea.novell.com> <544F49F9.3070208@intel.com> <544F78B80200007800042B95@mail.emea.novell.com> <54509A8A.9060606@intel.com> <5450BE27020000780004304A@mail.emea.novell.com> <5451AC56.7010303@intel.com> <54521100020000780004363A@mail.emea.novell.com> <545320F2.5030103@intel.com> <545354500200007800043D94@mail.emea.novell.com> <5457174C.8020400@intel.com> <5457515102000078000443B0@mail.emea.novell.com> <54574D8F.8060407@intel.com> <54575E2D0200007800044443@mail.emea.novell.com> <545767C4.7070806@intel.com> <5457787002000078000445C7@mail.emea.novell.com> <54576DF7.8060408@intel.com> <545784830200007800044627@mail.emea.novell.com> <54585EAA.20904@intel.com> <545894610200007800044A5B@mail.emea.novell.com> <545992A2.8070309@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <545992A2.8070309@intel.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: tiejun.chen@intel.com Cc: yang.z.zhang@intel.com, kevin.tian@intel.com, tim@xen.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org >>> "Chen, Tiejun" 11/05/14 3:59 AM >>> Everything up to here sounded reasonable. >Next, we need a new domctl to provide these info, 'pci_rdmforce' and >'rdm_force' when parse the config file. Certainly we may need to >introduce and set two new fields in strcut domain, and since then we >just use these fields to modify our current existing iommu callback >inside to support our policy. I mean we just expose those associated >RMRR entry. I think its easy to implement this since inside Xen we can >know which entry is owned by which device. So this can benefit us to >avoid modifying any tools codes and most Xen codes we already addressed. Whether a domctl is the right approach I can't really tell with this somewhat vague description. Jan