From: Avi Kivity <avi@redhat.com>
To: Tim Pepper <lnxninja@linux.vnet.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org
Subject: Re: [PATCH 0/4 v2] kvm: rework KVM mmu_shrink() code
Date: Sun, 22 Aug 2010 18:29:39 +0300 [thread overview]
Message-ID: <4C714263.8060102@redhat.com> (raw)
In-Reply-To: <20100820011054.GA11297@tpepper-t61p.dolavim.us>
On 08/20/2010 04:10 AM, Tim Pepper wrote:
> The following series is the four patches Dave Hansen had queued for test
> as mentioned last week in the thread:
> "[PATCH] kvm: make mmu_shrink() fit shrinker's requirement"
> Last week just before leaving for vacation Dave had noted in that thread
> that these four were ready to merge based on our perf team's testing
> finally having wrapped up. But it turns out he hadn't actually posted
> them after refactoring in response to comments back in June...
>
> I'm covering for him in his absence and had previously reviewed this set.
> This version contains fixes in response to the comments in June. The
> patches are pulled straight from Dave's development tree, as tested, with
> a minor build/merge change to patch #3 which was otherwise inadvertantly
> re-introducing an (unused) variable that Avi more recently had removed.
>
> Compared to the previous version from June:
> - patch #3 addresses Marcelo's comment about a double deaccounting
> of kvm->arch.n_used_mmu_pages
> - patch #4 includes protection of the used mmu page counts in response to
> Avi's comments
>
> Avi: if Dave's use of a per cpu counter in the refactored patch #4 is
> acceptable to you, then the series is for merging.
>
Applied, thanks for taking care of this.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-22 15:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-20 1:10 [PATCH 0/4 v2] kvm: rework KVM mmu_shrink() code Tim Pepper
2010-08-20 1:10 ` Tim Pepper
2010-08-22 15:29 ` Avi Kivity [this message]
2010-08-23 10:22 ` Avi Kivity
2010-08-23 10:27 ` Avi Kivity
2010-08-23 11:11 ` Xiaotian Feng
2010-08-23 11:28 ` Avi Kivity
2010-08-23 19:53 ` Tim Pepper
2010-08-24 2:07 ` Marcelo Tosatti
2010-08-24 2:31 ` [PATCH -kvm] kvm: fix regression from " Xiaotian Feng
2010-08-24 13:12 ` Marcelo Tosatti
2010-08-24 9:50 ` [PATCH 0/4 v2] kvm: " Xiaotian Feng
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=4C714263.8060102@redhat.com \
--to=avi@redhat.com \
--cc=dave@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lnxninja@linux.vnet.ibm.com \
--cc=mtosatti@redhat.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.