[Top][All Lists]

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

Re: [Qemu-devel] [Qemu-stable] [PATCH 00/54] Patch Round-up for stable 2

From: Peter Lieven
Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH 00/54] Patch Round-up for stable 2.11.1, freeze on 2018-02-12
Date: Fri, 16 Feb 2018 10:46:37 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1

Am 12.02.2018 um 17:13 schrieb Dr. David Alan Gilbert:
> * Peter Lieven (address@hidden) wrote:
>> Am 06.02.2018 um 20:14 schrieb Michael Roth:
>>> Hi everyone,
>>> The following new patches are queued for QEMU stable v2.11.1:
>>>    https://github.com/mdroth/qemu/commits/stable-2.11-staging
>>> The release is planned for 2017-02-14:
>>>    https://wiki.qemu.org/Planning/2.11
>>> Please respond here or CC address@hidden on any patches you
>>> think should be included in the release.
>>> Of particular importance would be any feedback on the various QEMU
>>> patches relating to Spectre/Meltdown mitigation. The current tree has
>>> what I understand to be the QEMU components required for x86, s390,
>>> and pseries, but feedback/confirmation from the various authors would
>>> be greatly appreciated.
>> Hi,
>> I also found the following patches that affect migration:
>> migration: Don't leak IO channels
>> migration: Recover block devices if failure in device state
>> migration/savevm.c: set MAX_VM_CMD_PACKAGED_SIZE to 1ul << 32
>> In general it seems that migration related patches are often not tagged 
>> qemu-stable.
>> David, can you check if there are patches missing?
> I'm always a bit cautious about forwarding stuff to stable; just because
> it's landed in our main branch it doesn't mean many people have tested
> it, so I'd rather wait unless it was particularly urgent.

Understood. Maybe we need a special mechanism to track such patches.
It would be good to have them in a stable release. Maybe tag them as 
or sth. Then we can recheck their status when a stable release is going to be 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]