[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191211155130.gk5qcuahzo2w3qyh@box>
Date: Wed, 11 Dec 2019 18:51:30 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Mircea CIRJALIU - MELIU <mcirjaliu@...defender.com>
Cc: "linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jerome Glisse <jglisse@...hat.com>,
Paolo Bonzini <pbonzini@...hat.com>,
"aarcange@...hat.com" <aarcange@...hat.com>
Subject: Re: [RFC PATCH v1 1/4] mm/remote_mapping: mirror a process address
space
On Wed, Dec 11, 2019 at 09:29:17AM +0000, Mircea CIRJALIU - MELIU wrote:
> Use a device to inspect another process address space via page table mirroring.
> Give this device a source process PID via an ioctl(), then use mmap()
> to analyze the source process address space like an ordinary file.
> Process address space mirroring is limited to anon VMAs.
> The device mirrors page tables on demand (faults) and invalidates them
> by listening to MMU notifier events.
It's way to brief to justify the new interface. Use cases? Why current
intefaces are not enough?
There's nothing in the description that would convince me to look at the
code.
--
Kirill A. Shutemov
Powered by blists - more mailing lists