From: Heiko Carstens <hca@linux.ibm.com>
To: Steffen Eiden <seiden@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Nico Boehr <nrb@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/1] s390: Add attestation query information
Date: Fri, 20 May 2022 13:11:14 +0200 [thread overview]
Message-ID: <Yod3Uiu2hRc9vas7@osiris> (raw)
In-Reply-To: <20220518135908.1110319-1-seiden@linux.ibm.com>
On Wed, May 18, 2022 at 01:59:07PM +0000, Steffen Eiden wrote:
> By design the uv-device does not check whether an incoming attestation
> measurement request only specifies valid plaintext flags or has the
> right request version, as these values are verified by the Ultravisor
> anyway. However, the userspace program that generates these requests
> might want to know which flags/versions are supported in order to
> create requests without trial and error. Therefore, we must expose the
> supported plaintext flags and versions to userspace.
>
> since v1:
> * rebased on Janosch's "kvm: s390: Add PV dump support" series
> * added rationale as this cover letter
Thanks for adding the cover letter! However what I really meant (and
failed to write) is that the rationale should be part of the patch
description. Anyway; whoever picks this patch will hopefully integrate
your cover letter description into the commit.
prev parent reply other threads:[~2022-05-20 11:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 13:59 [PATCH v2 0/1] s390: Add attestation query information Steffen Eiden
2022-05-18 13:59 ` [PATCH v2 1/1] " Steffen Eiden
2022-05-20 14:48 ` Janosch Frank
2022-05-24 14:55 ` Claudio Imbrenda
2022-06-01 10:02 ` Steffen Eiden
2022-06-23 6:26 ` Janosch Frank
2022-05-20 11:11 ` Heiko Carstens [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=Yod3Uiu2hRc9vas7@osiris \
--to=hca@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=seiden@linux.ibm.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