From: Marc Hartmayer <mhartmay@linux.ibm.com>
To: Andrew Jones <drjones@redhat.com>,
Marc Hartmayer <mhartmay@linux.ibm.com>
Cc: kvm@vger.kernel.org, Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [kvm-unit-tests RFC] s390x: Add Protected VM support
Date: Thu, 07 May 2020 15:14:53 +0200 [thread overview]
Message-ID: <871rnv7upe.fsf@linux.ibm.com> (raw)
In-Reply-To: <20200506135016.ml3k73siokhltyl5@kamzik.brq.redhat.com>
On Wed, May 06, 2020 at 03:50 PM +0200, Andrew Jones <drjones@redhat.com> wrote:
> On Wed, May 06, 2020 at 02:46:36PM +0200, 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>
>> ---
>> @@ -16,6 +16,8 @@
>> # # a test. The check line can contain multiple files
>> # # to check separated by a space but each check
>> # # parameter needs to be of the form <path>=<value>
>> +# pv_support = 0|1 # Optionally specify whether a test supports the
>> +# # execution as a PV guest.
>
> Maybe pv_supported vs. pv_support?
pv_supported is better, thanks.
>>
>> exec {fd}<"$unittests"
>>
>> while read -r -u $fd line; do
>> if [[ "$line" =~ ^\[(.*)\]$ ]]; then
>> - "$cmd" "$testname" "$groups" "$smp" "$kernel" "$opts" "$arch" "$check" "$accel" "$timeout"
This line was accidentally removed.
>> + if [ "${pv_support}" == 1 ]; then
>> + pv_cmd "$cmd" "$testname" "$groups" "$smp" "$kernel" "$opts" "$arch" "$check" "$accel" "$timeout"
>> + fi
>> +
>> testname=${BASH_REMATCH[1]}
>> smp=1
>> kernel=""
>> @@ -27,6 +48,7 @@ function for_each_unittest()
>> check=""
>> accel=""
>> timeout=""
>> + pv_support=""
>> elif [[ $line =~ ^file\ *=\ *(.*)$ ]]; then
>> kernel=$TEST_DIR/${BASH_REMATCH[1]}
>> elif [[ $line =~ ^smp\ *=\ *(.*)$ ]]; then
>> @@ -43,8 +65,14 @@ function for_each_unittest()
>> accel=${BASH_REMATCH[1]}
>> elif [[ $line =~ ^timeout\ *=\ *(.*)$ ]]; then
>> timeout=${BASH_REMATCH[1]}
>> + elif [[ $line =~ ^pv_support\ *=\ *(.*)$ ]]; then
>> + pv_support=${BASH_REMATCH[1]}
>> fi
>> done
>> +
>> "$cmd" "$testname" "$groups" "$smp" "$kernel" "$opts" "$arch" "$check" "$accel" "$timeout"
>> + if [ "${pv_support}" == 1 ]; then
>> + pv_cmd "$cmd" "$testname" "$groups" "$smp" "$kernel" "$opts" "$arch" "$check" "$accel" "$timeout"
>> + fi
>> exec {fd}<&-
>> }
>> --
>> 2.17.0
>>
>
> I don't think making the changes to scripts/common.bash will work for
> standalone tests.
With the fix above it works (tested on x86 and s390x).
$ make standalone
Written tests/selftest-setup.
Written tests/intercept.
Written tests/intercept_PV.
Written tests/emulator.
Written tests/emulator_PV.
Written tests/sieve.
Written tests/sieve_PV.
…
> Why not do this stuff in s390x/run instead?
I will try.
> Also,
> do you need the pv_support[ed] parameter? You could just do a
> [ -f "${kernel%.elf}.pv.img" ] to decide if you should run again
> with PV, right?
AFAIK, for the other test cases the kernel file is also not checked, but
this would be an option - thanks.
>
> Thanks,
> drew
>
Thanks for the feedback!
--
Kind regards / Beste Grüße
Marc Hartmayer
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Gregor Pillen
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2020-05-07 13:15 UTC|newest]
Thread overview: 10+ 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 12:46 ` Marc Hartmayer
2020-05-06 13:50 ` Andrew Jones
2020-05-07 13:14 ` Marc Hartmayer [this message]
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
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=871rnv7upe.fsf@linux.ibm.com \
--to=mhartmay@linux.ibm.com \
--cc=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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.