From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by sourceware.org (Postfix) with ESMTPS id 5C4713858D28 for ; Tue, 2 Apr 2024 16:37:24 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 5C4713858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=dabbelt.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=dabbelt.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 5C4713858D28 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2607:f8b0:4864:20::62d ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712075847; cv=none; b=p2inp6m1Dgk6zPRImXwuKe5lrjZo75GyIakqmhFq67jKxovGIYMesY0hLqOf/9BaXgQsnSWXOLv1uukBcl3POT1MI1/rCtDOA7QuoQjvtkpINvBkF4LbsL0mgq6PzL0dL+ypHtwbc3HqueMwGlePO5othaS/Klut26wJGYITsAQ= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1712075847; c=relaxed/simple; bh=UhCi7NU3jzseF9xukwRVHNQYr8sLMf1lYkxpaArT3W0=; h=DKIM-Signature:Date:Subject:From:To:Message-ID:Mime-Version; b=ZXa9Ef9K+NjXNZmTxNl0SwppLitfvaMSW0k32R3ZqeoRns54Ky7O6qUwl5M54Tbu0BjeRpOIjji2iBcgNauQyonF5bgJ48WpHqPKh+PTFcKddx74AfY9d0aJyuPgQ6/E8k1ecNpDIO5ZaeF/FcZWaZ8fHXYEZFzDlp7f/KceJkY= ARC-Authentication-Results: i=1; server2.sourceware.org Received: by mail-pl1-x62d.google.com with SMTP id d9443c01a7336-1e27f800ad0so4444575ad.1 for ; Tue, 02 Apr 2024 09:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20230601.gappssmtp.com; s=20230601; t=1712075843; x=1712680643; darn=sourceware.org; h=content-transfer-encoding:mime-version:message-id:to:from:cc :in-reply-to:subject:date:from:to:cc:subject:date:message-id :reply-to; bh=5+K/gQ3/9h6ydkblQCUWZWtqQYlOQPJrH+/MTFszWSk=; b=ch6TYVDBjusPtRQO52HwNz1AcQOYPOHcyEDswrm0peeuCj2CXpZZ11B5bKD5j3BwwZ /aFMMYSp47iyyauASuXl0xUWUFHtJ4zr+uJAa4d+YAmHG1JHOpviB44fvuvXG30PwusN foDJP2It3BRDGcJ+vyBlMKgNrQh7RmOPAWdT9IjXSDd2D5mLrBlnIlxhVQzGW/rV3yFu CWvf8WzVk1XgToC3LFDiBG17xbOyg4HhvZ1E+YZod1mcLRvpgiZbfygk+HwjEONO2MkI e5mvnm4OwOAsSmUX66Krq2WG0xhYxgRXv+ZIRtWQVrqPLVxiK9jH2bxfWTxbH82Z5pg0 d7Ew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712075843; x=1712680643; h=content-transfer-encoding:mime-version:message-id:to:from:cc :in-reply-to:subject:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=5+K/gQ3/9h6ydkblQCUWZWtqQYlOQPJrH+/MTFszWSk=; b=MFfIQON+K3v09g1kJlxw+pAYSpKB+rO+xTedqOXg0U+3t83CrVEbLz9kdYP0WBF1iO 9Dr/rVSnmwx3uhMf7U/QCdSln4HsssDxKhyiKHT5AwXOXIiOTtZ3SyUCdCNEr7J7AHfn KG1G+LHXPv9xm0YQJukJvt0nVwORkfZo4kKxz0dDPlME+XqfydP1yM3nUWN2GWTteiH3 a7ztgEqEDCEVOm3X7cQysTr7gYhyyVQgCTaTJ5eJHg/WT30jVceVRjJNZNptptrOtaoZ 4/b7SN/dRqG22SIbZRkOXWU397lRnO+OJcAR9yVTydh95CJLT5QkBqSFFcdxiV2v9p/o iEYw== X-Forwarded-Encrypted: i=1; AJvYcCXskx8WOkZFy5SEh1NY1NTQlpCE1o1zNAvHYo+MktyqSQH7GFU2I9IoPPeMsT+hFfjTWgfZa0yyWbL+ZH0wXnbzcQvS95PDhF5P X-Gm-Message-State: AOJu0YxeaK7jHRvOYcBZWKSEvwX8SjdKTxR+IDcD3OYcGY3KtXFohmWg Y9rJ8eTYIKaS5VrgJEPLDK1pJJ2dCEA+I9XQFZ5/PKL7fztoOcsrCcpYRshquCc= X-Google-Smtp-Source: AGHT+IH39TdCon/XhDoS0BU+ldb24kay7VcV8mD5m286Mgbf3N2xv39JElkEVEN/Rne2HdZxjVeEVA== X-Received: by 2002:a17:903:110d:b0:1de:fbc8:53af with SMTP id n13-20020a170903110d00b001defbc853afmr14953488plh.25.1712075843159; Tue, 02 Apr 2024 09:37:23 -0700 (PDT) Received: from localhost ([192.184.165.199]) by smtp.gmail.com with ESMTPSA id w20-20020a1709027b9400b001dca3a65200sm11328271pll.228.2024.04.02.09.37.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 Apr 2024 09:37:22 -0700 (PDT) Date: Tue, 02 Apr 2024 09:37:22 -0700 (PDT) X-Google-Original-Date: Tue, 02 Apr 2024 09:37:20 PDT (-0700) Subject: Re: [PATCH v6 3/3] RISC-V: Implement TLS Descriptors. In-Reply-To: CC: ishitatsuyuki@gmail.com, libc-alpha@sourceware.org, rui314@gmail.com, ruiu@bluewhale.systems, schwab@linux-m68k.org, Andrew Waterman , fweimer@redhat.com From: Palmer Dabbelt To: adhemerval.zanella@linaro.org Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-3.9 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Tue, 02 Apr 2024 08:32:59 PDT (-0700), adhemerval.zanella@linaro.org wrote: > > > On 02/04/24 12:25, Palmer Dabbelt wrote: > >> >>> I am not sure whether RISC-V maintainer would like to move to profilers >>> or would keep this extensions composability manner. >> >> What do you mean by "move to profilers"?  "move to profiles"? >> >> We have the profiles in RISC-V, but they don't really fix anything here: there's a ton of them, they still have various optional extensions, and the HW support is all over the place (we don't even have compatibility guarantees with individual extensions, for example). >> >> So I think for just sticking to the current base ABIs is the way to go.  Maybe at some point HW vendors will start shipping systems that are compatible with some common extension set and we can promote that to a new base ABI, but we're a way off from that happening. > > Indeed I meant 'profiles' here and my understanding was that something like > RVA22U64 as base would simplify things a bit (at least with the possible > testing/checking the multiple build permutations that using optional > extensions would incur). If we could get all the HW vendors to agree to something it wouldn't hurt, but trying to move to one of the newer profiles would mean dropping support for existing hardware (and thus breaking users who are stuck with it, a lot of this newer hardware seems pretty buggy right now). Vendors seem to be implementing stuff that's close to the profiles, but it's still a bit of a mess -- plus we end up with the whole vendor self-certification issue, which means it's really hard to tell what HW actually does from the marketing material. I'm hoping that something like Android will help here, as there we'll have people who are actually shipping systems defining the compatibility requirements. With any luck that will start getting these issues at least understood over at RVI, but it's still going to be a long process before we get stuff sane.