[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen 4.2.3-rc2 and 4.1.6-rc2 have been tagged

>>> On 02.09.13 at 20:17, Andrew Cooper <andrew.cooper3@xxxxxxxxxx> wrote:
> 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"

I can see the value of the latter, but the former seems to be pure
cleanup (which we don't normally backport).

> 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"

The real meat here is the second one, and for a backport I'd
prefer to limit the change to this, even if that means that we'll
have to add an #ifdef CONFIG_X86 to common code.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.