From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [V1 PATCH 1/3] pvh: early return from hvm_hap_nested_page_fault
Date: Thu, 27 Feb 2014 18:25:05 -0800 [thread overview]
Message-ID: <20140227182505.160841e8@mantra.us.oracle.com> (raw)
In-Reply-To: <20140227105605.GB53925@deinos.phlegethon.org>
On Thu, 27 Feb 2014 11:56:05 +0100
Tim Deegan <tim@xen.org> wrote:
> At 17:03 -0800 on 24 Feb (1393257835), Mukesh Rathor wrote:
> > pvh does not support nested hvm at present. As such, return if pvh.
>
> Nack, sorry.
>
> 1: this is the nested pagefault (i.e. EPT/NPT) handler, not part of
> the nested HVM code.
yeah, jan already pointed that out. i just quickly whipped it out last
minute after seeing a crash in hvm_hap_nested_page_fault from running
xentrace on pvh. anyways, i'll take a look at it.
> 2: If there _is_ a problem with the interaction between nested HVM and
> PVH, the right way to fix it is to enforce that they can't both be
> enabled at the same time, and then make sure all the nested-HVM code
> properly checks for being enabled. It's not a good idea to scatter
> PVH checks all over code for unrelated features.
Yup. thanks.
Mueksh
>
> > Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com>
> > ---
> > xen/arch/x86/hvm/hvm.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> > index 69f7e74..a4a3dcf 100644
> > --- a/xen/arch/x86/hvm/hvm.c
> > +++ b/xen/arch/x86/hvm/hvm.c
> > @@ -1416,6 +1416,9 @@ int hvm_hap_nested_page_fault(paddr_t gpa,
> > int sharing_enomem = 0;
> > mem_event_request_t *req_ptr = NULL;
> >
> > + if ( is_pvh_vcpu(v) )
> > + return 0;
> > +
> > /* On Nested Virtualization, walk the guest page table.
> > * If this succeeds, all is fine.
> > * If this fails, inject a nested page fault into the guest.
> > --
> > 1.8.3.1
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-02-28 2:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 1:03 [V1 PATCH 0/3] pvh: misc bug fixes Mukesh Rathor
2014-02-25 1:03 ` [V1 PATCH 1/3] pvh: early return from hvm_hap_nested_page_fault Mukesh Rathor
2014-02-25 1:03 ` [V1 PATCH 2/3] pvh: fix pirq path for pvh Mukesh Rathor
2014-02-25 1:03 ` [V1 PATCH 3/3] pvh: disallow PHYSDEVOP_pirq_eoi_gmfn_v2/v1 Mukesh Rathor
[not found] ` <530C7362020000780011F0F0@nat28.tlf.novell.com>
[not found] ` <530C7663020000780011F104@nat28.tlf.novell.com>
[not found] ` <20140225152514.GA4322@konrad-lan.dumpdata.com>
[not found] ` <530CD069020000780011F3D1@nat28.tlf.novell.com>
[not found] ` <20140225123314.334b7fec@mantra.us.oracle.com>
[not found] ` <530DC4A6020000780011F6C0@nat28.tlf.novell.com>
[not found] ` <20140227190649.47d4eb7a@mantra.us.oracle.com>
[not found] ` <5310524802000078001201B8@nat28.tlf.novell.com>
2014-03-03 12:30 ` George Dunlap
2014-03-04 7:44 ` Jan Beulich
2014-02-25 9:28 ` [V1 PATCH 2/3] pvh: fix pirq path for pvh Jan Beulich
2014-02-25 20:44 ` Mukesh Rathor
2014-02-26 9:44 ` Jan Beulich
2014-02-25 9:26 ` [V1 PATCH 1/3] pvh: early return from hvm_hap_nested_page_fault Jan Beulich
2014-02-27 10:56 ` Tim Deegan
2014-02-28 2:25 ` Mukesh Rathor [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=20140227182505.160841e8@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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).