| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20091013064006.GC9470@elte.hu> Date: Tue, 13 Oct 2009 08:40:06 +0200 From: Ingo Molnar <mingo@...e.hu> To: Jason Gunthorpe <jgunthorpe@...idianresearch.com> Cc: Pavel Machek <pavel@....cz>, Roland Dreier <rdreier@...co.com>, Peter Zijlstra <peterz@...radead.org>, linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>, Anton Blanchard <anton@...ba.org>, general@...ts.openfabrics.org, akpm@...ux-foundation.org, torvalds@...ux-foundation.org, Jeff Squyres <jsquyres@...co.com> Subject: Re: [ofa-general] Re: [GIT PULL] please pull ummunotify * Jason Gunthorpe <jgunthorpe@...idianresearch.com> wrote: > On Mon, Oct 12, 2009 at 10:20:46PM +0200, Ingo Molnar wrote: > > It might be more acceptable because the flag-hint mechanism can at most > > cause over-flushing - while with perf events we might miss to invalidate > > a range altogether. > > Right. Overflushing is not important, but missing an event entirely is > not recoverable (at least within the current kernel APIs). So if we detect event loss in the perf event case (should not happen with sufficient buffering but it is a possibility the code should be prepared for) then we can just flush the [0,-1ULL] range, right? Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists