From: Andrea Arcangeli <andrea@qumranet.com>
To: Robin Holt <holt@sgi.com>
Cc: Christoph Lameter <clameter@sgi.com>,
Avi Kivity <avi@qumranet.com>, Izik Eidus <izike@qumranet.com>,
kvm-devel@lists.sourceforge.net,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
steiner@sgi.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, daniel.blueman@quadrics.com
Subject: Re: [patch 2/4] mmu_notifier: Callbacks to invalidate address ranges
Date: Sun, 3 Feb 2008 03:23:56 +0100 [thread overview]
Message-ID: <20080203022356.GD7185@v2.random> (raw)
In-Reply-To: <20080201233528.GE12099@sgi.com>
On Fri, Feb 01, 2008 at 05:35:28PM -0600, Robin Holt wrote:
> No, we need a callout when we are becoming more restrictive, but not
> when becoming more permissive. I would have to guess that is the case
> for any of these callouts. It is for both GRU and XPMEM. I would
> expect the same is true for KVM, but would like a ruling from Andrea on
> that.
I still hope I don't need to take any lock in _range_start and that
losing coherency (w/o risking global memory corruption but only
risking temporary userland data corruption thanks to the page pin) is
ok for KVM.
If I would have to take a lock in _range_start like XPMEM is forced to
do (GRU is by far not forced to it, if it would switch to my #v5) then
it would be a problem.
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <andrea-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Robin Holt <holt-sJ/iWh9BUns@public.gmane.org>
Cc: Peter Zijlstra
<a.p.zijlstra-/NLkJaSkS4VmR6Xm/wNWPw@public.gmane.org>,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
steiner-sJ/iWh9BUns@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>,
kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
daniel.blueman-xqY44rlHlBpWk0Htik3J/w@public.gmane.org,
Christoph Lameter <clameter-sJ/iWh9BUns@public.gmane.org>
Subject: Re: [patch 2/4] mmu_notifier: Callbacks to invalidate address ranges
Date: Sun, 3 Feb 2008 03:23:56 +0100 [thread overview]
Message-ID: <20080203022356.GD7185@v2.random> (raw)
In-Reply-To: <20080201233528.GE12099-sJ/iWh9BUns@public.gmane.org>
On Fri, Feb 01, 2008 at 05:35:28PM -0600, Robin Holt wrote:
> No, we need a callout when we are becoming more restrictive, but not
> when becoming more permissive. I would have to guess that is the case
> for any of these callouts. It is for both GRU and XPMEM. I would
> expect the same is true for KVM, but would like a ruling from Andrea on
> that.
I still hope I don't need to take any lock in _range_start and that
losing coherency (w/o risking global memory corruption but only
risking temporary userland data corruption thanks to the page pin) is
ok for KVM.
If I would have to take a lock in _range_start like XPMEM is forced to
do (GRU is by far not forced to it, if it would switch to my #v5) then
it would be a problem.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <andrea@qumranet.com>
To: Robin Holt <holt@sgi.com>
Cc: Christoph Lameter <clameter@sgi.com>,
Avi Kivity <avi@qumranet.com>, Izik Eidus <izike@qumranet.com>,
kvm-devel@lists.sourceforge.net,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
steiner@sgi.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, daniel.blueman@quadrics.com
Subject: Re: [patch 2/4] mmu_notifier: Callbacks to invalidate address ranges
Date: Sun, 3 Feb 2008 03:23:56 +0100 [thread overview]
Message-ID: <20080203022356.GD7185@v2.random> (raw)
In-Reply-To: <20080201233528.GE12099@sgi.com>
On Fri, Feb 01, 2008 at 05:35:28PM -0600, Robin Holt wrote:
> No, we need a callout when we are becoming more restrictive, but not
> when becoming more permissive. I would have to guess that is the case
> for any of these callouts. It is for both GRU and XPMEM. I would
> expect the same is true for KVM, but would like a ruling from Andrea on
> that.
I still hope I don't need to take any lock in _range_start and that
losing coherency (w/o risking global memory corruption but only
risking temporary userland data corruption thanks to the page pin) is
ok for KVM.
If I would have to take a lock in _range_start like XPMEM is forced to
do (GRU is by far not forced to it, if it would switch to my #v5) then
it would be a problem.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-02-03 2:24 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 5:04 [patch 0/4] [RFC] EMMU Notifiers V5 Christoph Lameter
2008-02-01 5:04 ` Christoph Lameter
2008-02-01 5:04 ` [patch 1/4] mmu_notifier: Core code Christoph Lameter
2008-02-01 5:04 ` Christoph Lameter
2008-02-01 10:55 ` Robin Holt
2008-02-01 10:55 ` Robin Holt
2008-02-01 10:55 ` Robin Holt
2008-02-01 11:04 ` Robin Holt
2008-02-01 11:04 ` Robin Holt
2008-02-01 19:14 ` Christoph Lameter
2008-02-01 19:14 ` Christoph Lameter
2008-02-01 19:14 ` Christoph Lameter
2008-02-01 5:04 ` [patch 2/4] mmu_notifier: Callbacks to invalidate address ranges Christoph Lameter
2008-02-01 5:04 ` Christoph Lameter
2008-02-01 10:49 ` Robin Holt
2008-02-01 10:49 ` Robin Holt
2008-02-01 10:49 ` Robin Holt
2008-02-01 19:14 ` Christoph Lameter
2008-02-01 19:14 ` Christoph Lameter
2008-02-01 19:14 ` Christoph Lameter
2008-02-01 22:09 ` Robin Holt
2008-02-01 22:09 ` Robin Holt
2008-02-01 23:19 ` Christoph Lameter
2008-02-01 23:19 ` Christoph Lameter
2008-02-01 23:35 ` Robin Holt
2008-02-01 23:35 ` Robin Holt
2008-02-01 23:35 ` Robin Holt
2008-02-02 0:05 ` Christoph Lameter
2008-02-02 0:05 ` Christoph Lameter
2008-02-02 0:05 ` Christoph Lameter
2008-02-02 0:21 ` Robin Holt
2008-02-02 0:21 ` Robin Holt
2008-02-02 0:21 ` Robin Holt
2008-02-02 0:38 ` Robin Holt
2008-02-02 0:38 ` Robin Holt
2008-02-02 0:38 ` Robin Holt
2008-02-03 2:23 ` Andrea Arcangeli [this message]
2008-02-03 2:23 ` Andrea Arcangeli
2008-02-03 2:23 ` Andrea Arcangeli
2008-02-01 5:04 ` [patch 3/4] mmu_notifier: invalidate_page callbacks Christoph Lameter
2008-02-01 5:04 ` Christoph Lameter
2008-02-01 5:04 ` [patch 4/4] mmu_notifier: Support for driverws with revers maps (f.e. for XPmem) Christoph Lameter
2008-02-01 5:04 ` Christoph Lameter
2008-02-01 11:58 ` Extending mmu_notifiers to handle __xip_unmap in a sleepable context? Robin Holt
2008-02-01 11:58 ` Robin Holt
2008-02-01 11:58 ` Robin Holt
2008-02-01 12:10 ` Robin Holt
2008-02-01 12:10 ` Robin Holt
2008-02-01 12:10 ` Robin Holt
2008-02-01 19:17 ` Christoph Lameter
2008-02-01 19:17 ` Christoph Lameter
2008-02-01 19:17 ` Christoph Lameter
2008-02-03 1:39 ` [patch 0/4] [RFC] EMMU Notifiers V5 Andrea Arcangeli
2008-02-03 1:39 ` Andrea Arcangeli
2008-02-03 13:41 ` Robin Holt
2008-02-03 13:41 ` Robin Holt
2008-02-03 13:41 ` Robin Holt
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 5:56 [patch 0/4] [RFC] MMU Notifiers V1 Christoph Lameter
2008-01-25 5:56 ` [patch 2/4] mmu_notifier: Callbacks to invalidate address ranges Christoph Lameter
2008-01-25 5:56 ` Christoph Lameter
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=20080203022356.GD7185@v2.random \
--to=andrea@qumranet.com \
--cc=a.p.zijlstra@chello.nl \
--cc=avi@qumranet.com \
--cc=clameter@sgi.com \
--cc=daniel.blueman@quadrics.com \
--cc=holt@sgi.com \
--cc=izike@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=steiner@sgi.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.