All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Gregory Haskins <gregory.haskins@gmail.com>,
	kvm-devel <kvm@vger.kernel.org>,
	RT <linux-rt-users@vger.kernel.org>,
	"Yang, Sheng" <sheng.yang@intel.com>
Subject: Re: Host latency peaks due to kvm-intel
Date: Sat, 25 Jul 2009 17:52:05 +0300	[thread overview]
Message-ID: <4A6B1C15.6090608@redhat.com> (raw)
In-Reply-To: <4A6981B0.3000008@siemens.com>

On 07/24/2009 12:41 PM, Jan Kiszka wrote:
> Jan (who is now patching his guest to avoid wbinvd where possible)
>
>    

Is there ever a case where it is required?  What about under a 
hypervisor (i.e. check the hypervisor enabled bit).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  parent reply	other threads:[~2009-07-25 14:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 18:07 Host latency peaks due to kvm-intel Jan Kiszka
2009-07-23 19:43 ` Gregory Haskins
2009-07-24  9:41   ` Jan Kiszka
2009-07-24 12:01     ` Gregory Haskins
2009-07-25  8:15     ` Avi Kivity
2009-07-25  9:55       ` Jan Kiszka
2009-07-25 13:27         ` Avi Kivity
2009-07-26 14:23           ` Jan Kiszka
2009-07-26 19:16         ` H. Peter Anvin
2009-07-27  1:11           ` Yang, Sheng
2009-07-27  9:08             ` cpuinfo and HVM features (was: Host latency peaks due to kvm-intel) Jan Kiszka
2009-07-27  9:29               ` Yang, Sheng
2009-07-27 10:31               ` cpuinfo and HVM features Avi Kivity
2009-07-25 14:52     ` Avi Kivity [this message]
2009-07-26 10:34       ` Host latency peaks due to kvm-intel Sujit Karataparambil
2009-07-26 14:34       ` Jan Kiszka
2009-07-26 14:45         ` Avi Kivity
2009-07-26 14:52           ` Jan Kiszka

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=4A6B1C15.6090608@redhat.com \
    --to=avi@redhat.com \
    --cc=gregory.haskins@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sheng.yang@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.