From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] qemu-system: new package
Date: Fri, 17 Oct 2014 22:14:06 -0300 [thread overview]
Message-ID: <5441BEDE.1000102@zacarias.com.ar> (raw)
In-Reply-To: <54419C9C.7050705@mind.be>
On 10/17/2014 07:47 PM, Arnout Vandecappelle wrote:
>> potentially miss the opportunity for new arch and/or platform support.
>> So even if target != host version is fixed/possible you'll still clash
>> on host-qemu (user) vs. host-qemu (system) versions since you might want
>> to do the perl module dance (original purpose of host-qemu) vs. platform
>> emulation.
>
> This one I don't understand. If you need version 2.0.2 for host-qemu-system,
> then surely you also need this version for host-qemu-user? So what is the point
> of treating them as separate packages? Isn't it much easier to build qemu-user
> and qemu-system in one shot (like how it's done for the target qemu)?
The only shared code in qemu for user vs. system is just basically CPU
emulation.
For system you've got all of the hardware (audio/ hw/ net/ directories
and so on) which isn't used by user at all.
For user it deals with what we can call "ABI" (userland, linux-user/ dir
in qemu) which isn't used by system at all, and has arch bits as well.
When there are system emulations broken with the latest version of qemu
it isn't necessarily a problem with the cpu emulation, the same can
happen to user emulation without affecting system.
So if you're like 100% sure user both will work right if system does for
X version go ahead, i don't think it's a safe assumption.
Just google around a bit:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1284344
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668658
Regards.
next prev parent reply other threads:[~2014-10-18 1:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 20:20 [Buildroot] [PATCH 1/3] qemu-system: new package Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 2/3] configs/qemu: update for host-qemu-system Gustavo Zacarias
2014-05-03 20:20 ` [Buildroot] [PATCH 3/3] configs/qemu: bump relevant kernel/header versions Gustavo Zacarias
2014-10-12 15:17 ` [Buildroot] [PATCH 1/3] qemu-system: new package Thomas Petazzoni
2014-10-12 19:03 ` Gustavo Zacarias
2014-10-15 17:01 ` Arnout Vandecappelle
2014-10-16 13:53 ` Gustavo Zacarias
2014-10-17 22:47 ` Arnout Vandecappelle
2014-10-18 1:14 ` Gustavo Zacarias [this message]
2014-10-19 20:27 ` Arnout Vandecappelle
2014-10-19 20:54 ` Thomas Petazzoni
2014-10-20 1:53 ` Gustavo Zacarias
2014-10-20 19:41 ` Arnout Vandecappelle
2014-10-20 21:16 ` Thomas Petazzoni
2014-10-20 22:45 ` Gustavo Zacarias
2014-10-21 7:16 ` Thomas Petazzoni
2014-10-21 18:20 ` Yann E. MORIN
2014-10-22 10:23 ` Peter Korsgaard
2014-10-21 19:45 ` Arnout Vandecappelle
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=5441BEDE.1000102@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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