On Wed 07-11-18 14:04:13, Andrew Morton wrote:
> On Wed, 7 Nov 2018 11:18:29 +0100 Michal Hocko wrote:
>
> > From: Michal Hocko
> >
> > The memory offlining failure reporting is inconsistent and insufficient.
> > Some error paths simply do not report the failure to the log at all.
> > When we
On Wed 07-11-18 14:04:13, Andrew Morton wrote:
[...]
> Fix:
>
> ---
> a/mm/memory_hotplug.c~mm-memory_hotplug-print-reason-for-the-offlining-failure-fix
> +++ a/mm/memory_hotplug.c
> @@ -1576,7 +1576,7 @@ static int __ref __offline_pages(unsigne
> MIGRATE_MOVA
On Thu 08-11-18 11:53:21, Anshuman Khandual wrote:
>
>
> On 11/07/2018 03:48 PM, Michal Hocko wrote:
> > From: Michal Hocko
> >
> > The memory offlining failure reporting is inconsistent and insufficient.
> > Some error paths simply do not report the failure to the log at all.
> > When we do re
On 11/07/2018 03:48 PM, Michal Hocko wrote:
> From: Michal Hocko
>
> The memory offlining failure reporting is inconsistent and insufficient.
> Some error paths simply do not report the failure to the log at all.
> When we do report there are no details about the reason of the failure
> and th
On Wed, 7 Nov 2018 11:18:29 +0100 Michal Hocko wrote:
> From: Michal Hocko
>
> The memory offlining failure reporting is inconsistent and insufficient.
> Some error paths simply do not report the failure to the log at all.
> When we do report there are no details about the reason of the failur
From: Michal Hocko
The memory offlining failure reporting is inconsistent and insufficient.
Some error paths simply do not report the failure to the log at all.
When we do report there are no details about the reason of the failure
and there are several of them which makes memory offlining failur
6 matches
Mail list logo
