All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerome Glisse <jglisse@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Dan Williams <dan.j.williams@intel.com>,
	David Nellans <dnellans@nvidia.com>
Subject: Re: [PATCH 00/15] HMM (Heterogeneous Memory Management) v24
Date: Fri, 30 Jun 2017 15:49:56 -0400	[thread overview]
Message-ID: <20170630194956.GB4275@redhat.com> (raw)
In-Reply-To: <960ef002-3cfd-5b91-054e-aa685abc5f1f@nvidia.com>

On Thu, Jun 29, 2017 at 10:32:49PM -0700, John Hubbard wrote:
> On 06/28/2017 11:00 AM, Jérôme Glisse wrote:
> > 
> > Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i
> > test same kernel as kbuild system, git branch:
> > 
> > https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v24
> > 
> > Change since v23 is code comment fixes, simplify kernel configuration and
> > improve allocation of new page on migration do device memory (last patch
> > in this patchset).
> 
> Hi Jerome,
> 
> Tiny note: one more change is that hmm_devmem_fault_range() has been
> removed (and thanks for taking care of that, btw).

True i forgot to mention that.

> 
> Anyway, this looks good. A basic smoke test shows the following:
> 
> 1. We definitely *require* your other patch, 
> "[PATCH] x86/mm/hotplug: fix BUG_ON() after hotremove by not freeing pud v3",
> otherwise I will reliably hit that bug every time I run my simple page fault
> test. So, let me know if I should ping that thread. It looks like your patch
> was not rejected, but I can't tell if (!rejected == accepted), there. :)

Ingo did pick it up so it should shows in Linus tree soon i expect.

Cheers,
Jérôme

WARNING: multiple messages have this Message-ID (diff)
From: Jerome Glisse <jglisse@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, Dan Williams <dan.j.williams@intel.com>,
	David Nellans <dnellans@nvidia.com>
Subject: Re: [PATCH 00/15] HMM (Heterogeneous Memory Management) v24
Date: Fri, 30 Jun 2017 15:49:56 -0400	[thread overview]
Message-ID: <20170630194956.GB4275@redhat.com> (raw)
In-Reply-To: <960ef002-3cfd-5b91-054e-aa685abc5f1f@nvidia.com>

On Thu, Jun 29, 2017 at 10:32:49PM -0700, John Hubbard wrote:
> On 06/28/2017 11:00 AM, Jerome Glisse wrote:
> > 
> > Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i
> > test same kernel as kbuild system, git branch:
> > 
> > https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v24
> > 
> > Change since v23 is code comment fixes, simplify kernel configuration and
> > improve allocation of new page on migration do device memory (last patch
> > in this patchset).
> 
> Hi Jerome,
> 
> Tiny note: one more change is that hmm_devmem_fault_range() has been
> removed (and thanks for taking care of that, btw).

True i forgot to mention that.

> 
> Anyway, this looks good. A basic smoke test shows the following:
> 
> 1. We definitely *require* your other patch, 
> "[PATCH] x86/mm/hotplug: fix BUG_ON() after hotremove by not freeing pud v3",
> otherwise I will reliably hit that bug every time I run my simple page fault
> test. So, let me know if I should ping that thread. It looks like your patch
> was not rejected, but I can't tell if (!rejected == accepted), there. :)

Ingo did pick it up so it should shows in Linus tree soon i expect.

Cheers,
Jerome

--
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-06-30 19:50 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 18:00 [PATCH 00/15] HMM (Heterogeneous Memory Management) v24 Jérôme Glisse
2017-06-28 18:00 ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 01/15] hmm: heterogeneous memory management documentation v2 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 02/15] mm/hmm: heterogeneous memory management (HMM for short) v4 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 03/15] mm/hmm/mirror: mirror process address space on device with HMM helpers v3 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 04/15] mm/hmm/mirror: helper to snapshot CPU page table v3 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 05/15] mm/hmm/mirror: device page fault handler Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 06/15] mm/memory_hotplug: introduce add_pages Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 07/15] mm/ZONE_DEVICE: new type of ZONE_DEVICE for unaddressable memory v4 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-07-01  0:16   ` kbuild test robot
2017-07-01  0:16     ` kbuild test robot
2017-06-28 18:00 ` [PATCH 08/15] mm/ZONE_DEVICE: special case put_page() for device private pages v2 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 09/15] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v6 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-07-18 21:41   ` Evgeny Baskakov
2017-07-18 21:41     ` Evgeny Baskakov
2017-07-28 11:10   ` Michal Hocko
2017-07-28 11:10     ` Michal Hocko
2017-07-31 17:21     ` Jerome Glisse
2017-07-31 17:21       ` Jerome Glisse
2017-08-01 12:17       ` Michal Hocko
2017-08-01 12:17         ` Michal Hocko
2017-06-28 18:00 ` [PATCH 10/15] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v3 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 11/15] mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 12/15] mm/migrate: new memory migration helper for use with device memory v4 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 13/15] mm/migrate: migrate_vma() unmap page from vma while collecting pages Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 14/15] mm/migrate: support un-addressable ZONE_DEVICE page in migration v2 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-28 18:00 ` [PATCH 15/15] mm/migrate: allow migrate_vma() to alloc new page on empty entry v3 Jérôme Glisse
2017-06-28 18:00   ` Jérôme Glisse
2017-06-30  5:32 ` [PATCH 00/15] HMM (Heterogeneous Memory Management) v24 John Hubbard
2017-06-30  5:32   ` John Hubbard
2017-06-30 19:49   ` Jerome Glisse [this message]
2017-06-30 19:49     ` Jerome Glisse
2017-07-19 11:48 ` Yisheng Xie
2017-07-19 11:48   ` Yisheng Xie
2017-07-20 17:18   ` Jerome Glisse
2017-07-20 17:18     ` Jerome Glisse
2017-07-21  9:03     ` Yisheng Xie
2017-07-21  9:03       ` Yisheng Xie

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=20170630194956.GB4275@redhat.com \
    --to=jglisse@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=dnellans@nvidia.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.