From: "José Pekkarinen" <jose.pekkarinen@foxhound.fi>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: x86@kernel.org, hpa@zytor.com, kvm@vger.kernel.org,
seanjc@google.com, dave.hansen@linux.intel.com,
linux-kernel@vger.kernel.org, mingo@redhat.com, bp@alien8.de,
tglx@linutronix.de,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH] kvm/sev: remove redundant MISC_CG_RES_SEV_ES
Date: Thu, 12 Oct 2023 16:45:30 +0000 [thread overview]
Message-ID: <6a777c72a6dc15ad80ecbedd4c6c35d9@foxhound.fi> (raw)
In-Reply-To: <9faf1a1a-af49-5f6f-9f33-6cf57f884c44@redhat.com>
On 2023-10-12 13:43, Paolo Bonzini wrote:
> On 10/10/23 19:49, José Pekkarinen wrote:
>> SEV-ES is an extra encrypted state that shares common resources
>> with SEV. Using an extra CG for its purpose doesn't seem to
>> provide much value. This patch will clean up the control group
>> along with multiple checks that become redundant with it.
>>
>> The patch will also remove a redundant logic on sev initialization
>> that produces SEV-ES to be disabled, while supported by the cpu
>> and requested by the user through the sev_es parameter.
>
> In what sense is it shared? The SEV ASIDs and the SEV-ES ASIDs are
> separate (and in both cases limited) resources, and therefore they
> have separate cgroups.
Nevermind this patch, after a painful bios upgrade I got sev-es
available in it, and I was able to launch some test vm on it, so this
may only be breaking things. Sorry for the noise!
José.
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2023-10-12 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 17:49 [PATCH] kvm/sev: remove redundant MISC_CG_RES_SEV_ES José Pekkarinen
2023-10-12 13:43 ` Paolo Bonzini
2023-10-12 16:45 ` José Pekkarinen [this message]
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=6a777c72a6dc15ad80ecbedd4c6c35d9@foxhound.fi \
--to=jose.pekkarinen@foxhound.fi \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).