From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Nico Boehr <nrb@linux.ibm.com>
Cc: kvm@vger.kernel.org, frankja@linux.ibm.com, thuth@redhat.com
Subject: Re: [kvm-unit-tests PATCH v1 2/2] s390x: create persistent comm-key
Date: Thu, 21 Jul 2022 18:32:45 +0200 [thread overview]
Message-ID: <20220721183245.36b9d126@p-imbrenda> (raw)
In-Reply-To: <20220721132647.552298-3-nrb@linux.ibm.com>
On Thu, 21 Jul 2022 15:26:47 +0200
Nico Boehr <nrb@linux.ibm.com> wrote:
> To decrypt the dump of a PV guest, the comm-key (CCK) is required. Until
> now, no comm-key was provided to genprotimg, therefore decrypting the
> dump of a kvm-unit-test under PV was not possible.
>
> This patch makes sure that we create a random CCK if there's no
> $(TEST_DIR)/comm.key file.
>
> Also allow dumping of PV tests by passing the appropriate PCF to
> genprotimg (bit 34). --x-pcf is used to be compatible with older
> genprotimg versions, which don't support --enable-dump. 0xe0 is the
> default PCF value and only bit 34 is added.
>
> Unfortunately, recent versions of genprotimg removed the --x-comm-key
> argument which was used by older versions to specify the CCK. To support
> these versions, we need to parse the genprotimg help output and decide
> which argument to use.
I wonder if we can simply support only the newest version?
would make the code cleaner, and updating genprotimg is not too
complicated
[...]
next prev parent reply other threads:[~2022-07-21 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 13:26 [kvm-unit-tests PATCH v1 0/2] s390x: dump support for PV tests Nico Boehr
2022-07-21 13:26 ` [kvm-unit-tests PATCH v1 1/2] s390x: factor out common args for genprotimg Nico Boehr
2022-07-21 16:30 ` Claudio Imbrenda
2022-07-21 13:26 ` [kvm-unit-tests PATCH v1 2/2] s390x: create persistent comm-key Nico Boehr
2022-07-21 16:32 ` Claudio Imbrenda [this message]
2022-07-22 7:31 ` Nico Boehr
2022-08-24 8:15 ` Janosch Frank
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=20220721183245.36b9d126@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.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