From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51807) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yfu5Y-00056I-1P for qemu-devel@nongnu.org; Wed, 08 Apr 2015 13:48:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Yfu5U-0003DB-0a for qemu-devel@nongnu.org; Wed, 08 Apr 2015 13:48:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]:56012) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Yfu5T-0003Cw-RB for qemu-devel@nongnu.org; Wed, 08 Apr 2015 13:48:27 -0400 Message-ID: <552569E9.4010805@redhat.com> Date: Wed, 08 Apr 2015 13:48:25 -0400 From: John Snow MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Last call for release-critical fixes for 2.3... List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell , QEMU Developers Cc: Paolo Bonzini , Stefan Hajnoczi On 04/08/2015 11:20 AM, Peter Maydell wrote: > It looks like we have perhaps only a few more issues which need fixes > to go into 2.3, so what I'd like to do is hold rc3 until we have them > all fixed and then roll an rc3 which will with luck be our final > release (bar the version number). > > Can people reply to this mail if they have things that need to go in? > So far I know about: > * Stefan intends to submit a pullreq with a few patches tomorrow > * some patches from Dirk to use memory_region_allocate_system_memory > (though we've had several releases with this regression so it's > not a huge deal if these don't make it) > > Anything else? > > thanks > -- PMM > I am still working on testing it, but I think '[Qemu-devel] [PATCH] aio: strengthen memory barriers for bottom half scheduling' is likely something that should go in rc3 if it is to be our final RC. I am seeing a lot more missed completion notifications in my testing right now than I have even a month ago, so I am a little concerned. I'm trying to reproduce with this patch /right now/ to confirm it fixes my problem; it at least fixes Paul Leveille's.