Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp6101858pxb; Thu, 27 Jan 2022 06:36:05 -0800 (PST) X-Google-Smtp-Source: ABdhPJziWk4xqWg9qLtUV14cUzEBEJbVwDG2sd8RhIHld9JpJa7Ce6Gc2Hp4vCTKzwRqch7iWDBc X-Received: by 2002:a17:902:70cc:: with SMTP id l12mr3909405plt.83.1643294165113; Thu, 27 Jan 2022 06:36:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643294165; cv=none; d=google.com; s=arc-20160816; b=LnE02mUNahin3tG1ZrAlkgQMb4UJgX2IItO4BD+OaCcuDYpl4Z/XDZrZ8C9OV6tFNM eXiigrr5TIXuxqiS9d3eRb1Pv0ufSG3v5s/Qe7N6BmmZ5WPOcGAWXWaTQ1lMXIKBiyKQ 5PLKW8xRxzosAKpZalyjVOa7vffRbz7wpX8stybmJ9BkOAMfMiyU29z0UoTC7Mw2jUAN VlqCFfaGrlqUWy7zfC4zzSdP5nwHHPRXwbAVZpkMkOvC1oI6LS4gj79VMUgMYQkRKtal TfpMFYYWwrfrBczBewcxRhjTkXHm+akpT5KyH4VL81WLb2jjQ1b+5drKQnT6JwDevSIb ZGtA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=AOhO6ZjDaEUhBa8+sIPTVE1tTRmzaf4dyKwlHtpIs1Q=; b=KYQ8S2wiO5Es1Jm4ft3Y6ncBIL3vL/5RCcMqhKaEqnVUdaKWUU5pI/AH9hsQLTR82V WGOEMxnazCArcBKTxiWaY5MV7f8omAw64PyqTzZ3WQBEvBMh9VMaqzOkybG3466GbUNL Xp8GZrvMWE61nt55VF78XK1a6zaQSjDmm4qF/FD+B/TswRfDutyfNiLeaiHrTlyg0znC fH8vYHhtYYET4GfThB2WJc46lbRFpawYRUwMoXF5ctQeSEeIPCEf4v7N9FK8hD48NTA2 kQPZpYnjrga2InAhFi63HSPCwONuHkaFUx8S3IAuh7Elm336Ux4Cf509GOdC67DmygQN rJrQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id 15si2214497pgc.242.2022.01.27.06.35.49; Thu, 27 Jan 2022 06:36:05 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237905AbiA0IsZ (ORCPT + 99 others); Thu, 27 Jan 2022 03:48:25 -0500 Received: from mail-ua1-f42.google.com ([209.85.222.42]:47046 "EHLO mail-ua1-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232313AbiA0IsX (ORCPT ); Thu, 27 Jan 2022 03:48:23 -0500 Received: by mail-ua1-f42.google.com with SMTP id c36so3347727uae.13; Thu, 27 Jan 2022 00:48:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=AOhO6ZjDaEUhBa8+sIPTVE1tTRmzaf4dyKwlHtpIs1Q=; b=j/RMgKvB/JQ58GSxqsoGDfAacKeusydSeMVH5oa0TSCy3/dHiM0zkRabn8i/nK5u+6 3CdghNB+cyt2/k/xWtGlYxNcwPJKEF4LBqvhOaGTAl5/5nYqeef/vRlIE2bXcaeU2k9G XuhKcgOznDLEDgmTjgyHWa5U0ISSrqmi/A6MQF/GgpEkfrRCEg3KCU86yO4Y7CfjMkDX wmXsG6drG9P99+9e/n/c3nTR1H/oLJ+uklZbSOFGSNfcdf6AvF58K79N9W1kuKBSzqKq 2IlHQyDdrm64IXS4tjQRcRpCnVSHSeohg7VAAGSs3gMJ3v/NGbkaPqL2hBBEY28jKGG1 z5uw== X-Gm-Message-State: AOAM530hd5e8yHFiPCEax5nL/tgWN7Rn7igkMNzgr0xCNqJVvhsTIjXr XPx0m+WLHz9fcSMtb83YBL3+tGTEdT8bng== X-Received: by 2002:a9f:37ea:: with SMTP id q97mr1181877uaq.82.1643273302864; Thu, 27 Jan 2022 00:48:22 -0800 (PST) Received: from mail-ua1-f46.google.com (mail-ua1-f46.google.com. [209.85.222.46]) by smtp.gmail.com with ESMTPSA id m82sm438466vkm.29.2022.01.27.00.48.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 27 Jan 2022 00:48:22 -0800 (PST) Received: by mail-ua1-f46.google.com with SMTP id b37so3368680uad.12; Thu, 27 Jan 2022 00:48:22 -0800 (PST) X-Received: by 2002:a9f:2c0a:: with SMTP id r10mr1252380uaj.89.1643273301887; Thu, 27 Jan 2022 00:48:21 -0800 (PST) MIME-Version: 1.0 References: <20220120090918.2646626-1-atishp@rivosinc.com> <20220120090918.2646626-7-atishp@rivosinc.com> <1AA3005C-E9C8-4E4B-900D-DD48B37CEA41@jrtc27.com> In-Reply-To: From: Geert Uytterhoeven Date: Thu, 27 Jan 2022 09:48:09 +0100 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 6/6] RISC-V: Do not use cpumask data structure for hartid bitmap To: Atish Patra Cc: Jessica Clarke , Atish Patra , Linux Kernel Mailing List , Anup Patel , Albert Ou , Damien Le Moal , devicetree , Jisheng Zhang , Krzysztof Kozlowski , linux-riscv , Palmer Dabbelt , Paul Walmsley , Rob Herring Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Atish, On Thu, Jan 27, 2022 at 2:02 AM Atish Patra wrote: > On Wed, Jan 26, 2022 at 1:10 AM Geert Uytterhoeven wrote: > > On Wed, Jan 26, 2022 at 9:28 AM Geert Uytterhoeven wrote: > > > On Wed, Jan 26, 2022 at 3:21 AM Atish Patra wrote: > > > > On Tue, Jan 25, 2022 at 2:26 PM Jessica Clarke wrote: > > > > > On 20 Jan 2022, at 09:09, Atish Patra wrote: > > > > > > Currently, SBI APIs accept a hartmask that is generated from struct > > > > > > cpumask. Cpumask data structure can hold upto NR_CPUs value. Thus, it > > > > > > is not the correct data structure for hartids as it can be higher > > > > > > than NR_CPUs for platforms with sparse or discontguous hartids. > > > > > > > > > > > > Remove all association between hartid mask and struct cpumask. > > > > > > > > > > > > Reviewed-by: Anup Patel (For Linux RISC-V changes) > > > > > > Acked-by: Anup Patel (For KVM RISC-V changes) > > > > > > Signed-off-by: Atish Patra > > > > > > > I am yet to reproduce it on my end. > > > > @Geert Uytterhoeven: can you please try the below diff on your end. > > > > > > Unfortunately it doesn't fix the issue for me. > > > > > > /me debugging... > > > > Found it: after this commit, the SBI_EXT_RFENCE_REMOTE_FENCE_I and > > SBI_EXT_RFENCE_REMOTE_SFENCE_VMA ecalls are now called with > > hmask = 0x8000000000000001 and hbase = 1 instead of hmask = 3 and > > hbase = 0. > > > > cpuid 1 maps to hartid 0 > > cpuid 0 maps to hartid 1 > > > > __sbi_rfence_v02:364: cpuid 1 hartid 0 > > __sbi_rfence_v02:377: hartid 0 hbase 1 > > hmask |= 1UL << (hartid - hbase); > > > > oops > > > > __sbi_rfence_v02_call:303: SBI_EXT_RFENCE_REMOTE_FENCE_I hmask > > 8000000000000001 hbase 1 > > > > Ahh yes. hmask will be incorrect if the bootcpu(cpu 0) is a higher > hartid and it is trying to do a remote tlb flush/IPI > to lower the hartid. We should generate the hartid array before the loop. > > Can you try this diff ? It seems to work for me during multiple boot > cycle on the unleashed. > > You can find the patch here as well > https://github.com/atishp04/linux/commits/v5.17-rc1 Thanks, that fixes the issue for me. > --- a/arch/riscv/kernel/sbi.c > +++ b/arch/riscv/kernel/sbi.c > @@ -8,6 +8,8 @@ > #include > #include > #include > +#include > + > #include > #include > > @@ -85,7 +87,7 @@ static unsigned long > __sbi_v01_cpumask_to_hartmask(const struct cpumask *cpu_mas > pr_warn("Unable to send any request to hartid > BITS_PER_LONG for > SBI v0.1\n"); > break; > } > - hmask |= 1 << hartid; > + hmask |= 1UL << hartid; > } > > return hmask; > @@ -160,7 +162,7 @@ static int __sbi_send_ipi_v01(const struct cpumask > *cpu_mask) > { > unsigned long hart_mask; > > - if (!cpu_mask) > + if (!cpu_mask || cpumask_empty(cpu_mask)) > cpu_mask = cpu_online_mask; > hart_mask = __sbi_v01_cpumask_to_hartmask(cpu_mask); > > @@ -176,7 +178,7 @@ static int __sbi_rfence_v01(int fid, const struct > cpumask *cpu_mask, > int result = 0; > unsigned long hart_mask; > > - if (!cpu_mask) > + if (!cpu_mask || cpumask_empty(cpu_mask)) > cpu_mask = cpu_online_mask; > hart_mask = __sbi_v01_cpumask_to_hartmask(cpu_mask); > > @@ -236,6 +238,18 @@ static int __sbi_rfence_v01(int fid, const struct > cpumask *cpu_mask, > static void sbi_set_power_off(void) {} > #endif /* CONFIG_RISCV_SBI_V01 */ > > +static int cmp_ulong(const void *A, const void *B) > +{ > + const unsigned long *a = A, *b = B; > + > + if (*a < *b) > + return -1; > + else if (*a > *b) > + return 1; > + else > + return 0; > +} > + > static void __sbi_set_timer_v02(uint64_t stime_value) > { > #if __riscv_xlen == 32 > @@ -251,13 +265,22 @@ static int __sbi_send_ipi_v02(const struct > cpumask *cpu_mask) > { > unsigned long hartid, cpuid, hmask = 0, hbase = 0; > struct sbiret ret = {0}; > - int result; > + int result, index = 0, max_index = 0; > + unsigned long hartid_arr[NR_CPUS] = {0}; > > - if (!cpu_mask) > + if (!cpu_mask || cpumask_empty(cpu_mask)) > cpu_mask = cpu_online_mask; > > for_each_cpu(cpuid, cpu_mask) { > hartid = cpuid_to_hartid_map(cpuid); > + hartid_arr[index] = hartid; > + index++; > + } > + > + max_index = index; > + sort(hartid_arr, max_index, sizeof(unsigned long), cmp_ulong, NULL); > + for (index = 0; index < max_index; index++) { > + hartid = hartid_arr[index]; > if (hmask && ((hbase + BITS_PER_LONG) <= hartid)) { > ret = sbi_ecall(SBI_EXT_IPI, SBI_EXT_IPI_SEND_IPI, > hmask, hbase, 0, 0, 0, 0); > @@ -345,13 +368,21 @@ static int __sbi_rfence_v02(int fid, const > struct cpumask *cpu_mask, > unsigned long arg4, unsigned long arg5) > { > unsigned long hartid, cpuid, hmask = 0, hbase = 0; > - int result; > + int result, index = 0, max_index = 0; > + unsigned long hartid_arr[NR_CPUS] = {0}; That's up to 256 bytes on the stack. And more if the maximum number of cores is increased. > > - if (!cpu_mask) > + if (!cpu_mask || cpumask_empty(cpu_mask)) > cpu_mask = cpu_online_mask; > > for_each_cpu(cpuid, cpu_mask) { > hartid = cpuid_to_hartid_map(cpuid); > + hartid_arr[index] = hartid; > + index++; > + } > + max_index = index; > + sort(hartid_arr, max_index, sizeof(unsigned long), cmp_ulong, NULL); > + for (index = 0; index < max_index; index++) { > + hartid = hartid_arr[index]; That looks expensive to me. What about shifting hmask and adjusting hbase if a hartid is lower than the current hbase? > if (hmask && ((hbase + BITS_PER_LONG) <= hartid)) { > result = __sbi_rfence_v02_call(fid, hmask, hbase, > start, size, arg4, arg5); Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds