From: ehrhardt@linux.vnet.ibm.com
To: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, avi@qumranet.com,
qemu-devel@nongnu.org
Cc: ehrhardt@linux.vnet.ibm.com, hollisb@us.ibm.com
Subject: [Qemu-devel] [PATCH 0/3] kvm-userspace: kvmppc: fix build for ppc v2
Date: Tue, 30 Sep 2008 08:36:44 +0200 [thread overview]
Message-ID: <1222756604-10899-1-git-send-email-ehrhardt@linux.vnet.ibm.com> (raw)
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
*update
Short after resending v1 I realized that I forgot to put Avi and
qemu-devel@nongnu.org (for 2/3) on cc. I also updated the header text in 1/3 a
bit and verified my hostlongbits proposal on recent cross toolchain versions
because there was a question about that.
Updating and testing kvm-userspace for ppc after a too long time brought up
some issues fixed in this series.
The patches are small and their description should be comprehendible. Due to
the fact that most of the issues where build time issues I also started to
discuss about/establish some kind of automated build test for us that should
allow us to find such things faster.
Let me know if qumranet has such a process for x86 already and I should help
you to include powerpc.
[patches in series]
[PATCH 1/3] kvm-userspace: kvmppc: fix file header in libkvm-powerpc.c
[PATCH 2/3] kvm-userspace: kvmppc: fix hostlonbits detection when cross compiling
[PATCH 3/3] kvm-userspace: kvmppc: fix building userspace for powerpc
---
[diffstat]
Makefile | 3 ++-
kernel/powerpc/Makefile.pre | 1 +
kernel/powerpc/hack-module.awk | 5 +++++
libkvm/libkvm-powerpc.c | 14 +++++---------
qemu/Makefile.target | 2 +-
qemu/configure | 13 +++++++------
6 files changed, 21 insertions(+), 17 deletions(-)
next reply other threads:[~2008-09-30 6:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 6:36 ehrhardt [this message]
2008-09-30 14:19 ` [Qemu-devel] Re: [PATCH 0/3] kvm-userspace: kvmppc: fix build for ppc v2 Hollis Blanchard
2008-10-02 12:57 ` Avi Kivity
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=1222756604-10899-1-git-send-email-ehrhardt@linux.vnet.ibm.com \
--to=ehrhardt@linux.vnet.ibm.com \
--cc=avi@qumranet.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--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 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).