From: Blue Swirl <blauwirbel@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH 09/17] lm32: timer model
Date: Sat, 12 Feb 2011 08:56:17 +0200 [thread overview]
Message-ID: <AANLkTikzhBcijY9cJk_eHi2YL-QLdQyUJkYRDwOzOmY7@mail.gmail.com> (raw)
In-Reply-To: <201102112329.31258.michael@walle.cc>
On Sat, Feb 12, 2011 at 12:29 AM, Michael Walle <michael@walle.cc> wrote:
> Am Freitag 11 Februar 2011, 22:22:32 schrieb Blue Swirl:
>> > +static uint32_t timer_read(void *opaque, target_phys_addr_t addr)
>> > +{
>> > + LM32TimerState *s = opaque;
>> > + uint32_t r = 0;
>> > +
>> > + addr >>= 2;
>> > + switch (addr) {
>> > + case R_SR:
>> > + case R_CR:
>> > + case R_PERIOD:
>> > + r = s->regs[addr];
>> > + break;
>> > + case R_SNAPSHOT:
>> > + r = (uint32_t)ptimer_get_count(s->ptimer);
>> > + break;
>> > +
>> > + default:
>> > + hw_error("lm32_timer: read access to unkown register 0x"
>> > + TARGET_FMT_plx, addr << 2);
>>
>> Insecure, please fix also others.
> Many devices in hw/ treat memory access to unknown registers in that way. Are
> there any 'good' example models, where i can look at?
I think Sparc32 devices are OK, though for example DMA handling is not so clean.
> I guess i should print a
> warning instead?
That's one way, but if there are a lot of warnings it becomes a
nuisance. Tracepoints are a bit more flexible, but then they'd have to
be enabled.
next prev parent reply other threads:[~2011-02-12 6:56 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 23:11 [Qemu-devel] [PATCH 00/17 v2] LatticeMico32 target Michael Walle
2011-02-10 23:11 ` [Qemu-devel] [PATCH 01/17] LatticeMico32 target support Michael Walle
2011-02-10 23:11 ` [Qemu-devel] [PATCH 02/17] lm32: translation routines Michael Walle
2011-02-11 21:42 ` Blue Swirl
2011-02-11 22:23 ` Michael Walle
2011-02-12 6:49 ` Blue Swirl
2011-02-17 22:51 ` Michael Walle
2011-03-11 5:57 ` Alexander Graf
2011-03-16 23:08 ` Michael Walle
2011-03-16 23:48 ` Alexander Graf
2011-02-12 13:18 ` Michael Walle
2011-02-10 23:11 ` [Qemu-devel] [PATCH 03/17] lm32: translation code helper Michael Walle
2011-02-10 23:11 ` [Qemu-devel] [PATCH 04/17] lm32: machine state loading/saving Michael Walle
2011-02-10 23:11 ` [Qemu-devel] [PATCH 05/17] lm32: gdbstub support Michael Walle
2011-02-10 23:11 ` [Qemu-devel] [PATCH 06/17] lm32: interrupt controller model Michael Walle
2011-02-11 21:49 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 07/17] lm32: juart model Michael Walle
2011-02-11 21:09 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 08/17] lm32: pic and juart helper functions Michael Walle
2011-02-11 20:57 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 09/17] lm32: timer model Michael Walle
2011-02-11 21:22 ` Blue Swirl
2011-02-11 22:29 ` Michael Walle
2011-02-12 6:56 ` Blue Swirl [this message]
2011-02-10 23:12 ` [Qemu-devel] [PATCH 10/17] lm32: uart model Michael Walle
2011-02-11 21:16 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 11/17] lm32: system control model Michael Walle
2011-02-11 21:03 ` Blue Swirl
2011-02-11 22:35 ` Michael Walle
2011-02-12 7:54 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 12/17] lm32: support for creating device tree Michael Walle
2011-02-11 20:52 ` Blue Swirl
2011-02-11 22:40 ` Michael Walle
2011-02-12 7:56 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 13/17] lm32: EVR32 and uclinux BSP Michael Walle
2011-02-11 20:47 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 14/17] lm32: todo and documentation Michael Walle
2011-02-11 20:41 ` Blue Swirl
2011-02-11 22:45 ` Michael Walle
2011-02-12 8:00 ` Blue Swirl
2011-02-10 23:12 ` [Qemu-devel] [PATCH 15/17] lm32: opcode testsuite Michael Walle
2011-02-10 23:12 ` [Qemu-devel] [PATCH 16/17] Add lm32 target to configure Michael Walle
2011-02-10 23:12 ` [Qemu-devel] [PATCH 17/17] MAINTAINERS: add LatticeMico32 maintainer Michael Walle
2011-02-11 9:48 ` [Qemu-devel] Re: [PATCH 00/17 v2] LatticeMico32 target Edgar E. Iglesias
-- strict thread matches above, loose matches on Subject: below --
2011-02-17 22:45 [Qemu-devel] [PATCH 00/17 v3] " Michael Walle
2011-02-17 22:45 ` [Qemu-devel] [PATCH 09/17] lm32: timer model Michael Walle
2011-01-31 0:30 [Qemu-devel] [PATCH 00/17] LatticeMico32 target Michael Walle
2011-01-31 0:30 ` [Qemu-devel] [PATCH 09/17] lm32: timer model Michael Walle
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=AANLkTikzhBcijY9cJk_eHi2YL-QLdQyUJkYRDwOzOmY7@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=agraf@suse.de \
--cc=edgar.iglesias@gmail.com \
--cc=michael@walle.cc \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).