From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Keir Fraser <keir@xen.org>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Recommendations for backport from unstable to 4.1
Date: Fri, 6 Jul 2012 16:36:20 +0100 [thread overview]
Message-ID: <4FF705F4.9050600@citrix.com> (raw)
Hello,
Here are some more recommendations for backports from unstable to 4.1,
based upon the XenServer patch queue. Patches with a * do not apply
cleanly, and I can provide patches if you wish to backport them. The
rest should apply cleanly (unless I have missed a dependency on other
patches we have in our queue, which case I apologize)
The following are bugfixes:
* 23101:dd386a4b6595 # x86: fix tboot after c/s 23013:65d26504e843 (ACPI
cleanup)
23686:7c39a2c0d870 # pygrub: fix solaris kernel issue
23781:0849b0e59e24 # pm: don't truncate processors' ACPI IDs to 8 bits
23813:5535d7ce2673 # xen, vtd: Fix device check for devices behind
PCIe-to-PCI bridges
25162:478bec603d3d # xen: Fix schedule()'s grabbing of the schedule lock
25487:baa85434d0ec # x86/mm: fix mod_l1_entry() return value when
encountering r/o MMIO page
25489:cc46bd403bc4 # x86/PCI: fix guest_io_read() when pci_cfg_ok()
denies access
The following are not strictly bugfixes, but I feel they should be
considered:
* 23726:fd97ca086df6 # x86: update Intel CPUID masking code to latest spec
23731:48f72b389b04 # x86: add change missing in c/s 23726:fd97ca086df6
24261:64088ba60263 # x86/cpuidle: add Westmere-EX support to hw
residencies reading logic
24970:33980e36597b # x86/cpuidle: deny access to the I/O port used for
EM_SYSIO
* 25482:34c725807d21 # SVM: fix performance decrease with asid assignment
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next reply other threads:[~2012-07-06 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 15:36 Andrew Cooper [this message]
2012-07-09 9:32 ` Recommendations for backport from unstable to 4.1 Keir Fraser
2012-07-09 13:47 ` Andrew Cooper
2012-07-30 9:27 ` 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=4FF705F4.9050600@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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 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).