Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753446Ab3DURFI (ORCPT ); Sun, 21 Apr 2013 13:05:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:61153 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752848Ab3DURFH (ORCPT ); Sun, 21 Apr 2013 13:05:07 -0400 Date: Sun, 21 Apr 2013 19:02:02 +0200 From: Oleg Nesterov To: Jacob Shin Cc: Ingo Molnar , Peter Zijlstra , Arnaldo Carvalho de Melo , "H. Peter Anvin" , Thomas Gleixner , x86@kernel.org, Stephane Eranian , Jiri Olsa , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/5] perf: Add hardware breakpoint address mask Message-ID: <20130421170202.GA5358@redhat.com> References: <1365528113-5458-1-git-send-email-jacob.shin@amd.com> <20130420165334.GA14814@redhat.com> <20130420224757.GB6155@jshin-Toonie> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130420224757.GB6155@jshin-Toonie> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 972 Lines: 28 On 04/20, Jacob Shin wrote: > > On Sat, Apr 20, 2013 at 06:53:34PM +0200, Oleg Nesterov wrote: > > > > And does attr.bp_len "contribute" to the mask? > > > > I mean, if bp_len == X86_BREAKPOINT_LEN_8, does this mean that > > bp_bp_addr_mask and (bp_bp_addr_mask | 7) have the same effect? > > Yes it has the same effect. OK, thanks... So this is the "natural" extension. Given that currently bp_addr should be aligned, bp_len could be already bp_mask but I guess it is too late to change this, so we need another field. Hmm. Perhaps arch_has_hw_breakpoint_addr_mask(void) should be turned into arch_validate_hw_breakpoint_addr_mask(bp) which should also check that (bp_addr & bp_addr_mask) == 0. But I won't insist. Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/