From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Chen, Tiejun" Subject: Re: [v3][PATCH 05/16] xen: enable XENMEM_memory_map in hvm Date: Thu, 18 Jun 2015 16:53:29 +0800 Message-ID: <55828709.7030303@intel.com> References: <1433985325-16676-1-git-send-email-tiejun.chen@intel.com> <1433985325-16676-6-git-send-email-tiejun.chen@intel.com> <558164B2020000780008605B@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <558164B2020000780008605B@mail.emea.novell.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: yang.z.zhang@intel.com, andrew.cooper3@citrix.com, kevin.tian@intel.com, tim@xen.org, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 2015/6/17 18:14, Jan Beulich wrote: >>>> On 11.06.15 at 03:15, wrote: >> This patch enables XENMEM_memory_map in hvm. So we can use it to >> setup the e820 mappings. > > I think saying "hvmloader" instead of "we" would make things more > explicit. In the context here, "we" would be the hypervisor, and Fixed. > in that context enabling this subop to set up e820 mappings makes > no sense. > > As to the change itself: > Acked-by: Jan Beulich > Thanks Tiejun