From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752168AbcD3E7w (ORCPT ); Sat, 30 Apr 2016 00:59:52 -0400 Received: from mga14.intel.com ([192.55.52.115]:48187 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751062AbcD3E7v (ORCPT ); Sat, 30 Apr 2016 00:59:51 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,554,1455004800"; d="scan'208";a="795597310" From: Alexander Shishkin To: Mathieu Poirier Cc: Peter Zijlstra , Thomas Gleixner , x86@kernel.org, Borislav Petkov , Ingo Molnar , "linux-kernel\@vger.kernel.org" , vince@deater.net, Stephane Eranian , Arnaldo Carvalho de Melo Subject: Re: [PATCH v2 5/7] perf: Introduce address range filtering In-Reply-To: References: <1461771888-10409-1-git-send-email-alexander.shishkin@linux.intel.com> <1461771888-10409-6-git-send-email-alexander.shishkin@linux.intel.com> User-Agent: Notmuch/0.21 (http://notmuchmail.org) Emacs/24.5.1 (x86_64-pc-linux-gnu) Date: Sat, 30 Apr 2016 07:59:46 +0300 Message-ID: <87wpnfvghp.fsf@ashishki-desk.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Mathieu Poirier 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