From: David Hildenbrand <david@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
thuth@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests RFC 0/2] s390x: Add snippet support
Date: Thu, 20 May 2021 15:36:47 +0200 [thread overview]
Message-ID: <7c17d790-5a3c-d4ea-8d78-7148dbc6ca60@redhat.com> (raw)
In-Reply-To: <20210520094730.55759-1-frankja@linux.ibm.com>
On 20.05.21 11:47, Janosch Frank wrote:
> The SIE support allows us to run guests and test the hypervisor's
> (V)SIE implementation. However it requires that the guest instructions
> are binary which limits the complexity of the guest code.
>
> The snippet support provides a way to write guest code as ASM or C and
> simply memcpy it into guest memory. Some of the KVM-unit-test library
> can be re-used which further speeds up guest code development.
>
> The included mvpg-sie test helped us to deliver the KVM mvpg fixes
> which Claudio posted a short while ago. In the future I'll post Secure
> Execution snippet support patches which was my initial goal with this
> series anyway.
>
> I heard you liked tests so I put tests inside tests so you can test
> while you test.
The idea sounds sane to me.
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2021-05-20 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 9:47 [kvm-unit-tests RFC 0/2] s390x: Add snippet support Janosch Frank
2021-05-20 9:47 ` [kvm-unit-tests RFC 1/2] s390x: Add guest " Janosch Frank
2021-05-25 16:44 ` Claudio Imbrenda
2021-05-26 10:12 ` Janosch Frank
2021-06-21 10:10 ` Thomas Huth
2021-06-21 12:19 ` Janosch Frank
2021-06-21 12:32 ` Thomas Huth
2021-06-21 12:39 ` Janosch Frank
2021-06-21 13:28 ` Thomas Huth
2021-06-21 14:42 ` Janosch Frank
2021-06-21 14:59 ` Thomas Huth
2021-05-20 9:47 ` [kvm-unit-tests RFC 2/2] s390x: mvpg: Add SIE mvpg test Janosch Frank
2021-05-25 17:37 ` Claudio Imbrenda
2021-05-26 10:17 ` Janosch Frank
2021-05-27 14:35 ` Janosch Frank
2021-06-21 10:23 ` Thomas Huth
2021-06-21 12:41 ` Janosch Frank
2021-05-20 13:36 ` David Hildenbrand [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=7c17d790-5a3c-d4ea-8d78-7148dbc6ca60@redhat.com \
--to=david@redhat.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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).