From: David Hildenbrand <david@redhat.com>
To: Pierre Morel <pmorel@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org, borntraeger@de.ibm.com,
frankja@linux.ibm.com, cohuck@redhat.com, thuth@redhat.com,
hca@linux.ibm.com, gor@linux.ibm.com, wintera@linux.ibm.com,
seiden@linux.ibm.com, nrb@linux.ibm.com
Subject: Re: [PATCH v9 3/3] s390x: KVM: resetting the Topology-Change-Report
Date: Wed, 18 May 2022 16:33:48 +0200 [thread overview]
Message-ID: <cfe448f7-0b4e-680d-46a7-33ad25a4c09b@redhat.com> (raw)
In-Reply-To: <bae4e416-b0e9-31c6-c9d0-df6b5a5fd46f@linux.ibm.com>
On 16.05.22 16:21, Pierre Morel wrote:
>
>
> On 5/12/22 12:01, David Hildenbrand wrote:
>>>>
>>>> I think we prefer something like u16 when copying to user space.
>>>
>>> but then userspace also has to expect a u16, right?
>>
>> Yep.
>>
>
> Yes but in fact, inspired by previous discussion I had on the VFIO
> interface, that is the reason why I did prefer an int.
> It is much simpler than a u16 and the definition of a bit.
>
> Despite a bit in a u16 is what the s3990 achitecture proposes I thought
> we could make it easier on the KVM/QEMU interface.
>
> But if the discussion stops here, I will do as you both propose change
> to u16 in KVM and userland and add the documentation for the interface.
In general, we pass via the ABI fixed-sized values -- u8, u16, u32, u64
... instead of int. Simply because sizeof(int) is in theory variable
(e.g., 32bit vs 64bit).
Take a look at arch/s390/include/uapi/asm/kvm.h and you won't find any
usage of int or bool.
Having that said, I'll let the maintainers decide. Using e.g., u8 is
just the natural thing to do on a Linux ABI, but we don't really support
32 bit ... maybe we'll support 128bit at one point? ;)
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-05-18 14:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 9:24 [PATCH v9 0/3] s390x: KVM: CPU Topology Pierre Morel
2022-05-06 9:24 ` [PATCH v9 1/3] s390x: KVM: ipte lock for SCA access should be contained in KVM Pierre Morel
2022-05-12 9:08 ` David Hildenbrand
2022-05-16 16:30 ` Pierre Morel
2022-05-12 11:32 ` Janosch Frank
2022-05-16 14:13 ` Pierre Morel
2022-05-06 9:24 ` [PATCH v9 2/3] s390x: KVM: guest support for topology function Pierre Morel
2022-05-12 9:24 ` David Hildenbrand
2022-05-16 14:13 ` Pierre Morel
2022-06-17 14:49 ` Pierre Morel
2022-05-12 11:41 ` Janosch Frank
2022-05-16 10:41 ` Pierre Morel
2022-05-19 9:01 ` Christian Borntraeger
2022-05-19 9:23 ` Pierre Morel
2022-05-19 9:36 ` Christian Borntraeger
2022-05-06 9:24 ` [PATCH v9 3/3] s390x: KVM: resetting the Topology-Change-Report Pierre Morel
2022-05-12 9:31 ` David Hildenbrand
2022-05-12 9:52 ` Claudio Imbrenda
2022-05-12 10:01 ` David Hildenbrand
2022-05-16 14:21 ` Pierre Morel
2022-05-18 14:33 ` David Hildenbrand [this message]
2022-05-18 16:55 ` Pierre Morel
2022-05-16 10:36 ` Pierre Morel
2022-05-18 10:51 ` Pierre Morel
2022-05-18 15:26 ` [PATCH v9 0/3] s390x: KVM: CPU Topology Christian Borntraeger
2022-05-18 16:41 ` Pierre Morel
2022-05-19 5:46 ` Heiko Carstens
2022-05-19 8:07 ` Christian Borntraeger
2022-05-19 9:02 ` Pierre Morel
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=cfe448f7-0b4e-680d-46a7-33ad25a4c09b@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=seiden@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=wintera@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