From: mirak <mirak.spam@wanadoo.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: qemu ELF Loader Kernel integration
Date: Thu, 31 Mar 2005 17:09:07 +0200 [thread overview]
Message-ID: <d2h3nr$ae7$4@sea.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0503311145550.22079@ext-ssh.movial.fi>
Valtteri Rahkonen wrote:
> On Thu, 31 Mar 2005, PhilippGühring wrote:
>
>> Hi,
>>
>> Is it possible to integrate qemu(-ppc) into the Linux kernel, so that
>> when a
>> program tries to start a Linux-ELF-ppc executable, that qemu is being
>> used to
>> start it normally?
>
>
> Yes, see binfmt_misc (kernel support for misc binaries).
>
>> It would be useful for embedded systems development for
>> cross-compilation:
>> The resulting binaries could be tried natively on the development system.
>> If I would do it manually, I could start
>> qemu-ppc binary
>> But in some enviroments, the binary is started automatically by a
>> third-party
>> product, therefore being able to launch the binary directly would be
>> helpful.
>
>
> If you have a binfmt_misc compiled to your kernel and you have
> registered qemu as a ppc interpreter then qemu will be started
> automatically when executing the ppc binaries. You will need to register
> qemu as your interprer in proc interface
> (/proc/sys/fs/binfmt_misc/register).
Would this work for for exemple the flash player plugin or is it only
for executables ?
I am interested in doing that the other way around, for i386 code on
linux ppc.
next prev parent reply other threads:[~2005-03-31 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 8:48 [Qemu-devel] qemu ELF Loader Kernel integration Philipp Gühring
2005-03-31 8:41 ` Panagiotis Issaris
2005-03-31 8:57 ` Valtteri Rahkonen
2005-03-31 15:09 ` mirak [this message]
2005-04-01 1:32 ` [Qemu-devel] " Mark Williamson
2005-04-05 14:19 ` David Woodhouse
2005-03-31 8:59 ` [Qemu-devel] " Lennert Buytenhek
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='d2h3nr$ae7$4@sea.gmane.org' \
--to=mirak.spam@wanadoo.fr \
--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 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.