From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:22414 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727715AbhAMLIV (ORCPT ); Wed, 13 Jan 2021 06:08:21 -0500 Subject: Re: [kvm-unit-tests PATCH v4 9/9] s390x: sclp: Add CPU entry offset comment References: <20210112132054.49756-1-frankja@linux.ibm.com> <20210112132054.49756-10-frankja@linux.ibm.com> <6f93c964-9606-246c-7266-85044803e49b@redhat.com> From: Janosch Frank Message-ID: Date: Wed, 13 Jan 2021 12:06:32 +0100 MIME-Version: 1.0 In-Reply-To: <6f93c964-9606-246c-7266-85044803e49b@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-ID: To: David Hildenbrand , kvm@vger.kernel.org Cc: thuth@redhat.com, borntraeger@de.ibm.com, imbrenda@linux.ibm.com, cohuck@redhat.com, linux-s390@vger.kernel.org On 1/13/21 11:25 AM, David Hildenbrand wrote: > On 12.01.21 14:20, Janosch Frank wrote: >> Let's make it clear that there is something at the end of the >> struct. The exact offset is reported by the cpu_offset member. >> >> Signed-off-by: Janosch Frank >> --- >> lib/s390x/sclp.h | 5 ++++- >> 1 file changed, 4 insertions(+), 1 deletion(-) >> >> diff --git a/lib/s390x/sclp.h b/lib/s390x/sclp.h >> index dccbaa8..395895f 100644 >> --- a/lib/s390x/sclp.h >> +++ b/lib/s390x/sclp.h >> @@ -134,7 +134,10 @@ typedef struct ReadInfo { >> uint8_t reserved7[134 - 128]; >> uint8_t byte_134_diag318 : 1; >> uint8_t : 7; >> - struct CPUEntry entries[0]; >> + /* >> + * The cpu entries follow, they start at the offset specified >> + * in offset_cpu. >> + */ > > I mean, that's just best practice. At least when I spot "[0];" and the > end of a struct, I know what's happening. > > No strong opinion about the comment, I wouldn't need it to understand it. The comment was a wish by Thomas. Anyway, it doesn't hurt :) > >> } __attribute__((packed)) ReadInfo; >> >> typedef struct ReadCpuInfo { >> > >