From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: kvm@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Marcelo Tosatti <mtosatti@redhat.com>,
Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH v3 1/2] KVM: MMIO: Lock coalesced device when checking for available entry
Date: Mon, 18 Jul 2011 17:24:53 +0300 [thread overview]
Message-ID: <4E244235.8@redhat.com> (raw)
In-Reply-To: <1310998635-31608-1-git-send-email-levinsasha928@gmail.com>
On 07/18/2011 05:17 PM, Sasha Levin wrote:
> Move the check whether there are available entries to within the spinlock.
> This allows working with larger amount of VCPUs and reduces premature
> exits when using a large number of VCPUs.
Looks good, with the fixed kvm@ address too.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-18 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 14:17 [PATCH v3 1/2] KVM: MMIO: Lock coalesced device when checking for available entry Sasha Levin
2011-07-18 14:17 ` [PATCH v3 2/2] x86: Raise the hard VCPU count limit Sasha Levin
2011-07-18 14:24 ` Avi Kivity [this message]
2011-07-19 16:02 ` [PATCH v3 1/2] KVM: MMIO: Lock coalesced device when checking for available entry Marcelo Tosatti
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=4E244235.8@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=penberg@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.