linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Hillf Danton" <hillf.zj@alibaba-inc.com>
To: 'Alexey Perevalov' <a.perevalov@samsung.com>,
	'Andrea Arcangeli' <aarcange@redhat.com>
Cc: "'Dr . David Alan Gilbert'" <dgilbert@redhat.com>,
	linux-mm@kvack.org, i.maximets@samsung.com
Subject: Re: [PATCH v2] userfaultfd: provide pid in userfault msg
Date: Mon, 27 Mar 2017 11:57:43 +0800	[thread overview]
Message-ID: <015d01d2a6ae$4a3abf10$deb03d30$@alibaba-inc.com> (raw)
In-Reply-To: <105a751b-254a-d2e3-441e-1418a8e30905@samsung.com>


On March 25, 2017 7:48 PM Alexey Perevalov wrote:
> On 03/23/2017 12:42 PM, Hillf Danton wrote:
> > On March 23, 2017 2:29 AM Alexey Perevalov wrote:
> >>   static inline struct uffd_msg userfault_msg(unsigned long address,
> >>   					    unsigned int flags,
> >> -					    unsigned long reason)
> >> +					    unsigned long reason,
> >> +					    unsigned int features)
> > Nit: the type of feature is u64 by define.
> 
> Yes, let me clarify once again,

Thanks:)

> type of features is u64, but in struct uffdio_api, which used for handling
> UFFDIO_API.
> Function userfault_msg is using in handle_userfault, when only
> context (struct userfaultfd_ctx) is available, features inside context is
> type of unsigned int and uffd_ctx_features is using for casting.
> It's more likely question to maintainer, but due to userfaultfd_ctx is
> internal only
> structure, it's not a big problem to extend it in the future.
> 
You are right.

Hillf

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

  reply	other threads:[~2017-03-27  3:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170322182915eucas1p1e82e604ec8a37d6cd82fdccabe173b87@eucas1p1.samsung.com>
2017-03-22 18:29 ` [PATCH v2] Illuminate thread id to user space Alexey Perevalov
     [not found]   ` <CGME20170322182918eucas1p204ef2f7aadb0ac41d11f15ef434c74c4@eucas1p2.samsung.com>
2017-03-22 18:29     ` [PATCH v2] userfaultfd: provide pid in userfault msg Alexey Perevalov
2017-03-23  9:42       ` Hillf Danton
2017-03-23 10:07         ` Alexey Perevalov
2017-03-25 11:47         ` Alexey Perevalov
2017-03-27  3:57           ` Hillf Danton [this message]
2017-03-29 17:19       ` Andrea Arcangeli

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='015d01d2a6ae$4a3abf10$deb03d30$@alibaba-inc.com' \
    --to=hillf.zj@alibaba-inc.com \
    --cc=a.perevalov@samsung.com \
    --cc=aarcange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=i.maximets@samsung.com \
    --cc=linux-mm@kvack.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