From: Alex Bligh <alex@alex.org.uk>
To: "Benoît Canet" <benoit.canet@irqsave.net>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Ping Fan Liu <pingfank@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, Alex Bligh <alex@alex.org.uk>
Subject: Re: [Qemu-devel] [PATCH 0/2] qemu-timer: make qemu_timer_mod_ns() and qemu_timer_del() thread-safe
Date: Mon, 12 Aug 2013 22:20:15 +0100 [thread overview]
Message-ID: <FD8A4736445BE04D3BBFD12A@nimrod.local> (raw)
In-Reply-To: <20130812203133.GF5061@irqsave.net>
Benoit,
--On 12 August 2013 22:31:34 +0200 Benoît Canet <benoit.canet@irqsave.net>
wrote:
> Is there a git tree on which I could rebase my throttling series on top of
> the new timers ?
API wise, mine should do, at:
https://github.com/abligh/qemu/tree/aio-timers10
That won't have Stefan's thread-safe stuff in but that's not needed
yet.
You should just be able to run scripts/switch-timer-api [list of files]
and it should convert your source code to the new timer API. I would
be interested to know whether this works.
--
Alex Bligh
prev parent reply other threads:[~2013-08-12 21:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 12:49 [Qemu-devel] [PATCH 0/2] qemu-timer: make qemu_timer_mod_ns() and qemu_timer_del() thread-safe Stefan Hajnoczi
2013-08-12 12:49 ` [Qemu-devel] [PATCH 1/2] qemu-timer: drop outdated signal safety comments Stefan Hajnoczi
2013-08-12 13:15 ` Alex Bligh
2013-08-12 12:49 ` [Qemu-devel] [PATCH 2/2] qemu-timer: make qemu_timer_mod_ns() and qemu_timer_del() thread-safe Stefan Hajnoczi
2013-08-12 13:19 ` Alex Bligh
2013-08-15 0:05 ` liu ping fan
2013-08-15 8:01 ` Stefan Hajnoczi
2013-08-15 8:22 ` liu ping fan
2013-08-15 8:24 ` liu ping fan
2013-08-15 12:00 ` Stefan Hajnoczi
2013-08-19 12:15 ` Paolo Bonzini
2013-08-15 8:43 ` Alex Bligh
2013-08-19 12:12 ` Paolo Bonzini
2013-08-12 20:31 ` [Qemu-devel] [PATCH 0/2] " Benoît Canet
2013-08-12 21:20 ` Alex Bligh [this message]
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=FD8A4736445BE04D3BBFD12A@nimrod.local \
--to=alex@alex.org.uk \
--cc=benoit.canet@irqsave.net \
--cc=pbonzini@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--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 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).