From: Marcelo Tosatti <mtosatti@redhat.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: gleb@redhat.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, xiaoguangrong@linux.vnet.ibm.com
Subject: Re: [PATCH v2] kvm: Fix user memslot overlap check
Date: Fri, 30 Nov 2012 18:18:59 -0200 [thread overview]
Message-ID: <20121130201858.GB19821@amt.cnet> (raw)
In-Reply-To: <20121129210725.9364.72668.stgit@bling.home>
On Thu, Nov 29, 2012 at 02:07:59PM -0700, Alex Williamson wrote:
> Prior to memory slot sorting this loop compared all of the user memory
> slots for overlap with new entries. With memory slot sorting, we're
> just checking some number of entries in the array that may or may not
> be user slots. Instead, walk all the slots with kvm_for_each_memslot,
> which has the added benefit of terminating early when we hit the first
> empty slot, and skip comparison to private slots.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> Cc: stable@vger.kernel.org
Applied, thanks.
prev parent reply other threads:[~2012-11-30 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 21:07 [PATCH v2] kvm: Fix user memslot overlap check Alex Williamson
2012-11-30 20:18 ` Marcelo Tosatti [this message]
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=20121130201858.GB19821@amt.cnet \
--to=mtosatti@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiaoguangrong@linux.vnet.ibm.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