public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: kvm@vger.kernel.org
Subject: Re: KVM crash on unusual PM->RM transition
Date: Tue, 14 Apr 2009 19:07:22 +0300	[thread overview]
Message-ID: <49E4B4BA.8010801@redhat.com> (raw)
In-Reply-To: <49E4B046.5040008@zytor.com>

H. Peter Anvin wrote:
> Any reason to not make use of Qemu in userspace, rather than relying on
> the in-kernel interpreter for these?  The kernel interpreter is
> obviously The Right Thing to avoid frequent ping-pong into the kernel,
> but it seems to me that such a potential "long-term" situation might be
> better handled by Qemu?
>   

It's a faq; there are multiple reasons:

- it would make the kernel/user interface complicated; right now the 
model is "kvm emulates the cpu and optionally lapic, ioapic, and pit'; 
that would change to "kvm sometimes emulates the cpu, but sometimes 
doesn't".  We'd need to add a description of when userspace can jump 
back into the kernel (AMD for example is perfectly happy in real mode).

- it would require a way for userspace to access the in-kernel 
lapic/ioapic/pit, and for these components to inject interrupts into 
userspace.

- it requires anyone using kvm to implement a complete x86 emulator.

- qemu doesn't do smp.

with emulate_invalid_guest_space we're actually pretty close to running 
big real mode; but no one's working on it so it's stagnated.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  reply	other threads:[~2009-04-14 16:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 23:42 KVM crash on unusual PM->RM transition H. Peter Anvin
2009-04-14  5:42 ` H. Peter Anvin
2009-04-14  8:14   ` Avi Kivity
2009-04-14 15:48     ` H. Peter Anvin
2009-04-14 16:07       ` Avi Kivity [this message]
2009-04-14 16:10         ` H. Peter Anvin
2009-04-14 16:16           ` Avi Kivity
2009-04-14 16:17             ` H. Peter Anvin

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=49E4B4BA.8010801@redhat.com \
    --to=avi@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.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