From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
Subject: Re: [kvm-ppc-devel] [PATCH 0 of 7] PowerPC Embedded KVM qemu enablement patches
Date: Mon, 28 Jan 2008 10:48:36 -0600 [thread overview]
Message-ID: <1201538916.8969.6.camel@basalt> (raw)
In-Reply-To: <479E0029.3090906-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
On Mon, 2008-01-28 at 10:17 -0600, Anthony Liguori wrote:
> Jerone Young wrote:
> > The issue here is that qemu does not support u-boot firmware. What we
> > are doing is actually loading a u-boot image and booting Linux directly
> > with a pre made device tree (which is something normally u-boot firmware
> > would provide Linux). So this code wouldn't fit into plain qemu just
> > yet.
> >
>
> In theory, it would still work with QEMU though right? It just requires
> a custom guest kernel.
Qemu does not emulate the 440 core, but that's what our KVM code
supports. Bamboo is a 440EP reference board, so the Bamboo setup will be
useless to qemu until they get 440 support.
That said, there are only 2 places that we make KVM-specific calls in
this code, and those can easily be protected with "kvm_allowed" checks
in the future.
--
Hollis Blanchard
IBM Linux Technology Center
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-01-28 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 3:16 [PATCH 0 of 7] PowerPC Embedded KVM qemu enablement patches Jerone Young
2008-01-28 3:16 ` [PATCH 1 of 7] Enhnace kvm-userspace configure script for powerpc Jerone Young
2008-01-28 3:16 ` [PATCH 2 of 7] Ensure 4kB page alignment for embedded powerpc when using kvm Jerone Young
2008-01-28 3:16 ` [PATCH 3 of 7] Chnage so that Powerpc & IA64 do not have KVM_EXTRA_PAGES set Jerone Young
2008-01-28 3:16 ` [PATCH 4 of 7] Add vcpu to arguments of powerpc libkvm callbacks Jerone Young
2008-01-28 3:16 ` [PATCH 5 of 7] Add qemu powerpc build support Jerone Young
2008-01-28 3:16 ` [PATCH 6 of 7] Add powerpc KVM support to qemu Jerone Young
2008-01-28 3:16 ` [PATCH 7 of 7] Add Powerpc 440 board model "bamboo" to take advantage of Powerpc KVM Jerone Young
2008-01-28 3:46 ` [PATCH 0 of 7] PowerPC Embedded KVM qemu enablement patches Anthony Liguori
[not found] ` <479D5032.6050807-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-28 16:01 ` Jerone Young
2008-01-28 16:17 ` Anthony Liguori
[not found] ` <479E0029.3090906-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-01-28 16:20 ` Jerone Young
2008-01-28 16:48 ` Hollis Blanchard [this message]
2008-01-28 11:03 ` 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=1201538916.8969.6.camel@basalt \
--to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
--cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@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