From: Andi Kleen <andi@firstfloor.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"venkatesh.pallipadi@intel.com" <venkatesh.pallipadi@intel.com>
Subject: Re: [PATCH] x86: Use clflush() instead of wbinvd() whenever possible when changing mapping
Date: Fri, 24 Jul 2009 15:16:49 +0200 [thread overview]
Message-ID: <20090724131649.GC2045@basil.fritz.box> (raw)
In-Reply-To: <4A699784.9020803@vmware.com>
> No. It was motivated by the assumption that wbinvd() is just bad:
Ok, got it now.
> Qoute:
>
> WBINVD is a very nasty operation. I was talking to some CPU people and they
> really recommended to get rid of it as far as possible. Stopping the CPU
> for msecs is just wrong and there are apparently even some theoretical live
> lock situations. - It is not interruptible in earlier VT versions and
> messes up real time in the hypervisor. Some people were doing KVM on rt
> kernels and had latency spikes from that.
>
>
> /Qoute
> (I believe you wrote that ?)
Yes. That's still true and that's one reason to not use it.
-Andi
next prev parent reply other threads:[~2009-07-24 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-24 7:53 [PATCH] x86: Use clflush() instead of wbinvd() whenever possible when changing mapping Thomas Hellstrom
2009-07-24 10:05 ` Andi Kleen
2009-07-24 10:21 ` Thomas Hellstrom
2009-07-24 10:58 ` Andi Kleen
2009-07-24 11:14 ` Thomas Hellstrom
2009-07-24 13:16 ` Andi Kleen [this message]
2009-07-30 9:07 ` Pavel Machek
2009-08-02 16:22 ` Thomas Hellström
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=20090724131649.GC2045@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=thellstrom@vmware.com \
--cc=venkatesh.pallipadi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox