From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
david@redhat.com, thuth@redhat.com, seiden@linux.ibm.com,
mhartmay@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH 3/8] s390x: sie: Add UV information into VM struct
Date: Tue, 23 Nov 2021 11:54:47 +0100 [thread overview]
Message-ID: <20211123115447.25d9ab9c@p-imbrenda> (raw)
In-Reply-To: <20211123103956.2170-4-frankja@linux.ibm.com>
On Tue, 23 Nov 2021 10:39:51 +0000
Janosch Frank <frankja@linux.ibm.com> wrote:
> We need to save the handles for the VM and the VCPU so we can retrieve
> them easily after their creation. Since the SIE lib is single guest
multiple guest CPUs will be needed for testing some functions, but I
guess that's something for me to do :)
> cpu only we only save one vcpu handle.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> lib/s390x/sie.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/lib/s390x/sie.h b/lib/s390x/sie.h
> index c6eb6441..1a12faa7 100644
> --- a/lib/s390x/sie.h
> +++ b/lib/s390x/sie.h
> @@ -200,6 +200,11 @@ union {
> uint64_t gvrd; /* 0x01f8 */
> } __attribute__((packed));
>
> +struct vm_uv {
> + uint64_t vm_handle;
> + uint64_t vcpu_handle;
> +};
> +
> struct vm_save_regs {
> uint64_t grs[16];
> uint64_t fprs[16];
> @@ -220,6 +225,7 @@ struct vm {
> struct vm_save_area save_area;
> void *sca; /* System Control Area */
> uint8_t *crycb; /* Crypto Control Block */
> + struct vm_uv uv; /* PV UV information */
> /* Ptr to first guest page */
> uint8_t *guest_mem;
> };
next prev parent reply other threads:[~2021-11-23 11:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 10:39 [kvm-unit-tests PATCH 0/8] s390x: sie: Add PV snippet support Janosch Frank
2021-11-23 10:39 ` [kvm-unit-tests PATCH 1/8] lib: s390x: sie: Add sca allocation and freeing Janosch Frank
2021-11-23 10:51 ` Claudio Imbrenda
2021-11-23 10:39 ` [kvm-unit-tests PATCH 2/8] s390x: sie: Add PV fields to SIE control block Janosch Frank
2021-11-23 10:52 ` Claudio Imbrenda
2021-11-23 10:39 ` [kvm-unit-tests PATCH 3/8] s390x: sie: Add UV information into VM struct Janosch Frank
2021-11-23 10:54 ` Claudio Imbrenda [this message]
2021-11-23 12:49 ` Janosch Frank
2021-11-23 10:39 ` [kvm-unit-tests PATCH 4/8] s390x: uv: Add more UV call functions Janosch Frank
2021-11-23 10:56 ` Claudio Imbrenda
2021-11-23 10:39 ` [kvm-unit-tests PATCH 5/8] s390x: lib: Extend UV library with PV guest management Janosch Frank
2021-11-23 11:13 ` Claudio Imbrenda
2021-11-23 10:39 ` [kvm-unit-tests PATCH 6/8] lib: s390: sie: Add PV guest register handling Janosch Frank
2021-11-23 11:14 ` Claudio Imbrenda
2021-11-23 10:39 ` [kvm-unit-tests PATCH 7/8] s390x: snippets: Add PV support Janosch Frank
2021-11-23 11:22 ` Claudio Imbrenda
2021-11-26 13:28 ` Janosch Frank
2021-12-03 9:29 ` Janosch Frank
2022-01-13 13:10 ` Janosch Frank
2022-01-13 13:17 ` Claudio Imbrenda
2021-11-23 10:39 ` [kvm-unit-tests PATCH 8/8] s390x: sie: Add PV diag test Janosch Frank
2021-11-23 11:41 ` Claudio Imbrenda
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=20211123115447.25d9ab9c@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mhartmay@linux.ibm.com \
--cc=seiden@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