Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org, Thiemo Seufer <ths@networkno.de>
Subject: Re: [PATCH] Make c0_compare_int_usable more bullet proof
Date: Mon, 22 Oct 2007 10:31:39 +0100	[thread overview]
Message-ID: <20071022093139.GA5588@linux-mips.org> (raw)
In-Reply-To: <20071020.005445.75183929.anemo@mba.ocn.ne.jp>

On Sat, Oct 20, 2007 at 12:54:45AM +0900, Atsushi Nemoto wrote:

> Use write_c0_compare(read_c0_count()) to clear interrupt.
> And use delta value based on its speed for faster probing.

Hmm...  This one makes c0_compare_int_usable() fails when I run a malta
kernel on last week's qemu.

  Ralf

  reply	other threads:[~2007-10-22 12:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-19 15:54 [PATCH] Make c0_compare_int_usable more bullet proof Atsushi Nemoto
2007-10-22  9:31 ` Ralf Baechle [this message]
2007-10-22 14:37   ` Atsushi Nemoto
2007-10-22 16:12     ` Atsushi Nemoto
  -- strict thread matches above, loose matches on Subject: below --
2007-10-22 16:14 Atsushi Nemoto
2007-10-22 19:26 ` Ralf Baechle

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=20071022093139.GA5588@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.org \
    --cc=ths@networkno.de \
    /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