Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp294324ybi; Tue, 18 Jun 2019 23:03:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqzprASfIoDFuqRqpUhVkEhS2IdbqbalK6aNfMCK0kJEmR3y5y/cDICzEPtfggDsC0l+BIX3 X-Received: by 2002:a63:1658:: with SMTP id 24mr5473561pgw.167.1560924187414; Tue, 18 Jun 2019 23:03:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560924187; cv=none; d=google.com; s=arc-20160816; b=wzQfX69zB9CZSQw5Vl2E0Z90yjgDEgms8qWTh3fy7VZm/Tn8Dj9D7ojfZrtObh7H5k VjcrsUg405K2s01ff/L6+WfNTjG/WfRcTJOi7VxLL8+jBQdq1en9pN6EAhJdK5fIrnmf ymO4RIXLDx3W1cUlqDTCQH9ln5f41TDZNFSo/oCfzU7hswK++4tb7zmnDX62gaB59lHi RNuFsk3g5ZDKuIJS0/qo2gAe27SRgLGjgCg3FAZwUZiNqOwox9jmrni2QbFKELMVzTZp brOrNZl6HdO7aq1/As5r8HARoOlKiEzAordIMiaFPB3LKkG+A1w9F/+2RH1MhGY3fXod vppw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :references:cc:to:subject:from; bh=739WvKBcEUvL0+Zitq71eyPDVFgIjEtZrY71f3bYIpA=; b=qfiBMdO9YM81PRLSNy9TKjmB3rksAYHLhYiajioXmKXyBMysL2LH3DjIXdWxHTkZBg AcsIvczfX1ysdYl670mH3AYLsOCGHTpleW8VQ3W1NejRAmDN0tKmcWHmxcG+Xet1eN7E HAu9xE52w9iZKH/t8jOvNqhhhsacgRrt2feEBF2HcSeG2EP4WOPk6WjlNkEh+J7QSKbu gun4wmsS0kS+yammZpfGxArAHPqwiKhJ7cmWy5QlOMI8Ni2ShDTXxvqdqwQhOaVEO0wT UIT/gWOEq4G8udYyE6G1lsimNUAkPaGPHV0lxZavUi73bqupBSnPEs6OSBGgapz62AHV fiJw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j71si2198038pgd.167.2019.06.18.23.02.50; Tue, 18 Jun 2019 23:03:07 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=ibm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730428AbfFSGCq (ORCPT + 99 others); Wed, 19 Jun 2019 02:02:46 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:22168 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725866AbfFSGCq (ORCPT ); Wed, 19 Jun 2019 02:02:46 -0400 Received: from pps.filterd (m0098417.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x5J627wV124765 for ; Wed, 19 Jun 2019 02:02:44 -0400 Received: from e06smtp04.uk.ibm.com (e06smtp04.uk.ibm.com [195.75.94.100]) by mx0a-001b2d01.pphosted.com with ESMTP id 2t7ephhuq0-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 19 Jun 2019 02:02:44 -0400 Received: from localhost by e06smtp04.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 19 Jun 2019 07:02:35 +0100 Received: from b06avi18626390.portsmouth.uk.ibm.com (9.149.26.192) by e06smtp04.uk.ibm.com (192.168.101.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 19 Jun 2019 07:02:32 +0100 Received: from d06av23.portsmouth.uk.ibm.com (d06av23.portsmouth.uk.ibm.com [9.149.105.59]) by b06avi18626390.portsmouth.uk.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x5J62Ndg33882608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 19 Jun 2019 06:02:23 GMT Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 44450A4055; Wed, 19 Jun 2019 06:02:31 +0000 (GMT) Received: from d06av23.portsmouth.uk.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A1C66A4051; Wed, 19 Jun 2019 06:02:29 +0000 (GMT) Received: from [9.124.31.60] (unknown [9.124.31.60]) by d06av23.portsmouth.uk.ibm.com (Postfix) with ESMTP; Wed, 19 Jun 2019 06:02:29 +0000 (GMT) From: Ravi Bangoria Subject: Re: [PATCH 4/5] Powerpc/hw-breakpoint: Optimize disable path To: Michael Neuling Cc: mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, npiggin@gmail.com, christophe.leroy@c-s.fr, naveen.n.rao@linux.vnet.ibm.com, Ravi Bangoria References: <20190618042732.5582-1-ravi.bangoria@linux.ibm.com> <20190618042732.5582-5-ravi.bangoria@linux.ibm.com> Date: Wed, 19 Jun 2019 11:32:28 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 19061906-0016-0000-0000-0000028A5A0F X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19061906-0017-0000-0000-000032E7AE7E Message-Id: X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-06-19_03:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=361 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1906190049 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/18/19 11:45 AM, Michael Neuling wrote: > On Tue, 2019-06-18 at 09:57 +0530, Ravi Bangoria wrote: >> Directly setting dawr and dawrx with 0 should be enough to >> disable watchpoint. No need to reset individual bits in >> variable and then set in hw. > > This seems like a pointless optimisation to me. > > I'm all for adding more code/complexity if it buys us some performance, but I > can't imagine this is a fast path (nor have you stated any performance > benefits). This gets called from sched_switch. I expected the improvement when we switch from monitored process to non-monitored process. With such scenario, I tried to measure the difference in execution time of set_dawr but I don't see any improvement. So I'll drop the patch.