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
| ||
|
Date: Sat, 30 Apr 2016 07:59:46 +0300 From: Alexander Shishkin <alexander.shishkin@...ux.intel.com> To: Mathieu Poirier <mathieu.poirier@...aro.org> Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>, Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org, Borislav Petkov <bp@...en8.de>, Ingo Molnar <mingo@...hat.com>, "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>, vince@...ter.net, Stephane Eranian <eranian@...gle.com>, Arnaldo Carvalho de Melo <acme@...radead.org> Subject: Re: [PATCH v2 5/7] perf: Introduce address range filtering Mathieu Poirier <mathieu.poirier@...aro.org> writes: > I see two things in this work: [trimmed 700+ lines of context that had no purpose] > 1) A framework to deal with filters described in user space. > 2) An implementation for address filtering that will work for both > Intel and ARM. > > This will work well for address filtering (for both PT and CS) but > what happens when we want to introduce new filters? This is > inevitable and some filters will be architecture agnostic while others > architecture specific. Haven't we been through this [1] already? [1] http://marc.info/?l=linux-kernel&m=145013911827358 Regards, -- Alex
Powered by blists - more mailing lists