From: Peter Zijlstra <peterz@infradead.org>
To: Avi Kivity <avi@redhat.com>
Cc: Srivatsa Vaddagiri <vatsa.ml@gmail.com>,
"Zhang, Xiantao" <xiantao.zhang@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
"Yang, Xiaowei" <xiaowei.yang@intel.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
"Li, Xin" <xin.li@intel.com>, Ingo Molnar <mingo@elte.hu>,
Mike Galbraith <efault@gmx.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
vatsa@linux.vnet.ibm.com
Subject: Re: VM performance issue in KVM guests.
Date: Thu, 15 Apr 2010 15:33:18 +0200 [thread overview]
Message-ID: <1271338398.1674.13.camel@laptop> (raw)
In-Reply-To: <4BC6CBE3.8020207@redhat.com>
On Thu, 2010-04-15 at 11:18 +0300, Avi Kivity wrote:
>
> Certainly that has even greater potential for Linux guests. Note that
> we spin on mutexes now, so we need to prevent preemption while the lock
> owner is running.
either that, or disable spinning on (para) virt kernels. Para virt
kernels could possibly extend the thing by also checking to see if the
owner's vcpu is running.
next prev parent reply other threads:[~2010-04-15 13:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EB8593BCECAB3D40A8248BE0B6400A3846903F4C@shzsmsx502.ccr.corp.intel.com>
2010-04-10 19:27 ` VM performance issue in KVM guests Avi Kivity
2010-04-12 2:04 ` Zhang, Xiantao
2010-04-12 6:40 ` Avi Kivity
2010-04-13 0:50 ` Zhang, Xiantao
2010-04-13 6:46 ` Avi Kivity
2010-04-14 3:24 ` Zhang, Xiantao
2010-04-14 8:14 ` Avi Kivity
2010-04-16 2:27 ` Zhang, Xiantao
2010-04-17 19:02 ` Avi Kivity
[not found] ` <p2o2eae271004142158xaa5da968ueff0c2afe6894f9d@mail.gmail.com>
2010-04-15 8:18 ` Avi Kivity
2010-04-15 13:33 ` Peter Zijlstra [this message]
2010-04-15 16:43 ` Srivatsa Vaddagiri
2010-04-16 10:40 ` Peter Zijlstra
2010-04-19 1:32 ` Zhang, Xiantao
2010-04-17 19:04 ` Avi Kivity
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=1271338398.1674.13.camel@laptop \
--to=peterz@infradead.org \
--cc=avi@redhat.com \
--cc=eddie.dong@intel.com \
--cc=efault@gmx.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=vatsa.ml@gmail.com \
--cc=vatsa@linux.vnet.ibm.com \
--cc=xiantao.zhang@intel.com \
--cc=xiaowei.yang@intel.com \
--cc=xin.li@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