From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: 452efb didn't show up in the list
Date: Thu, 1 Apr 2010 22:22:53 +0200 [thread overview]
Message-ID: <m2mfb8d4f71004011322n1a6f803am81e826d56a7adce2@mail.gmail.com> (raw)
In-Reply-To: <j2wf43fc5581004011259n1684007eqdb809e8cb1ad2d12@mail.gmail.com>
2010/4/1 Blue Swirl <blauwirbel@gmail.com>:
> Which list?
This mailing list?
> On 4/1/10, Artyom Tarasenko <atar4qemu@googlemail.com> wrote:
>> and looks wrong or incomplete to me:
>>
>> >According to Sun4M System Architecture Manual chapter 5.3.2, a limit
>> >of 0 will not generate interrupts.
>>
>> This is indeed correct, but the chapter 5.3.2 also explains why:
>>
>> "Setting the limit register to 0 allows the counter to free run. Since the
>> timer always resets to a value of 500 nS after reaching maximum count,
>> there is no match and no interrupts are generated."
>>
>> The part about 500 nS (0x00000200 in the counter register) and
>> no match seems to be not addressed.
>
> The 500ns offset part could be addressed by making the timer period
> shorter by 1 tick. I doubt such a change would have any visible
> difference with QEMU, except that tick count of 0 should never appear
> in the counter but it may now.
as well as all the other values between 0 and 0x200. But it's less
important I guess.
> For the no match part, t->reached should not be set if t->limit == 0.
--
Regards,
Artyom Tarasenko
solaris/sparc under qemu blog: http://tyom.blogspot.com/
next prev parent reply other threads:[~2010-04-01 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 19:41 [Qemu-devel] 452efb didn't show up in the list Artyom Tarasenko
2010-04-01 19:59 ` [Qemu-devel] " Blue Swirl
2010-04-01 20:22 ` Artyom Tarasenko [this message]
2010-04-01 20:31 ` Blue Swirl
2010-04-02 16:18 ` Blue Swirl
2010-04-02 20:32 ` Artyom Tarasenko
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=m2mfb8d4f71004011322n1a6f803am81e826d56a7adce2@mail.gmail.com \
--to=atar4qemu@googlemail.com \
--cc=blauwirbel@gmail.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).