From: Avi Kivity <avi@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
kvm-devel <kvm@vger.kernel.org>, lguest <lguest@ozlabs.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Lguest] [PATCH] lguest: fix on Intel when KVM loaded (unhandled trap 13)
Date: Tue, 26 May 2009 16:54:25 +0300 [thread overview]
Message-ID: <4A1BF491.1090501@redhat.com> (raw)
In-Reply-To: <20090526123914.1823adae@lxorguk.ukuu.org.uk>
Alan Cox wrote:
> On Tue, 26 May 2009 20:54:41 +0930
> Rusty Russell <rusty@rustcorp.com.au> wrote:
>
>
>> When KVM is loaded, and hence VT set up, the vmcall instruction in an
>> lguest guest causes a #GP, not #UD.
>>
>> Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
>>
>
> Shouldn't that be fixed in KVM ?
>
KVM never saw that VMCALL or #GP.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-05-26 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 11:24 [PATCH] lguest: fix on Intel when KVM loaded (unhandled trap 13) Rusty Russell
2009-05-26 11:39 ` Alan Cox
2009-05-26 13:54 ` Avi Kivity [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=4A1BF491.1090501@redhat.com \
--to=avi@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=kvm@vger.kernel.org \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@linux-foundation.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