From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: Re: [RFC PATCH 0/8]: PVH : PV guest in HVM container
Date: Thu, 16 Aug 2012 10:42:49 -0400 [thread overview]
Message-ID: <20120816144249.GA17735@phenom.dumpdata.com> (raw)
In-Reply-To: <20120815175224.36457451@mantra.us.oracle.com>
On Wed, Aug 15, 2012 at 05:52:24PM -0700, Mukesh Rathor wrote:
> Hi,
>
> Following are series of patches for PVH linux changes. xen
> patches will follow later.
>
> A PVH is a PV guest that runs in an HVM container. Its only available
> for x86_64 only. It runs in ring 0 (the kernel), has native page tables,
> native IDT, and requires HAP. It uses lot of HVM code paths. Both in
> the guest and xen, the guest is viewed as pv guest, and is_hvm()
> would return false. It uses event channels thereby eliminating APIC
> emulation code paths in xen.
>
> This series of patches implment this feature. They were built on
> top of fc6bdb59a501740b28ed3b616641a22c8dc5dd31 from the following
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
Neat. I like the patches. The one thing that you might also want to expose so
is something like this:
diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kconfig
index fdce49c..cd60024 100644
--- a/arch/x86/xen/Kconfig
+++ b/arch/x86/xen/Kconfig
@@ -27,6 +27,13 @@ config XEN_PVHVM
def_bool y
depends on XEN && PCI && X86_LOCAL_APIC
+config XEN_PVH
+ def_bool n
+ depends on XEN_DOM0 && SPECIAL_PTE?
+ help
+ Run initial domain in a HVM container. The hypervisor
+ must have the extensions.. blah blah.
+
config XEN_MAX_DOMAIN_MEMORY
int
default 500 if X86_64
diff --git a/include/xen/xen.h b/include/xen/xen.h
index e823639..0317a36 100644
--- a/include/xen/xen.h
+++ b/include/xen/xen.h
@@ -20,9 +20,12 @@ extern enum xen_domain_type xen_domain_type;
xen_domain_type == XEN_HVM_DOMAIN)
/* xen_pv_domain check is necessary as start_info ptr is null in HVM. Also,
* note, xen PVH domain shares lot of HVM code */
+#ifdef CONFIG_XEN_PVH
#define xen_pvh_domain() (xen_pv_domain() && \
(xen_start_info->flags & SIF_IS_PVINHVM))
-
+#else
+#define xen_pvh_domain() (0)
+#endif
#ifdef CONFIG_XEN_DOM0
#include <xen/interface/xen.h>
#include <asm/xen/hypervisor.h>
That way we can work through all the kinks without having to worry
about causing revert issues or adding extra undue config build options.
Better yet, it allows to test all your code in pure PV and HVM to make
sure nothing broke. And when all is ready this can be removed.
>
>
> Thanks,
> Mukesh
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-08-16 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 0:52 [RFC PATCH 0/8]: PVH : PV guest in HVM container Mukesh Rathor
2012-08-16 14:42 ` Konrad Rzeszutek Wilk [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120816144249.GA17735@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Xen-devel@lists.xensource.com \
--cc=mukesh.rathor@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).