qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: edgar.iglesias@gmail.com
To: qemu-devel@nongnu.org
Cc: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>, aurelien@aurel32.net
Subject: [Qemu-devel] [PATCH 0/3] mips: Handle late r4k timers
Date: Tue, 18 Jan 2011 00:29:39 +0100	[thread overview]
Message-ID: <1295306982-29629-1-git-send-email-edgar.iglesias@gmail.com> (raw)

From: Edgar E. Iglesias <edgar.iglesias@gmail.com>

Linux runs a test to check if the internal r4k timer is usable prior
to enabling it. The test basically starts a timer, repeatedly
compares cp0_count with cp0_compare and finally when the
timer should have hit it verifies that the irq line is asserted.
Depending on host timing, qemu may fail this test. On my x86_64 host,
we basically always fail it.

The following set of patches makes qemu pass the test reliably.

Edgar E. Iglesias (3):
  mips: Break TBs after mfc0_count
  mips: Break out cpu_mips_timer_expire
  mips: Expire late timers when reading cp0_count

 hw/mips_timer.c         |   43 +++++++++++++++++++++++++++++--------------
 target-mips/translate.c |    4 +++-
 2 files changed, 32 insertions(+), 15 deletions(-)

-- 
1.7.2.2

             reply	other threads:[~2011-01-17 23:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 23:29 edgar.iglesias [this message]
2011-01-17 23:29 ` [Qemu-devel] [PATCH 1/3] mips: Break TBs after mfc0_count edgar.iglesias
2011-01-18 10:34   ` Aurelien Jarno
2011-01-18 10:43     ` Edgar E. Iglesias
2011-01-18 11:50     ` Edgar E. Iglesias
2011-01-17 23:29 ` [Qemu-devel] [PATCH 2/3] mips: Break out cpu_mips_timer_expire edgar.iglesias
2011-01-18 10:35   ` [Qemu-devel] " Aurelien Jarno
2011-01-17 23:29 ` [Qemu-devel] [PATCH 3/3] mips: Expire late timers when reading cp0_count edgar.iglesias
2011-01-18  0:33   ` [Qemu-devel] " Edgar E. Iglesias
2011-01-18 10:36     ` Aurelien Jarno
2011-01-18 10:41       ` Edgar E. Iglesias
2011-01-18 10:52         ` Aurelien Jarno

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=1295306982-29629-1-git-send-email-edgar.iglesias@gmail.com \
    --to=edgar.iglesias@gmail.com \
    --cc=aurelien@aurel32.net \
    --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).