From: Avi Kivity <avi@qumranet.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm-devel@lists.sourceforge.net,
Carsten Emde <Carsten.Emde@osadl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] 2.6.23.1-rt4 and kvm 48
Date: Tue, 30 Oct 2007 13:37:51 +0200 [thread overview]
Message-ID: <4727178F.8040005@qumranet.com> (raw)
In-Reply-To: <472716C1.1090102@siemens.com>
Jan Kiszka wrote:
> Avi Kivity wrote:
>
>> Jan Kiszka wrote:
>>
>>> Interesting result - you've read about the wbinvd issues? Is there no
>>> wbinvd in the bios shipped with older kvm? Which VM extension did you
>>> test, both Intel and AMD? I would bet that your X issues are due to the
>>> same effect. X startup/shutdown involves a lot of wbinvd calls on my
>>> test boxes.
>>>
>>>
>>>
>> kvm.git now traps invd and wbinvd on amd, so there shouldn't be any
>> issues there.
>>
>
> So kvm can then simply ignore the instructions, or what does it do about
> them? I recall some replies in the related thread that some more work
> may be required.
>
>
It currently ignores the instructions. When device passthrough is
implemented more work will be needed.
--
Any sufficiently difficult bug is indistinguishable from a feature.
next prev parent reply other threads:[~2007-10-30 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:09 2.6.23.1-rt4 and kvm 48 David Brown
2007-10-30 4:18 ` [kvm-devel] " Avi Kivity
2007-10-30 7:38 ` Carsten Emde
2007-10-30 9:49 ` Jan Kiszka
2007-10-30 10:02 ` Alexander Graf
2007-10-30 11:07 ` Avi Kivity
2007-10-30 11:34 ` Jan Kiszka
2007-10-30 11:37 ` Avi Kivity [this message]
2007-11-01 9:28 ` Dor Laor
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=4727178F.8040005@qumranet.com \
--to=avi@qumranet.com \
--cc=Carsten.Emde@osadl.org \
--cc=jan.kiszka@siemens.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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