All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Burns <lists.xensource.com@adslpipe.co.uk>
To: xen-devel@lists.xensource.com
Subject: Re: State of Xen in upstream Linux
Date: Thu, 31 Jul 2008 08:27:26 +0100	[thread overview]
Message-ID: <4891695E.4040607@adslpipe.co.uk> (raw)
In-Reply-To: <48910C99.10606@goop.org>

On 31/07/2008 01:51, Jeremy Fitzhardinge wrote:

> what's new with Xen.  

Thanks for the write-up (and the work itself!)

>     What's missing?  What do you depend on?  

I realise pv_ops dom0 should come first to save users' pain in that 
dept, currently I use pciback/front on 2.6.18 kernels, any idea when 
this might re-appear either in domU or dom0 pv_ops kernels?

  reply	other threads:[~2008-07-31  7:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-31  0:51 State of Xen in upstream Linux Jeremy Fitzhardinge
2008-07-31  7:27 ` Andy Burns [this message]
2008-07-31  9:08 ` [Xen-devel] " Daniel P. Berrange
2008-07-31 17:54   ` Grant McWilliams
2008-07-31 18:08     ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:19       ` [Xen-users] Re: [Xen-devel] " Alexey Eremenko
2008-07-31 18:28         ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:48           ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 18:58             ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 20:07               ` Re: [Xen-devel] " Grant McWilliams
2008-07-31 20:14                 ` [Xen-users] " Jeremy Fitzhardinge
2008-07-31 18:36       ` [Xen-users] Re: [Xen-devel] " Dr. David Alan Gilbert
2008-07-31 18:45         ` [Xen-users] " Jeremy Fitzhardinge
2008-08-01  8:34     ` Re: [Xen-devel] " Daniel P. Berrange
2008-08-12 11:14 ` Pasi Kärkkäinen
2008-08-12 16:24   ` Jeremy Fitzhardinge
2008-08-26  8:30     ` State of Xen in upstream Linux / pv_ops dom0 Pasi Kärkkäinen
2008-08-26 15:20       ` Jeremy Fitzhardinge

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=4891695E.4040607@adslpipe.co.uk \
    --to=lists.xensource.com@adslpipe.co.uk \
    --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.