From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Fix core dumps of guests > 2 GB in size on i386
Date: Fri, 17 Nov 2006 12:12:43 +0000 [thread overview]
Message-ID: <20061117121243.GA11444@redhat.com> (raw)
In-Reply-To: <C18336CF.4B30%Keir.Fraser@cl.cam.ac.uk>
On Fri, Nov 17, 2006 at 09:52:15AM +0000, Keir Fraser wrote:
> On 15/11/06 22:02, "Daniel P. Berrange" <berrange@redhat.com> wrote:
>
> > The attached patch adds the O_LARGEFILE flag when opening the file. It
> > is also neccessary to add additional CFLAGS & LDFLAGS to enable use of
> > the POSIX Largefile standard. There are two ways to enable LFS support,
> > in implicit mode all types, functions & macros are automatically changed
> > to the 64 bit variants at compile time - this however changes the ABI
> > contract - eg size_t is now 64-bits instead of 32.
>
> I like the implicit method. I think it's unlikely to bite us. A lot of tools
> subdirs are defining _FILE_OFFSET_BITS=64 anyway (and not using getconf!).
> I'll provide a portable common CFLAGS/LDFLAGS addition in tools/Rules.mk.
Well there are two methods in libxc which expose a size_t argument so the
implicit method will break ABI changing these from 32 to 64 bits.
xenctrl.h:int xc_tbuf_enable(int xc_handle, size_t cnt, unsigned long *mfn,
xenctrl.h:int xc_acm_op(int xc_handle, int cmd, void *arg, size_t arg_size);
They are probably only called from other apps / libraries in the tools/
dir, so perhaps we don't care about ABI breakage in these two functions.
Must make sure the python binding is still working correctly though because
a 64-bit size_t on 32-bit arch will no longer fit in Python's native Int
type - will have to switch to Long
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2006-11-17 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 22:02 Fix core dumps of guests > 2 GB in size on i386 Daniel P. Berrange
2006-11-17 9:52 ` Keir Fraser
2006-11-17 12:12 ` Daniel P. Berrange [this message]
2006-11-17 13:47 ` Keir Fraser
2006-11-17 18:47 ` Daniel P. Berrange
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=20061117121243.GA11444@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.