From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Avi Kivity <avi@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH 1/3 - qemu-kvm stable-1.0] Fix conditional build of various x86 specific bits
Date: Thu, 24 May 2012 13:03:51 +1000 [thread overview]
Message-ID: <1337828631.3038.62.camel@pasglop> (raw)
In-Reply-To: <4FBDA23C.5000608@web.de>
> > An equivalent of this is already in qemu-kvm master as commit id
> > 20ad1def644494f5055d129961d46b050c0a6158
>
> What is the interest of patching qemu-kvm for non-x86? It is not
> supposed to be used for this. And the affected bits are history in 1.1
> (or 1.2 latest). Are there distros proving QEMU based on qemu-kvm for
> non-x86 hosts?
Fedora uses qemu-kvm as their "upstream" qemu source tree for all qemu
builds, KVM and non-KVM ones, for all targets.
These fixes are necessary to make qemu in fc17 (and later) to build
ppc64-softmmu targets (with and without KVM).
Cheers,
Ben.
next prev parent reply other threads:[~2012-05-24 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 2:14 [PATCH 1/3 - qemu-kvm stable-1.0] Fix conditional build of various x86 specific bits Benjamin Herrenschmidt
2012-05-24 2:51 ` Jan Kiszka
2012-05-24 3:03 ` Benjamin Herrenschmidt [this message]
2012-06-01 23:07 ` Marcelo Tosatti
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=1337828631.3038.62.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox