From: Anthony Wright <anthony@overnetdata.com>
To: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: What is the current state of Dom0 kernel support?
Date: Thu, 18 Jun 2009 23:35:48 +0100 [thread overview]
Message-ID: <4A3AC144.9010602@overnetdata.com> (raw)
In-Reply-To: <652FFB2C8F91E3428799B1FFF8B490C95FCF55132A@FTLPMAILBOX01.citrite.net>
I've seen a number of posts relating to dom0 support in more recent
kernel versions, but I'm unsure what the current situation is and
wondered if somebody might be able clarify things.
I saw a lot of activity around 2.6.30 to get the dom0 patches accepted
into the mainline kernel, but now while I believe the 2.6.31 merge
window is open I see very little activity. There was an interesting
thread prior to the merge window opening on the subject of dom0 support
and wondered if as a result of this there's been a decision not to try
to get the patches accepted at this time? If this is the case is there a
plan to try again in the future?
I also saw a thread from Kier recently on the subject of the xenbits
linux trees, and wondered if any decision came out of that? Within the
thread I saw mention of a number of other kernel patch sets that offer
dom0 in a more recent kernels, but certain features seem to be missing
from each one.
If I wanted to to use a more recent kernel for dom0 within the next 3
months what options are available, and do these options have any
limitations?
thanks,
Anthony Wright.
next prev parent reply other threads:[~2009-06-18 22:35 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 9:32 Xen Source Code Overview Document Stephen Spector
2009-06-18 22:35 ` Anthony Wright [this message]
2009-06-22 4:48 ` What is the current state of Dom0 kernel support? Thiago Camargo Martins Cordeiro
2009-06-22 9:21 ` Dennis Krul
2009-06-26 18:04 ` Jeremy Fitzhardinge
2009-06-26 18:21 ` Tim Post
2009-06-26 18:29 ` Jeremy Fitzhardinge
2009-07-08 22:14 ` Pasi Kärkkäinen
2009-07-09 0:23 ` Jeremy Fitzhardinge
2009-07-09 8:58 ` M A Young
2009-07-09 22:24 ` Pasi Kärkkäinen
2009-07-15 8:22 ` Pasi Kärkkäinen
2009-07-21 13:03 ` What is the current state of Dom0 kernel support? / crash Pasi Kärkkäinen
2009-07-22 19:14 ` Jeremy Fitzhardinge
2009-07-22 19:35 ` Pasi Kärkkäinen
2009-07-22 19:55 ` Jeremy Fitzhardinge
2009-07-22 19:58 ` Pasi Kärkkäinen
2009-07-22 19:57 ` Pasi Kärkkäinen
2009-07-22 20:25 ` Jeremy Fitzhardinge
2009-07-22 20:53 ` Pasi Kärkkäinen
2009-07-29 20:48 ` Jeremy Fitzhardinge
2009-07-30 8:48 ` Pasi Kärkkäinen
2009-07-30 11:35 ` Pasi Kärkkäinen
2009-08-10 16:43 ` Pasi Kärkkäinen
2009-08-10 16:52 ` Jeremy Fitzhardinge
2009-08-10 19:27 ` Pasi Kärkkäinen
2009-08-11 19:58 ` What is the current state of Dom0 kernel support? / crash with 2.6.31-rc5 32bit PAE Pasi Kärkkäinen
2009-08-11 20:12 ` Jeremy Fitzhardinge
2009-08-13 20:17 ` Jeremy Fitzhardinge
2009-08-14 14:15 ` Pasi Kärkkäinen
2009-08-17 15:04 ` What is the current state of Dom0 kernel support? / 2.6.31-rc5 32bit PAE works now! Pasi Kärkkäinen
2009-08-17 15:26 ` Pasi Kärkkäinen
2009-08-17 17:51 ` Jeremy Fitzhardinge
2009-07-23 8:22 ` What is the current state of Dom0 kernel support? Anthony Wright
2009-07-23 8:31 ` Pasi Kärkkäinen
2009-07-23 8:37 ` Keir Fraser
2009-07-24 2:55 ` Simon Horman
2009-07-09 10:11 ` Xen Source Code Overview Document Zhigang Wang
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=4A3AC144.9010602@overnetdata.com \
--to=anthony@overnetdata.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.