From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40009) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMgpW-0007zK-37 for qemu-devel@nongnu.org; Tue, 04 Aug 2015 14:20:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZMgpR-0006vb-0K for qemu-devel@nongnu.org; Tue, 04 Aug 2015 14:20:50 -0400 Received: from e39.co.us.ibm.com ([32.97.110.160]:54374) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMgpQ-0006vR-QL for qemu-devel@nongnu.org; Tue, 04 Aug 2015 14:20:44 -0400 Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 4 Aug 2015 12:20:44 -0600 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Michael Roth In-Reply-To: <55BB335A.1010009@kamp.de> References: <55BB2DF7.8010808@kamp.de> <55BB302D.50108@redhat.com> <55BB335A.1010009@kamp.de> Message-ID: <20150804182038.17567.57344@loki> Date: Tue, 04 Aug 2015 13:20:38 -0500 Subject: Re: [Qemu-devel] [Qemu-stable] Recent patches for 2.4 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Lieven , Paolo Bonzini , Stefan Hajnoczi Cc: "qemu-devel@nongnu.org" , qemu-stable@nongnu.org Quoting Peter Lieven (2015-07-31 03:35:38) > Am 31.07.2015 um 10:22 schrieb Paolo Bonzini: > > > > On 31/07/2015 10:12, Peter Lieven wrote: > >> Hi Paolo, hi Stefan, > >> > >> you submitted some fixes for 2.4 recently. None of the folloing had qe= mu-stable in CC. Is this not stable material? > > In general I send less and less patches to qemu-stable as we get closer > > to the new release, because I'm not sure anymore if they apply. > = > My background was that Michael Roth just send an announcement for an upco= ming 2.3.1 release. > = > > > > Let's look at your list: > > > >> ca96ac4 AioContext: force event loop iteration using BH > >> a076972 AioContext: avoid leaking BHs on cleanup > >> fed105e virtio-blk-dataplane: delete bottom half before the AioContext= is freed > >> 05e514b AioContext: optimize clearing the EventNotifier > >> 21a03d1 AioContext: fix broken placement of event_notifier_test_and_cl= ear > >> eabc977 AioContext: fix broken ctx->dispatching optimization > > These could in principle be backported, but the bug was only visible on > > aarch64 hosts and only in relatively special circumstances (UEFI > > firmware, KVM, virtio-scsi, many disks) so I didn't Cc qemu-stable. > = > I was not aware that all those patches belong to a single bug on aarch64. > = > > > >> 52c91da memory: do not add a reference to the owner of aliased regions > > This could be backported, yes. Feel free to send it to qemu-stable. > > However, the bug was only visible with virtio 1. > = > Applies cleanly to 2.3.1-staging. I've gone ahead and applied locally but I may end up dropping it if I can verify this is specifically a virtio-1 issue. > = > > > >> edec47c main-loop: fix qemu_notify_event for aio_notify optimization > > Part of the above AioContext series. > = > So either the whole series or none of them I guess? > = > > > >> deb809e memory: count number of active VGA logging clients > > Not this one, it's new in 2.5. > > > >> ab28bd2 rcu: actually register threads that have RCU read-side critica= l sections > > Probably has conflicts, but can be sent to qemu-stable. > = > Has conflicts and I am not 100% sure to resolve them. > = > > > >> 9172f42 qemu-char: handle EINTR for TCP character devices > > Can be sent to qemu-stable if it applies to 2.4. > = > Applies cleanly to 2.3.1-staging. Also applied locally, thanks! > = > Peter >=20