From: David Hildenbrand <david@redhat.com>
To: Alistair Popple <apopple@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, mhocko@suse.com, jhubbard@nvidia.com,
ying.huang@intel.com, osalvador@suse.de,
baolin.wang@linux.alibaba.com, ziy@nvidia.com,
shy828301@gmail.com, ryan.roberts@arm.com
Subject: Re: [PATCH 2/2] selftests/migration: Disable NUMA balancing and check migration status
Date: Wed, 9 Aug 2023 11:35:52 +0200 [thread overview]
Message-ID: <0950ca9c-4f39-f56a-fee9-5ee42ede86e3@redhat.com> (raw)
In-Reply-To: <20230807063945.911582-2-apopple@nvidia.com>
On 07.08.23 08:39, Alistair Popple wrote:
> The migration selftest was only checking the return code and not the
> status array for migration success/failure. Update the test to check
> both. This uncovered a bug in the return code handling of
> do_pages_move().
>
> Also disable NUMA balancing as that can lead to unexpected migration
> failures.
As raised in a sub-thread, is that still required with the mm-unstable
patch:
commit 3c471b04db7604974e3bea45e2d9c7c27a905536
Author: David Hildenbrand <david@redhat.com>
Date: Thu Aug 3 16:32:02 2023 +0200
mm/gup: reintroduce FOLL_NUMA as FOLL_HONOR_NUMA_FAULT
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-08-09 9:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 6:39 [PATCH 1/2] mm/migrate.c: Fix return code when migration fails Alistair Popple
2023-08-07 6:39 ` [PATCH 2/2] selftests/migration: Disable NUMA balancing and check migration status Alistair Popple
2023-08-07 9:15 ` Ryan Roberts
2023-08-07 12:41 ` Alistair Popple
2023-08-07 13:42 ` Ryan Roberts
2023-08-09 4:21 ` Alistair Popple
2023-08-09 9:34 ` David Hildenbrand
2023-08-09 13:39 ` Ryan Roberts
2023-08-10 8:23 ` Alistair Popple
2023-08-09 9:35 ` David Hildenbrand [this message]
2023-08-09 10:46 ` Alistair Popple
2023-08-07 8:39 ` [PATCH 1/2] mm/migrate.c: Fix return code when migration fails Michal Hocko
2023-08-07 12:31 ` Alistair Popple
2023-08-07 13:07 ` Michal Hocko
2023-08-09 4:10 ` Alistair Popple
2023-08-11 7:37 ` Huang, Ying
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=0950ca9c-4f39-f56a-fee9-5ee42ede86e3@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=jhubbard@nvidia.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=osalvador@suse.de \
--cc=ryan.roberts@arm.com \
--cc=shy828301@gmail.com \
--cc=ying.huang@intel.com \
--cc=ziy@nvidia.com \
/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