From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Jan Beulich" <JBeulich@novell.com>
Subject: Re: [PATCH 12/12] Nested Virtualization:
	 hap-on-hap
Date: Fri, 29 Apr 2011 10:03:28 +0100
Message-ID: <4DBA9B00020000780003EDAA@vpn.id2.novell.com>
References: <201103091531.04219.Christoph.Egger@amd.com>
	<201103311725.13871.Christoph.Egger@amd.com> <4D9B39BA.8090807@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <4D9B39BA.8090807@amd.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Tim Deegan <Tim.Deegan@citrix.com>
List-Id: xen-devel@lists.xenproject.org

>>> On 05.04.11 at 17:48, Christoph Egger <Christoph.Egger@amd.com> wrote:
>diff -r cfde4384be14 -r 28809c365861 xen/include/asm-x86/domain.h
>--- a/xen/include/asm-x86/domain.h
>+++ b/xen/include/asm-x86/domain.h
>...
>@@ -225,6 +227,7 @@ struct paging_vcpu {
> #define MAX_CPUID_INPUT 40
> typedef xen_domctl_cpuid_t cpuid_input_t;
>=20
>+#define MAX_NESTEDP2M 10
> struct p2m_domain;
> struct time_scale {
>     int shift;
>@@ -258,6 +261,12 @@ struct arch_domain
>     struct paging_domain paging;
>     struct p2m_domain *p2m;
>=20
>+    /* nestedhvm: translate l2 guest physical to host physical */
>+    struct p2m_domain *nested_p2m[MAX_NESTEDP2M];
>+    spinlock_t nested_p2m_lock;
>+    int nested_p2m_locker;
>+    const char *nested_p2m_function;
>+
>     /* NB. protected by d->event_lock and by irq_desc[irq].lock */
>     int *irq_pirq;
>     int *pirq_irq;

Was there a specific reason to add this to struct arch_domain
instead of struct hvm_domain? I.e. can any pf these fields be
used on pv (or idle) domains?

Thanks, Jan