[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v3 5/8] s390/sclp: use cpu offset to locate cpu entries
From: |
Cornelia Huck |
Subject: |
Re: [PATCH v3 5/8] s390/sclp: use cpu offset to locate cpu entries |
Date: |
Mon, 22 Jun 2020 12:47:23 +0200 |
On Thu, 18 Jun 2020 18:22:55 -0400
Collin Walling <walling@linux.ibm.com> wrote:
> The start of the CPU entry region in the Read SCP Info response data is
> denoted by the offset_cpu field. As such, QEMU needs to begin creating
> entries at this address. Note that the length of the Read SCP Info data
> (data_len) denotes the same value as the cpu offset.
>
> This is in preparation of when Read SCP Info inevitably introduces new
> bytes that push the start of the CPUEntry field further away.
>
> Read CPU Info is unlikely to ever change, so let's not bother
> accounting for the offset there.
>
> Signed-off-by: Collin Walling <walling@linux.ibm.com>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> ---
> hw/s390x/sclp.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
- [PATCH v3 0/8] s390: Extended-Length SCCB & DIAGNOSE 0x318, Collin Walling, 2020/06/18
- [PATCH v3 2/8] s390/sclp: check sccb len before filling in data, Collin Walling, 2020/06/18
- [PATCH v3 1/8] s390/sclp: get machine once during read scp/cpu info, Collin Walling, 2020/06/18
- [PATCH v3 5/8] s390/sclp: use cpu offset to locate cpu entries, Collin Walling, 2020/06/18
- [PATCH v3 4/8] s390/sclp: read sccb from mem based on sccb length, Collin Walling, 2020/06/18
- [PATCH v3 3/8] s390/sclp: rework sclp boundary and length checks, Collin Walling, 2020/06/18
- [PATCH v3 8/8] s390: guest support for diagnose 0x318, Collin Walling, 2020/06/18