All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	John Levon <levon@movementarian.org>
Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault
Date: Thu, 03 Jul 2008 13:05:06 +0200	[thread overview]
Message-ID: <486CB262.8070208@suse.de> (raw)
In-Reply-To: <486CB023.3080605@redhat.com>

Gerd Hoffmann schrieb:
> Kevin Wolf wrote:
>> Actually, I think Xen PV is a different architecture, not just a
>> different PC machine.
> 
> That isn't visible to qemu though as cpu virtualization is handled by
> the xen hypervisor.
> 
>> So to be consistent with qemu it would be a
>> separate binary like qemu-system-xenpv.
> 
> I wouldn't do it that way for the reason outlined above, but it is an
> option, yes.

It's not only the CPU virtualization I'm talking about. PV machines also
have "hardware" devices completely different from PCs. Just look at
pc_init1(), that's all stuff PV machines won't need.

Concerning the CPU, I think of it as an architecture which is only
usable through an accelerator. Certainly it would be possible to do a
normal qemu emulation for this architecture, it just wouldn't make too
much sense.

>> HVM on the other hand would be more of an accelerator for the existing
>> x86 system emulation, just like kqemu or KVM.
> 
> Yep, sort of.  And some plumbing for xenbus for guests with pv-on-hvm
> drivers installed.
> 
> Glauber Costa is working on a nice abstraction layer for qemu
> accelerators btw.  Intention is to get kvm upstream merged.  It should
> also make it easier to get xen hvm support merged upstream.

Yes, I'm aware of his patches. That's actually why I used the term
"accelerator".

Kevin

  reply	other threads:[~2008-07-03 11:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 18:37 [PATCH] qemu-xen: Fix PV segfault Kevin Wolf
2008-07-01 11:42 ` Kevin Wolf
2008-07-01 17:31 ` Ian Jackson
2008-07-02  7:54   ` Kevin Wolf
2008-07-02  8:38     ` Gerd Hoffmann
2008-07-02 14:19       ` John Levon
2008-07-02 14:32         ` Ian Jackson
2008-07-02 14:35           ` Stefan de Konink
2008-07-02 14:38           ` John Levon
2008-07-02 14:50             ` Ian Jackson
2008-07-02 14:55               ` Kevin Wolf
2008-07-02 14:59               ` Stefan de Konink
2008-07-02 15:14                 ` Ian Jackson
2008-07-02 15:28                   ` Stefan de Konink
2008-07-02 15:39                     ` Daniel P. Berrange
2008-07-02 16:00                   ` John Levon
2008-07-02 17:14                     ` Ian Jackson
2008-07-02 15:00               ` Daniel P. Berrange
2008-07-02 15:05               ` Daniel P. Berrange
2008-07-02 15:08               ` John Levon
2008-07-02 14:46           ` Kevin Wolf
2008-07-02 14:52           ` Daniel P. Berrange
2008-07-02 15:59           ` Gerd Hoffmann
2008-07-03  8:01         ` Gerd Hoffmann
2008-07-03  8:16           ` Kevin Wolf
2008-07-03 10:55             ` Gerd Hoffmann
2008-07-03 11:05               ` Kevin Wolf [this message]
2008-07-03 11:17                 ` Kevin Wolf
2008-07-03 11:18                 ` Gerd Hoffmann
2008-07-03  9:32           ` Ian Jackson
2008-07-03 11:13             ` Gerd Hoffmann
2008-07-02 10:21     ` Ian Jackson
2008-07-02 11:30       ` Kevin Wolf

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=486CB262.8070208@suse.de \
    --to=kwolf@suse.de \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=kraxel@redhat.com \
    --cc=levon@movementarian.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.