From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [RFC] Handling more than one internal CPU timer.
Date: Mon, 26 Mar 2007 09:00:10 +0200 [thread overview]
Message-ID: <1174892411.6794.17.camel@rapid> (raw)
Embedded PowerPC have the need of implementing 3 timers in the core
area:
- a fixed interval timer
- a programable interval timer
- a watchdog timer
Those 3 timers are fully independant and can raise different exceptions
(eventually at the same time). For this reason, they cannot be
implemented properly using the existing CPU_INTERRUPT_TIMER. My proposal
would be to add more definitions for another CPU_INTERRUPT_TIMER2 and
CPU_INTERUUPT_WDT in cpu-all.h.
As many embedded processors may have this need, it seems to be that this
could be useful for other targets too....
Another solution would be to add another bitfield to the CPU definition
structure, but then the CPU_INTERRUPT current definitions become less
useful imho.
Please comment.
--
J. Mayer <l_indien@magic.fr>
Never organized
reply other threads:[~2007-03-26 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1174892411.6794.17.camel@rapid \
--to=l_indien@magic.fr \
--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).