[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [PATCH] mm, oom: distinguish blockable mode for mmu notifiers
- To: Michal Hocko <mhocko@xxxxxxxxxx>
- From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 20 Jul 2018 16:01:25 -0700
- Cc: kvm@xxxxxxxxxxxxxxx, Radim Krčmář <rkrcmar@xxxxxxxxxx>, David Airlie <airlied@xxxxxxxx>, Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx>, Sudeep Dutt <sudeep.dutt@xxxxxxxxx>, dri-devel@xxxxxxxxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, Andrea Arcangeli <aarcange@xxxxxxxxxx>, "David \(ChunMing\) Zhou" <David1.Zhou@xxxxxxx>, Dimitri Sivanich <sivanich@xxxxxxx>, linux-rdma@xxxxxxxxxxxxxxx, amd-gfx@xxxxxxxxxxxxxxxxxxxxx, Jason Gunthorpe <jgg@xxxxxxxx>, Doug Ledford <dledford@xxxxxxxxxx>, David Rientjes <rientjes@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, intel-gfx@xxxxxxxxxxxxxxxxxxxxx, Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx>, Leon Romanovsky <leonro@xxxxxxxxxxxx>, Jérôme Glisse <jglisse@xxxxxxxxxx>, Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx>, Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Mike Marciniszyn <mike.marciniszyn@xxxxxxxxx>, Felix Kuehling <felix.kuehling@xxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Christian König <christian.koenig@xxxxxxx>, Ashutosh Dixit <ashutosh.dixit@xxxxxxxxx>, Alex Deucher <alexander.deucher@xxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>, Dennis Dalessandro <dennis.dalessandro@xxxxxxxxx>
- Delivery-date: Fri, 20 Jul 2018 23:01:55 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Tue, 17 Jul 2018 10:12:01 +0200 Michal Hocko <mhocko@xxxxxxxxxx> wrote:
> > Any suggestions regarding how the driver developers can test this code
> > path? I don't think we presently have a way to fake an oom-killing
> > event? Perhaps we should add such a thing, given the problems we're
> > having with that feature.
>
> The simplest way is to wrap an userspace code which uses these notifiers
> into a memcg and set the hard limit to hit the oom. This can be done
> e.g. after the test faults in all the mmu notifier managed memory and
> set the hard limit to something really small. Then we are looking for a
> proper process tear down.
Chances are, some of the intended audience don't know how to do this
and will either have to hunt down a lot of documentation or will just
not test it. But we want them to test it, so a little worked step-by-step
example would help things along please.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel
|
