From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@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: Xenner design and kvm msr handling
Date: Tue, 21 Apr 2009 19:15:45 +0300 [thread overview]
Message-ID: <49EDF131.9060705@redhat.com> (raw)
In-Reply-To: <49EDEDAD.20900@redhat.com>
Gerd Hoffmann wrote:
> On 04/21/09 15:33, Avi Kivity wrote:
>> Gerd Hoffmann wrote:
>>> Not sure, have to dig into the xen code to figure.
>>>
>>> Could be xen doesn't remember the page in the first place. They might
>>> let the illegal instruction fault handler patch the opcode. At least I
>>> vaguely remember some discussions about that.
>
> Xen does a simple msr-triggered memcpy() as well, without keeping
> track of the page. On a quick glimpse I can't find a opcode patching
> place either. Hmm.
>
Maybe migration is cooperative, that is the host tells the guest it is
migrated, so it can re-register the hypercall area?
--
error compiling committee.c: too many arguments to function
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@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: Xenner design and kvm msr handling
Date: Tue, 21 Apr 2009 19:15:45 +0300 [thread overview]
Message-ID: <49EDF131.9060705@redhat.com> (raw)
In-Reply-To: <49EDEDAD.20900@redhat.com>
Gerd Hoffmann wrote:
> On 04/21/09 15:33, Avi Kivity wrote:
>> Gerd Hoffmann wrote:
>>> Not sure, have to dig into the xen code to figure.
>>>
>>> Could be xen doesn't remember the page in the first place. They might
>>> let the illegal instruction fault handler patch the opcode. At least I
>>> vaguely remember some discussions about that.
>
> Xen does a simple msr-triggered memcpy() as well, without keeping
> track of the page. On a quick glimpse I can't find a opcode patching
> place either. Hmm.
>
Maybe migration is cooperative, that is the host tells the guest it is
migrated, so it can re-register the hypercall area?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-04-21 16:16 UTC|newest]
Thread overview: 39+ 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
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 [this message]
2009-04-21 16:15 ` Avi Kivity
2009-04-22 10:02 ` Gerd Hoffmann
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=49EDF131.9060705@redhat.com \
--to=avi@redhat.com \
--cc=andi@firstfloor.org \
--cc=anthony@codemonkey.ws \
--cc=kraxel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.