From: Hollis Blanchard <hollisb@us.ibm.com>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: [kvm-ppc-devel] [PATCH 0 of 3] Portability: allow for non-x86
Date: Mon, 03 Dec 2007 21:30:22 +0000 [thread overview]
Message-ID: <patchbomb.1196717422@basalt> (raw)
These patches allow us to stop unconditionally including x86 headers, which
allows us to provide alternative definitions. The first two just split things
out to avoid circular header dependencies.
In fact, with just a couple additional hacks, I was finally able to get a stub
PowerPC implementation building.
7 files changed, 127 insertions(+), 70 deletions(-)
drivers/kvm/i8259.c | 1
drivers/kvm/iodev.h | 63 ++++++++++++++++++++++++++++++++++++++++++
drivers/kvm/irq.h | 8 ++++-
drivers/kvm/kvm.h | 72 ++++--------------------------------------------
drivers/kvm/kvm_main.c | 4 --
drivers/kvm/types.h | 41 +++++++++++++++++++++++++++
drivers/kvm/x86.h | 8 +++++
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
next reply other threads:[~2007-12-03 21:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 21:30 Hollis Blanchard [this message]
2007-12-03 21:30 ` [kvm-ppc-devel] [PATCH 1 of 3] Move address types to their own Hollis Blanchard
2007-12-04 13:35 ` [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 3] Move address types Carsten Otte
2007-12-03 21:30 ` [kvm-ppc-devel] [PATCH 2 of 3] Move IO device definitions to its Hollis Blanchard
2007-12-04 13:41 ` [kvm-ppc-devel] [kvm-devel] [PATCH 2 of 3] Move IO device Carsten Otte
[not found] ` <4755590F.60301-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-12-04 14:58 ` [kvm-ppc-devel] [kvm-devel] [PATCH 2 of 3] Move IO Hollis Blanchard
2007-12-03 21:30 ` [kvm-ppc-devel] [PATCH 3 of 3] Stop including x86-specific headers Hollis Blanchard
2007-12-04 13:37 ` [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] Stop including Carsten Otte
2007-12-05 10:14 ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] Portability: allow 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=patchbomb.1196717422@basalt \
--to=hollisb@us.ibm.com \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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