From: Hollis Blanchard <hollisb@us.ibm.com>
To: linuxppc-dev@ozlabs.org, kvm-devel@lists.sourceforge.net
Cc: kvm-ppc-devel@lists.sourceforge.net
Subject: [PATCH 0 of 3] KVM for PowerPC 440
Date: Mon, 07 Apr 2008 15:53:31 -0500 [thread overview]
Message-ID: <patchbomb.1207601611@localhost.localdomain> (raw)
Implement initial support for KVM for PowerPC 440. There are just two small
prerequisite patches, and then the bulk of the code can't be split easily.
Please review; I would like to submit these for 2.6.26. There is plenty of work
to do, both functional and optimization, but this code is sufficient to run
unmodified 440 Linux guests on a 440 Linux host. What's your favorite bike shed
color?
(Note for current users: since KVM_EXIT_DCR changed, you must rebuild your
userspace to match this kernel.)
next reply other threads:[~2008-04-07 20:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 20:53 Hollis Blanchard [this message]
2008-04-07 20:53 ` [PATCH 1 of 3] [POWERPC 44x] Export tlb_44x_hwater for KVM Hollis Blanchard
2008-04-10 14:30 ` Josh Boyer
2008-04-07 20:53 ` [PATCH 2 of 3] [KVM] Add DCR access information to struct kvm_run Hollis Blanchard
2008-04-08 1:11 ` David Gibson
2008-04-08 3:25 ` Hollis Blanchard
2008-04-08 3:54 ` David Gibson
2008-04-08 4:06 ` Hollis Blanchard
2008-04-08 4:16 ` David Gibson
2008-04-10 16:47 ` Josh Boyer
2008-04-07 20:53 ` [PATCH 3 of 3] [KVM POWERPC] PowerPC 440 KVM implementation Hollis Blanchard
2008-04-08 2:12 ` Josh Boyer
2008-04-08 4:00 ` Hollis Blanchard
2008-04-08 2:58 ` Arnd Bergmann
2008-04-08 4:19 ` Hollis Blanchard
2008-04-08 5:09 ` [kvm-ppc-devel] " Arnd Bergmann
2008-04-10 11:55 ` [PATCH 0 of 3] KVM for PowerPC 440 Josh Boyer
2008-04-10 14:26 ` Hollis Blanchard
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.1207601611@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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).