From: Janosch Frank <frankja@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>, qemu-s390x@nongnu.org
Cc: qemu-devel@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>,
"Claudio Imbrenda" <imbrenda@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Eric Farman" <farman@linux.ibm.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: Re: [PATCH v2 3/4] s390x/pv: Introduce a s390_pv_check() helper for runtime
Date: Mon, 9 Jan 2023 10:49:29 +0100 [thread overview]
Message-ID: <8e04a10e-8978-494c-5d0f-2507e78134aa@linux.ibm.com> (raw)
In-Reply-To: <bc3ec4b4-1c7a-a4a9-01ea-78fca7ad10c6@kaod.org>
On 1/9/23 10:27, Cédric Le Goater wrote:
> On 1/9/23 10:04, Janosch Frank wrote:
>> On 1/6/23 08:53, Cédric Le Goater wrote:
>>> From: Cédric Le Goater <clg@redhat.com>
>>>
>>> If a secure kernel is started in a non-protected VM, the OS will hang
>>> during boot without giving a proper error message to the user.
>>
>> Most of the time you see nothing in the console because libvirt is too slow. If you start the VM in paused mode, attach a console and then resume it, then you'll see a nice error message.
>
> If you wait long enough, the VM fails to mount / and falls into the dracut
> initrams.
I have the feeling that we're not talking about the same thing here.
A PV VM always starts out as a non-PV VM and is put into PV mode via two
diag308 subcodes (8 & 10). ALL PV subcodes (8 - 10) are spec exceptions
if the host isn't enabled for PV.
There is no way to run a secure image in a non-PV environment. What's
being run is a non-secure bootloader that initiates the switch into
secure mode.
Either the switch fails and we return with DIAG_308_RC_INVAL_FOR_PV to
the non-PV bootloader or we start running in PV mode and __never__
return to the bootloader without a reboot.
>
>>> Perform the checks on Confidential Guest support at runtime with an
>>> helper called from the service call switching the guest to protected
>>> mode.
>>
>> If we don't have PV support then the subcodes >=8 are a specification exception
>> so this is never executed AFAIK.
>
> It is. The test on huge page size was added just above this change.
And the huge page test only applies if the PV feature is in the cpumodel
which also means that the host is PV enabled since it's based on the
capability:
if (subcode >= DIAG308_PV_SET && !s390_has_feat(S390_FEAT_UNPACK)) {
s390_program_interrupt(env, PGM_SPECIFICATION, ra);
return;
}
>
> Thanks,
>
> C.
>
>>
>>> if (env->psw.mask & PSW_MASK_PSTATE) {
>>> s390_program_interrupt(env, PGM_PRIVILEGED, ra);
>>> @@ -176,6 +177,12 @@ out:
>>> return;
>>> }
>>> + if (!s390_pv_check(&local_err)) {
>>> + error_report_err(local_err);
>>> + env->regs[r1 + 1] = DIAG_308_RC_INVAL_FOR_PV;
>>> + return;
>>> + }
>>> +
>>> s390_ipl_reset_request(cs, S390_RESET_PV);
>>> break;
>>> default:
>>
>
next prev parent reply other threads:[~2023-01-09 9:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 7:53 [PATCH v2 0/4] s390x/pv: Improve protected VM support Cédric Le Goater
2023-01-06 7:53 ` [PATCH v2 1/4] s390x/pv: Implement a CGS check helper Cédric Le Goater
2023-01-09 13:34 ` Thomas Huth
2023-01-09 13:57 ` Cédric Le Goater
2023-01-09 14:12 ` Thomas Huth
2023-01-09 14:28 ` Cédric Le Goater
2023-01-06 7:53 ` [PATCH v2 2/4] s390x/pv: Check for support on the host Cédric Le Goater
2023-01-09 8:45 ` Janosch Frank
2023-01-09 9:44 ` Cédric Le Goater
2023-01-09 10:49 ` Janosch Frank
2023-01-06 7:53 ` [PATCH v2 3/4] s390x/pv: Introduce a s390_pv_check() helper for runtime Cédric Le Goater
2023-01-09 9:04 ` Janosch Frank
2023-01-09 9:27 ` Cédric Le Goater
2023-01-09 9:49 ` Janosch Frank [this message]
2023-01-09 13:30 ` Cédric Le Goater
2023-01-09 13:45 ` Janosch Frank
2023-01-09 13:53 ` Cédric Le Goater
2023-01-09 14:31 ` Janosch Frank
2023-01-09 14:52 ` Janosch Frank
2023-01-09 15:24 ` Cédric Le Goater
2023-01-06 7:53 ` [PATCH v2 4/4] s390x/pv: Move check on hugepage under s390_pv_guest_check() Cédric Le Goater
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=8e04a10e-8978-494c-5d0f-2507e78134aa@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@kaod.org \
--cc=clg@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/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).