From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/4] qemu-timer: introduce usable pointer-free API
Date: Fri, 09 Jan 2015 10:07:00 +0100 [thread overview]
Message-ID: <54AF9A34.9090207@redhat.com> (raw)
In-Reply-To: <20150109021046.GA6087@fam-t430.nay.redhat.com>
On 09/01/2015 03:10, Fam Zheng wrote:
> On Thu, 01/08 11:03, Paolo Bonzini wrote:
>> The current pointer free API for timers is very low level. Introduce
>> a new API that matches timer_new_ns/us/ms and also a new API timer_deinit
>> that can be used instead of timer_free.
>>
>> Finally, mechanically change timer macro names in vmstate, to make it
>> clear that they accept a pointer.
>>
>> This prepares for conversion of timers from QEMUTimer * to QEMUTimer.
>
> Novice question: what's the advantage, please?
No need to free them, so no memory leaks. From a quick look I found two
(hw/net/pcnet.c and hw/char/serial.c).
Also it matches more recent device model APIs like memory regions or
throttling.
Paolo
> Fam
>
>>
>> Paolo
>>
>> Paolo Bonzini (4):
>> qemu-timer: rename timer_init to timer_init_tl
>> qemu-timer: add timer_init and timer_init_ns/us/ms
>> qemu-timer: introduce timer_deinit
>> vmstate: accept QEMUTimer in VMSTATE_TIMER*, add VMSTATE_TIMER_PTR*
>>
>> hw/acpi/ich9.c | 2 +-
>> hw/acpi/piix4.c | 2 +-
>> hw/arm/stellaris.c | 2 +-
>> hw/block/fdc.c | 2 +-
>> hw/char/cadence_uart.c | 2 +-
>> hw/char/serial.c | 4 +-
>> hw/core/ptimer.c | 2 +-
>> hw/dma/pl330.c | 2 +-
>> hw/input/lm832x.c | 2 +-
>> hw/intc/armv7m_nvic.c | 2 +-
>> hw/isa/vt82c686.c | 2 +-
>> hw/misc/macio/cuda.c | 2 +-
>> hw/net/pcnet.c | 2 +-
>> hw/sd/sdhci.c | 4 +-
>> hw/timer/a9gtimer.c | 2 +-
>> hw/timer/arm_mptimer.c | 2 +-
>> hw/timer/hpet.c | 2 +-
>> hw/timer/mc146818rtc.c | 4 +-
>> hw/usb/hcd-ehci.c | 2 +-
>> hw/usb/hcd-ohci.c | 2 +-
>> hw/usb/hcd-uhci.c | 2 +-
>> hw/usb/hcd-xhci.c | 2 +-
>> hw/usb/redirect.c | 2 +-
>> hw/watchdog/wdt_i6300esb.c | 2 +-
>> hw/watchdog/wdt_ib700.c | 2 +-
>> include/block/aio.h | 2 +-
>> include/migration/vmstate.h | 18 +++++++--
>> include/qemu/timer.h | 94 ++++++++++++++++++++++++++++++++++++++++++---
>> qemu-timer.c | 20 +++++++---
>> target-arm/machine.c | 4 +-
>> 30 files changed, 149 insertions(+), 45 deletions(-)
>>
>> --
>> 2.1.0
>>
>>
>
>
next prev parent reply other threads:[~2015-01-09 9:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 10:03 [Qemu-devel] [PATCH 0/4] qemu-timer: introduce usable pointer-free API Paolo Bonzini
2015-01-08 10:03 ` [Qemu-devel] [PATCH 1/4] qemu-timer: rename timer_init to timer_init_tl Paolo Bonzini
2015-01-08 10:03 ` [Qemu-devel] [PATCH 2/4] qemu-timer: add timer_init and timer_init_ns/us/ms Paolo Bonzini
2015-01-09 2:19 ` Fam Zheng
2015-01-09 10:39 ` Paolo Bonzini
2015-01-08 10:03 ` [Qemu-devel] [PATCH 3/4] qemu-timer: introduce timer_deinit Paolo Bonzini
2015-01-08 10:03 ` [Qemu-devel] [PATCH 4/4] vmstate: accept QEMUTimer in VMSTATE_TIMER*, add VMSTATE_TIMER_PTR* Paolo Bonzini
2015-01-15 9:04 ` Amit Shah
2015-01-15 9:14 ` Paolo Bonzini
2015-01-09 2:10 ` [Qemu-devel] [PATCH 0/4] qemu-timer: introduce usable pointer-free API Fam Zheng
2015-01-09 9:07 ` Paolo Bonzini [this message]
2015-01-10 1:35 ` Fam Zheng
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=54AF9A34.9090207@redhat.com \
--to=pbonzini@redhat.com \
--cc=famz@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).