From: Peter Chubb <peter.chubb@nicta.com.au>
To: Peter Crosthwaite <peter.crosthwaite@petalogix.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Peter Chubb <peter.chubb@nicta.com.au>,
Paul Brook <paul@codesourcery.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Subject: Re: [Qemu-devel] Broken Microblaze timer
Date: Fri, 15 Jun 2012 15:07:55 +1000 [thread overview]
Message-ID: <w4k3z9go2c.wl%peter@chubb.wattle.id.au> (raw)
In-Reply-To: <CAEgOgz5Ud9E-1HOyUyHe8yQLn0mkJ6nBnWW+8_zw8dKn+A+6uw@mail.gmail.com>
>>>>> "Peter" == Peter Crosthwaite <peter.crosthwaite@petalogix.com> writes:
Peter> So ptimer has safeguards against misuse in periodic mode but
Peter> not one-shot mode? This strikes me as inconsistent. I.E. for
Peter> one use case the safeguard is in ptimer, and the other in the
Peter> client device. I think if we are in the bussiness of putting
Peter> these safeguards in ptimer itself then it should be there for
Peter> all use cases yes? I.E. the fix for this is making sure
Peter> one-shot ptimer give the cpu a look in.
When a one-shot timer fires, it has to be reset by the CPU before
it'll fire again. So the CPU always gets a look in --- or ought to.
--
Dr Peter Chubb peter.chubb AT nicta.com.au
http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA
prev parent reply other threads:[~2012-06-15 5:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 2:29 [Qemu-devel] Broken Microblaze timer Peter Crosthwaite
2012-06-14 9:19 ` Paolo Bonzini
2012-06-14 22:39 ` Peter Chubb
2012-06-15 4:40 ` Peter Crosthwaite
2012-06-15 5:07 ` Peter Chubb [this message]
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=w4k3z9go2c.wl%peter@chubb.wattle.id.au \
--to=peter.chubb@nicta.com.au \
--cc=aliguori@us.ibm.com \
--cc=edgar.iglesias@gmail.com \
--cc=paul@codesourcery.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@petalogix.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).