public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@qumranet.com>
To: Arn <cse.syslab@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: Query on mmu-notifiers
Date: Tue, 22 Jul 2008 17:27:14 +0200	[thread overview]
Message-ID: <20080722152714.GT13826@duo.random> (raw)
In-Reply-To: <896ae46a0807151700u51977601l33089b3f164de868@mail.gmail.com>

Sorry for the late reply I was on vacation last week.

On Tue, Jul 15, 2008 at 08:00:57PM -0400, Arn wrote:
> Hi,
> 
> The recent 2.6.26 release didn't say anything about mmu-notifiers. My
> impression was that it will be going to be included
> in that release. Where can I download and try it out, what host/guest

Yes, it should be included any moment in 2.6.27-rc, Andrew should be
taking care of it, crossing fingers here...

> kernel should I use and are there any current issues/bugs ?

You can use 2.6.25/6 plus these three patches applied in order:

       http://kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.26-rc7/mmu-notifier-v18/list_del_init_rcu
       http://kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.26-rc7/mmu-notifier-v18/mm_take_all_locks
       http://kernel.org/pub/linux/kernel/people/andrea/patches/v2.6/2.6.26-rc7/mmu-notifier-v18/mmu-notifier-core

I posted the latest kvm-mmu-notifier patch on this list a few days
before your question, that has to be applied to kvm.git. That's all.

With the last patch I posted there are two issues pointed out by
Marcelo, with largepages and with aliases but you won't risk to
notice, I'm correcting those as I write this.

      reply	other threads:[~2008-07-22 15:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  0:00 Query on mmu-notifiers Arn
2008-07-22 15:27 ` Andrea Arcangeli [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=20080722152714.GT13826@duo.random \
    --to=andrea@qumranet.com \
    --cc=cse.syslab@gmail.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