From: Andrew Morton <akpm@linux-foundation.org>
To: Andy Lutomirski <luto@kernel.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH 1/6] mm: Add a vm_special_mapping .fault method
Date: Fri, 11 Dec 2015 14:28:14 -0800 [thread overview]
Message-ID: <20151211142814.25cc806e3f5180d525ee807e@linux-foundation.org> (raw)
In-Reply-To: <4e911d2752d3b9e52d7496e46b389fc630cdc3a8.1449803537.git.luto@kernel.org>
On Thu, 10 Dec 2015 19:21:42 -0800 Andy Lutomirski <luto@kernel.org> wrote:
> From: Andy Lutomirski <luto@amacapital.net>
>
> Requiring special mappings to give a list of struct pages is
> inflexible: it prevents sane use of IO memory in a special mapping,
> it's inefficient (it requires arch code to initialize a list of
> struct pages, and it requires the mm core to walk the entire list
> just to figure out how long it is), and it prevents arch code from
> doing anything fancy when a special mapping fault occurs.
>
> Add a .fault method as an alternative to filling in a .pages array.
>
> ...
>
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -568,10 +568,27 @@ static inline void clear_tlb_flush_pending(struct mm_struct *mm)
> }
> #endif
>
> +struct vm_fault;
> +
> struct vm_special_mapping
> {
We may as well fix the code layout while we're in there.
> - const char *name;
> + const char *name; /* The name, e.g. "[vdso]". */
> +
> + /*
> + * If .fault is not provided, this is points to a
s/is//
> + * NULL-terminated array of pages that back the special mapping.
> + *
> + * This must not be NULL unless .fault is provided.
> + */
> struct page **pages;
> +
> + /*
> + * If non-NULL, then this is called to resolve page faults
> + * on the special mapping. If used, .pages is not checked.
> + */
> + int (*fault)(const struct vm_special_mapping *sm,
> + struct vm_area_struct *vma,
> + struct vm_fault *vmf);
> };
>
> enum tlb_flush_reason {
> diff --git a/mm/mmap.c b/mm/mmap.c
> index 2ce04a649f6b..f717453b1a57 100644
> --- a/mm/mmap.c
> +++ b/mm/mmap.c
> @@ -3030,11 +3030,16 @@ static int special_mapping_fault(struct vm_area_struct *vma,
> pgoff_t pgoff;
> struct page **pages;
>
> - if (vma->vm_ops == &legacy_special_mapping_vmops)
> + if (vma->vm_ops == &legacy_special_mapping_vmops) {
> pages = vma->vm_private_data;
> - else
> - pages = ((struct vm_special_mapping *)vma->vm_private_data)->
> - pages;
> + } 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.
--
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:[~2015-12-11 22:28 UTC|newest]
Thread overview: 11+ 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 ` [PATCH 1/6] mm: Add a vm_special_mapping .fault method Andy Lutomirski
2015-12-11 22:28 ` Andrew Morton [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 22:33 ` Andrew Morton
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 ` [PATCH 4/6] x86,vdso: Use .fault for the vdso text mapping 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 ` [PATCH 6/6] x86/vdso: Disallow vvar access to vclock IO for never-used vclocks 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=20151211142814.25cc806e3f5180d525ee807e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox