qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [RFC PATCH v2 1/9] Add Rust SEV library as subproject


From: Tyler Fanelli
Subject: Re: [RFC PATCH v2 1/9] Add Rust SEV library as subproject
Date: Thu, 5 Oct 2023 19:41:31 -0400
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0

On 10/5/23 2:03 AM, Philippe Mathieu-Daudé wrote:
Hi Tyler,

On 4/10/23 22:34, Tyler Fanelli wrote:
The Rust sev library provides a C API for the AMD SEV launch ioctls, as
well as the ability to build with meson. Add the Rust sev library as a
QEMU subproject with the goal of outsourcing all SEV launch ioctls to C
APIs provided by it.

Signed-off-by: Tyler Fanelli <tfanelli@redhat.com>
---
  meson.build                   | 8 ++++++++
  meson_options.txt             | 2 ++
  scripts/meson-buildoptions.sh | 3 +++
  subprojects/sev.wrap          | 6 ++++++
  target/i386/meson.build       | 2 +-
  5 files changed, 20 insertions(+), 1 deletion(-)
  create mode 100644 subprojects/sev.wrap


diff --git a/subprojects/sev.wrap b/subprojects/sev.wrap
new file mode 100644
index 0000000000..5be1faccf6
--- /dev/null
+++ b/subprojects/sev.wrap
@@ -0,0 +1,6 @@
+[wrap-git]
+url = https://github.com/tylerfanelli/sev
+revision = b81b1da5df50055600a5b0349b0c4afda677cccb

Why use your tree instead of the mainstream one?

Before this gets merged we need to mirror the subproject
on our GitLab namespace, then use the mirror URL here.

The required meson changes for the sev library are still in review, so I'm still working on a personal branch. Those patches are a blocker for this series right now.

This is moreso another RFC to get feedback on building Rust libraries as QEMU subprojects (and if this is the proper way to do so).


Tyler




reply via email to

[Prev in Thread] Current Thread [Next in Thread]