From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58259) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1elGjT-00089I-4I for qemu-devel@nongnu.org; Mon, 12 Feb 2018 11:13:32 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1elGjP-000634-Hq for qemu-devel@nongnu.org; Mon, 12 Feb 2018 11:13:31 -0500 Date: Mon, 12 Feb 2018 16:13:23 +0000 From: "Dr. David Alan Gilbert" Message-ID: <20180212161323.GC2545@work-vm> References: <20180206191515.25830-1-mdroth@linux.vnet.ibm.com> <1fa746ad-7640-6159-26e3-b2fb378c68af@kamp.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1fa746ad-7640-6159-26e3-b2fb378c68af@kamp.de> Subject: Re: [Qemu-devel] [Qemu-stable] [PATCH 00/54] Patch Round-up for stable 2.11.1, freeze on 2018-02-12 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven Cc: Michael Roth , qemu-devel@nongnu.org, qemu-stable@nongnu.org, christian.ehrhardt@canonical.com * Peter Lieven (pl@kamp.de) 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 qemu-stable@nongnu.org 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. The 'migration: Recover block devices if failure in device state' is probably a good candidate. Another one would be Greg Kurz's: 875fcd013ab68c64802998b22f54f0184479d21b - migration: incoming postcopy advise sanity checks Dave > Thank you, > Peter > -- Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK