linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	Huang Ying <ying.huang@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] Add MCE support to KVM
Date: Mon, 20 Apr 2009 14:20:55 +0200	[thread overview]
Message-ID: <49EC68A7.8080403@redhat.com> (raw)
In-Reply-To: <49EC5C3A.6020108@redhat.com>

On 04/20/09 13:27, Avi Kivity wrote:
> Gerd Hoffmann wrote:
>>>> Well, xenner doesn't do vmcalls, so the page isn't vendor specific.
>>>
>>> Well, for true pv (not pv-on-hvm) it wouldn't use the MSR, would it?
>>
>> Yes, the MSR is used for pv-on-hvm only.
>
> So it isn't relevant for Xenner?

It is.  I still plan to merge xenner into qemu, and also support 
xenstyle pv-on-hvm drivers.

> That said, I'd like to be able to emulate the Xen HVM hypercalls. But in
> any case, they hypercall implementation has to be in the kernel,

No.  With Xenner the xen hypercall emulation code lives in guest address 
space.

> so I
> don't see why the MSR shouldn't be.

I don't care that much, but /me thinks it would be easier to handle in 
userspace ...

> Especially if we need to support
> tricky bits like continuations.

Is there any reason to?  I *think* xen does it for better scheduling 
latency.  But with xen emulation sitting in guest address space we can 
schedule the guest at will anyway.

>> Same MSR, multiple writes (page number in the low bits).
>
> Nasty. The hypervisor has to remember all of the pages, so it can update
> them for live migration.

Xenner doesn't need update-on-migration, so there is no need at all to 
remember this.  At the end of the day it is just memcpy(guest, data, 
PAGESIZE) triggered by wrmsr.

cheers,
   Gerd

  reply	other threads:[~2009-04-20 12:21 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-08  1:53 [PATCH] Add MCE support to KVM Huang Ying
2009-04-09 15:50 ` Avi Kivity
2009-04-10  3:00   ` Huang Ying
2009-04-11 12:04     ` Avi Kivity
2009-04-11 12:19       ` Andi Kleen
2009-04-11 12:25         ` Avi Kivity
2009-04-13  8:26           ` Andi Kleen
2009-04-13  2:41       ` Huang Ying
2009-04-13 13:02         ` Avi Kivity
2009-04-14  2:04           ` Huang Ying
2009-04-14 10:45             ` Avi Kivity
2009-04-15  7:24               ` Huang Ying
2009-04-18 22:17           ` Anthony Liguori
2009-04-19  8:33             ` Avi Kivity
2009-04-20  7:52               ` Gerd Hoffmann
2009-04-20  8:26                 ` Avi Kivity
2009-04-20  8:59                   ` Gerd Hoffmann
2009-04-20  9:05                     ` Avi Kivity
2009-04-20 10:04                       ` Andi Kleen
2009-04-20 11:02                         ` Avi Kivity
2009-04-20 11:23                       ` Gerd Hoffmann
2009-04-20 11:27                         ` Avi Kivity
2009-04-20 12:20                           ` Gerd Hoffmann [this message]
2009-04-20 12:43                             ` Avi Kivity
2009-04-20 13:24                               ` Gerd Hoffmann
2009-04-20 13:45                                 ` Avi Kivity
2009-04-21  9:14                                   ` Xenner design and kvm msr handling Gerd Hoffmann
2009-04-21 10:14                                     ` Avi Kivity
2009-04-21 11:41                                       ` Gerd Hoffmann
2009-04-21 12:27                                         ` Avi Kivity
2009-04-21 12:47                                           ` Gerd Hoffmann
2009-04-21 13:33                                             ` Avi Kivity
2009-04-21 16:00                                               ` Gerd Hoffmann
2009-04-21 16:15                                                 ` Avi Kivity
2009-04-22 10:02                                                   ` Gerd Hoffmann
2009-04-21 16:04               ` [PATCH] Add MCE support to KVM Anthony Liguori
2009-04-21 16:17                 ` Avi Kivity

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=49EC68A7.8080403@redhat.com \
    --to=kraxel@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.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).