From: Andrew Morton <akpm@linux-foundation.org>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: willy@infradead.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: Change return type to vm_fault_t
Date: Thu, 8 Mar 2018 14:26:58 -0800 [thread overview]
Message-ID: <20180308142658.285e0b2ab50b81449783cd4a@linux-foundation.org> (raw)
In-Reply-To: <20180308130523.GA30642@jordon-HP-15-Notebook-PC>
On Thu, 8 Mar 2018 18:35:23 +0530 Souptick Joarder <jrdr.linux@gmail.com> wrote:
> Use new return type vm_fault_t for fault handler
> in struct vm_operations_struct.
I can't find vm_fault_t?
> vmf_insert_mixed(), vmf_insert_pfn() and vmf_insert_page()
> are newly added inline wrapper functions.
Why?
> index ad06d42..a4d8853 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -379,17 +379,18 @@ struct vm_operations_struct {
> void (*close)(struct vm_area_struct * area);
> int (*split)(struct vm_area_struct * area, unsigned long addr);
> int (*mremap)(struct vm_area_struct * area);
> - int (*fault)(struct vm_fault *vmf);
> - int (*huge_fault)(struct vm_fault *vmf, enum page_entry_size pe_size);
> + vm_fault_t (*fault)(struct vm_fault *vmf);
> + vm_fault_t (*huge_fault)(struct vm_fault *vmf,
> + enum page_entry_size pe_size);
Well if we're going to do this then we should convert all the
.page_mkwrite() instances and a bunch of other stuff to use vm_fault_t.
It's a lot of work. Perhaps we should just keep using "int".
next prev parent reply other threads:[~2018-03-08 22:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 13:05 Souptick Joarder
2018-03-08 22:22 ` Matthew Wilcox
2018-03-08 23:22 ` Andrew Morton
2018-03-08 23:48 ` Matthew Wilcox
2018-03-09 6:28 ` Souptick Joarder
2018-03-08 22:26 ` Andrew Morton [this message]
2018-03-08 22:55 ` Matthew Wilcox
2018-04-14 21:33 Souptick Joarder
2018-05-29 14:31 Souptick Joarder
2018-05-29 14:50 ` Matthew Wilcox
2018-05-29 15:55 ` Souptick Joarder
2018-05-29 17:34 ` Matthew Wilcox
2018-05-30 3:40 ` Souptick Joarder
2018-05-30 11:16 ` Matthew Wilcox
2018-06-02 14:44 ` Souptick Joarder
2018-06-02 14:44 ` Souptick Joarder
2018-06-02 14:55 ` Souptick Joarder
2018-06-02 14:59 ` Luc Van Oostenryck
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=20180308142658.285e0b2ab50b81449783cd4a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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