From: Joerg Roedel jroe...@suse.de
This notifier closes an important gap in the current
mmu_notifier implementation, the existing call-backs are
called too early or too late to reliably manage a non-CPU
TLB. Specifically, invalidate_range_start() is called when
all pages are still mapped and
From: Joerg Roedel jroe...@suse.de
This notifier closes two important gaps with the current
invalidate_range_start()/end() notifiers. The _start() part
is called when all pages are still mapped while the _end()
notifier is called when all pages are potentially unmapped
and already freed.
This
From: Joerg Roedel jroe...@suse.de
This notifier closes two important gaps with the current
invalidate_range_start()/end() notifiers. The _start() part
is called when all pages are still mapped while the _end()
notifier is called when all pages are potentially unmapped
and already freed.
This
On Thu, 24 Jul 2014 16:35:39 +0200
Joerg Roedel j...@8bytes.org wrote:
From: Joerg Roedel jroe...@suse.de
This notifier closes an important gap with the current
invalidate_range_start()/end() notifiers. The _start() part
is called when all pages are still mapped while the _end()
notifier
On Fri, Jul 25, 2014 at 01:16:39PM -0700, Jesse Barnes wrote:
On Thu, 24 Jul 2014 16:35:39 +0200
Joerg Roedel j...@8bytes.org wrote:
From: Joerg Roedel jroe...@suse.de
This notifier closes an important gap with the current
invalidate_range_start()/end() notifiers. The _start() part
On Fri, 25 Jul 2014 23:38:06 +0200
Joerg Roedel j...@8bytes.org wrote:
On Fri, Jul 25, 2014 at 01:16:39PM -0700, Jesse Barnes wrote:
To allow managing external TLBs the MMU-notifiers need to
catch the moment when pages are unmapped but not yet freed.
This new notifier catches that
On Fri, Jul 25, 2014 at 11:38:06PM +0200, Joerg Roedel wrote:
On Fri, Jul 25, 2014 at 01:16:39PM -0700, Jesse Barnes wrote:
To allow managing external TLBs the MMU-notifiers need to
catch the moment when pages are unmapped but not yet freed.
This new notifier catches that moment and
On Fri, Jul 25, 2014 at 02:42:13PM -0700, Jesse Barnes wrote:
On Fri, 25 Jul 2014 23:38:06 +0200
Joerg Roedel j...@8bytes.org wrote:
I though about removing the need for invalidate_range_end too when
writing the patches, and possible solutions are
1) Add
From: Joerg Roedel jroe...@suse.de
This notifier closes an important gap with the current
invalidate_range_start()/end() notifiers. The _start() part
is called when all pages are still mapped while the _end()
notifier is called when all pages are potentially unmapped
and already freed.
This does
