From: "Jörg Rödel" <joro@8bytes.org>
To: svsm-devel@coconut-svsm.dev
Subject: [svsm-devel] Linux and QEMU branches updated
Date: Tue, 17 Dec 2024 17:23:44 +0100 [thread overview]
Message-ID: <Z2GlkOf63fGpsks2@8bytes.org> (raw)
Hi everyone,
A few weeks ago we discussed the plan to update the Linux and QEMU
development branches for the SVSM to the versions Roy provided.
Today I made this change and updated the `svsm` branches in both
repositories. I also updated the SVSM tree to work with the new KVM
base, which includes updated documentation, launch script, and disabling
one of the unit-tests[1].
So hereby I ask everyone to update their development/test environments
to use the latest Linux, QEMU and SVSM branches from the project.
Why is this important?
There is a PR pending for the SVSM which introduces the use of the TPR
for managing IRQ priorities. This is part of the ongoing work to enable
IRQs in the SVSM and add the ability to send IPIs, which is required to
enable other platforms besides AMD SEV-SNP.
With the old 6.8-based kernel the TPR was shared across VMPLs, which
made the SVSM observe values set by the Linux kernel. This breaks the
SVSM as soon as Linux initialized the local APIC.
Going forward, when the SVSM TPR PR gets merged, the SVSM will no longer
work on the 6.8 kernel, so please everyone make sure to update your
development/test environments and let me know in case you run into any
problems.
Regards,
Joerg
[1] That test fails now because it relies on an intercept bit no longer
set.
next reply other threads:[~2024-12-17 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 16:23 Jörg Rödel [this message]
2024-12-18 11:09 ` [svsm-devel] Linux and QEMU branches updated Stefano Garzarella
2024-12-18 11:16 ` Jörg Rödel
2024-12-18 11:40 ` Oliver Steffen
2024-12-18 12:00 ` Jörg Rödel
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=Z2GlkOf63fGpsks2@8bytes.org \
--to=joro@8bytes.org \
--cc=svsm-devel@coconut-svsm.dev \
/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