From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Marc Hartmayer <mhartmay@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
kvm@vger.kernel.org
Cc: Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Andrew Jones <drjones@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests RFC] s390x: Add Protected VM support
Date: Thu, 7 May 2020 14:34:51 +0200 [thread overview]
Message-ID: <2900c255-5ccb-2c99-b376-0b502e7becac@de.ibm.com> (raw)
In-Reply-To: <877dxo6i6v.fsf@linux.ibm.com>
On 07.05.20 14:30, Marc Hartmayer wrote:
> On Wed, May 06, 2020 at 04:03 PM +0200, Janosch Frank <frankja@linux.ibm.com> wrote:
>> On 5/6/20 2:46 PM, Marc Hartmayer wrote:
>>> Add support for Protected Virtual Machine (PVM) tests. For starting a
>>> PVM guest we must be able to generate a PVM image by using the
>>> `genprotimg` tool from the s390-tools collection. This requires the
>>> ability to pass a machine-specific host-key document, so the option
>>> `--host-key-document` is added to the configure script.
>>>
>>> Signed-off-by: Marc Hartmayer <mhartmay@linux.ibm.com>
>
> […snip…]
>
>>> [intercept]
>>> file = intercept.elf
>>> +pv_support = 1
>>
>> So, let's do this discussion once more:
>> Why would we need a opt-in for something which works on all our current
>> tests? I'd much rather have a opt-out or just a bail-out when running
>> the test like I already implemented for the storage key related
>> tests...
>>
>> I don't see any benefit for this right now other than forcing me to add
>> another line to this file that was not needed before..
>>
>
> Okay. So shall I add an option ’pv_not_supported’? Or simply assume that
> the actual test cases will handle it?
I would suggest to fix the testcases (e.g. do an early exit when we are running
secure and we know it does not work)
prev parent reply other threads:[~2020-05-07 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 12:46 [kvm-unit-tests RFC] s390x: Add Protected VM support Marc Hartmayer
2020-05-06 13:50 ` Andrew Jones
2020-05-07 13:14 ` Marc Hartmayer
2020-05-07 13:40 ` Marc Hartmayer
2020-05-06 14:03 ` Janosch Frank
2020-05-06 14:05 ` David Hildenbrand
2020-05-06 14:26 ` Janosch Frank
2020-05-07 12:30 ` Marc Hartmayer
2020-05-07 12:34 ` Christian Borntraeger [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=2900c255-5ccb-2c99-b376-0b502e7becac@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
--cc=pbonzini@redhat.com \
--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