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

Ian Jackson wrote:
> Gerd Hoffmann writes ("Re: [Xen-devel] Re: [PATCH] qemu-xen: Fix PV segfault"):
>> Looked at the qemu-xen tree and the branches therein today (missed the
>> original announcement as I was on vacation at that point in time).
>> Ian's plan seems to be to upstream mostly bugfixes (qemu branch), not
>> any xen-specific code.
> 
> I would like the xen code to go upstream as well eventually.  However
> upstream have said that they're not happy with some of the things
> which are essential in our tree.  For example, they are opposed to the
> mapcache, which is essential for decoupling guest addresses from
> qemu's address space (particularly since the guest maybe 64-bit and
> qemu only 32-bit!)

That doesn't mean we can't upstream any xen bits.  The whole pv domain
support doesn't need mapcache in the first place for example.

Didn't check how intrusive mapcache is, but would it be an option to
make it optional?  So upstream has most other bits, you have a much
smaller patch queue.

Also I'd expect that if you run guests that big that the 32bit address
space limits become problematic, wouldn't you run 64bit xen+dom0 anyway
for performance reasons?

cheers,
  Gerd

-- 
http://kraxel.fedorapeople.org/xenner/

  reply	other threads:[~2008-07-03 11:13 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
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 [this message]
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=486CB467.9030404@redhat.com \
    --to=kraxel@redhat.com \
    --cc=Ian.Jackson@eu.citrix.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.