From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753877AbcKIRjT (ORCPT ); Wed, 9 Nov 2016 12:39:19 -0500 Received: from mail-qt0-f179.google.com ([209.85.216.179]:35017 "EHLO mail-qt0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752546AbcKIRjS (ORCPT ); Wed, 9 Nov 2016 12:39:18 -0500 Subject: Re: [PATCH V2 3/5] arm64: hw_breakpoint: Handle inexact watchpoint addresses To: Pavel Labath , Will Deacon References: <22f4d20911e39efa0b8a6f7082d6839b80bb16b0.1476941895.git.panand@redhat.com> <20161108032941.GC20591@arm.com> Cc: Mark Rutland , linux-arm-kernel , linux-kernel@vger.kernel.org, Jan Kratochvil , onestero@redhat.com, Pavel Labath From: Pratyush Anand Message-ID: Date: Wed, 9 Nov 2016 23:09:10 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 08 November 2016 05:28 PM, Pavel Labath wrote: >>> + if (min_dist > 0 && min_dist != -1) { >>> >> + /* No exact match found. */ >>> >> + wp = slots[closest_match]; >>> >> + info = counter_arch_bp(wp); >>> >> + info->trigger = addr; >>> >> + perf_bp_event(wp, regs); >>> >> + } >> > >> > Why don't we need to bother with the stepping in the case of a non-exact >> > match? > Good catch. I think we do. I must have dropped that part somehow. > > Pratyush, could you include the attached fixup in the next batch? Ok, will do. ~Pratyush