Re: [Xen-devel] backport requests for 4.x-testing

[Keir Fraser <keir@xxxxxxx>]

On 07/03/2012 07:25, "Roderick Colenbrander" <thunderbird2k@xxxxxxxxx>
wrote:

> I would like to nominate 2 patches to be backported to Xen 4.1:
> 24458 (libxl: print out vifname in create dryrun.)
> 24459 (libxl: write vifname in xenstore if set.)

These need to be Acked or backported by a toolstack maintainer.

 -- Keir

> Thanks,
> Roderick Colenbrander
> 
> On Tue, Mar 6, 2012 at 3:04 AM, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
> wrote:
>> 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@xxxxxxxxxxxxx
>>> http://lists.xen.org/xen-devel
>> 
>> --
>> Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
>> T: +44 (0)1223 225 900, http://www.citrix.com
>> 
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxx
>> http://lists.xen.org/xen-devel
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel