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

Not at this point anymore; I'll take a close look for 4.2.4.


Xen-devel mailing list



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