All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan de Konink <skinkie@xs4all.nl>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Gerd Hoffmann <kraxel@redhat.com>,
	Kevin Wolf <kwolf@suse.de>, John Levon <levon@movementarian.org>
Subject: Re: Re: [PATCH] qemu-xen: Fix PV segfault
Date: Wed, 02 Jul 2008 16:35:52 +0200	[thread overview]
Message-ID: <486B9248.9060202@xs4all.nl> (raw)
In-Reply-To: <18539.37231.372982.478747@mariner.uk.xensource.com>

Ian Jackson schreef:
> John Levon writes ("Re: [Xen-devel] Re: [PATCH] qemu-xen: Fix PV segfault"):
>> On Wed, Jul 02, 2008 at 10:38:32AM +0200, Gerd Hoffmann wrote:
>>> While I'm at it:  There is a patch queue with at
>>> http://kraxel.fedorapeople.org/patches/
>>>
>>> The plan is to submit that stuff upstream, so regular qemu will have xen
>>> support.  Right now the patch queue has only paravirt bits.  It comes
>> I'm confused, I thought that was the point of the qemu-xen tree
> 
> Gerd Hoffman's tree seems to be something entirely different.  I'm not
> sure I understand what the point of it is.  The reason why everyone is
> using qemu is that it has all of the hardware emulation device models.
> 
> Qemu proper (ie upstream) also uses the CPU emulator (translator,
> now).  KVM and Xen don't use that because they run the code on the
> physical CPU one way or another.
> 
> Gerd Hoffman's setup doesn't use the device models, nor the CPU
> emulator.  Really as far as I can tell the only thing he wants from
> qemu is the command line parser !  This is quite bizarre as it's not a
> very good command line parser (qemu upstream are considering replacing
> it with something more data-driven and more modular).

I think the primary idea is to get away from xend, and qemu gets the job 
done.


Stefan

  reply	other threads:[~2008-07-02 14:35 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 [this message]
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
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=486B9248.9060202@xs4all.nl \
    --to=skinkie@xs4all.nl \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@suse.de \
    --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.