From: Andrew Cooper <andrew.cooper3@citrix.com>
To: xen-devel@lists.xen.org
Subject: Re: backport requests for 4.x-testing
Date: Tue, 6 Mar 2012 11:04:13 +0000 [thread overview]
Message-ID: <4F55EF2D.7010302@citrix.com> (raw)
In-Reply-To: <4F55F15F02000078000769AC@nat28.tlf.novell.com>
On 06/03/12 10:13, Jan Beulich wrote:
> For a (hopefully soon) upcoming 4.1.3 and 4.0.4, may I ask to consider
> the following changesets from -unstable for backporting:
May I add the following suggestions. These are all patches which we
have cherry picked for XenServer.
The changesets with *'s are not a clean backport, and I can provide
patches against Xen-4.1.x for them.
> For 4.0 and 4.1:
> 24155 (x86/IO-APIC: refine EOI-ing of migrating level interrupts)
> 24190 (x86/mm: change return code for log-dirty disabling)
> 24201 (x86: small fixes to pcpu platform op handling)
> 24282 (x86/mm: Don't lose track of the log dirty bitmap)
> 24389 (x86, amd: Disable GartTlbWlkErr when BIOS forgets it)
> 24417 (x86/emulator: workaround for AMD erratum 573)
> 24535 (x86/vMSI: miscellaneous fixes)
> 24888 (passthrough: release assigned PCI devices earlier during domain shutdown)
>
> For 4.1:
23554 (shadow: adjust early heuristics)
23610 (x86: consolidate cpu_core_id and phys_proc_id)
23611 (AMD: core-pair detection)
23795* (x86: ICH10 Quirks) - We have just had to backport this for a
customer escalation on xen-3.x, if it would be accepted there
23811* (UART: dont write spurious char)
> 23853+23955 (pv cpuid emulation for xsave)
> 23908 (p2m: query/modify p2mt with p2m_lock held)
23936*,23937,23938*,23939,23940,23941 (Various ocaml fixes)
> 24156 (x86/IRQ: prevent vector sharing within IO-APICs, requiring
> 23900 [kzalloc])
> 24157 (x86/xsave: provide guests with finit-like environment)
24320 (ocaml: release global lock during some hypercalls)
> 24357 (tools/firmware: remove "_PS0/3" Method)
24414 (oxenstored: install configuration file)
> 24448 (x86/passthrough: don't leak guest IRQs)
(I can provide a backported version of 24448 if required)
> 24517 (Move IOMMU faults handling into softirq for VT-d)
24518 (sched_credit: performance improvement)
> 24527 (iommu: Move IOMMU faults handling into softirq for AMD-Vi)
24542, 24543, 24570, 24571 (xenoprof fixes)
> 24701 (Fix error recovery path in __gnttab_map_grant_ref)
24709 (libxc: replace malloc with alloca on hot path)
24832 (libxc: remove tests of alloca() return value)
24870* (IOAPIC: prevent directed EOI support trashing io_ack mode)
> 24883 (x86/mm: Don't check for invalid bits in non-present PTEs)
> 24950 (Grant table: fix a bug when grant copying a previous grant mapped page)
>
> For 4.0 (already in 4.1)
> 24168 (x86/vioapic: clear remote IRR when switching RTE to edge triggered mode)
> 24193 (Trivial fix for rc val in hap track dirty vram)
> 24344+24345 (tools/x86_64: Fix cpuid() inline asm to not clobber stack's red zone)
> 24358 (KEXEC: fix kexec_get_range_compat to fail vocally)
> 24690 (x86: avoid deadlock after a PCI SERR NMI)
> 24742 (gnttab: miscellaneous fixes)
>
> Especially some of the 4.0 ones may be non-trivial backports - already
> backported version can be provided.
>
> Thanks, Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
next prev parent reply other threads:[~2012-03-06 11:04 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 10:13 backport requests for 4.x-testing Jan Beulich
2012-03-06 10:38 ` Keir Fraser
2012-03-06 11:04 ` Andrew Cooper [this message]
2012-03-07 7:25 ` Roderick Colenbrander
2012-03-07 9:43 ` Keir Fraser
2012-03-13 16:50 ` Ian Jackson
2012-03-13 17:25 ` Teck Choon Giam
2012-03-13 17:52 ` Teck Choon Giam
2012-03-13 18:23 ` Teck Choon Giam
2012-03-14 10:03 ` Ian Jackson
2012-03-14 9:58 ` Ian Jackson
2012-03-14 11:37 ` Ian Jackson
2012-03-14 23:08 ` Teck Choon Giam
2012-03-19 14:22 ` Teck Choon Giam
2012-04-03 15:04 ` Ian Jackson
2012-03-07 9:43 ` Keir Fraser
2012-03-07 10:44 ` Andrew Cooper
2012-03-07 10:59 ` Keir Fraser
2012-03-07 11:06 ` Jan Beulich
2012-03-07 11:08 ` Andrew Cooper
2012-03-07 19:38 ` Ian Campbell
2012-03-08 10:38 ` Andrew Cooper
2012-03-08 10:42 ` Keir Fraser
2012-03-13 16:52 ` Ian Jackson
2012-03-24 17:27 ` Konrad Rzeszutek Wilk
2012-03-29 9:22 ` Keir Fraser
2012-03-29 11:32 ` Teck Choon Giam
2012-03-29 11:42 ` Teck Choon Giam
2012-03-29 15:11 ` Konrad Rzeszutek Wilk
2012-03-29 15:26 ` Teck Choon Giam
2012-03-29 15:56 ` Konrad Rzeszutek Wilk
2012-03-29 16:20 ` Teck Choon Giam
2012-03-29 16:23 ` Konrad Rzeszutek Wilk
2012-03-29 16:39 ` Teck Choon Giam
2012-03-29 11:55 ` Stefano Stabellini
2012-03-29 15:31 ` Jan Beulich
2012-03-29 17:06 ` Stefano Stabellini
2012-03-30 8:23 ` Keir Fraser
2012-03-30 9:59 ` Stefano Stabellini
2012-04-03 15:08 ` Ian Jackson
2012-04-03 15:15 ` Teck Choon Giam
2012-04-03 16:58 ` Ian Jackson
2012-04-03 19:50 ` Teck Choon Giam
2012-04-03 20:02 ` Teck Choon Giam
2012-04-04 10:22 ` Ian Jackson
2012-04-04 12:54 ` Teck Choon Giam
2012-04-04 15:09 ` Ian Jackson
2012-03-07 9:18 ` Keir Fraser
2012-03-07 10:10 ` Jan Beulich
2012-03-08 10:00 ` Jan Beulich
2012-03-08 10:05 ` Keir Fraser
2012-03-08 10:45 ` Jan Beulich
2012-03-08 11:00 ` Keir Fraser
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=4F55EF2D.7010302@citrix.com \
--to=andrew.cooper3@citrix.com \
--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).