Received: by 2002:a5d:9c59:0:0:0:0:0 with SMTP id 25csp2473169iof; Wed, 8 Jun 2022 05:49:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw+kLJsL+Gzw1Tv74XdcV+SdyDDtXtQEAXJsT2XGJYxGeY9/huhqBCBht5Q8txNFwTz1/DD X-Received: by 2002:a17:902:aa4b:b0:164:11ad:af0f with SMTP id c11-20020a170902aa4b00b0016411adaf0fmr34344639plr.54.1654692567084; Wed, 08 Jun 2022 05:49:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1654692567; cv=none; d=google.com; s=arc-20160816; b=gStj93gpfYVUmAcRpTSsTckDA/JDYjath0sAzTBrFLJqe42uOSOpIXAQM2jrvbPjv1 AwR0VgeeewIMFj/ZtuWV1IqgSrutM+k9bnuCgmHMKfYy2RDi57qBRnRXBnV85d9xZdsE AE5TdoqXY0VZZAU2jYOaDb+CH0TGB6R8N8GVrBtZ3zX8LxRW+QaQARNvw7sr2QeMzYCb kjBP4A4MWbXLPLGgkcqK8fxHe+T3nz+N/Y7X0/Tm2S3E0wTmrdAszYE0dxI1hFtF0L5K qC9Ah+/WBBzliPvrypEX9yXDdY9X/cBp351ZYraoOI1FjWIROcGQhKMc+DOgMTvT59ox dzCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=n7JpFyUZhQORnjRJpPV+q5mdIFu/JI18mjMTlPHX3cs=; b=vafmtlXrKJRVjD91TW7kNZ3uw04smNgBn7YHkamEbe71aubz46RNandp6RUH7/LSwJ 4H6Wwk0bj9xr2/ALe8j/2j2RonId5+apPVgkHjFs7TpZuOlUQLe/iA/Yrv0LR59bAXe5 5qUAiZuPjLQxh/Ua5osp7WkRRNT/Jpef4/xxlTedXZ+J5Vq6O0FxmajBs4B9b2zMqtB+ fELCTHyCk6RJvjs/VQ4DUTi/Yb6d9UqeQcFMV7/o6TnnQfTDEIFUUDBC3flV4o8ECd/n Gb9jEQDWX5E3L90iPmx8A13tsYZ36DdrttQEsOjIobnfbtFeIxgrUWZUaML63puLiGk/ 4AcQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=sntech.de Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id d1-20020a056a0024c100b0050fbf917944si32335146pfv.51.2022.06.08.05.49.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Jun 2022 05:49:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=sntech.de Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id B5DD21E440E; Wed, 8 Jun 2022 05:24:00 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239160AbiFHMXw convert rfc822-to-8bit (ORCPT + 99 others); Wed, 8 Jun 2022 08:23:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54982 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239113AbiFHMXl (ORCPT ); Wed, 8 Jun 2022 08:23:41 -0400 Received: from gloria.sntech.de (gloria.sntech.de [185.11.138.130]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 91AFB1C590E for ; Wed, 8 Jun 2022 05:23:38 -0700 (PDT) Received: from ip5b412258.dynamic.kabel-deutschland.de ([91.65.34.88] helo=diego.localnet) by gloria.sntech.de with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1nyuij-0006jK-8c; Wed, 08 Jun 2022 14:23:33 +0200 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Palmer Dabbelt , Ron Economos Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [GIT PULL] RISC-V Patches for the 5.19 Merge Window, Part 1 Date: Wed, 08 Jun 2022 14:23:32 +0200 Message-ID: <1767879.8hzESeGDPO@diego> In-Reply-To: <06c46bde-5d3f-9123-93b4-9e0f3824ac3a@w6rz.net> References: <827324415.0ifERbkFSE@diego> <06c46bde-5d3f-9123-93b4-9e0f3824ac3a@w6rz.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="iso-8859-1" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Mittwoch, 8. Juni 2022, 02:12:47 CEST schrieb Ron Economos: > On 6/7/22 4:36 PM, Heiko St?bner wrote: > > Am Dienstag, 7. Juni 2022, 22:46:52 CEST schrieb Ron Economos: > >> On 5/31/22 10:13 AM, Palmer Dabbelt wrote: > >>> The following changes since commit 9282d0996936c5fbf877c0d096a3feb456c878ad: > >>> > >>> csky: Move to generic ticket-spinlock (2022-05-11 11:50:15 -0700) > >>> > >>> are available in the Git repository at: > >>> > >>> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git tags/riscv-for-linus-5.19-mw0 > >>> > >>> for you to fetch changes up to 7699f7aacf3ebfee51c670b6f796b2797f0f7487: > >>> > >>> RISC-V: Prepare dropping week attribute from arch_kexec_apply_relocations[_add] (2022-05-30 16:04:37 -0700) > >>> > >>> ---------------------------------------------------------------- > >>> RISC-V Patches for the 5.19 Merge Window, Part 1 > >>> > >>> * Support for the Svpbmt extension, which allows memory attributes to be > >>> encoded in pages. > >>> > >>> > >>> Heiko Stuebner (12): > >>> riscv: integrate alternatives better into the main architecture > >>> riscv: allow different stages with alternatives > >>> riscv: implement module alternatives > >>> riscv: implement ALTERNATIVE_2 macro > >>> riscv: extend concatenated alternatives-lines to the same length > >>> riscv: prevent compressed instructions in alternatives > >>> riscv: move boot alternatives to after fill_hwcap > >>> riscv: Fix accessing pfn bits in PTEs for non-32bit variants > >>> riscv: add RISC-V Svpbmt extension support > >>> riscv: remove FIXMAP_PAGE_IO and fall back to its default value > >>> riscv: don't use global static vars to store alternative data > >>> riscv: add memory-type errata for T-Head > >>> > >> An issue was found on the HiFive Unmatched with the 5.19-rc1 kernel. The > >> following warning occurs during boot: > >> > >> riscv64 kernel: > >> ---------------------------------------------------------------- > >> riscv64 kernel: WARNING: Missing the following errata may cause > >> potential issues > >> riscv64 kernel: SiFive Errata[0]:cip-453 > >> riscv64 kernel: SiFive Errata[1]:cip-1200 > >> riscv64 kernel: Please enable the corresponding Kconfig to apply them > >> riscv64 kernel: > >> ---------------------------------------------------------------- > >> > >> I've manually bisected the problem to this commit: > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff689fd21cb13098305bae3f8d0c0065df2e2fc1 > > hmm, on first glance I can't really see how that specific commit would > > affect Sifive erratas. Patches directly before this one did change > > alternative / errata things though. > > > > (1) From looking at your output, it seems at least CONFIG_ERRATA_SIFIVE > > is enabled as the general sifive errata code is running, but are the > > individual erratas also still enabled in your config? > > They're default=y forever and weren't touched by the svpbmt series, > > but it'd be nice to know how the config looks, to see if the Kconfig > > settings are strange somewhere > > > > > > (2) Going from the list on > > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/?h=ff689fd21cb13098305bae3f8d0c0065df2e2fc1 > > > > could you maybe check if it's really working with the parent of the > > commit you found. (i.e. patches before the svpbmt addition). > > > > Also just to be sure, it still works correctly with 5.18, right? > > > > > > Thanks > > Heiko > > > > > Yes, that commit was surprising. I also thought it would have been one > of the previous "alternatives" commits. But I tested them all, and the > warning only appears with the "add RISC-V Svpbmt extension support" > commit. In other words, "git checkout 100631b" works fine, but "git > checkout ff689fd" does not. after talking with Ron a bit more, we came across the finding that the warnings actually happen later in the boot process, pointing to modules. Which lead me to [0] for explanation of the issue and a possible fix. [0] https://lore.kernel.org/r/20220608120849.1695191-1-heiko@sntech.de/