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

Re: [Xen-devel] [PATCH v7 3/7] xen/pvh: Create a new file for Xen specific PVH code

To: Maran Wilson <maran.wilson@xxxxxxxxxx>, x86@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, pbonzini@xxxxxxxxxx
From: Juergen Gross <jgross@xxxxxxxx>
Date: Tue, 17 Apr 2018 08:29:49 +0200
Cc: rkrcmar@xxxxxxxxxx, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, boris.ostrovsky@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, roger.pau@xxxxxxxxxx
Delivery-date: Tue, 17 Apr 2018 06:30:10 +0000
List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 17/04/18 01:12, Maran Wilson wrote:
> We need to refactor PVH entry code so that support for other hypervisors
> like Qemu/KVM can be added more easily.
> 
> The first step in that direction is to create a new file that will
> eventually hold the Xen specific routines.
> 
> Signed-off-by: Maran Wilson <maran.wilson@xxxxxxxxxx>

Reviewed-by: Juergen Gross <jgross@xxxxxxxx>


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

References:
- [Xen-devel] [PATCH v7 0/7] KVM: x86: Allow Qemu/KVM to use PVH entry point
  - From: Maran Wilson
- [Xen-devel] [PATCH v7 3/7] xen/pvh: Create a new file for Xen specific PVH code
  - From: Maran Wilson

Prev by Date: Re: [Xen-devel] [PATCH v7 2/7] xen/pvh: Move PVH entry code out of Xen specific tree
Next by Date: Re: [Xen-devel] [PATCH v7 6/7] xen/pvh: Add memory map pointer to hvm_start_info struct
Previous by thread: [Xen-devel] [PATCH v7 3/7] xen/pvh: Create a new file for Xen specific PVH code
Next by thread: [Xen-devel] [PATCH v7 5/7] xen/pvh: Move Xen code for getting mem map via hcall out of common file
Index(es):
- Date
- Thread

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