From: Andrea Arcangeli <aarcange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, Nick Piggin <npiggin@suse.de>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
lsf10-pc@lists.linuxfoundation.org, linux-scsi@vger.kernel.org
Subject: Re: [Lsf10-pc] Current MM topics for LSF10/MM Summit 8-9 August in Boston
Date: Mon, 21 Jun 2010 16:45:20 +0200 [thread overview]
Message-ID: <20100621144520.GB5787@random.random> (raw)
In-Reply-To: <4C1F77CD.40509@redhat.com>
On Mon, Jun 21, 2010 at 05:31:41PM +0300, Avi Kivity wrote:
> On 06/21/2010 05:29 PM, Andrea Arcangeli wrote:
> > On Mon, Jun 21, 2010 at 05:18:56PM +0300, Gleb Natapov wrote:
> >
> >> Avi did the fix. We discussed using MADV_DONTFORK for that, but calling
> >> madvise() from kernel deemed to be messy.
> >>
> > Agree that calling madvise looks messy. It's possible to set
> > VM_DONTCOPY under mmap_sem write mode and it'll work as well.
> >
>
> But we aren't guaranteed to get our own vma, yes?
Correct, one would need to call split_vma like madvise_behavior does
before setting the flag. For sure current fix is simpler ;).
> Note kvm shouldn't be calling do_mmap() in any case. I let that in
> because it was simple and because we had a userspace interface relying
> on that, but that's no longer the case, so I'll make that page kernel owned.
Agree ;).
--
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:[~2010-06-21 14:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 20:50 Current topics for LSF10/MM Summit 8-9 August in Boston James Bottomley
2010-06-17 6:35 ` Nicholas A. Bellinger
2010-06-17 13:27 ` [Lsf10-pc] " James Bottomley
2010-06-17 13:27 ` James Bottomley
2010-06-17 16:00 ` Christof Schmitt
2010-06-17 16:00 ` Christof Schmitt
2010-06-17 16:07 ` James Bottomley
2010-06-17 16:07 ` James Bottomley
2010-06-17 16:13 ` Boaz Harrosh
2010-06-17 16:13 ` Boaz Harrosh
2010-06-17 16:34 ` Vladislav Bolkhovitin
2010-06-17 16:34 ` Vladislav Bolkhovitin
2010-06-17 16:42 ` James Bottomley
2010-06-17 16:42 ` James Bottomley
2010-06-17 17:11 ` Vladislav Bolkhovitin
2010-06-17 17:11 ` Vladislav Bolkhovitin
2010-06-17 17:37 ` James Bottomley
2010-06-17 17:55 ` Vladislav Bolkhovitin
2010-06-17 17:55 ` Vladislav Bolkhovitin
2010-06-18 11:41 ` Christof Schmitt
2010-06-18 11:41 ` Christof Schmitt
2010-06-18 12:18 ` [Lsf10-pc] " J. Bruce Fields
2010-06-18 12:18 ` J. Bruce Fields
2010-06-21 12:05 ` Current MM " Nick Piggin
2010-06-21 12:05 ` Nick Piggin
2010-06-21 13:16 ` [Lsf10-pc] " Andrea Arcangeli
2010-06-21 13:22 ` Gleb Natapov
2010-06-21 14:09 ` Andrea Arcangeli
2010-06-21 14:18 ` Gleb Natapov
2010-06-21 14:29 ` Andrea Arcangeli
2010-06-21 14:31 ` Avi Kivity
2010-06-21 14:31 ` Avi Kivity
2010-06-21 14:45 ` Andrea Arcangeli [this message]
2010-06-22 3:30 ` KOSAKI Motohiro
2010-06-22 3:30 ` KOSAKI Motohiro
2010-06-21 20:00 ` David Rientjes
2010-06-21 20:13 ` James Bottomley
2010-06-21 20:13 ` James Bottomley
2010-07-01 18:30 ` Larry Woodman
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=20100621144520.GB5787@random.random \
--to=aarcange@redhat.com \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf10-pc@lists.linuxfoundation.org \
--cc=npiggin@suse.de \
/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.