From: "Kirill A. Shutemov" <k.shutemov@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] EABI fcntl on x86_64
Date: Mon, 19 Mar 2007 17:25:26 +0200 [thread overview]
Message-ID: <20070319152526.GA22236@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0703191126160.12505@trantor.stuart.netsweng.com>
[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]
On [Mon, 19.03.2007 11:30], Stuart Anderson wrote:
>
> When running ARM EABI binaries on x86_64, the target_eabi_flock64
> structure is already padded correct so the padding is not needed.
>
> This patch adds an #ifdef to only include the _pad member on 32-but
> hosts.
Are you sure that problem is in padding? Please, look at my patch
in post "[PATCH] fcntl64 fix".
>
>
> Stuart
>
> Stuart R. Anderson anderson@netsweng.com
> Network & Software Engineering http://www.netsweng.com/
> 1024D/37A79149: 0791 D3B8 9A4C 2CDC A31F
> BD03 0A62 E534 37A7 9149
Content-Description: fcntl fix
> Index: linux-user/syscall_defs.h
> ===================================================================
> RCS file: /sources/qemu/qemu/linux-user/syscall_defs.h,v
> retrieving revision 1.30
> diff -u -r1.30 syscall_defs.h
> --- linux-user/syscall_defs.h 22 Oct 2006 00:18:54 -0000 1.30
> +++ linux-user/syscall_defs.h 19 Mar 2007 15:25:58 -0000
> @@ -1409,7 +1409,9 @@
> struct target_eabi_flock64 {
> short l_type;
> short l_whence;
> +#if HOST_LONG_BITS == 32
> int __pad;
> +#endif
> unsigned long long l_start;
> unsigned long long l_len;
> int l_pid;
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-03-19 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-19 15:30 [Qemu-devel] [PATCH] EABI fcntl on x86_64 Stuart Anderson
2007-03-19 15:25 ` Kirill A. Shutemov [this message]
2007-03-19 15:38 ` Paul Brook
2007-03-19 15:57 ` Stuart Anderson
2007-03-19 16:16 ` Stuart Anderson
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=20070319152526.GA22236@localhost.localdomain \
--to=k.shutemov@gmail.com \
--cc=qemu-devel@nongnu.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).