All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Lutomirski <luto@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andy Lutomirski <luto@amacapital.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/6] mm: Add a vm_special_mapping .fault method
Date: Mon, 14 Dec 2015 10:17:09 +0100	[thread overview]
Message-ID: <20151214091709.GA29878@gmail.com> (raw)
In-Reply-To: <20151211142814.25cc806e3f5180d525ee807e@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> > +	} else {
> > +		struct vm_special_mapping *sm = vma->vm_private_data;
> > +
> > +		if (sm->fault)
> > +			return sm->fault(sm, vma, vmf);
> > +
> > +		pages = sm->pages;
> > +	}
> >  
> >  	for (pgoff = vmf->pgoff; pgoff && *pages; ++pages)
> >  		pgoff--;
> 
> Otherwise looks OK.  I'll assume this will be merged via an x86 tree.

Yeah, was hoping to be able to do that with your Acked-by.

Thanks,

	Ingo

--
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: Ingo Molnar <mingo@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Andy Lutomirski <luto@kernel.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andy Lutomirski <luto@amacapital.net>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/6] mm: Add a vm_special_mapping .fault method
Date: Mon, 14 Dec 2015 10:17:09 +0100	[thread overview]
Message-ID: <20151214091709.GA29878@gmail.com> (raw)
In-Reply-To: <20151211142814.25cc806e3f5180d525ee807e@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> > +	} else {
> > +		struct vm_special_mapping *sm = vma->vm_private_data;
> > +
> > +		if (sm->fault)
> > +			return sm->fault(sm, vma, vmf);
> > +
> > +		pages = sm->pages;
> > +	}
> >  
> >  	for (pgoff = vmf->pgoff; pgoff && *pages; ++pages)
> >  		pgoff--;
> 
> Otherwise looks OK.  I'll assume this will be merged via an x86 tree.

Yeah, was hoping to be able to do that with your Acked-by.

Thanks,

	Ingo

  reply	other threads:[~2015-12-14  9:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  3:21 [PATCH 0/6] mm, x86/vdso: Special IO mapping improvements Andy Lutomirski
2015-12-11  3:21 ` Andy Lutomirski
2015-12-11  3:21 ` [PATCH 1/6] mm: Add a vm_special_mapping .fault method Andy Lutomirski
2015-12-11  3:21   ` Andy Lutomirski
2015-12-11 22:28   ` Andrew Morton
2015-12-11 22:28     ` Andrew Morton
2015-12-14  9:17     ` Ingo Molnar [this message]
2015-12-14  9:17       ` Ingo Molnar
2015-12-11  3:21 ` [PATCH 2/6] mm: Add vm_insert_pfn_prot Andy Lutomirski
2015-12-11  3:21   ` Andy Lutomirski
2015-12-11 22:33   ` Andrew Morton
2015-12-11 22:33     ` Andrew Morton
2015-12-11 22:44     ` Andy Lutomirski
2015-12-11 22:44       ` Andy Lutomirski
2015-12-11  3:21 ` [PATCH 3/6] x86/vdso: Track each mm's loaded vdso image as well as its base Andy Lutomirski
2015-12-11  3:21   ` Andy Lutomirski
2015-12-11  3:21 ` [PATCH 4/6] x86,vdso: Use .fault for the vdso text mapping Andy Lutomirski
2015-12-11  3:21   ` Andy Lutomirski
2015-12-11  3:21 ` [PATCH 5/6] x86,vdso: Use .fault instead of remap_pfn_range for the vvar mapping Andy Lutomirski
2015-12-11  3:21   ` Andy Lutomirski
2015-12-11  3:21 ` [PATCH 6/6] x86/vdso: Disallow vvar access to vclock IO for never-used vclocks Andy Lutomirski
2015-12-11  3:21   ` 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=20151214091709.GA29878@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@amacapital.net \
    --cc=luto@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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 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.