From: Ian Campbell <Ian.Campbell@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: <xen-devel@lists.xenproject.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
<linux-kernel@vger.kernel.org>,
"David Vrabel" <david.vrabel@citrix.com>, <patches@linaro.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
<linux-arm-kernel@lists.infradead.org>,
"Roger Pau Monne" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH v2] xen/block: Correctly define structures in public headers on ARM32 and ARM64
Date: Thu, 12 Dec 2013 14:19:20 +0000 [thread overview]
Message-ID: <1386857960.11201.57.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <1386085237-8334-1-git-send-email-julien.grall@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2673 bytes --]
On Tue, 2013-12-03 at 15:40 +0000, Julien Grall wrote:
> On ARM (32 bits and 64 bits), the double-word is 8-bytes aligned. This will
> result on different structure from Xen and Linux repositories.
>
> As Linux is using __packed__ attribute, it must have a 4-bytes padding before
> each "id" field.
>
> This change breaks guest block support with older kernel. IMHO, it's acceptable
> because Xen on ARM is still on Tech Preview and the hypercall ABI is not yet
> freezed.
>
> Only one architecture (x86_32) doesn't have 64-bit ABI for the block interface.
> Don't add padding if Linux is compiled for this architecture.
Konrad asked for confirmation that this didn't change x86.
Using
http://stackoverflow.com/questions/9788679/how-to-get-the-relative-adress-of-a-field-in-a-structure-dump-c
I created offsets.py as described there then for i386, amd64, arm, arm64
before and after I built with CONFIG_DEBUG_INFO but not
CONFIG_DEBUG_INFO_REDUCED then:
$ cat script
python
sys.path.insert(0, '')
import offsets
end
offsets-of "struct blkif_request"
offsets-of "struct blkif_request_rw"
offsets-of "struct blkif_request_discard"
offsets-of "struct blkif_request_other"
offsets-of "struct blkif_request_indirect"
$ gdb -x script --batch drivers/block/xen-blkfront.o
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
_pad1 => 3
id => 7
sector_number => 15
seg => 23
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
_pad2 => 3
id => 7
sector_number => 15
nr_sectors => 23
_pad3 => 31
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
_pad3 => 3
id => 7
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
_pad1 => 3
id => 7
sector_number => 15
handle => 23
_pad2 => 25
indirect_grefs => 27
_pad3 => 59
}
There is no difference to either x86 arch:
$ diff -q x86_32.{before,after} && echo same
same
$ diff -q x86_64.{before,after} && echo same
same
$
And crucially:
$ diff -q arm.after arm64.after && echo same
same
$ diff -q arm.after x86_64.after && echo same
same
$
Full results attached.
Ian.
[-- Attachment #2: arm.after --]
[-- Type: text/plain, Size: 624 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
_pad1 => 3
id => 7
sector_number => 15
seg => 23
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
_pad2 => 3
id => 7
sector_number => 15
nr_sectors => 23
_pad3 => 31
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
_pad3 => 3
id => 7
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
_pad1 => 3
id => 7
sector_number => 15
handle => 23
_pad2 => 25
indirect_grefs => 27
_pad3 => 59
}
[-- Attachment #3: arm.before --]
[-- Type: text/plain, Size: 564 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
id => 3
sector_number => 11
seg => 19
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
id => 3
sector_number => 11
nr_sectors => 19
_pad3 => 27
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
id => 3
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
id => 3
sector_number => 11
handle => 19
_pad2 => 21
indirect_grefs => 23
_pad3 => 55
}
[-- Attachment #4: arm64.after --]
[-- Type: text/plain, Size: 624 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
_pad1 => 3
id => 7
sector_number => 15
seg => 23
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
_pad2 => 3
id => 7
sector_number => 15
nr_sectors => 23
_pad3 => 31
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
_pad3 => 3
id => 7
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
_pad1 => 3
id => 7
sector_number => 15
handle => 23
_pad2 => 25
indirect_grefs => 27
_pad3 => 59
}
[-- Attachment #5: arm64.before --]
[-- Type: text/plain, Size: 564 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
id => 3
sector_number => 11
seg => 19
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
id => 3
sector_number => 11
nr_sectors => 19
_pad3 => 27
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
id => 3
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
id => 3
sector_number => 11
handle => 19
_pad2 => 21
indirect_grefs => 23
_pad3 => 55
}
[-- Attachment #6: x86_32.after --]
[-- Type: text/plain, Size: 564 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
id => 3
sector_number => 11
seg => 19
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
id => 3
sector_number => 11
nr_sectors => 19
_pad3 => 27
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
id => 3
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
id => 3
sector_number => 11
handle => 19
_pad2 => 21
indirect_grefs => 23
_pad3 => 55
}
[-- Attachment #7: x86_32.before --]
[-- Type: text/plain, Size: 564 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
id => 3
sector_number => 11
seg => 19
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
id => 3
sector_number => 11
nr_sectors => 19
_pad3 => 27
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
id => 3
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
id => 3
sector_number => 11
handle => 19
_pad2 => 21
indirect_grefs => 23
_pad3 => 55
}
[-- Attachment #8: x86_64.after --]
[-- Type: text/plain, Size: 624 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
_pad1 => 3
id => 7
sector_number => 15
seg => 23
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
_pad2 => 3
id => 7
sector_number => 15
nr_sectors => 23
_pad3 => 31
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
_pad3 => 3
id => 7
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
_pad1 => 3
id => 7
sector_number => 15
handle => 23
_pad2 => 25
indirect_grefs => 27
_pad3 => 59
}
[-- Attachment #9: x86_64.before --]
[-- Type: text/plain, Size: 624 bytes --]
struct blkif_request {
operation => 0
u => 1
}
struct blkif_request_rw {
nr_segments => 0
handle => 1
_pad1 => 3
id => 7
sector_number => 15
seg => 23
}
struct blkif_request_discard {
flag => 0
_pad1 => 1
_pad2 => 3
id => 7
sector_number => 15
nr_sectors => 23
_pad3 => 31
}
struct blkif_request_other {
_pad1 => 0
_pad2 => 1
_pad3 => 3
id => 7
}
struct blkif_request_indirect {
indirect_op => 0
nr_segments => 1
_pad1 => 3
id => 7
sector_number => 15
handle => 23
_pad2 => 25
indirect_grefs => 27
_pad3 => 59
}
next prev parent reply other threads:[~2013-12-12 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 15:40 Julien Grall
2013-12-03 16:00 ` One Thousand Gnomes
2013-12-03 16:19 ` Julien Grall
2013-12-03 16:32 ` One Thousand Gnomes
2013-12-03 16:41 ` Ian Campbell
2013-12-03 17:03 ` One Thousand Gnomes
2013-12-03 18:03 ` Konrad Rzeszutek Wilk
2013-12-03 17:10 ` David Vrabel
2013-12-03 18:01 ` Konrad Rzeszutek Wilk
2013-12-12 14:19 ` Ian Campbell [this message]
2013-12-12 15:11 ` [Xen-devel] " Roger Pau Monné
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=1386857960.11201.57.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=julien.grall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=roger.pau@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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
all inboxes | Powered by JetHome®