xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Florian Wagner <f_wagner@syscomp.de>,
	"Zhang, Xiantao" <xiantao.zhang@intel.com>,
	M A Young <m.a.young@durham.ac.uk>
Subject: Re: Sixth (and final?) release candidate for Xen 3.4.3
Date: Sat, 8 May 2010 09:05:34 +0100	[thread overview]
Message-ID: <C80AD9DE.13B81%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4BE49E3F.7080608@goop.org>

On 08/05/2010 00:11, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:

>>> As I know, you have to backport extra Csets like 28089, 21092, and 21161
>>> from
>>> xen-unstable.hg to make it work well with latest pv_ops kernel except the
>>> Csets Keir had indicated.
>>>     
>> Doesn't sound like 3.4.3 is going to support pv_ops then.
>>   
> 
> Florian and M A Young have reported success with 3.4.3-rc, so it isn't
> completely non-functional.  How essential are those changes?   28089
> doesn't appear in my tree ("abort: unknown revision '28089'"), but 21092
> ("Allow all unused GSI to be configured via IO-APIC by new pv_ops dom0")
> and 21161 ("Make c/s 21089 work again with c/s 21092") both look pertient.

I doubt anyone is running pv_ops dom0 in serious production uses yet. So I'm
not sure backporting this sort of stuff to our very stable branch is really
necessary. Anyone running pv_ops dom0 is likely not scared of Xen 4.0.

 -- Keir

  reply	other threads:[~2010-05-08  8:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 12:00 Sixth (and final?) release candidate for Xen 3.4.3 Keir Fraser
2010-05-05  9:50 ` M A Young
2010-05-06 14:13 ` M A Young
2010-05-06 14:26   ` Keir Fraser
2010-05-06 16:13     ` M A Young
2010-05-06 16:34       ` Keir Fraser
2010-05-07  2:03         ` Zhang, Xiantao
2010-05-07  7:10           ` Keir Fraser
2010-05-07 23:11             ` Jeremy Fitzhardinge
2010-05-08  8:05               ` Keir Fraser [this message]
2010-05-08 11:00                 ` Boris Derzhavets
2010-05-08 15:14                   ` Errors when loading 2.6.32.12 under Xen 4.0 on ASUS P5Q-E Boris Derzhavets
2010-05-12 17:50                 ` Sixth (and final?) release candidate for Xen 3.4.3 Langsdorf, Mark
2010-05-12 19:21                   ` Keir Fraser
2010-05-12 19:42                     ` Langsdorf, Mark
2010-05-06 18:50   ` Jeremy Fitzhardinge
2010-05-06 19:13     ` M A Young
2010-05-06 20:17       ` Jeremy Fitzhardinge
2010-05-07 18:33         ` M A Young

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=C80AD9DE.13B81%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=f_wagner@syscomp.de \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --cc=m.a.young@durham.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    --cc=xiantao.zhang@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).