Re: [PATCH] mm/mmn: prevent unpaired invalidate_start and invalidate_end with non-blocking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Jason Gunthorpe <jgg@xxxxxxxxxxxx>
Subject: Re: [PATCH] mm/mmn: prevent unpaired invalidate_start and invalidate_end with non-blocking
From: Christoph Hellwig <hch@xxxxxx>
Date: Thu, 8 Aug 2019 09:00:02 +0200
Cc: "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>, Michal Hocko <mhocko@xxxxxxxx>, Jérôme Glisse <jglisse@xxxxxxxxxx>, Andrea Arcangeli <aarcange@xxxxxxxxxx>, Christoph Hellwig <hch@xxxxxx>
In-reply-to: <20190807191627.GA3008@ziepe.ca>
References: <20190807191627.GA3008@ziepe.ca>
User-agent: Mutt/1.5.17 (2007-11-01)

This looks like a pretty big hammer, but probably about the best we can
do until locking moves to common code..

References:
- [PATCH] mm/mmn: prevent unpaired invalidate_start and invalidate_end with non-blocking
  - From: Jason Gunthorpe

Prev by Date: Re: [PATCH 04/15] mm: remove the pgmap field from struct hmm_vma_walk
Next by Date: Re: [PATCH] nouveau/hmm: map pages after migration
Previous by thread: [PATCH] mm/mmn: prevent unpaired invalidate_start and invalidate_end with non-blocking
Next by thread: Re: [PATCH] mm/mmn: prevent unpaired invalidate_start and invalidate_end with non-blocking
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux