qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Collin Walling <walling@linux.ibm.com>,
	qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: thuth@redhat.com, mst@redhat.com, cohuck@redhat.com,
	david@redhat.com, pasic@linux.ibm.com, borntraeger@de.ibm.com,
	svens@linux.ibm.com, pbonzini@redhat.com, mihajlov@linux.ibm.com,
	rth@twiddle.net
Subject: Re: [PATCH v3 4/8] s390/sclp: read sccb from mem based on sccb length
Date: Fri, 19 Jun 2020 10:18:40 +0200	[thread overview]
Message-ID: <f233c178-dfab-5ab5-324c-2f3bd15737f6@linux.ibm.com> (raw)
In-Reply-To: <20200618222258.23287-5-walling@linux.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 3185 bytes --]

On 6/19/20 12:22 AM, Collin Walling wrote:
> The header of the SCCB contains the actual length of the SCCB. Instead
> of using a static 4K size, let's allow for a variable size determined
> by the value set in the header. The proper checks are already in place
> to ensure the SCCB length is sufficent to store a full response, and
> that the length does not cross any explicitly-set boundaries.
> 
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> Reviewed-by: Thomas Huth <thuth@redhat.com>

I wonder if this brings a measureable performance penalty with it for
protected guests. It's another ioctl to move the remaining bytes from
KVM to QEMU. On the other hand it's only sclp...

Reviewed-by: Janosch Frank <frankja@linux.ibm.com>

> ---
>  hw/s390x/sclp.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/hw/s390x/sclp.c b/hw/s390x/sclp.c
> index 0710138f91..772b7b3b01 100644
> --- a/hw/s390x/sclp.c
> +++ b/hw/s390x/sclp.c
> @@ -256,9 +256,8 @@ int sclp_service_call_protected(CPUS390XState *env, uint64_t sccb,
>      SCLPDevice *sclp = get_sclp_device();
>      SCLPDeviceClass *sclp_c = SCLP_GET_CLASS(sclp);
>      SCCB work_sccb;
> -    hwaddr sccb_len = sizeof(SCCB);
>  
> -    s390_cpu_pv_mem_read(env_archcpu(env), 0, &work_sccb, sccb_len);
> +    s390_cpu_pv_mem_read(env_archcpu(env), 0, &work_sccb, sizeof(SCCBHeader));
>  
>      if (!sclp_command_code_valid(code)) {
>          work_sccb.h.response_code = cpu_to_be16(SCLP_RC_INVALID_SCLP_COMMAND);
> @@ -269,6 +268,9 @@ int sclp_service_call_protected(CPUS390XState *env, uint64_t sccb,
>          goto out_write;
>      }
>  
> +    s390_cpu_pv_mem_read(env_archcpu(env), 0, &work_sccb,
> +                         be16_to_cpu(work_sccb.h.length));
> +
>      sclp_c->execute(sclp, &work_sccb, code);
>  out_write:
>      s390_cpu_pv_mem_write(env_archcpu(env), 0, &work_sccb,
> @@ -283,8 +285,6 @@ int sclp_service_call(CPUS390XState *env, uint64_t sccb, uint32_t code)
>      SCLPDeviceClass *sclp_c = SCLP_GET_CLASS(sclp);
>      SCCB work_sccb;
>  
> -    hwaddr sccb_len = sizeof(SCCB);
> -
>      /* first some basic checks on program checks */
>      if (env->psw.mask & PSW_MASK_PSTATE) {
>          return -PGM_PRIVILEGED;
> @@ -302,7 +302,7 @@ int sclp_service_call(CPUS390XState *env, uint64_t sccb, uint32_t code)
>       * from playing dirty tricks by modifying the memory content after
>       * the host has checked the values
>       */
> -    cpu_physical_memory_read(sccb, &work_sccb, sccb_len);
> +    cpu_physical_memory_read(sccb, &work_sccb, sizeof(SCCBHeader));
>  
>      /* Valid sccb sizes */
>      if (be16_to_cpu(work_sccb.h.length) < sizeof(SCCBHeader)) {
> @@ -318,6 +318,9 @@ int sclp_service_call(CPUS390XState *env, uint64_t sccb, uint32_t code)
>          goto out_write;
>      }
>  
> +    /* the header contains the actual length of the sccb */
> +    cpu_physical_memory_read(sccb, &work_sccb, be16_to_cpu(work_sccb.h.length));
> +
>      sclp_c->execute(sclp, &work_sccb, code);
>  out_write:
>      cpu_physical_memory_write(sccb, &work_sccb,
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-19  8:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 22:22 [PATCH v3 0/8] s390: Extended-Length SCCB & DIAGNOSE 0x318 Collin Walling
2020-06-18 22:22 ` [PATCH v3 1/8] s390/sclp: get machine once during read scp/cpu info Collin Walling
2020-06-19  8:12   ` Janosch Frank
2020-06-22 10:30   ` Cornelia Huck
2020-06-18 22:22 ` [PATCH v3 2/8] s390/sclp: check sccb len before filling in data Collin Walling
2020-06-19 14:45   ` David Hildenbrand
2020-06-22 10:32   ` Cornelia Huck
2020-06-24 12:01   ` Thomas Huth
2020-06-18 22:22 ` [PATCH v3 3/8] s390/sclp: rework sclp boundary and length checks Collin Walling
2020-06-19 10:50   ` Janosch Frank
2020-06-22 10:43     ` Cornelia Huck
2020-06-22 15:20     ` Christian Borntraeger
2020-06-22 15:22   ` Christian Borntraeger
2020-06-22 15:54     ` Collin Walling
2020-06-18 22:22 ` [PATCH v3 4/8] s390/sclp: read sccb from mem based on sccb length Collin Walling
2020-06-19  8:18   ` Janosch Frank [this message]
2020-06-22 10:45   ` Cornelia Huck
2020-06-18 22:22 ` [PATCH v3 5/8] s390/sclp: use cpu offset to locate cpu entries Collin Walling
2020-06-19  8:21   ` Janosch Frank
2020-06-22 10:47   ` Cornelia Huck
2020-06-18 22:22 ` [PATCH v3 6/8] s390/sclp: add extended-length sccb support for kvm guest Collin Walling
2020-06-24 12:36   ` Cornelia Huck
2020-06-24 12:40     ` Thomas Huth
2020-06-24 12:55       ` Cornelia Huck
2020-06-24 14:49         ` Collin Walling
2020-06-24 14:57           ` Cornelia Huck
2020-06-24 15:19             ` Thomas Huth
2020-06-18 22:22 ` [PATCH v3 7/8] s390/kvm: header sync for diag318 Collin Walling
2020-06-18 22:22 ` [PATCH v3 8/8] s390: guest support for diagnose 0x318 Collin Walling
2020-06-19  9:21   ` Janosch Frank
2020-06-24 12:49   ` Cornelia Huck
2020-06-18 22:33 ` [PATCH v3 0/8] s390: Extended-Length SCCB & DIAGNOSE 0x318 no-reply
2020-06-18 22:51 ` no-reply

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=f233c178-dfab-5ab5-324c-2f3bd15737f6@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=mihajlov@linux.ibm.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=svens@linux.ibm.com \
    --cc=thuth@redhat.com \
    --cc=walling@linux.ibm.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).