public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ijc@hellion.org.uk>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@suse.de>, Rusty Russell <rusty@rustcorp.com.au>,
	virtualization@lists.linux-foundation.org,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Anthony Liguori <aliguori@us.ibm.com>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 3/3] Time to make CONFIG_PARAVIRT non-experimental.
Date: Wed, 19 Sep 2007 11:43:00 +0100	[thread overview]
Message-ID: <1190198580.13585.34.camel@localhost.localdomain> (raw)
In-Reply-To: <46F09EA1.7060606@goop.org>

On Tue, 2007-09-18 at 20:59 -0700, Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> > At least the Xen port seems to have specific requirements
> > and essentially only work on xen-unstable (?) [or at least
> > some very new Xen version] which probably very few
> > people use.
> >   
> 
> Only on 64-bit hosts, because of bugs in the 64-bit compat layer. 
> 32-on-32 and 64-on-64 (when its done) should work fine.

All the required fixes for 32on64 are queued for Xen 3.1.1 too. The
proposed updates are at
http://xenbits.xensource.com/xen-3.1-testing.pq.hg

Ian.

-- 
Ian Campbell
Current Noise: Detonation - Sword-Carved Skin

The executioner is, I hear, very expert, and my neck is very slender.
		-- Anne Boleyn


  reply	other threads:[~2007-09-19 10:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-14  5:17 [PATCH 1/3] Normalize config options for guest support Rusty Russell
2007-09-14  5:18 ` [PATCH 2/3] Consolidate host virtualization support under Virtualization menu Rusty Russell
2007-09-14  5:21   ` [PATCH 3/3] Time to make CONFIG_PARAVIRT non-experimental Rusty Russell
2007-09-18 10:57     ` Andi Kleen
2007-09-18 20:04       ` Charles N Wyble
2007-09-18 20:20         ` Andi Kleen
2007-09-18 20:27           ` Charles N Wyble
2007-09-18 20:41             ` Andi Kleen
2007-09-20 15:45             ` Satyam Sharma
2007-09-20 16:09               ` Charles N Wyble
2007-09-20 16:47                 ` Satyam Sharma
2007-09-18 21:34       ` Rusty Russell
2007-09-18 21:52         ` Andi Kleen
2007-09-19  1:53           ` Rusty Russell
2007-09-19  3:59           ` Jeremy Fitzhardinge
2007-09-19 10:43             ` Ian Campbell [this message]
2007-09-14 16:19   ` [PATCH 2/3] Consolidate host virtualization support under Virtualization menu Randy Dunlap
2007-09-14 20:01     ` Jan Engelhardt
2007-09-15  3:05     ` Rusty Russell
2007-09-15  8:49       ` Alexey Eremenko
2007-09-16  7:43         ` Rusty Russell
2007-09-16 14:56           ` Jeremy Fitzhardinge
2007-09-17 19:31             ` Zachary Amsden
2007-09-17 23:30               ` Charles N Wyble
2007-09-18  0:18                 ` Jeremy Fitzhardinge
2007-09-18 20:11                   ` Charles N Wyble
2007-09-19  9:38                     ` Alexey Eremenko

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=1190198580.13585.34.camel@localhost.localdomain \
    --to=ijc@hellion.org.uk \
    --cc=ak@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=chrisw@sous-sol.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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