From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1B465C432C0 for ; Sat, 23 Nov 2019 03:14:11 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id DF35D2071C for ; Sat, 23 Nov 2019 03:14:10 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=sifive.com header.i=@sifive.com header.b="aqNVL7xV" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726638AbfKWDNt (ORCPT ); Fri, 22 Nov 2019 22:13:49 -0500 Received: from mail-il1-f193.google.com ([209.85.166.193]:46616 "EHLO mail-il1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726085AbfKWDNs (ORCPT ); Fri, 22 Nov 2019 22:13:48 -0500 Received: by mail-il1-f193.google.com with SMTP id q1so9086476ile.13 for ; Fri, 22 Nov 2019 19:13:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:from:to:cc:subject:in-reply-to:message-id:references :user-agent:mime-version; bh=Qdi4xJuJjta2u9BrlQQY9FpGcN9H5nfrgZO9QjBGHhk=; b=aqNVL7xVNyuMCGR0fX2PLBMKf2jeELkaON/ndcZFsGUF+jI7+VKi/S1FP3MFvVBPHD oTgap/KMM07d9IdlSVF54qH7OxrSRXqxynmzFns5iePgt2kS2gQwaqnqmXSdE+JNncQB pZe/9aDETflvjjsHP6xHIQGcJzPqyKXAUgiG2xsQBHt3vxJUIBf2WSUp5epBGDqUbYUJ pvm6ccpqLMUz4Nwqnak0d80xlHMrt/S2NdQhEG1OAdFVzBJbam+gJb8LPqmVSFXSr8Dv 9xvDq45I9HtFq4kT3eebp7TY9GTXGii6CXfcSaR7+g59X28giS/IakHFPFhXB5a3u1OR wdEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:message-id :references:user-agent:mime-version; bh=Qdi4xJuJjta2u9BrlQQY9FpGcN9H5nfrgZO9QjBGHhk=; b=Sm8CgICdpYr4VRgWvtT3Ev0RQhWYRbU5HZLQvimnz2hptrht/XBa4MfqpTPpkybRWz TDds52+LqdjWeKAF0HYpdn4VXVglw+sAD/mo/gaV+37SOVNqlvwp+T1a/2PCL4E3NGcy QxvaCTpsM9D4t4uC47eT/F7ZS6COXrj4hBngqfKSc6/5hTNu1vghEwlvfEeg20ThFzAo IlnAzxdYxf1ZqsgQ5DoZOzV5i0Zzb+MSrBWI9XXYO94q3Kv19HiPQ7frlbyss1G4PUDd tnQmC8T/KAB/gE7eouosPgKUIe4EMZBiVgdQNRNr4UkxjLvJoFQi+PpPBK5/19PiCsg/ K3nA== X-Gm-Message-State: APjAAAWz+jktTeIr5tZG9HjE/BSaDXqNtlCuOBUTkpo7REhZXnQCR9n8 234pTMYQkufk3ZUd94BhwkksQErcNZM= X-Google-Smtp-Source: APXvYqwLehW6jT9h73wjWDikxsJDU3y94CGY9KVHlLXmuBEF+b78ooLizwVHu0RmqsPNgCJOLq+t1w== X-Received: by 2002:a05:6638:91:: with SMTP id v17mr12217947jao.97.1574478827962; Fri, 22 Nov 2019 19:13:47 -0800 (PST) Received: from localhost ([64.62.168.194]) by smtp.gmail.com with ESMTPSA id t6sm3468008ilq.53.2019.11.22.19.13.46 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Nov 2019 19:13:47 -0800 (PST) Date: Fri, 22 Nov 2019 19:13:45 -0800 (PST) From: Paul Walmsley X-X-Sender: paulw@viisi.sifive.com To: Palmer Dabbelt cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/2] riscv: defconfigs: enable debugging options In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21.9999 (DEB 301 2018-08-15) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 22 Nov 2019, Palmer Dabbelt wrote: > Does it make sense to turn on some CONFIG_*_SELFTEST entries as well? I know > I've found RISC-V bugs with ATOMIC64_SELFTEST before, but they do take a while > to run. I just turned on > > diff --git a/arch/riscv/configs/defconfig b/arch/riscv/configs/defconfig > index 420a0dbef386..90001c3746cd 100644 > --- a/arch/riscv/configs/defconfig > +++ b/arch/riscv/configs/defconfig > @@ -100,4 +100,18 @@ CONFIG_9P_FS=y > CONFIG_CRYPTO_USER_API_HASH=y > CONFIG_CRYPTO_DEV_VIRTIO=y > CONFIG_PRINTK_TIME=y > +CONFIG_DEBUG_RT_MUTEXES=y > +CONFIG_DEBUG_SPINLOCK=y > +CONFIG_DEBUG_MUTEXES=y > +CONFIG_DEBUG_RWSEMS=y > +CONFIG_DEBUG_ATOMIC_SLEEP=y > +CONFIG_DEBUG_LOCKING_API_SELFTESTS=y > +CONFIG_LOCK_TORTURE_TEST=y > +CONFIG_WW_MUTEX_SELFTEST=y > +CONFIG_RCU_PERF_TEST=y > +CONFIG_RCU_TORTURE_TEST=y > # CONFIG_RCU_TRACE is not set > +CONFIG_PERCPU_TEST=m > +CONFIG_ATOMIC64_SELFTEST=y > +CONFIG_TEST_LKM=m > +CONFIG_TEST_USER_COPY=m > > as an experiment and OE looks like it's still functional, but it looks like the > lock torture stuff keeps running and the RCU torture can't run at the same > time. Thanks - that's a good idea. Will take a look to see what tests can be enabled that don't take too much time (and don't conflict) and will put together another patch. If anyone has any feedback or suggestions here, they would be welcome. - Paul