Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp911569ybt; Fri, 10 Jul 2020 16:01:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzbXCQeBD2gAfnzn2uEYb69xbVuW7M2EExrJGt0edUJARp48z7FDBfUZ3rlCSIskuzekHdh X-Received: by 2002:a50:9dc8:: with SMTP id l8mr79608777edk.248.1594422065620; Fri, 10 Jul 2020 16:01:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594422065; cv=none; d=google.com; s=arc-20160816; b=yLXe9pkt/PrMCweEYPz3gaH3Z/tbG/3xSxc5dbWmSQeWgG/fzsT2s2Ex7l5wRvbWze 5EEAtsrA4vIhMmvEmbyClc30Bdxm8rInwSfTK7jqs9KGL/+J16yD8U96ITE0qm4UZfNz rRxfqZwYQvfvQmQ/nLS395lamvxy5dBrkg1x60lhcuPCsPt/bXLP/oycwQqvL1Uk9QIR 9kWC4pxZ4QxZZbUn6nCQp4Zy+sMp7FkNNPlfF5oBEivI0lcBi6wS3lT8IRFtrg79d0XO NK27GTCvVejie4EfHu6KJ1mKLMThUCFw6ny1QGZghIEuhgZzF4NWfcc44qZfEA8WvCUF Qx2g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=DpFZ8oXD3zQsHdykw+PWBwDWMh4nmKIdN37BDefTAoc=; b=HeJBCe0+qKvMgxv0xBHfpuqHf+q8DSojT+zHB+rf202pwQ/Y67IbGw4wMSooAwEF7b O1fZOEboLm+svszIbD2yAagfqU+HRXRWvvd62+Dr27OPHY/NPECF1wpeZ4U/QqEJ6ch/ upzUznxl9uO7sAmIMxFzwHinu+vuWY5LHZRACYxNVM47R8iBdO0vqoLOG+nlmBxuD4P/ jFlS5Cq2hbwrTbisc2PgXIvoHfbfXPL1ZkLBRop5gV1GoQ7pFLN7o81WhZheuiSaOCYj h4QX4RbG1xIjH18sW5k8s+pNAYpPg7t3TF3wnAyqKmDF6giGy5SHWH9GJ6D+nJvivZtG HZvw== 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 k13si5143733edx.360.2020.07.10.16.00.42; Fri, 10 Jul 2020 16:01:05 -0700 (PDT) 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 S1726769AbgGJW7o (ORCPT + 99 others); Fri, 10 Jul 2020 18:59:44 -0400 Received: from relay1-d.mail.gandi.net ([217.70.183.193]:31475 "EHLO relay1-d.mail.gandi.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726578AbgGJW7n (ORCPT ); Fri, 10 Jul 2020 18:59:43 -0400 X-Originating-IP: 50.39.163.217 Received: from localhost (50-39-163-217.bvtn.or.frontiernet.net [50.39.163.217]) (Authenticated sender: josh@joshtriplett.org) by relay1-d.mail.gandi.net (Postfix) with ESMTPSA id 5ED8E240002; Fri, 10 Jul 2020 22:59:35 +0000 (UTC) Date: Fri, 10 Jul 2020 15:59:34 -0700 From: Josh Triplett To: Christian Brauner Cc: Nick Desaulniers , alex.gaynor@gmail.com, Greg KH , geofft@ldpreload.com, jbaublitz@redhat.com, Masahiro Yamada , Linus Torvalds , Miguel Ojeda , Steven Rostedt , LKML , clang-built-linux , keescook@chromium.org Subject: Re: Linux kernel in-tree Rust support Message-ID: <20200710225934.GA16881@localhost> References: <20200710062803.GA1071395@kroah.com> <20200710125022.alry7wkymalmv3ge@wittgenstein> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200710125022.alry7wkymalmv3ge@wittgenstein> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 10, 2020 at 02:50:22PM +0200, Christian Brauner wrote: > On Fri, Jul 10, 2020 at 08:28:03AM +0200, Greg KH wrote: > > On Thu, Jul 09, 2020 at 11:41:47AM -0700, Nick Desaulniers wrote: > > > Hello folks, > > > I'm working on putting together an LLVM "Micro Conference" for the > > > upcoming Linux Plumbers Conf > > > (https://www.linuxplumbersconf.org/event/7/page/47-attend). It's not > > > solidified yet, but I would really like to run a session on support > > > for Rust "in tree." I suspect we could cover technical aspects of > > > what that might look like (I have a prototype of that, was trivial to > > > wire up KBuild support), but also a larger question of "should we do > > > this?" or "how might we place limits on where this can be used?" > > > > > > Question to folks explicitly in To:, are you planning on attending plumbers? > > > > > > If so, would this be an interesting topic that you'd participate in? > > > > Yes, I'll be there. > > We actually had this dicussion a while back and there were some more > people interested in this. I'd be interested to attend this and I've > spoken with Kees and a few others about this topic at last Plumbers (I > think Greg might have been around for this informal discussion as well. > But I might be imagining things.). I was around for one of the informal conversations with Greg and Kees and others. As I recall, Greg's biggest condition for initial introduction of this was to do the same kind of "turn this Kconfig option on and turn an option under it off" trick that LTO uses, so that neither "make allnoconfig" nor "make allyesconfig" would require Rust until we've had plenty of time to experiment with it. And that seems entirely reasonable to me too. - Josh