From: Jan Kiszka <jan.kiszka-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Carsten Emde
<Carsten.Emde-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: 2.6.23.1-rt4 and kvm 48
Date: Tue, 30 Oct 2007 12:34:25 +0100 [thread overview]
Message-ID: <472716C1.1090102@siemens.com> (raw)
In-Reply-To: <47271057.5040102-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
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.
> I hope that Intel will add similar traps in future
> iterations of VT.
Yep.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-30 11:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 14:09 2.6.23.1-rt4 and kvm 48 David Brown
[not found] ` <9c21eeae0710290709x527cf4fcq52bb410907ff496-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-10-30 4:18 ` Avi Kivity
[not found] ` <4726B088.1010709-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-30 7:38 ` Carsten Emde
[not found] ` <4726DF66.4000000-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-10-30 9:49 ` Jan Kiszka
[not found] ` <4726FE2A.1040607-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org>
2007-10-30 10:02 ` Alexander Graf
2007-10-30 11:07 ` Avi Kivity
[not found] ` <47271057.5040102-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-30 11:34 ` Jan Kiszka [this message]
2007-10-30 11:37 ` [kvm-devel] " Avi Kivity
2007-11-01 9:28 ` Dor Laor
[not found] ` <47299C43.1070703-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-05 20:27 ` Carsten Emde
[not found] ` <472F7CA7.8060707-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-11-06 5:22 ` David Brown
[not found] ` <9c21eeae0711052122y483b06d8ycbcfbfb95fb36663-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-11-06 8:12 ` Dor Laor
[not found] ` <47302208.2090301-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-06 9:53 ` Carsten Emde
[not found] ` <473039B2.1010106-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org>
2007-11-06 14:53 ` David Brown
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=472716C1.1090102@siemens.com \
--to=jan.kiszka-kv7wefo6altbdgjk7y7tuq@public.gmane.org \
--cc=Carsten.Emde-Q945KHDl0DbYtjvyW6yDsg@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.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