From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] Convert .flat files to 32-bit elf format
Date: Sun, 05 Dec 2010 14:37:36 +0200 [thread overview]
Message-ID: <4CFB8790.8000100@redhat.com> (raw)
In-Reply-To: <C2B85915-8842-4099-9721-4C5484760255@suse.de>
On 12/05/2010 02:05 PM, Alexander Graf wrote:
> >
> > diff --git a/config-x86-common.mak b/config-x86-common.mak
> > index b541c1c..c5508b3 100644
> > --- a/config-x86-common.mak
> > +++ b/config-x86-common.mak
> > @@ -20,9 +20,12 @@ CFLAGS += -m$(bits)
> > libgcc := $(shell $(CC) -m$(bits) --print-libgcc-file-name)
> >
> > FLATLIBS = lib/libcflat.a $(libgcc)
> > -%.flat: %.o $(FLATLIBS) flat.lds
> > +%.elf: %.o $(FLATLIBS) flat.lds
> > $(CC) $(CFLAGS) -nostdlib -o $@ -Wl,-T,flat.lds $(filter %.o, $^) $(FLATLIBS)
> >
> > +%.flat: %.elf
> > + objcopy -O elf32-i386 $^ $@
>
> Not sure it's that great to call 32bit elf binaries ".flat". I'd rather expect a flat file when reading that file extension ;). Mind to just call it ".elf32"?
It's a reminder from the good old days that these were flat files loaded
by kvmctl.
> Alternatively, you could also use real flat files and shove a multiboot header into the binary.
I'll rename them in a later patch. .elf32 isn't a good name either, it
implies 32-bit execution, whereas it's just the file format due to
multiboot constraints. Maybe .test (and .test32 and .test64 when we
build both).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-12-05 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-05 8:15 [PATCH] Convert .flat files to 32-bit elf format Avi Kivity
2010-12-05 12:05 ` Alexander Graf
2010-12-05 12:37 ` Avi Kivity [this message]
2010-12-05 12:48 ` Alexander Graf
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=4CFB8790.8000100@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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.