From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
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: Fri, 07 May 2010 16:11:59 -0700 [thread overview]
Message-ID: <4BE49E3F.7080608@goop.org> (raw)
In-Reply-To: <C8097B6A.1373B%keir.fraser@eu.citrix.com>
On 05/07/2010 12:10 AM, Keir Fraser wrote:
> On 07/05/2010 03:03, "Zhang, Xiantao" <xiantao.zhang@intel.com> wrote:
>
>
>>> Hm, there were changes to 3.4.3 to make it work better with pv_ops
>>> dom0 kernels. I'm thinking things like xen-3.4-testing:19862 and
>>> 19863. I suggest you post more details and you should get help from
>>> pv_ops people (I cc'ed a couple of them :-). They may be able to tell
>>> you straight off whether your pv_ops kernel is too
>>> old/new/weird/whatever, for example.
>>>
>> 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.
J
next prev parent reply other threads:[~2010-05-07 23:11 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 [this message]
2010-05-08 8:05 ` Keir Fraser
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=4BE49E3F.7080608@goop.org \
--to=jeremy@goop.org \
--cc=f_wagner@syscomp.de \
--cc=keir.fraser@eu.citrix.com \
--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 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.