From: Jerome Glisse <jglisse@redhat.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
"Andrew Morton" <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, "David (ChunMing) Zhou" <David1.Zhou@amd.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@linux.ie>,
"Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Doug Ledford" <dledford@redhat.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Mike Marciniszyn" <mike.marciniszyn@intel.com>,
"Dennis Dalessandro" <dennis.dalessandro@intel.com>,
"Sudeep Dutt" <sudeep.dutt@intel.com>,
"Ashutosh Dixit" <ashutosh.dixit@intel.com>,
"Dimitri Sivanich" <sivanich@sgi.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Juergen Gross" <jgross@suse.com>,
"Andrea Arcangeli" <aarcange@redhat.com>,
"Felix Kuehling" <felix.kuehling@amd.com>,
kvm@vger.kernel.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-rdma@vger.kernel.org, xen-devel@lists.xenproject.org,
"Christian König" <christian.koenig@amd.com>,
"David Rientjes" <rientjes@google.com>,
"Leon Romanovsky" <leonro@mellanox.com>
Subject: Re: [PATCH] mm, oom: distinguish blockable mode for mmu notifiers
Date: Fri, 24 Aug 2018 13:33:32 -0400 [thread overview]
Message-ID: <20180824173332.GD4244@redhat.com> (raw)
In-Reply-To: <20180824164003.GW29735@dhcp22.suse.cz>
On Fri, Aug 24, 2018 at 06:40:03PM +0200, Michal Hocko wrote:
> On Fri 24-08-18 11:12:40, Jerome Glisse wrote:
> [...]
> > I am fine with Michal patch, i already said so couple month ago first time
> > this discussion did pop up, Michal you can add:
> >
> > Reviewed-by: Jérôme Glisse <jglisse@redhat.com>
>
> So I guess the below is the patch you were talking about?
>
> From f7ac75277d526dccd011f343818dc6af627af2af Mon Sep 17 00:00:00 2001
> From: Michal Hocko <mhocko@suse.com>
> Date: Fri, 24 Aug 2018 15:32:24 +0200
> Subject: [PATCH] mm, mmu_notifier: be explicit about range invalition
> non-blocking mode
>
> If invalidate_range_start is called for !blocking mode then all
> callbacks have to guarantee they will no block/sleep. The same obviously
> applies to invalidate_range_end because this operation pairs with the
> former and they are called from the same context. Make sure this is
> appropriately documented.
In my branch i already updated HMM to be like other existing user
ie all blocking operation in the start callback. But yes it would
be wise to added such comments.
>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> ---
> include/linux/mmu_notifier.h | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index 133ba78820ee..698e371aafe3 100644
> --- a/include/linux/mmu_notifier.h
> +++ b/include/linux/mmu_notifier.h
> @@ -153,7 +153,9 @@ struct mmu_notifier_ops {
> *
> * If blockable argument is set to false then the callback cannot
> * sleep and has to return with -EAGAIN. 0 should be returned
> - * otherwise.
> + * otherwise. Please note that if invalidate_range_start approves
> + * a non-blocking behavior then the same applies to
> + * invalidate_range_end.
> *
> */
> int (*invalidate_range_start)(struct mmu_notifier *mn,
> --
> 2.18.0
>
> --
> Michal Hocko
> SUSE Labs
next prev parent reply other threads:[~2018-08-24 17:33 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 11:50 [PATCH] mm, oom: distinguish blockable mode for mmu notifiers Michal Hocko
2018-07-16 23:12 ` Andrew Morton
2018-07-17 4:03 ` Leon Romanovsky
2018-07-17 8:12 ` Michal Hocko
2018-07-20 23:01 ` Andrew Morton
2018-07-23 8:43 ` Michal Hocko
2018-07-19 9:12 ` Michal Hocko
2018-07-21 0:09 ` Andrew Morton
2018-07-23 7:03 ` Michal Hocko
2018-07-23 7:11 ` Michal Hocko
2018-07-23 8:11 ` Michal Hocko
2018-07-24 14:17 ` Michal Hocko
2018-07-24 19:53 ` Andrew Morton
2018-07-25 6:17 ` Michal Hocko
2018-07-24 21:07 ` David Rientjes
2018-07-25 6:13 ` Michal Hocko
2018-08-24 10:54 ` Tetsuo Handa
2018-08-24 11:32 ` Michal Hocko
2018-08-24 11:43 ` Christian König
2018-08-24 11:52 ` Michal Hocko
2018-08-24 11:57 ` Christian König
2018-08-24 12:03 ` Michal Hocko
2018-08-24 12:18 ` Christian König
2018-08-24 12:33 ` Michal Hocko
2018-08-24 12:52 ` Christian König
2018-08-24 13:01 ` Michal Hocko
2018-08-24 13:10 ` Christian König
2018-08-24 13:24 ` Michal Hocko
2018-08-24 13:28 ` Christian König
2018-08-24 13:40 ` Michal Hocko
2018-08-24 13:44 ` Christian König
2018-08-24 13:52 ` Michal Hocko
2018-08-26 8:40 ` Tetsuo Handa
2018-08-27 7:41 ` Christian König
2018-09-06 22:46 ` Tetsuo Handa
2018-08-24 15:08 ` Jerome Glisse
2018-08-24 11:36 ` Michal Hocko
2018-08-24 13:02 ` Tetsuo Handa
2018-08-24 13:32 ` Michal Hocko
2018-08-24 14:52 ` Tetsuo Handa
2018-08-24 15:12 ` Jerome Glisse
2018-08-24 16:40 ` Michal Hocko
2018-08-24 17:33 ` Jerome Glisse [this message]
2018-08-24 16:38 ` Michal Hocko
2018-08-24 14:40 ` Jerome Glisse
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=20180824173332.GD4244@redhat.com \
--to=jglisse@redhat.com \
--cc=David1.Zhou@amd.com \
--cc=aarcange@redhat.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ashutosh.dixit@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=christian.koenig@amd.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jgross@suse.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mike.marciniszyn@intel.com \
--cc=pbonzini@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.com \
--cc=rkrcmar@redhat.com \
--cc=rodrigo.vivi@intel.com \
--cc=sivanich@sgi.com \
--cc=sudeep.dutt@intel.com \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).