public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Eric Northup <digitaleric@google.com>, KVM <kvm@vger.kernel.org>
Subject: Re: [RFC] KVM MMU: improve large munmap efficiency
Date: Sun, 29 Jan 2012 22:22:50 +0900	[thread overview]
Message-ID: <20120129222250.c69609adad5dd196cda91575@gmail.com> (raw)
In-Reply-To: <4F2526FE.8040603@redhat.com>

On Sun, 29 Jan 2012 13:01:18 +0200
Avi Kivity <avi@redhat.com> wrote:

> > Tested by attaching a debugger to a running qemu w/kvm and running
> > "call munmap(0, 1UL << 46)".
> >
> 
> How about computing the intersection of (start, end) with the hva ranges
> in kvm->memslots?
> 
> If there is no intersection, you exit immediately.

I think introducing kvm_handle_hva_range() is the right thing if we really
care about unmapping large area at once.

Current iteration:
for each page
	for each slot
		for each level

My suggestion:
for each slot
	for each level
		for each page

This way compiler can optimize the task to be a simple iteration over the
rmap array.

But I could not imagine why unmapping 128GB is needed.
mmu_notifier will not do such crazy thing.

	Takuya

> 
> It's still possible for the work to drop the intersection to be larger
> than dropping the entire shadow, but it's unlikely.

  reply	other threads:[~2012-01-29 13:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26 23:24 [RFC] KVM MMU: improve large munmap efficiency Eric Northup
2012-01-27  0:59 ` Takuya Yoshikawa
2012-01-27  1:13   ` Takuya Yoshikawa
2012-01-29 11:01 ` Avi Kivity
2012-01-29 13:22   ` Takuya Yoshikawa [this message]
2012-01-29 13:25     ` Avi Kivity
2012-01-29 13:50       ` Takuya Yoshikawa

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=20120129222250.c69609adad5dd196cda91575@gmail.com \
    --to=takuya.yoshikawa@gmail.com \
    --cc=avi@redhat.com \
    --cc=digitaleric@google.com \
    --cc=kvm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox