All of lore.kernel.org
 help / color / mirror / Atom feed
From: Xuebing Wang <xbing6list@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Alex Bligh <alex@alex.org.uk>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel]  Questions about timer
Date: Sun, 23 Feb 2014 11:46:04 +0800	[thread overview]
Message-ID: <53096EFC.9040001@gmail.com> (raw)

Hi Community,

I am new to qemu, I am trying to familiarize myself with aarch64 
timer/interrupt support (maybe someone already did this, but not merged 
into mainline yet).

As shown in include/qemu/timer.h, there are 6 categories of APIs:
- QEMUClockType
- QEMUTimerList
- QEMUTimerListGroup
- QEMUTimer
- General utility functions
- Low level clock functions

I have a few questions:

Q1) All QEMUTimerList functions are private to qemu-timer.c. Can we make 
them static and remove them from include/qemu/timer.h because they are 
NOT APIs?

Q2) The implementation of other categories of API functions are kind of 
inter-wined, does it make sense to re-organize them in qemu-timer.c, and 
make them strictly follow the sequence in include/qemu/timer.h?

Q3) Below functions are NOT implemented in qemu-timer.c, but declared in 
include/qemu/timer.h, should we address this?
- qemu_clock_warp
- timer_get and timer_put
- cpu_get_ticks, cpu_enable_ticks, cpu_disable_ticks

Q4) Do we need this API qemu_clock_get_main_loop_timerlist?

-- 
Thanks,
Xuebing Wang

             reply	other threads:[~2014-02-23  3:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  3:46 Xuebing Wang [this message]
2014-02-23  9:44 ` [Qemu-devel] Questions about timer Alex Bligh

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=53096EFC.9040001@gmail.com \
    --to=xbing6list@gmail.com \
    --cc=alex@alex.org.uk \
    --cc=pbonzini@redhat.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 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.