xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Keir Fraser <keir@xen.org>, George Dunlap <dunlapg@umich.edu>,
	Tim Deegan <tim@xen.org>, Jan Beulich <jbeulich@suse.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH RFC] x86/hvm: unify HVM and PVH hypercall tables.
Date: Thu, 15 May 2014 16:35:57 -0700	[thread overview]
Message-ID: <20140515163557.70c821e8@mantra.us.oracle.com> (raw)
In-Reply-To: <201405151432.s4FEWZZd010054@aserz7022.oracle.com>

On Thu, 15 May 2014 10:32:24 -0400
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:

> 
> On May 15, 2014 6:30 AM, Tim Deegan <tim@xen.org> wrote:
> >
> > At 14:39 -0400 on 08 May (1399556383), Konrad Rzeszutek Wilk wrote: 
> > > On Thu, May 08, 2014 at 04:31:30PM +0100, Tim Deegan wrote: 
> > > > Stage one of many in merging PVH and HVM code in the
> > > > hypervisor. 
> > > > 
> > > > This exposes a few new hypercalls to HVM guests, all of which
> > > > were already available to PVH ones: 
> > > > 
> > > >  - XENMEM_memory_map / XENMEM_machine_memory_map /
> > > >XENMEM_machphys_mapping: These are basically harmless, if a bit
> > > >useless to plain HVM. 
> > > > 
> > > >  - VCPUOP_send_nmi / VCPUOP_initialise / VCPUOP[_is]_up /
> > > >VCPUOP_down This will eventually let HVM guests bring up APs the
> > > >way PVH ones do. For now, the VCPUOP_initialise paths are still
> > > >gated on is_pvh. 
> > > 
> > > I had a similar patch to enable this under HVM and found out that 
> > > if the guest issues VCPUOP_send_nmi we get in Linux: 
> > > 
> > > [    3.611742] Corrupted low memory at c000fffc (fffc phys) =
> > > 00029b00 [    2.386785] Corrupted low memory at ffff88000000fff8
> > > (fff8 phys) = 2990000000000 
> > > 
> > > http://mid.gmane.org/20140422183443.GA6817@phenom.dumpdata.com 
> >
> > Right, thanks.  Do you think that's likely to be a hypervisor bug,
> > or just a "don't do that then"?
> 
> It is a bug. But I don't know where and had not had a chance to
> investigate this further.
> 
> My feeling is that it is APIC emulation but I might be quite off.
> >
> > AFAICT PVH domains need this as they have no other way of sending 
> > NMIs. 
> >
> 
> Perhaps. The vAPIC that Boris had been looking at could make this
> work via the APIC path.

But, VCPUOP_send_nmi works for PVH right, and only HVM has problem?

mukesh


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

  reply	other threads:[~2014-05-15 23:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-15 14:32 [PATCH RFC] x86/hvm: unify HVM and PVH hypercall tables Konrad Rzeszutek Wilk
2014-05-15 23:35 ` Mukesh Rathor [this message]
2014-05-16 12:45   ` Konrad Rzeszutek Wilk
  -- strict thread matches above, loose matches on Subject: below --
2014-05-08 15:31 Tim Deegan
2014-05-08 16:53 ` George Dunlap
2014-05-15 10:25   ` Tim Deegan
2014-05-08 18:39 ` Konrad Rzeszutek Wilk
2014-05-15 10:30   ` Tim Deegan
2014-05-15 11:58     ` Jan Beulich
2014-05-09  8:08 ` Jan Beulich
2014-05-15 10:34   ` Tim Deegan
2014-05-16  0:19     ` Mukesh Rathor

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=20140515163557.70c821e8@mantra.us.oracle.com \
    --to=mukesh.rathor@oracle.com \
    --cc=dunlapg@umich.edu \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --cc=konrad.wilk@oracle.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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).