From: "Blue Swirl" <blauwirbel@gmail.com>
To: Thiemo Seufer <ths@networkno.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/linux-user elfload.c
Date: Fri, 6 Jul 2007 00:46:12 +0300 [thread overview]
Message-ID: <f43fc5580707051446t28c503f9o55440d9e059b2008@mail.gmail.com> (raw)
In-Reply-To: <20070704204850.GC1209@networkno.de>
On 7/4/07, Thiemo Seufer <ths@networkno.de> wrote:
> Blue Swirl wrote:
> > Modified files:
> > linux-user : elfload.c
> I think this will break loading of 32bit kernels in a 64bit capable
> Qemu (like MIPS64). Could you make the test of ELFCLASS a runtime
> check?
The ELF loader is different for system emulator (loader.c and
elf_ops.h vs. elfload.c) (why?), this patch was for linux-user. It's
not possible to load 32 bit files with a 64 bit user emulator
currently. For Sparc that might be useful as there is a hybrid ELF
format used by Solaris, where the file is 32 bits but the CPU is 64
bits.
The same 64 to 32 bit symbol conversion happens on system emulator
side already. ELF class selects the correct version of elf_ops
(loader.c:232), therefore either word size is OK.
next prev parent reply other threads:[~2007-07-05 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-05 13:23 [Qemu-devel] qemu/linux-user elfload.c Blue Swirl
2007-07-04 20:48 ` Thiemo Seufer
2007-07-05 21:46 ` Blue Swirl [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-26 23:31 Paul Brook
2007-10-07 15:59 Jocelyn Mayer
2007-06-22 10:13 Thiemo Seufer
2006-12-14 13:32 Thiemo Seufer
2006-02-04 19:30 Paul Brook
2005-10-30 20:58 Fabrice Bellard
2005-08-21 10:12 Fabrice Bellard
2005-02-10 22:00 Fabrice Bellard
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=f43fc5580707051446t28c503f9o55440d9e059b2008@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=ths@networkno.de \
/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).