public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: dor.laor-atKUWr5tajBWk0Htik3J/w@public.gmane.org
Cc: kvm-ppc-devel
	<kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
	kvm-devel
	<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [kvm-ppc-devel]  [RFC PATCH] current PowerPC patch
Date: Fri, 19 Oct 2007 17:23:10 -0500	[thread overview]
Message-ID: <1192832590.10451.46.camel@basalt> (raw)
In-Reply-To: <47192C6D.8020602-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

On Sat, 2007-10-20 at 00:15 +0200, Dor Laor wrote:
> Hollis Blanchard wrote:
> > This patch can now execute guest userspace (I'm not saying it's
> complete
> > or stable or anything though). I need to put together a more
> > full-featured ramdisk to test userspace more completely.
> >
> > That reminds me, what is the status of KVM VirtIO work? If I can put
> a
> > virt-io driver in the guest and not need to deal with storage device
> > emulation that would make me very happy.
> >
> >   
> Hi Hollis,
> Good luck for the new patch and the ongoing kvm arch support.
> Sadly KVM's virtio support didn't change much after the forum. Rusty
> did improve virtio shared mem and added  pci like configuration space
> as discussed in the forum.
> I was too busy with other things. The good thing is that in a week
> I'll be back on it.

OK.

> Nevertheless, even with pv block driver you'll need to boot with a 
> virtual device and then move to a pv one.
> It will remain this way until we'll add boot from pv support. It will 
> happen but further on. 

I guess you're talking about an x86 BIOS restriction? I don't expect
that to be a problem for us, since I'm not currently planning to execute
firmware inside the guest VM. That would require a lot of unnecessary
emulation to handle probing and very early configuration (e.g. SDRAM).

We can just inform the guest of the (virtual) system topology via the
device tree data structure, which is how firmware usually presents that
information on PowerPC systems.

-- 
Hollis Blanchard
IBM Linux Technology Center


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  parent reply	other threads:[~2007-10-19 22:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 18:15 [RFC PATCH] current PowerPC patch Hollis Blanchard
2007-10-19 22:15 ` Dor Laor
     [not found]   ` <47192C6D.8020602-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-19 22:23     ` Hollis Blanchard [this message]
2007-10-22 11:01 ` Carsten Otte

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=1192832590.10451.46.camel@basalt \
    --to=hollisb-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
    --cc=dor.laor-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