From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, Fantu <fantonifabio@tiscali.it>
Subject: Re: xen.git branches
Date: Thu, 04 Mar 2010 10:48:09 -0800 [thread overview]
Message-ID: <4B900069.2030204@goop.org> (raw)
In-Reply-To: <20100304182010.GA20263@phenom.dumpdata.com>
On 03/04/2010 10:20 AM, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 04, 2010 at 10:25:26AM -0800, Jeremy Fitzhardinge wrote:
>
>> On 03/03/2010 11:18 PM, Fantu wrote:
>>
>>> Now i start to use xen/stable, what are the feature missing?
>>>
>>>
>> ACPI power management is the main one. pci passthrough was only added
>> yesterday, so it could do with some testing.
>>
> Thought the PCI backend is not yet in. So you are left with this funny
> position of running 2.6.31.x as Dom0 and 2.6.32.x for DomU to do PCI
> passthrough. Should have those patches (pciback) soon enough though.
>
Ah, OK. That too.
J
next prev parent reply other threads:[~2010-03-04 18:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 18:04 xen.git branches Jeremy Fitzhardinge
2010-03-04 7:18 ` Fantu
2010-03-04 18:25 ` Jeremy Fitzhardinge
2010-03-04 18:20 ` Konrad Rzeszutek Wilk
2010-03-04 18:48 ` Jeremy Fitzhardinge [this message]
2010-03-04 19:24 ` Sander Eikelenboom
2010-03-04 20:10 ` Jeremy Fitzhardinge
2010-03-05 0:29 ` Noboru Iwamatsu
2010-03-05 7:26 ` Pasi Kärkkäinen
2010-03-18 23:19 ` xen.git branches / pvops kernel pvusb support Pasi Kärkkäinen
2010-03-18 23:33 ` Jeremy Fitzhardinge
2010-04-12 13:05 ` Pasi Kärkkäinen
2010-06-07 14:59 ` Pasi Kärkkäinen
2010-06-07 15:07 ` Sander Eikelenboom
2010-08-17 19:00 ` porting pvusb drivers to pvops kernel Pasi Kärkkäinen
2010-08-17 22:08 ` Sander Eikelenboom
2010-08-18 0:52 ` Noboru Iwamatsu
2010-08-18 0:08 ` James Harper
2010-08-18 6:28 ` Pasi Kärkkäinen
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=4B900069.2030204@goop.org \
--to=jeremy@goop.org \
--cc=fantonifabio@tiscali.it \
--cc=konrad.wilk@oracle.com \
--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.