From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: mmu notifier calls in apply_to_page_range()
Date: Fri, 09 Jul 2010 10:41:51 -0700 [thread overview]
Message-ID: <4C375F5F.5000907@goop.org> (raw)
In-Reply-To: <20100709173612.GF5741@random.random>
On 07/09/2010 10:36 AM, Andrea Arcangeli wrote:
> I'm not opposed to removing it, I've been wondering if it made any
> sense in the first place but then there was no point not to add
> it. Just calling apply_to_page_range in non blocking context doesn't
> look so good.
>
That's a good point. It should be safe if the pagetable is already
fully populated; I should double-check that's true in our case.
J
next prev parent reply other threads:[~2010-07-09 17:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 15:06 mmu notifier calls in apply_to_page_range() Jeremy Fitzhardinge
2010-07-09 15:12 ` Andrea Arcangeli
2010-07-09 15:51 ` Jeremy Fitzhardinge
2010-07-09 16:22 ` Andrea Arcangeli
2010-07-09 17:30 ` Jeremy Fitzhardinge
2010-07-09 17:36 ` Andrea Arcangeli
2010-07-09 17:41 ` Jeremy Fitzhardinge [this message]
2010-07-09 18:31 ` Andrea Arcangeli
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=4C375F5F.5000907@goop.org \
--to=jeremy@goop.org \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.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