qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Tyler Fanelli <tfanelli@redhat.com>
Cc: "Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
	"Stefan Hajnoczi" <stefanha@redhat.com>,
	qemu-devel@nongnu.org, pbonzini@redhat.com, mtosatti@redhat.com,
	marcandre.lureau@gmail.com,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Mike Frysinger" <vapier@gentoo.org>,
	"WANG Xuerui" <xen0n@gentoo.org>,
	"Andreas K. Hüttel" <dilfridge@gentoo.org>,
	"Sergei Trofimovich" <slyfox@gentoo.org>,
	"YunQiang Su" <syq@debian.org>,
	"Michael Tokarev" <mjt@tls.msk.ru>,
	qemu-discuss <qemu-discuss@nongnu.org>,
	"Joelle van Dyne" <j@getutm.app>, "Stefan Weil" <sw@weilnetz.de>
Subject: Re: [RFC PATCH v2 1/9] Add Rust SEV library as subproject
Date: Mon, 16 Oct 2023 15:38:09 +0200	[thread overview]
Message-ID: <0184aa1d-bca7-d174-9a1a-2a5496f13e39@linaro.org> (raw)
In-Reply-To: <ZSz/dxLsHPt2+2XN@redhat.com>

On 16/10/23 11:16, Daniel P. Berrangé wrote:
> On Fri, Oct 13, 2023 at 02:20:16PM -0400, Tyler Fanelli wrote:
>> Hi Manos,
>>
>> Thanks for the heads up, I was using rust 1.71.1. Will update the series
>> with 1.72.1
>>
>> Stefan, Philippe, or Daniel: is there a specific policy for the Rust version
>> we should be developing on for crates in qemu?
> 
> There are a couple of dimensions to this.
> 
> First is the matter of what operating system and architecture pairs are
> supported as targets for the Rust toolchain, and the standard library.
> We'll need both to work of course.
> 
> Second there is the matter of what versions of Rust are shipped in the
> various operating systems currently.
> 
> In a previous discussion there was a wiki page fleshed out with this
> info:
> 
>     https://wiki.qemu.org/RustInQemu
> 
> but the min versions are certainly out of date now.
> 
> Third there is the question of whether distros have facility for pulling
> in newer toolchain versions, and if so should we be willing to use them.
> This is relevant for the long life distros like RHEL, which might ship
> with a variety of Rust versions. Historically we've been very conservative
> but with Python last year we adopted a more aggressive policy of being
> willing to take any newer version available from the distro vendor, not
> merely the oldest baseline. I suspect we'll want a similar approach with
> rust.

Cc'ing distrib package maintainers to have their feedback on this.

> Anyhow, I think you could probably start by updatnig that RustInQemu
> wiki page so that it reflects the current state of the world in terms
> of support tiers and versions.



  reply	other threads:[~2023-10-16 13:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 20:34 [RFC PATCH v2 0/9] i386/sev: Use C API of Rust SEV library Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 1/9] Add Rust SEV library as subproject Tyler Fanelli
2023-10-05  6:03   ` Philippe Mathieu-Daudé
2023-10-05 23:41     ` Tyler Fanelli
2023-10-11  3:05     ` Tyler Fanelli
2023-10-05 15:54   ` Stefan Hajnoczi
2023-10-11  3:10     ` Tyler Fanelli
2023-10-13 18:09       ` Manos Pitsidianakis
2023-10-13 18:20         ` Tyler Fanelli
2023-10-16  9:16           ` Daniel P. Berrangé
2023-10-16 13:38             ` Philippe Mathieu-Daudé [this message]
2023-10-16 13:51             ` Stefan Hajnoczi
2024-03-05 13:47   ` Daniel P. Berrangé
2024-03-05 15:40     ` Philippe Mathieu-Daudé
2023-10-04 20:34 ` [RFC PATCH v2 2/9] i386/sev: Replace INIT and ES_INIT ioctls with sev library equivalents Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 3/9] i386/sev: Replace LAUNCH_START ioctl with sev library equivalent Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 4/9] i386/sev: Replace UPDATE_DATA " Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 5/9] i386/sev: Replace LAUNCH_UPDATE_VMSA " Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 6/9] i386/sev: Replace LAUNCH_MEASURE " Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 7/9] i386/sev: Replace LAUNCH_SECRET " Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 8/9] i386/sev: Replace LAUNCH_FINISH " Tyler Fanelli
2023-10-04 20:34 ` [RFC PATCH v2 9/9] i386/sev: Replace SEV_ATTESTATION_REPORT " Tyler Fanelli

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0184aa1d-bca7-d174-9a1a-2a5496f13e39@linaro.org \
    --to=philmd@linaro.org \
    --cc=berrange@redhat.com \
    --cc=dilfridge@gentoo.org \
    --cc=j@getutm.app \
    --cc=manos.pitsidianakis@linaro.org \
    --cc=marcandre.lureau@gmail.com \
    --cc=mjt@tls.msk.ru \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=slyfox@gentoo.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    --cc=syq@debian.org \
    --cc=tfanelli@redhat.com \
    --cc=vapier@gentoo.org \
    --cc=xen0n@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).