From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged
Date: Mon, 2 Sep 2013 19:17:20 +0100 [thread overview]
Message-ID: <5224D630.1050701@citrix.com> (raw)
In-Reply-To: <52208C8C02000078000EFAD7@nat28.tlf.novell.com>
On 30/08/13 11:14, Jan Beulich wrote:
> All,
>
> with the goal of releasing by the end of next week (with little of no
> further changes) - please test!
>
> Thanks, Jan
Looking through the list of patches backported in XenServer,
Ian:
Can I strongly recommend 704302ce9404c73cfb687d31adcf67094ab5bb53
"oxenstored: Protect oxenstored from malicious domains." for backport to
all trees.
Jan:
Can I suggest possibly:
* fca11da0ec956b17d7450d7776c3ffa22a8f538a "x86: Special case
__HYPERVISOR_iret rather more when writing hypercall pages"
* 3e787021fb2420851c7bdc3911ea53c728ba5ac0 "x86/Intel: add support for
Haswell CPU models"
As a group - more detail in the console ring in the case of a crash:
* 66450c1d1ab3c4480bbba949113b95d1ab6a943a "xen/conring: Write to
console ring even if console lock is busted"
* cc90bf1894daf9f97791495e2256e7e342e25704 "xen/conring: Clean up
writing to the console ring"
As a group - improvements around console_force_unlock():
* 44db24103ff1c53a13afebf4d72ad853cee07786 "fix gdbstub build c/s
c8177e691f"
* 7b9fa702ca323164d6b49e8b639a57f880454a8c "watchdog/crash: Always
disable watchdog in console_force_unlock()"
* 896934596614b44c20a37263c9decb0b639ef995 "x86/watchdog: Tweak
implementation given new common code"
* c8177e691f0f611240853326712d43482ec949bf "watchdog: Move watchdog from
being x86 specific to common code"
~Andrew
next prev parent reply other threads:[~2013-09-02 18:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 10:14 Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged Jan Beulich
2013-09-02 18:17 ` Andrew Cooper [this message]
2013-09-03 11:05 ` Ian Jackson
2013-09-03 14:34 ` Andrew Cooper
2013-09-03 14:48 ` Ian Jackson
2013-09-03 14:58 ` Ian Campbell
2013-09-03 15:36 ` Lars Kurth
2013-09-04 8:03 ` Jan Beulich
2013-09-04 10:33 ` Ian Jackson
2013-09-06 12:31 ` Lars Kurth
2013-09-06 12:38 ` Jan Beulich
2013-09-04 7:10 ` Jan Beulich
2013-09-12 9:11 ` Jan Beulich
2013-09-26 8:08 ` Ping: backport proposals (was: Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged) Jan Beulich
2013-09-26 9:31 ` Ping: backport proposals Andrew Cooper
2013-09-26 10:08 ` Jan Beulich
2013-09-27 8:34 ` Jan Beulich
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=5224D630.1050701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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.