From: Janosch Frank <frankja@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
david@redhat.com, cohuck@redhat.com
Subject: Re: [kvm-unit-tests PATCH 3/5] lib: s390x: uv: Int type cleanup
Date: Mon, 5 Jul 2021 11:33:02 +0200 [thread overview]
Message-ID: <3876955c-24bd-2052-e634-8436f7558df4@linux.ibm.com> (raw)
In-Reply-To: <d2798bf7-3018-e311-1dfb-120144fb343d@redhat.com>
On 7/4/21 9:51 AM, Thomas Huth wrote:
> On 29/06/2021 15.33, Janosch Frank wrote:
>> These structs have largely been copied from the kernel so they still
>> have the old uint short types which we want to avoid in favor of the
>> uint*_t ones.
>>
>> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
>> ---
>> lib/s390x/asm/uv.h | 142 +++++++++++++++++++++++----------------------
>> 1 file changed, 72 insertions(+), 70 deletions(-)
>>
>> diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
>> index dc3e02d..96a2a7e 100644
>> --- a/lib/s390x/asm/uv.h
>> +++ b/lib/s390x/asm/uv.h
>> @@ -12,6 +12,8 @@
>> #ifndef _ASMS390X_UV_H_
>> #define _ASMS390X_UV_H_
>>
>> +#include <stdint.h>
>> +
>> #define UVC_RC_EXECUTED 0x0001
>> #define UVC_RC_INV_CMD 0x0002
>> #define UVC_RC_INV_STATE 0x0003
>> @@ -68,73 +70,73 @@ enum uv_cmds_inst {
>> };
>>
>> struct uv_cb_header {
>> - u16 len;
>> - u16 cmd; /* Command Code */
>> - u16 rc; /* Response Code */
>> - u16 rrc; /* Return Reason Code */
>> + uint16_t len;
>> + uint16_t cmd; /* Command Code */
>> + uint16_t rc; /* Response Code */
>> + uint16_t rrc; /* Return Reason Code */
>> } __attribute__((packed)) __attribute__((aligned(8)));
>
> Hmm, for files that are more or less a copy from the corresponding kernel
> header, I'm not sure whether it makes sense to convert them to the stdint.h
> types? It might be better to keep the kernel types so that updates to this
> header can be ported more easily to the kvm-unit-tests later?
sie.h contents are 90% sblk which came directly from KVM...
Do you really want to have exceptions for one file? Because if that's
the case then I see no sense in changing other things over since I
prefer using short types.
>
> Thomas
>
next prev parent reply other threads:[~2021-07-05 9:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 13:33 [kvm-unit-tests PATCH 0/5] s390x: sie and uv cleanups Janosch Frank
2021-06-29 13:33 ` [kvm-unit-tests PATCH 1/5] s390x: sie: Add missing includes Janosch Frank
2021-06-30 8:59 ` Cornelia Huck
2021-07-04 7:47 ` Thomas Huth
2021-07-23 17:10 ` Claudio Imbrenda
2021-06-29 13:33 ` [kvm-unit-tests PATCH 2/5] s390x: sie: Fix sie.h integer types Janosch Frank
2021-06-30 9:00 ` Cornelia Huck
2021-07-04 7:45 ` Thomas Huth
2021-07-23 17:10 ` Claudio Imbrenda
2021-06-29 13:33 ` [kvm-unit-tests PATCH 3/5] lib: s390x: uv: Int type cleanup Janosch Frank
2021-06-30 9:03 ` Cornelia Huck
2021-07-04 7:51 ` Thomas Huth
2021-07-05 9:33 ` Janosch Frank [this message]
2021-07-05 9:41 ` Thomas Huth
2021-07-23 17:15 ` Claudio Imbrenda
2021-06-29 13:33 ` [kvm-unit-tests PATCH 4/5] lib: s390x: uv: Add offset comments to uv_query and extend it Janosch Frank
2021-06-30 9:06 ` Cornelia Huck
2021-06-30 9:43 ` Janosch Frank
2021-07-23 17:22 ` Claudio Imbrenda
2021-06-29 13:33 ` [kvm-unit-tests PATCH 5/5] lib: s390x: Print if a pgm happened while in SIE Janosch Frank
2021-06-30 9:12 ` Cornelia Huck
2021-07-23 17:25 ` 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=3876955c-24bd-2052-e634-8436f7558df4@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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