qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: kvm-ppc@vger.kernel.org
Subject: [Qemu-devel] PowerPC KVM support
Date: Thu, 11 Dec 2008 14:52:26 -0600	[thread overview]
Message-ID: <1229028752-9480-1-git-send-email-hollisb@us.ibm.com> (raw)

These patches implement KVM support for the PowerPC Bamboo board, a system
built around the 440EP SoC. In the KVM model, the KVM kernel module is
responsible for all instruction execution, so it doesn't matter that TCG
doesn't emulate the 440 core.

We've only tested KVM and Bamboo with the -kernel option. I have no idea what
it would take to run a firmware like u-boot inside the VM, but it's basically
the same problem as running u-boot inside a 405 VM (which I know
Jean-Christophe is working on).

There are a couple issues I'd appreciate feedback on:

- The "bamboo" machine shows up as an option ("-M \?"), but if a user selects
  it without KVM support, they will just get an error. I don't like that, but
  register_machines() is called before --enable-kvm is recognized.

- We call cpu_ppc_init("405") to create a CPUState, because some CPUState
  fields are required outside of TCG. We could instead create a "KVM" CPU
  name, or a cpu_ppc_init_kvm() function. I'd prefer to stay on a common code
  path though, so that if new CPUState fields are introduced in the future,
  there's no KVM-specific path that breaks.

- I'd like to use ppc4xx_sdram_adjust() with the existing 405 targets as well,
  but nobody can tell me how to get a functioning 405 qemu so I can't test it.
  I may submit a separate patch series for this anyways.

-Hollis

             reply	other threads:[~2008-12-11 20:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11 20:52 Hollis Blanchard [this message]
2008-12-11 20:52 ` [Qemu-devel] [PATCH 1/6] Include headers for types used in helper_regs.h Hollis Blanchard
2008-12-11 20:52   ` [Qemu-devel] [PATCH 2/6] kvm: sync vcpu state during initialization Hollis Blanchard
2008-12-11 20:57     ` [Qemu-devel] " Hollis Blanchard
2008-12-11 21:24     ` [Qemu-devel] " Anthony Liguori
2008-12-13  0:23       ` Hollis Blanchard
2008-12-13  0:24         ` Hollis Blanchard
2008-12-13 16:37           ` Anthony Liguori
2008-12-11 20:52   ` [Qemu-devel] [PATCH 3/6] Enable KVM for ppcemb Hollis Blanchard
2008-12-11 21:19     ` Blue Swirl
2008-12-12  0:04       ` Hollis Blanchard
2008-12-11 21:30     ` Anthony Liguori
2008-12-11 22:54       ` Hollis Blanchard
2008-12-14  1:37         ` Hollis Blanchard
2008-12-14  3:29           ` Anthony Liguori
2008-12-11 20:52   ` [Qemu-devel] [PATCH 4/6] Implement device tree support needed for Bamboo emulation Hollis Blanchard
2008-12-11 21:33     ` Anthony Liguori
2008-12-11 20:52   ` [Qemu-devel] [PATCH 5/6] PowerPC 440EP SoC emulation Hollis Blanchard
2008-12-11 20:52   ` [Qemu-devel] [PATCH 6/6] IBM PowerPC 440EP Bamboo reference board emulation Hollis Blanchard
2008-12-11 21:25     ` Blue Swirl
2008-12-11 21:39     ` Anthony Liguori
2008-12-11 23:08       ` 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=1229028752-9480-1-git-send-email-hollisb@us.ibm.com \
    --to=hollisb@us.ibm.com \
    --cc=kvm-ppc@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).