All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] Last call for release-critical fixes for 2.3...
Date: Wed, 08 Apr 2015 13:48:25 -0400	[thread overview]
Message-ID: <552569E9.4010805@redhat.com> (raw)
In-Reply-To: <CAFEAcA__c2ey2AxgSm+zk+UEDAAuO_n-q=LnjUgCHRUuyFS7Tg@mail.gmail.com>



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.

  reply	other threads:[~2015-04-08 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 15:20 [Qemu-devel] Last call for release-critical fixes for 2.3 Peter Maydell
2015-04-08 17:48 ` John Snow [this message]
2015-04-09  9:08   ` Stefan Hajnoczi
2015-04-08 18:10 ` Andreas Färber
2015-04-10 13:46   ` Peter Maydell
2015-04-10 14:38     ` Andreas Färber
2015-04-13 12:20 ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=552569E9.4010805@redhat.com \
    --to=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.