From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] qemu-system: new package
Date: Sun, 19 Oct 2014 22:54:51 +0200 [thread overview]
Message-ID: <20141019225451.3aa6176e@free-electrons.com> (raw)
In-Reply-To: <54441E9F.8080802@mind.be>
Dear Arnout Vandecappelle,
On Sun, 19 Oct 2014 22:27:11 +0200, Arnout Vandecappelle wrote:
> > 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
>
> So what I hear you say is that there really is a case for specifying the
> qemu-user and qemu-system version separately, and that that's what this whole
> discussion really is about. And I guess you may want to build at the same time a
> host-qemu-user of one version and a host-qemu-system of another version, correct?
>
> Still, the .mk file of qemu-user and qemu-system are 90% the same. It would be
> nice to be able to factor that out somehow. However, it makes complete sense to
> have them as separate packages first and merge them later.
>
> So the question is: is the need for separate host-qemu-system and
> host-qemu-user versions more important than the additional complexity of
> specifying a nearly-identical .mk file twice?
Despite Gustavo's explanation, I'm not sure to see what is the need to
have a different version for host-qemu-system and host-qemu-user.
If a given version of host-qemu-system works for a given
architecture/platform, then surely, host-qemu-user should work for the
same architecture. The opposite is obviously not true, but it doesn't
matter much: we can keep whatever version gets host-qemu-system working.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-19 20:54 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
2014-10-19 20:27 ` Arnout Vandecappelle
2014-10-19 20:54 ` Thomas Petazzoni [this message]
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=20141019225451.3aa6176e@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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