[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v2 0/3] x86: per-domain mapping adjustments


  • To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Tue, 26 Feb 2013 16:59:31 +0000
  • Delivery-date: Tue, 26 Feb 2013 16:59:51 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac4UQqUP3e6aGcOub0esEKrxTJIl2w==
  • Thread-topic: [Xen-devel] [PATCH v2 0/3] x86: per-domain mapping adjustments

On 26/02/2013 15:56, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> The main goal being the re-work of the hypercall argument translation
> area management, this series first breaks out per-domain mapping
> management into its own set of functions, in order to then use this
> for setting up the translation areas in per-domain space.
> 
> While doing this I also realized that it's pointless for the
> map_domain_page() code to track L1 page table pointers in a
> separate Xen heap page - we can equally well use the linear
> page table for the manipulations needed here.
> 
> 1: introduce create_perdomain_mapping()
> 2: rework hypercall argument translation area setup
> 3: use linear L1 page table for map_domain_page() page table manipulation
> 
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Acked-by: Keir Fraser <keir@xxxxxxx>

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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.