[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84d83148-41a3-d0e8-be80-56187a8e8ccc@nvidia.com>
Date: Tue, 11 Jul 2017 12:35:03 -0700
From: Evgeny Baskakov <ebaskakov@...dia.com>
To: Jerome Glisse <jglisse@...hat.com>
CC: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
John Hubbard <jhubbard@...dia.com>,
David Nellans <dnellans@...dia.com>,
Mark Hairgrove <mhairgrove@...dia.com>,
Sherry Cheung <SCheung@...dia.com>,
Subhash Gutti <sgutti@...dia.com>
Subject: Re: [HMM 12/15] mm/migrate: new memory migration helper for use with
device memory v4
On 7/11/17 11:49 AM, Jerome Glisse wrote:
>
> What are the symptoms ? The program just stop making any progress and you
> trigger a sysrequest to dump current states of each threads ? In this
> log i don't see migration_entry_wait() anymore but it seems to be waiting
> on page lock so there might be 2 issues here.
>
> Jérôme
That is correct, the program is not making any progress.
The stack traces in the kernel log are produced by a "sysrq w" (blocked
tasks) command.
Thanks,
--
Evgeny Baskakov
NVIDIA
Powered by blists - more mailing lists