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=-6.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 5A99CC432C1 for ; Tue, 24 Sep 2019 23:42:11 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 1BD1920872 for ; Tue, 24 Sep 2019 23:42:11 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="GkkQOXgR" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 1BD1920872 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:44056 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCuRe-0003Ia-7T for qemu-devel@archiver.kernel.org; Tue, 24 Sep 2019 19:42:10 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:54072) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iCuQE-0002bb-VJ for qemu-devel@nongnu.org; Tue, 24 Sep 2019 19:40:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iCuQD-0006HY-Ad for qemu-devel@nongnu.org; Tue, 24 Sep 2019 19:40:42 -0400 Received: from mail-lf1-x142.google.com ([2a00:1450:4864:20::142]:40020) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iCuQ9-0006G0-5Z; Tue, 24 Sep 2019 19:40:37 -0400 Received: by mail-lf1-x142.google.com with SMTP id d17so2710947lfa.7; Tue, 24 Sep 2019 16:40:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qetquSP6tDAhKdSLO341teori+DiY4EAVr8iIiPuMY0=; b=GkkQOXgRCQCIqT2+Cwd0jYfOg+e0zGvE1ymzqUZrmF2C4/42toAQRXzP0293N+5plG W0fZ8e709VIRnnHqYO6r16O52mEj+XDJPGV9erJMaNAnZkssgA3RFeXWGt717ujIsOwQ Z6OJ7hBwAu73ykH6is27ASetNWrYJqdmuCXY1pq8JCgpsbcxPFGl0CfBzd+iWxzst68M 0wvhDKZeCQtpqGsbuLz7B268Bf7YAQ+F4A4uOj7Xe+PLCgce5NHaXwy7zVsc5oG77Q+a hwrXtw1NoKV6B/IqwltGs2GuPYuzgGOWbzkMipkm5K40kKFE6ZCf+t+E/T1bisgIFLc6 GETw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qetquSP6tDAhKdSLO341teori+DiY4EAVr8iIiPuMY0=; b=uT4rfYMign0bejh4Jk7AF7SMEgm2FFiTmj2mbcRby9t9zrqW2os7T2I83m6YfcIQhT xo7uqgp8IrhaP/VkJhRmtKwImOaig3ZIpTbVFNRPCOK+Jy7oRsMprkBcCRbCJbzOQ652 LUNGBE0OlByI1fzBKd2wksB7nT9Pbj3tjDPS2UPsDfIQyRnTYwbTQEIM39feKA5jVWuC Qd2FKUEDtSdKslqHbdneiE6bhgkVd6q6YSVf7rRrzSHFcJahBwXZKzqpnNSKkbg4Fl2Y wMnU+VySsq7eC85rMU0QhTmVerfdo2CoA1DlLq71kikENrrc/zuKskmxl3bmqVT/sy5v ezEg== X-Gm-Message-State: APjAAAWvuOgn5Xl1IA9QDF2e4CJHuF/Dz01X3BQ1YEN4XK2B8OE/k/rH /Cg4hk3Dh79D55xJxuLTc6lPadeefGXWgf09VRE= X-Google-Smtp-Source: APXvYqwoZQM8izTVagw45kshu3Vx7Jczmnxd386hrLzwQ3lB6iU7wNO4Vd3Y3ZVOxllXO3PrWf3Qaz4RtTWLf/VArSg= X-Received: by 2002:a19:48c3:: with SMTP id v186mr3535101lfa.141.1569368436007; Tue, 24 Sep 2019 16:40:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Alistair Francis Date: Tue, 24 Sep 2019 16:35:53 -0700 Message-ID: Subject: Re: [Qemu-devel] [PATCH] atomic failures on qemu-system-riscv64 To: Palmer Dabbelt Content-Type: text/plain; charset="UTF-8" X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2a00:1450:4864:20::142 X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: me@carlosedp.com, "open list:RISC-V" , Richard Henderson , "qemu-devel@nongnu.org Developers" , Joel Sing , Alistair Francis , marco@decred.org Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" On Tue, Sep 24, 2019 at 1:04 PM Palmer Dabbelt wrote: > > On Tue, 24 Sep 2019 11:29:25 PDT (-0700), alistair23@gmail.com wrote: > > On Mon, Jun 24, 2019 at 11:21 AM Joel Sing wrote: > >> > >> On 19-06-17 16:52:44, Richard Henderson wrote: > >> > On 6/16/19 12:19 PM, Joel Sing wrote: > >> > > + /* > >> > > + * Clear the load reservation, since an SC must fail if there is > >> > > + * an SC to any address, in between an LR and SC pair. > >> > > + */ > >> > > + tcg_gen_movi_tl(load_res, 0); > >> > > + > >> > > gen_set_label(l2); > >> > > >> > This clear needs to be moved down below label l2. > >> > Otherwise, with lr / sc / sc, the second sc could succeed in error. > >> > >> Indeed, thanks. > >> > >> > FWIW, other targets have used -1 as the "invalid" load reservation, since the > >> > architecture does not require address 0 to be unmapped. This should be quite > >> > visible in M-mode with paging disabled and ram at offset 0. Often, other > >> > targets require alignment for the lr/sc address, though I don't see that for riscv. > >> > >> I've switched to -1 as suggested. Regarding the alignment for reservations, the > >> specification does require this, although I do not recall seeing any enforcement > >> of this by qemu itself. > >> > >> New diff follows. > >> > >> From 8ef31a2ce8ef1cbeee92995a0b2994f480e9bb6d Mon Sep 17 00:00:00 2001 > >> From: Joel Sing > >> Date: Tue, 25 Jun 2019 02:44:24 +1000 > >> Subject: [PATCH] Clear load reservations on qemu riscv target > >> > >> This prevents a load reservation from being placed in one context/process, > >> then being used in another, resulting in an SC succeeding incorrectly and > >> breaking atomics. > >> > >> Signed-off-by: Joel Sing > >> --- > >> target/riscv/cpu.c | 1 + > >> target/riscv/cpu_helper.c | 9 +++++++++ > >> target/riscv/insn_trans/trans_rva.inc.c | 8 +++++++- > >> 3 files changed, 17 insertions(+), 1 deletion(-) > >> > >> diff --git a/target/riscv/cpu.c b/target/riscv/cpu.c > >> index d61bce6d55..e7c8bf48fc 100644 > >> --- a/target/riscv/cpu.c > >> +++ b/target/riscv/cpu.c > >> @@ -281,6 +281,7 @@ static void riscv_cpu_reset(CPUState *cs) > >> env->pc = env->resetvec; > >> #endif > >> cs->exception_index = EXCP_NONE; > >> + env->load_res = -1; > >> set_default_nan_mode(1, &env->fp_status); > >> } > >> > >> diff --git a/target/riscv/cpu_helper.c b/target/riscv/cpu_helper.c > >> index b17f169681..6a07b12e65 100644 > >> --- a/target/riscv/cpu_helper.c > >> +++ b/target/riscv/cpu_helper.c > >> @@ -113,6 +113,15 @@ void riscv_cpu_set_mode(CPURISCVState *env, target_ulong newpriv) > >> } > >> /* tlb_flush is unnecessary as mode is contained in mmu_idx */ > >> env->priv = newpriv; > >> + > >> + /* Clear the load reservation - otherwise a reservation placed in one > >> + * context/process can be used by another, resulting in an SC succeeding > >> + * incorrectly. Version 2.2 of the ISA specification explicitly requires > >> + * this behaviour, while later revisions say that the kernel "should" use > >> + * an SC instruction to force the yielding of a load reservation on a > >> + * preemptive context switch. As a result, do both. > >> + */ > >> + env->load_res = -1; > >> } > >> > >> /* get_physical_address - get the physical address for this virtual address > >> diff --git a/target/riscv/insn_trans/trans_rva.inc.c b/target/riscv/insn_trans/trans_rva.inc.c > >> index f6dbbc065e..fadd88849e 100644 > >> --- a/target/riscv/insn_trans/trans_rva.inc.c > >> +++ b/target/riscv/insn_trans/trans_rva.inc.c > >> @@ -61,7 +61,7 @@ static inline bool gen_sc(DisasContext *ctx, arg_atomic *a, TCGMemOp mop) > >> > >> gen_set_label(l1); > >> /* > >> - * Address comparion failure. However, we still need to > >> + * Address comparison failure. However, we still need to > >> * provide the memory barrier implied by AQ/RL. > >> */ > >> tcg_gen_mb(TCG_MO_ALL + a->aq * TCG_BAR_LDAQ + a->rl * TCG_BAR_STRL); > >> @@ -69,6 +69,12 @@ static inline bool gen_sc(DisasContext *ctx, arg_atomic *a, TCGMemOp mop) > >> gen_set_gpr(a->rd, dat); > >> > >> gen_set_label(l2); > >> + /* > >> + * Clear the load reservation, since an SC must fail if there is > >> + * an SC to any address, in between an LR and SC pair. > >> + */ > >> + tcg_gen_movi_tl(load_res, -1); > >> + > >> tcg_temp_free(dat); > >> tcg_temp_free(src1); > >> tcg_temp_free(src2); > >> -- > > > > This patch causes boot failures when booting systemd built with musl on RV64. > > > > It could possibly be a musl bug, but I wanted to throw that out here > > first to see what people think. > > Looking at the musl port, I see at least one bug in their atomics jumping out > at me: > > diff --git a/arch/riscv64/atomic_arch.h b/arch/riscv64/atomic_arch.h > index c9765342..41ad4d04 100644 > --- a/arch/riscv64/atomic_arch.h > +++ b/arch/riscv64/atomic_arch.h > @@ -14,7 +14,7 @@ static inline int a_cas(volatile int *p, int t, int s) > " sc.w.aqrl %1, %4, (%2)\n" > " bnez %1, 1b\n" > "1:" > - : "=&r"(old), "=r"(tmp) > + : "=&r"(old), "=&r"(tmp) > : "r"(p), "r"(t), "r"(s) > : "memory"); > return old; > @@ -31,7 +31,7 @@ static inline void *a_cas_p(volatile void *p, void *t, void *s) > " sc.d.aqrl %1, %4, (%2)\n" > " bnez %1, 1b\n" > "1:" > - : "=&r"(old), "=r"(tmp) > + : "=&r"(old), "=&r"(tmp) > : "r"(p), "r"(t), "r"(s) > : "memory"); > return old; > > It's a shot in the dark as to whether that'll fix your bug, but I could at > least see a mechanism for it: before we yielded load reservations on context > switches then that backwards branch would never be taken, so we wouldn't notice > if tmp was allocated into one of the same registers as the inputs. Even if it > doesn't fix your issue it's still a bug so I'll send the patch out, just LMK so > I can indicate how important the issue is. I haven't had a chance to test this fix yet. The bug was reported by Khem (and other OE people) as it's break musl for RISC-V. > > This should manifest on hardware, but it looks like we managed to drop that SC > patch. I'll go send the patch out now... Thanks, do you mind CCing me? Alistair > > > > > Alistair > > > >> 2.21.0 > >> > >>