From: Julien Grall <julien@xen.org>
To: Jan Beulich <jbeulich@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wl@xen.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <jgrall@amazon.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
George Dunlap <george.dunlap@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] pvcalls: Document explicitly the padding for all arches
Date: Wed, 29 Apr 2020 15:01:12 +0100 [thread overview]
Message-ID: <9eb39857-2e33-4a6b-1825-f9dc537a6515@xen.org> (raw)
In-Reply-To: <240bc5e8-f8fd-217a-fa10-7628ac9d4e6e@suse.com>
Hi,
On 22/04/2020 10:20, Jan Beulich wrote:
>> Even if it was possible to use the sub-structs defined in the header
>> that way, keep in mind that we also wrote:
>>
>> /* dummy member to force sizeof(struct xen_pvcalls_request)
>> * to match across archs */
>> struct xen_pvcalls_dummy {
>> uint8_t dummy[56];
>> } dummy;
>
> This has nothing to do with how a consumer may use the structs.
>
>> And the spec also clarifies that the size of each specific request is
>> always 56 bytes.
>
> Sure, and I didn't mean to imply that a consumer would be allowed
> to break this requirement. Still something like this
>
> int pvcall_new_socket(struct xen_pvcalls_socket *s) {
> struct xen_pvcalls_request req = {
> .req_id = REQ_ID,
> .cmd = PVCALLS_SOCKET,
> .u.socket = *s,
> };
>
> return pvcall(&req);
> }
>
> may break.
I think I understand your concern now. So yes I agree this would break
32-bit consumer.
As the padding is at the end of the structure, I think a 32-bit frontend
and 64-bit backend (or vice-versa) should currently work without any
trouble. The problem would come later if we decide to extend a command.
I will document the padding only for non 32-bit x86 guest and rework the
documentation.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2020-04-29 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 10:49 [PATCH] pvcalls: Document explicitly the padding for all arches Julien Grall
2020-04-20 8:04 ` Jan Beulich
2020-04-20 13:34 ` Julien Grall
2020-04-20 13:45 ` Jan Beulich
2020-04-21 23:27 ` Stefano Stabellini
2020-04-22 9:20 ` Jan Beulich
2020-04-29 14:01 ` Julien Grall [this message]
2020-04-29 14:05 ` Jan Beulich
2020-04-29 14:14 ` Julien Grall
2020-04-29 14:56 ` Jan Beulich
2020-04-29 15:06 ` Julien Grall
2020-04-29 15:23 ` Jan Beulich
2020-04-29 15:30 ` Julien Grall
2020-04-29 15:57 ` Jan Beulich
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=9eb39857-2e33-4a6b-1825-f9dc537a6515@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jgrall@amazon.com \
--cc=jgross@suse.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
/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).