From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: "Kuehling, Felix" <Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
Cc: "alex.deucher-5C7GfCeVMHo@public.gmane.org"
<alex.deucher-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>,
"jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org"
<jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
"airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH 0/2] Two bug-fixes for HMM
Date: Thu, 6 Jun 2019 12:11:49 -0300 [thread overview]
Message-ID: <20190606151149.GA5506@ziepe.ca> (raw)
In-Reply-To: <20190510195258.9930-1-Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
On Fri, May 10, 2019 at 07:53:21PM +0000, Kuehling, Felix wrote:
> These problems were found in AMD-internal testing as we're working on
> adopting HMM. They are rebased against glisse/hmm-5.2-v3. We'd like to get
> them applied to a mainline Linux kernel as well as drm-next and
> amd-staging-drm-next sooner rather than later.
>
> Currently the HMM in amd-staging-drm-next is quite far behind hmm-5.2-v3,
> but the driver changes for HMM are expected to land in 5.2 and will need to
> be rebased on those HMM changes.
>
> I'd like to work out a flow between Jerome, Dave, Alex and myself that
> allows us to test the latest version of HMM on amd-staging-drm-next so
> that ideally everything comes together in master without much need for
> rebasing and retesting.
I think we have that now, I'm running a hmm.git that is clean and can
be used for merging into DRM related trees (and RDMA). I've commited
to send this tree to Linus at the start of the merge window.
See here:
https://lore.kernel.org/lkml/20190524124455.GB16845@ziepe.ca/
The tree is here:
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=hmm
However please consult with me before making a merge commit to be
co-ordinated. Thanks
I see in this thread that AMDGPU missed 5.2 beacause of the
co-ordination problems this tree is intended to solve, so I'm very
hopeful this will help your work move into 5.3!
> Maybe having Jerome's latest HMM changes in drm-next. However, that may
> create dependencies where Jerome and Dave need to coordinate their pull-
> requests for master.
>
> Felix Kuehling (1):
> mm/hmm: Only set FAULT_FLAG_ALLOW_RETRY for non-blocking
>
> Philip Yang (1):
> mm/hmm: support automatic NUMA balancing
I've applied both of these patches with Jerome's Reviewed-by to
hmm.git and added the missed Signed-off-by
If you test and confirm I think this branch would be ready for merging
toward the AMD tree.
Regards,
Jason
_______________________________________________
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: Jason Gunthorpe <jgg@ziepe.ca>
To: "Kuehling, Felix" <Felix.Kuehling@amd.com>
Cc: "jglisse@redhat.com" <jglisse@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
"alex.deucher@amd.com" <alex.deucher@amd.com>,
"airlied@gmail.com" <airlied@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 0/2] Two bug-fixes for HMM
Date: Thu, 6 Jun 2019 12:11:49 -0300 [thread overview]
Message-ID: <20190606151149.GA5506@ziepe.ca> (raw)
In-Reply-To: <20190510195258.9930-1-Felix.Kuehling@amd.com>
On Fri, May 10, 2019 at 07:53:21PM +0000, Kuehling, Felix wrote:
> These problems were found in AMD-internal testing as we're working on
> adopting HMM. They are rebased against glisse/hmm-5.2-v3. We'd like to get
> them applied to a mainline Linux kernel as well as drm-next and
> amd-staging-drm-next sooner rather than later.
>
> Currently the HMM in amd-staging-drm-next is quite far behind hmm-5.2-v3,
> but the driver changes for HMM are expected to land in 5.2 and will need to
> be rebased on those HMM changes.
>
> I'd like to work out a flow between Jerome, Dave, Alex and myself that
> allows us to test the latest version of HMM on amd-staging-drm-next so
> that ideally everything comes together in master without much need for
> rebasing and retesting.
I think we have that now, I'm running a hmm.git that is clean and can
be used for merging into DRM related trees (and RDMA). I've commited
to send this tree to Linus at the start of the merge window.
See here:
https://lore.kernel.org/lkml/20190524124455.GB16845@ziepe.ca/
The tree is here:
https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/log/?h=hmm
However please consult with me before making a merge commit to be
co-ordinated. Thanks
I see in this thread that AMDGPU missed 5.2 beacause of the
co-ordination problems this tree is intended to solve, so I'm very
hopeful this will help your work move into 5.3!
> Maybe having Jerome's latest HMM changes in drm-next. However, that may
> create dependencies where Jerome and Dave need to coordinate their pull-
> requests for master.
>
> Felix Kuehling (1):
> mm/hmm: Only set FAULT_FLAG_ALLOW_RETRY for non-blocking
>
> Philip Yang (1):
> mm/hmm: support automatic NUMA balancing
I've applied both of these patches with Jerome's Reviewed-by to
hmm.git and added the missed Signed-off-by
If you test and confirm I think this branch would be ready for merging
toward the AMD tree.
Regards,
Jason
next prev parent reply other threads:[~2019-06-06 15:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 19:53 [PATCH 0/2] Two bug-fixes for HMM Kuehling, Felix
2019-05-10 19:53 ` Kuehling, Felix
[not found] ` <20190510195258.9930-1-Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
2019-05-10 19:53 ` [PATCH 1/2] mm/hmm: support automatic NUMA balancing Kuehling, Felix
2019-05-10 19:53 ` Kuehling, Felix
2019-05-10 20:13 ` Jerome Glisse
2019-05-10 20:13 ` Jerome Glisse
2019-05-13 21:27 ` Andrew Morton
2019-05-13 21:27 ` Andrew Morton
[not found] ` <20190513142720.3334a98cbabaae67b4ffbb5a-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2019-05-13 22:37 ` Jerome Glisse
2019-05-13 22:37 ` Jerome Glisse
2019-05-14 21:14 ` Kuehling, Felix
2019-05-14 21:14 ` Kuehling, Felix
2019-05-10 19:53 ` [PATCH 2/2] mm/hmm: Only set FAULT_FLAG_ALLOW_RETRY for non-blocking Kuehling, Felix
2019-05-10 19:53 ` Kuehling, Felix
[not found] ` <20190510195258.9930-3-Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
2019-05-10 20:14 ` Jerome Glisse
2019-05-10 20:14 ` Jerome Glisse
[not found] ` <20190510201403.GG4507-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2019-05-13 19:36 ` Kuehling, Felix
2019-05-13 19:36 ` Kuehling, Felix
[not found] ` <65328381-aa0d-353d-68dc-81060e7cebdf-5C7GfCeVMHo@public.gmane.org>
2019-05-13 19:49 ` Jerome Glisse
2019-05-13 19:49 ` Jerome Glisse
[not found] ` <20190513194925.GA31365-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2019-05-13 20:31 ` Kuehling, Felix
2019-05-13 20:31 ` Kuehling, Felix
2019-05-13 20:21 ` Deucher, Alexander
2019-05-13 20:21 ` Deucher, Alexander
[not found] ` <BN6PR12MB1809F26E6AF74BE9F96DB22DF70F0-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-05-14 21:12 ` Kuehling, Felix
2019-05-14 21:12 ` Kuehling, Felix
2019-05-14 21:58 ` Alex Deucher
2019-05-14 21:58 ` Alex Deucher
2019-06-06 15:11 ` Jason Gunthorpe [this message]
2019-06-06 15:11 ` [PATCH 0/2] Two bug-fixes for HMM Jason Gunthorpe
[not found] ` <20190606151149.GA5506-uk2M96/98Pc@public.gmane.org>
2019-06-06 19:04 ` Kuehling, Felix
2019-06-06 19:04 ` Kuehling, Felix
[not found] ` <1d309300-41d8-eb31-38c2-c6c9dd5c0ba8-5C7GfCeVMHo@public.gmane.org>
2019-06-06 19:20 ` Jason Gunthorpe
2019-06-06 19:20 ` Jason Gunthorpe
2019-06-06 19:16 ` Kuehling, Felix
2019-06-06 19:16 ` Kuehling, Felix
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=20190606151149.GA5506@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=Felix.Kuehling-5C7GfCeVMHo@public.gmane.org \
--cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=alex.deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=jglisse-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@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.