From: Cornelia Huck <cohuck@redhat.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
qemu-devel@nongnu.org, david@redhat.com
Subject: Re: [PATCH v10 09/16] s390x: protvirt: SCLP interpretation
Date: Thu, 19 Mar 2020 13:09:45 +0100 [thread overview]
Message-ID: <20200319130945.4134ed82.cohuck@redhat.com> (raw)
In-Reply-To: <20200318143047.2335-10-frankja@linux.ibm.com>
On Wed, 18 Mar 2020 10:30:40 -0400
Janosch Frank <frankja@linux.ibm.com> wrote:
> SCLP for a protected guest is done over the SIDAD, so we need to use
> the s390_cpu_pv_mem_* functions to access the SIDAD instead of guest
> memory when reading/writing SCBs.
>
> To not confuse the sclp emulation, we set 0x4000 as the SCCB address,
> since the function that injects the sclp external interrupt would
> reject a zero sccb address.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Reviewed-by: Claudio Imbrenda <imbrenda@linux.ibm.com>
> ---
> hw/s390x/sclp.c | 65 ++++++++++++++++++++++++++++++++++-------
> include/hw/s390x/sclp.h | 2 ++
> target/s390x/kvm.c | 25 ++++++++++++----
> 3 files changed, 76 insertions(+), 16 deletions(-)
>
> diff --git a/hw/s390x/sclp.c b/hw/s390x/sclp.c
> index af0bfbc2eca74767..6486890fecea4b3c 100644
> --- a/hw/s390x/sclp.c
> +++ b/hw/s390x/sclp.c
> @@ -33,6 +33,22 @@ static inline SCLPDevice *get_sclp_device(void)
> return sclp;
> }
>
> +static inline bool sclp_command_code_valid(uint32_t code)
> +{
> + switch (code & SCLP_CMD_CODE_MASK) {
> + case SCLP_CMDW_READ_SCP_INFO:
> + case SCLP_CMDW_READ_SCP_INFO_FORCED:
> + case SCLP_CMDW_READ_CPU_INFO:
> + case SCLP_CMDW_CONFIGURE_IOA:
> + case SCLP_CMDW_DECONFIGURE_IOA:
> + case SCLP_CMD_READ_EVENT_DATA:
> + case SCLP_CMD_WRITE_EVENT_DATA:
> + case SCLP_CMD_WRITE_EVENT_MASK:
> + return true;
> + }
> + return false;
> +}
> +
> static void prepare_cpu_entries(SCLPDevice *sclp, CPUEntry *entry, int *count)
> {
> MachineState *ms = MACHINE(qdev_get_machine());
> @@ -193,6 +209,43 @@ static void sclp_execute(SCLPDevice *sclp, SCCB *sccb, uint32_t code)
> }
> }
>
> +/*
> + * We only need the address to have something valid for the
> + * service_interrupt call.
> + */
> +#define SCLP_PV_DUMMY_ADDR 0x4000
> +int sclp_service_call_protected(CPUS390XState *env, uint64_t sccb,
> + uint32_t code)
> +{
> + SCLPDevice *sclp = get_sclp_device();
> + SCLPDeviceClass *sclp_c = SCLP_GET_CLASS(sclp);
> + SCCB work_sccb;
> + hwaddr sccb_len = sizeof(SCCB);
> +
> + /*
> + * Only a very limited number of calls is permitted by the
> + * Ultravisor and we support all of them, so we don't check for
This is no longer true, no?
> + * them. All other specification exceptions are also interpreted
> + * by the Ultravisor and hence never cause an exit we need to
> + * handle.
> + *
> + * Setting the CC is also done by the Ultravisor.
> + */
> + s390_cpu_pv_mem_read(env_archcpu(env), 0, &work_sccb, sccb_len);
> +
> + if (!sclp_command_code_valid(code)) {
> + work_sccb.h.response_code = cpu_to_be16(SCLP_RC_INVALID_SCLP_COMMAND);
> + goto out_write;
> + }
> +
> + sclp_c->execute(sclp, &work_sccb, code);
> +out_write:
> + s390_cpu_pv_mem_write(env_archcpu(env), 0, &work_sccb,
> + be16_to_cpu(work_sccb.h.length));
> + sclp_c->service_interrupt(sclp, SCLP_PV_DUMMY_ADDR);
> + return 0;
> +}
> +
> int sclp_service_call(CPUS390XState *env, uint64_t sccb, uint32_t code)
> {
> SCLPDevice *sclp = get_sclp_device();
next prev parent reply other threads:[~2020-03-19 12:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:30 [PATCH v10 00/16] s390x: Protected Virtualization support Janosch Frank
2020-03-18 14:30 ` [PATCH v10 01/16] s390x: Move diagnose 308 subcodes and rcs into ipl.h Janosch Frank
2020-03-18 16:42 ` Cornelia Huck
2020-03-18 20:29 ` Christian Borntraeger
2020-03-19 12:42 ` Claudio Imbrenda
2020-03-18 14:30 ` [PATCH v10 02/16] Sync pv Janosch Frank
2020-03-18 14:30 ` [PATCH v10 03/16] s390x: protvirt: Support unpack facility Janosch Frank
2020-03-19 11:08 ` Cornelia Huck
2020-03-19 11:55 ` Janosch Frank
2020-03-19 11:57 ` Christian Borntraeger
2020-03-19 11:57 ` Janosch Frank
2020-03-18 14:30 ` [PATCH v10 04/16] s390x: protvirt: Add migration blocker Janosch Frank
2020-03-18 14:30 ` [PATCH v10 05/16] s390x: protvirt: Inhibit balloon when switching to protected mode Janosch Frank
2020-03-18 17:27 ` Cornelia Huck
2020-03-18 14:30 ` [PATCH v10 06/16] s390x: protvirt: KVM intercept changes Janosch Frank
2020-03-18 14:30 ` [PATCH v10 07/16] s390x: Add SIDA memory ops Janosch Frank
2020-03-18 14:30 ` [PATCH v10 08/16] s390x: protvirt: Move STSI data over SIDAD Janosch Frank
2020-03-18 17:57 ` Cornelia Huck
2020-03-18 14:30 ` [PATCH v10 09/16] s390x: protvirt: SCLP interpretation Janosch Frank
2020-03-19 12:09 ` Cornelia Huck [this message]
2020-03-19 12:46 ` Janosch Frank
2020-03-19 12:50 ` Cornelia Huck
2020-03-18 14:30 ` [PATCH v10 10/16] s390x: protvirt: Set guest IPL PSW Janosch Frank
2020-03-18 18:00 ` Cornelia Huck
2020-03-19 8:19 ` Janosch Frank
2020-03-18 14:30 ` [PATCH v10 11/16] s390x: protvirt: Move diag 308 data over SIDA Janosch Frank
2020-03-19 12:12 ` Cornelia Huck
2020-03-18 14:30 ` [PATCH v10 12/16] s390x: protvirt: Disable address checks for PV guest IO emulation Janosch Frank
2020-03-18 14:30 ` [PATCH v10 13/16] s390x: protvirt: Move IO control structures over SIDA Janosch Frank
2020-03-19 12:23 ` Cornelia Huck
2020-03-19 12:50 ` Janosch Frank
2020-03-18 14:30 ` [PATCH v10 14/16] s390x: protvirt: Handle SIGP store status correctly Janosch Frank
2020-03-18 14:30 ` [PATCH v10 15/16] docs: system: Add protvirt docs Janosch Frank
2020-03-18 14:53 ` Cornelia Huck
2020-03-19 9:04 ` Janosch Frank
2020-03-19 9:59 ` Cornelia Huck
2020-03-18 16:50 ` Christian Borntraeger
2020-03-18 14:30 ` [PATCH v10 16/16] s390x: Add unpack facility feature to GA1 Janosch Frank
2020-03-18 16:43 ` Cornelia Huck
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=20200319130945.4134ed82.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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.