All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ia64@vger.kernel.org
Subject: Re: [00/03][PATCH] kvm-ia64 updates for linux-2.6.28-rc2
Date: Thu, 30 Oct 2008 09:36:21 +0000	[thread overview]
Message-ID: <49098015.4000901@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC2140C7FE4@pdsmsx503.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> 	It is a potential issue. If the vcpu goes to halt with the lock taken, other vcpus wants to take write lock, they have to wait until the all halted vcpus are waken up, so  it may impact performance.  :)

What is the impact?  Taking slots_lock for write is very rare.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: "Zhang, Xiantao" <xiantao.zhang@intel.com>
Cc: "kvm-ia64@vger.kernel.org" <kvm-ia64@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [00/03][PATCH] kvm-ia64 updates for linux-2.6.28-rc2
Date: Thu, 30 Oct 2008 11:36:21 +0200	[thread overview]
Message-ID: <49098015.4000901@redhat.com> (raw)
In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC2140C8363@pdsmsx503.ccr.corp.intel.com>

Zhang, Xiantao wrote:
> 	It is a potential issue. If the vcpu goes to halt with the lock taken, other vcpus wants to take write lock, they have to wait until the all halted vcpus are waken up, so  it may impact performance.  :)

What is the impact?  Taking slots_lock for write is very rare.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.


  parent reply	other threads:[~2008-10-30  9:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  4:39 [00/03][PATCH] kvm-ia64 updates for linux-2.6.28-rc2 Zhang, Xiantao
2008-10-29  4:39 ` Zhang, Xiantao
2008-10-29 14:27 ` Avi Kivity
2008-10-29 14:27   ` Avi Kivity
2008-10-29 14:33 ` Jes Sorensen
2008-10-29 14:33   ` Jes Sorensen
2008-10-29 14:45 ` Avi Kivity
2008-10-29 14:45   ` Avi Kivity
2008-10-29 14:51 ` Jes Sorensen
2008-10-29 14:51   ` Jes Sorensen
2008-10-30  1:05 ` Zhang, Xiantao
2008-10-30  1:05   ` Zhang, Xiantao
2008-10-30  9:36 ` Avi Kivity [this message]
2008-10-30  9:36   ` Avi Kivity
2008-10-30 10:16 ` Zhang, Xiantao
2008-10-30 10:16   ` Zhang, Xiantao

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=49098015.4000901@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ia64@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 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.