From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Lieven <pl@kamp.de>, Stefan Hajnoczi <stefanha@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] Recent patches for 2.4
Date: Mon, 21 Sep 2015 14:16:40 +0200 [thread overview]
Message-ID: <55FFF528.80504@redhat.com> (raw)
In-Reply-To: <55FFD351.3010305@kamp.de>
On 21/09/2015 11:52, Peter Lieven wrote:
>>
>> e4efd8a488d0a68b0af34d8ee245463df7c8bdf4 qemu-timer: initialize "timers_done_ev" to set
>> 12d69ac03b45156356b240424623719f15d8143e tests: remove irrelevant assertions from test-aio
>> 6493c975af75be5b8d9ade954239bdf5492b7911 aio-win32: reorganize polling loop
>> eabc977973103527bbb8fed69c91cfaa6691f8ab AioContext: fix broken ctx->dispatching optimization
>> 21a03d17f2edb1e63f7137d97ba355cc6f19d79f AioContext: fix broken placement of event_notifier_test_and_clear
>> 05e514b1d4d5bd4209e2c8bbc76ff05c85a235f3 AioContext: optimize clearing the EventNotifier
>> edec47cfef96209987cb7922286cb384916aae02 main-loop: fix qemu_notify_event for aio_notify optimization
>> fed105e2756dde98efa5e80baca02ae516dd1e51 virtio-blk-dataplane: delete bottom half before the AioContext is freed
>> a076972a4d36381d610a854f0c336507650a1d34 AioContext: avoid leaking BHs on cleanup
>> ca96ac44dcd290566090b2435bc828fded356ad9 AioContext: force event loop iteration using BH
>>
>> Paolo
>
> thanks, I will have a look at them. If I understand correctly I should
> consider backporting all?
It's the safest bet, yes.
Paolo
next prev parent reply other threads:[~2015-09-21 12:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 8:12 [Qemu-devel] Recent patches for 2.4 Peter Lieven
2015-07-31 8:22 ` Paolo Bonzini
2015-07-31 8:35 ` Peter Lieven
2015-07-31 9:29 ` Paolo Bonzini
2015-08-04 9:22 ` [Qemu-devel] [Qemu-stable] " Peter Lieven
2015-08-04 11:53 ` Paolo Bonzini
2015-08-04 11:57 ` Peter Lieven
2015-08-04 12:09 ` Paolo Bonzini
2015-08-04 12:29 ` Peter Lieven
2015-08-04 12:53 ` Peter Lieven
2015-08-04 23:23 ` ronnie sahlberg
2015-08-05 8:39 ` Paolo Bonzini
2015-08-06 7:51 ` Peter Lieven
2015-09-03 13:11 ` Peter Lieven
2015-09-07 16:28 ` Paolo Bonzini
2015-09-07 19:11 ` Peter Lieven
2015-09-07 19:14 ` Paolo Bonzini
2015-09-07 21:05 ` Peter Lieven
2015-09-21 7:40 ` Peter Lieven
2015-09-21 9:41 ` Paolo Bonzini
2015-09-21 9:52 ` Peter Lieven
2015-09-21 12:16 ` Paolo Bonzini [this message]
2015-08-04 18:20 ` Michael Roth
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=55FFF528.80504@redhat.com \
--to=pbonzini@redhat.com \
--cc=pl@kamp.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).