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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6927CC7EE23 for ; Fri, 24 Feb 2023 21:32:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229446AbjBXVcP (ORCPT ); Fri, 24 Feb 2023 16:32:15 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53828 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229487AbjBXVcP (ORCPT ); Fri, 24 Feb 2023 16:32:15 -0500 Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 085AF6F032 for ; Fri, 24 Feb 2023 13:31:57 -0800 (PST) Received: by mail-pl1-x62b.google.com with SMTP id e9so876752plh.2 for ; Fri, 24 Feb 2023 13:31:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dabbelt-com.20210112.gappssmtp.com; s=20210112; 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=cvJN8dmrmNJu4tTYhdlBrzcRSinLAy+Jhaplp/kCRiA=; b=wh807lSO9v29Yu6tO13IzDLOgiVo3Y9CLLlEMCaN5Bfph5SWKk/ief3r4cZyouTDq3 ekQ8BZiAaegZvDAKUQ41D41hsAmetgk6oRbzZgr5tZ8Ebv6rouEL0se6NNr8O8vuHMuA Y9E1KcrrOfgbPedMh8QVliNBmDLSSk306iIqsN5Z3WjNY4Kf8EbTZS61IOkrrZWWRWux SIrlqYQU9Ed7MRpv4GK6gK/n40iENTbOVq0sI7jnPIv4ay32p0xTWuzO+r4e3KUxS3Aw mV9fpIWYF+zc1nWP6gzHkwKwUixXjTuaac3chNZcBChKKjLuR16rINK9a4ShFPJKhkRy dJKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=cvJN8dmrmNJu4tTYhdlBrzcRSinLAy+Jhaplp/kCRiA=; b=wylRvOmBS1z7YSY+UacL52r3eEhoO/H0NyZFu1CUIdlgk9JD/PNywQoNRtPwTMZ72n 4oD0l/vI2mTz04RM3MHSiMIS6DroFZeWTI0AGHr1W8RcWzOIiKcBi3I1+d6I+E0uZMWj nIczlDGRZKabHOkSeHuYki+SmxhoeHJ9kxQtDuLYuSAdUoKIkO5+I+MI4skPBRHSeW9c twDrq6u+NoLp+uZ++nqAskFcuG7JP1CfNDoG3oxUKi2dxQdjTIGvtxXE+dV5sxsVvnfi ntabaSYP7SjRCWe8CUS7XhAzeTcXIZ9MqgLkoUdZ7EYNa+uB4a3VJHqFUSvRC9diaepO 4LwA== X-Gm-Message-State: AO0yUKXUt3nA16W7evugrduz0jmruM1CmFdPvA78jWzCAYALsS1uhVTt TT1yM0P9N+/TdTTqhJ2yZil+bA== X-Google-Smtp-Source: AK7set+inR9Bfe356VnjZRrkMmucPTHHx4QOqBABEwJbFOr2cvrtN9y1cnMB0g/q9qfmCnSJDZEm5g== X-Received: by 2002:a17:902:d506:b0:199:4d25:6a4d with SMTP id b6-20020a170902d50600b001994d256a4dmr997355plg.10.1677274316335; Fri, 24 Feb 2023 13:31:56 -0800 (PST) Received: from localhost ([50.221.140.188]) by smtp.gmail.com with ESMTPSA id jw9-20020a170903278900b0019a7d58e595sm6071070plb.143.2023.02.24.13.31.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 24 Feb 2023 13:31:55 -0800 (PST) Date: Fri, 24 Feb 2023 13:31:55 -0800 (PST) X-Google-Original-Date: Fri, 24 Feb 2023 13:31:09 PST (-0800) Subject: Re: [RFC 0/2] RISC-V: enable rust In-Reply-To: <20230224133609.2877396-1-conor.dooley@microchip.com> CC: linux-riscv@lists.infradead.org, Conor Dooley , Conor Dooley , ojeda@kernel.org, alex.gaynor@gmail.com, wedsonaf@gmail.com, boqun.feng@gmail.com, gary@garyguo.net, bjorn3_gh@protonmail.com, corbet@lwn.net, Paul Walmsley , nathan@kernel.org, ndesaulniers@google.com, trix@redhat.com, rust-for-linux@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, llvm@lists.linux.dev From: Palmer Dabbelt To: Conor Dooley Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: rust-for-linux@vger.kernel.org On Fri, 24 Feb 2023 05:36:08 PST (-0800), Conor Dooley wrote: > This is a somewhat blind (and maybe foolish) attempt at enabling Rust > for RISC-V. I've tested this on Icicle, and the modules seem to work. > I'd like to play around with Rust on RISC-V, but I'm not interested in > using downstream kernels, so figured I should try and see what's > missing... > I've tagged this as RFC in case I've missed some "WAaaaa you can't do > this" somewhere :) I'm fine with it, but IIRC the Rust support for most targets was pulled out as they weren't deemed ready to go yet. If the Rust folks are OK turning on RISC-V support then it's fine with me, but I think it's really more up to them at this point. So Acked-by: Palmer Dabbelt in case folks want to take it via some Rust-related tree, but I'm also fine taking it via the RISC-V tree if that's easier. > > Thanks, > Conor. > > CC: Miguel Ojeda > CC: Alex Gaynor > CC: Wedson Almeida Filho > CC: Boqun Feng > CC: Gary Guo > CC: Björn Roy Baron > CC: Jonathan Corbet > CC: Paul Walmsley > CC: Palmer Dabbelt > CC: Nathan Chancellor > CC: Nick Desaulniers > CC: Tom Rix > CC: rust-for-linux@vger.kernel.org > CC: linux-doc@vger.kernel.org > CC: linux-kernel@vger.kernel.org > CC: linux-riscv@lists.infradead.org > CC: llvm@lists.linux.dev > > Miguel Ojeda (2): > scripts: generate_rust_target: enable building on RISC-V > RISC-V: enable building the 64-bit kernels with rust support > > Documentation/rust/arch-support.rst | 2 ++ > arch/riscv/Kconfig | 1 + > arch/riscv/Makefile | 3 ++- > scripts/generate_rust_target.rs | 19 +++++++++++++++++++ > 4 files changed, 24 insertions(+), 1 deletion(-)