From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Jason Gunthorpe <jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Andrea Arcangeli
<aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Ralph Campbell
<rcampbell-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
John Hubbard <jhubbard-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"Felix.Kuehling-5C7GfCeVMHo@public.gmane.org"
<Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>,
"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
"linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org"
<linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org>,
Jerome Glisse <jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [RFC] mm/hmm: pass mmu_notifier_range to sync_cpu_device_pagetables
Date: Wed, 3 Jul 2019 00:49:12 +0200 [thread overview]
Message-ID: <20190702224912.GA24043@lst.de> (raw)
In-Reply-To: <20190702195317.GT31718-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Tue, Jul 02, 2019 at 07:53:23PM +0000, Jason Gunthorpe wrote:
> > I'm sending this out now since we are updating many of the HMM APIs
> > and I think it will be useful.
>
> This make so much sense, I'd like to apply this in hmm.git, is there
> any objection?
As this creates a somewhat hairy conflict for amdgpu, wouldn't it be
a better idea to wait a bit and apply it first thing for next merge
window?
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Ralph Campbell <rcampbell@nvidia.com>,
Christoph Hellwig <hch@lst.de>,
Jerome Glisse <jglisse@redhat.com>,
John Hubbard <jhubbard@nvidia.com>,
"Felix.Kuehling@amd.com" <Felix.Kuehling@amd.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrea Arcangeli <aarcange@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [RFC] mm/hmm: pass mmu_notifier_range to sync_cpu_device_pagetables
Date: Wed, 3 Jul 2019 00:49:12 +0200 [thread overview]
Message-ID: <20190702224912.GA24043@lst.de> (raw)
In-Reply-To: <20190702195317.GT31718@mellanox.com>
On Tue, Jul 02, 2019 at 07:53:23PM +0000, Jason Gunthorpe wrote:
> > I'm sending this out now since we are updating many of the HMM APIs
> > and I think it will be useful.
>
> This make so much sense, I'd like to apply this in hmm.git, is there
> any objection?
As this creates a somewhat hairy conflict for amdgpu, wouldn't it be
a better idea to wait a bit and apply it first thing for next merge
window?
next prev parent reply other threads:[~2019-07-02 22:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-08 0:14 [RFC] mm/hmm: pass mmu_notifier_range to sync_cpu_device_pagetables Ralph Campbell
2019-06-08 0:14 ` Ralph Campbell
[not found] ` <20190608001452.7922-1-rcampbell-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2019-06-08 9:10 ` Christoph Hellwig
2019-06-08 9:10 ` Christoph Hellwig
2019-06-08 11:41 ` Jason Gunthorpe
2019-06-08 11:41 ` Jason Gunthorpe
[not found] ` <20190608114133.GA14873-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2019-06-10 0:16 ` John Hubbard
2019-06-10 0:16 ` John Hubbard
2019-07-02 19:53 ` Jason Gunthorpe
2019-07-02 19:53 ` Jason Gunthorpe
[not found] ` <20190702195317.GT31718-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2019-07-02 20:11 ` Ralph Campbell
2019-07-02 20:11 ` Ralph Campbell
2019-07-02 22:49 ` Christoph Hellwig [this message]
2019-07-02 22:49 ` Christoph Hellwig
[not found] ` <20190702224912.GA24043-jcswGhMUV9g@public.gmane.org>
2019-07-02 22:59 ` Jason Gunthorpe
2019-07-02 22:59 ` Jason Gunthorpe
[not found] ` <20190702225911.GA11833-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2019-07-03 0:03 ` Christoph Hellwig
2019-07-03 0:03 ` Christoph Hellwig
2019-07-03 2:27 ` Kuehling, Felix
2019-07-03 2:27 ` Kuehling, Felix
[not found] ` <1dc82dc8-3e6f-1d6f-b14d-41ae3c1b2709-5C7GfCeVMHo@public.gmane.org>
2019-07-03 15:08 ` Jason Gunthorpe
2019-07-03 15:08 ` Jason Gunthorpe
2019-06-08 11:50 ` Jason Gunthorpe
2019-06-08 11:50 ` Jason Gunthorpe
2019-06-09 19:46 ` Ira Weiny
2019-06-09 19:46 ` Ira Weiny
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=20190702224912.GA24043@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=Felix.Kuehling-5C7GfCeVMHo@public.gmane.org \
--cc=aarcange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jhubbard-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rcampbell-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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.