From: "Jörg Rödel" <joro@8bytes.org>
To: "Gupta, Pankaj" <pankaj.gupta@amd.com>
Cc: svsm-devel@coconut-svsm.dev
Subject: Re: [svsm-devel] SVSM Host Kernel KVM Update Required
Date: Wed, 12 Mar 2025 15:54:32 +0100 [thread overview]
Message-ID: <Z9GgKF7w6Qa-HpIM@8bytes.org> (raw)
In-Reply-To: <c289de63-1723-4c00-9c3d-69628b80bec8@amd.com>
On Wed, Mar 12, 2025 at 03:33:15PM +0100, Gupta, Pankaj wrote:
> So, the support was not working and got triggered when config check in
> 'determine_cet_support()' was removed.
Right, actually it was broken before already when building with the
shadow-stack feature. But since this was not enabled by default nobody
noticed. With the feature check removed it triggered for everyone.
Regards,
Joerg
next prev parent reply other threads:[~2025-03-12 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:21 [svsm-devel] SVSM Host Kernel KVM Update Required Jörg Rödel
2025-03-12 9:36 ` Gupta, Pankaj
2025-03-12 9:48 ` Gupta, Pankaj
2025-03-12 10:02 ` Jörg Rödel
2025-03-12 14:33 ` Gupta, Pankaj
2025-03-12 14:54 ` Jörg Rödel [this message]
2025-03-12 20:05 ` Gupta, Pankaj
2025-03-13 5:54 ` 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=Z9GgKF7w6Qa-HpIM@8bytes.org \
--to=joro@8bytes.org \
--cc=pankaj.gupta@amd.com \
--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