Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp2855934imb; Mon, 4 Mar 2019 16:23:45 -0800 (PST) X-Google-Smtp-Source: AHgI3IbZULdxCMWTc0ACrq7LrtW808Tunm1gil43aMgqoQTFw5VCkajF1VQdBHKe52vz9V3sOH3c X-Received: by 2002:a62:445a:: with SMTP id r87mr22257484pfa.13.1551745424964; Mon, 04 Mar 2019 16:23:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551745424; cv=none; d=google.com; s=arc-20160816; b=YAqkAMg7brn2f1lpKedlRPu0r637k7BsJ3fTAvzgvnGF9AQQZY636rrOYhgvjQuJOJ TlsKiT7WqANRKAT2fHoroyXvSXT+pXJ+wHmC97dhID0DphBVxzQ+KKCchM5ux9xK8YjV I+TZnOc1MGMFvQt21qEcCQpXEZw3WMYFfYOUkWHyyAAOg4fCZQSbZFdE0GVAyQVCABog 19dJqOD3OBtVPG3RSMXagbtK0he5VYu/L1BN61HZdb8xOmj78UJhDxs65M/WUrY34N0v QuvL6UXLlkh1HsZuxvXUleE13NYgEhLp8PfYuT1U0y5tZ5ZCczHEYWJt0J2ol8zLqB1n 8Gtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=+u1vnxxvwLuIZn1sOdmq1XYMqV8SvqLOtudXjWlBMFI=; b=FllXakI0l3qyf+Gq8FUGdLWNKU0XSQYICtEgRdjLEzG01CV5y4bK7cVRkbjbo96GwC MyPGrY2ZHNrzCSAizW0bJN9Rh1Vv6/vQbJKMu5KT4Uze5DoRhgmRcYx00VDlLSqPd4jq bx+6GJ627JQJ17Bx7APXkjK90dCenT6oM6Ak9OyrUAUS7aVCYqsJBK8Ss0QZEKG4+hsU e8JC6eh3FhZuQ9MMf9xV7ORj+wBTY26B1mw5GQhpW5pxOSWpB8evbrB60hTzFhO4I5hv AtmVpEJY+7KYskfSPtcUGk5NbuIhjgXgrNar+YLnZyskBxTjHRFavLYnCX+x0RkcbboA uTdw== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n11si6033679pgv.491.2019.03.04.16.23.29; Mon, 04 Mar 2019 16:23:44 -0800 (PST) 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726850AbfCEAWE (ORCPT + 99 others); Mon, 4 Mar 2019 19:22:04 -0500 Received: from 59-120-53-16.HINET-IP.hinet.net ([59.120.53.16]:28879 "EHLO ATCSQR.andestech.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726066AbfCEAWE (ORCPT ); Mon, 4 Mar 2019 19:22:04 -0500 Received: from mail.andestech.com (atcpcs16.andestech.com [10.0.1.222]) by ATCSQR.andestech.com with ESMTP id x250KMj2014854; Tue, 5 Mar 2019 08:20:22 +0800 (GMT-8) (envelope-from vincentc@andestech.com) Received: from andestech.com (10.0.15.65) by ATCPCS16.andestech.com (10.0.1.222) with Microsoft SMTP Server id 14.3.123.3; Tue, 5 Mar 2019 08:21:20 +0800 Date: Tue, 5 Mar 2019 08:21:17 +0800 From: Vincent Chen To: Palmer Dabbelt CC: "aou@eecs.berkeley.edu" , "ebiederm@xmission.com" , Jim Wilson , Arnd Bergmann , "linux-riscv@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "deanbo422@gmail.com" Subject: Re: [PATCH 0/3] riscv: Fix debug instruction check and support trap-based WARN() Message-ID: <20190305002116.GA5887@andestech.com> References: <1551349891-22683-1-git-send-email-vincentc@andestech.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [10.0.15.65] X-DNSRBL: X-MAIL: ATCSQR.andestech.com x250KMj2014854 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 05, 2019 at 04:35:08AM +0800, Palmer Dabbelt wrote: > On Thu, 28 Feb 2019 02:31:28 PST (-0800), vincentc@andestech.com wrote: > > The handler for the debug exception will call is_valid_bugaddr(bugaddr) to > > check if the instruction in bugaddr is a real debug instruction. However, > > the expected instruction, ebreak, is possibly translated to c.ebreak by > > assmebler when C extension is supported. This patchset will add c.ebreak > > into the check mechanism. In addition, BUG() is currently unable to work in > > the kernel module due to an inappropriated condition in is_valid_bugaddr(). > > This issue will be fixed in this patchset. Finally, this patchset enables > > WARN() related functions to trap the code to help developers debug it. > > > > > > > > > > > > Vincent Chen (3): > > riscv: Add the support for c.ebreak check in is_valid_bugaddr() > > riscv: Support BUG() in kernel module > > riscv: Make WARN() related functions able to trigger a trap exception > > I'm finding this patch set a bit hard to follow, and I think it has more diff > than is necessary. For example, the first patch introduces a new die() only to > have it removed by the third patch. There's also some unnecessary > non-functional diff, like > > @@ -149,12 +161,13 @@ int is_valid_bugaddr(unsigned long pc) > if (probe_kernel_address((bug_insn_t *)pc, insn)) > return 0; > if ((insn & __INSN_LENGTH_MASK) == __INSN_LENGTH_32) > - return insn == __BUG_INSN_32; > + return (insn == __BUG_INSN_32); > else > - return (insn & __COMPRESSED_INSN_MASK) == __BUG_INSN_16; > + return ((insn & __COMPRESSED_INSN_MASK) == __BUG_INSN_16); > } > #endif /* CONFIG_GENERIC_BUG */ > > + > void __init trap_init(void) > { > /* > > I like the idea of the patch set, though. Do you have time to clean it up and > submit a v2? OK, I will improve it and submit a v2 patch.