All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>,
	Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 2/3] mm: Convert vm_insert_pfn_prot to vmf_insert_pfn_prot
Date: Tue, 26 Jan 2016 23:18:21 -0500	[thread overview]
Message-ID: <20160127041821.GQ2948@linux.intel.com> (raw)
In-Reply-To: <CALCETrWQdJFBMz+O3TtVfMwAapY1tJFg3PE+-Gjp7fOWkzrAAA@mail.gmail.com>

On Mon, Jan 25, 2016 at 09:35:36AM -0800, Andy Lutomirski wrote:
> On Mon, Jan 25, 2016 at 9:25 AM, Matthew Wilcox
> <matthew.r.wilcox@intel.com> wrote:
> > From: Matthew Wilcox <willy@linux.intel.com>
> >
> > Other than the name, the vmf_ version takes a pfn_t parameter, and
> > returns a VM_FAULT_ code suitable for returning from a fault handler.
> >
> > This patch also prevents vm_insert_pfn() from returning -EBUSY.
> > This is a good thing as several callers handled it incorrectly (and
> > none intentionally treat -EBUSY as a different case from 0).
> >
> > Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
> 
> This would be even nicer if you added vmf_insert_pfn as well :)

I've sent out patches adding it before ... my most recent attempt on
January 5th tied up with the DAX support for 1GB pages.  I'll keep
sending it until it sticks :-)

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Matthew Wilcox <matthew.r.wilcox@intel.com>,
	Ingo Molnar <mingo@redhat.com>, Kees Cook <keescook@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH 2/3] mm: Convert vm_insert_pfn_prot to vmf_insert_pfn_prot
Date: Tue, 26 Jan 2016 23:18:21 -0500	[thread overview]
Message-ID: <20160127041821.GQ2948@linux.intel.com> (raw)
In-Reply-To: <CALCETrWQdJFBMz+O3TtVfMwAapY1tJFg3PE+-Gjp7fOWkzrAAA@mail.gmail.com>

On Mon, Jan 25, 2016 at 09:35:36AM -0800, Andy Lutomirski wrote:
> On Mon, Jan 25, 2016 at 9:25 AM, Matthew Wilcox
> <matthew.r.wilcox@intel.com> wrote:
> > From: Matthew Wilcox <willy@linux.intel.com>
> >
> > Other than the name, the vmf_ version takes a pfn_t parameter, and
> > returns a VM_FAULT_ code suitable for returning from a fault handler.
> >
> > This patch also prevents vm_insert_pfn() from returning -EBUSY.
> > This is a good thing as several callers handled it incorrectly (and
> > none intentionally treat -EBUSY as a different case from 0).
> >
> > Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
> 
> This would be even nicer if you added vmf_insert_pfn as well :)

I've sent out patches adding it before ... my most recent attempt on
January 5th tied up with the DAX support for 1GB pages.  I'll keep
sending it until it sticks :-)

  reply	other threads:[~2016-01-27  4:18 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 17:25 [PATCH 0/3] Fixes for vm_insert_pfn_prot() Matthew Wilcox
2016-01-25 17:25 ` Matthew Wilcox
2016-01-25 17:25 ` [PATCH 1/3] x86: Honour passed pgprot in track_pfn_insert() and track_pfn_remap() Matthew Wilcox
2016-01-25 17:25   ` Matthew Wilcox
2016-01-25 17:33   ` Andy Lutomirski
2016-01-25 17:33     ` Andy Lutomirski
2016-01-25 17:46     ` Andy Lutomirski
2016-01-25 17:46       ` Andy Lutomirski
2016-01-27  4:40     ` Matthew Wilcox
2016-01-27  4:40       ` Matthew Wilcox
2016-01-27  5:44       ` Andy Lutomirski
2016-01-27  5:44         ` Andy Lutomirski
2016-01-29 14:49         ` Matthew Wilcox
2016-01-29 14:49           ` Matthew Wilcox
2016-01-29 22:19           ` Andy Lutomirski
2016-01-29 22:19             ` Andy Lutomirski
2016-02-09 14:24           ` Ingo Molnar
2016-02-09 14:24             ` Ingo Molnar
2016-02-10  3:06             ` Andy Lutomirski
2016-02-10  3:06               ` Andy Lutomirski
2016-02-09 16:09   ` [tip:x86/asm] x86/mm: " tip-bot for Matthew Wilcox
2016-01-25 17:25 ` [PATCH 2/3] mm: Convert vm_insert_pfn_prot to vmf_insert_pfn_prot Matthew Wilcox
2016-01-25 17:25   ` Matthew Wilcox
2016-01-25 17:35   ` Andy Lutomirski
2016-01-25 17:35     ` Andy Lutomirski
2016-01-27  4:18     ` Matthew Wilcox [this message]
2016-01-27  4:18       ` Matthew Wilcox
2016-01-25 17:25 ` [PATCH 3/3] dax: Handle write faults more efficiently Matthew Wilcox
2016-01-25 17:25   ` Matthew Wilcox
2016-01-25 17:38   ` Andy Lutomirski
2016-01-25 17:38     ` Andy Lutomirski
2016-01-27  4:17     ` Matthew Wilcox
2016-01-27  4:17       ` Matthew Wilcox
2016-01-27  5:22       ` Andy Lutomirski
2016-01-27  5:22         ` Andy Lutomirski
2016-01-27  6:01       ` Andy Lutomirski
2016-01-27  6:01         ` Andy Lutomirski

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=20160127041821.GQ2948@linux.intel.com \
    --to=willy@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=matthew.r.wilcox@intel.com \
    --cc=mingo@redhat.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.