public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: john stultz <johnstul@us.ibm.com>
Cc: dino@in.ibm.com, linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: IO-APIC problem with 2.6.14-rt9
Date: Fri, 11 Nov 2005 09:20:04 +0100	[thread overview]
Message-ID: <20051111082004.GA20977@elte.hu> (raw)
In-Reply-To: <20051111073841.GA16009@elte.hu>


* Ingo Molnar <mingo@elte.hu> wrote:

> > Grumble. :( I was hoping to submit my tod code to Andrew tomorrow, but 
> > this might block that.
> 
> hm, ARCH_HAS_READ_CURRENT_TIMER is upstream already. I have not 
> measured the udelay thing upstream, but i thought it would have the 
> same issue.  Does the GTOD code impact this code?

ah, i see - you changed __delay to always be loop-based. That is quite 
incorrect.

but i think there is a generic way to solve this: just busy-poll 
->read_cycles(). I.e. move __delay into the generic code too. This means 
even more architecture-specific code would be consolidated, which is 
always good.

	Ingo

  reply	other threads:[~2005-11-11  8:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 20:02 IO-APIC problem with 2.6.14-rt9 Dinakar Guniguntala
2005-11-10 20:02 ` Ingo Molnar
2005-11-10 20:30   ` Dinakar Guniguntala
2005-11-10 20:29     ` john stultz
2005-11-10 20:55       ` Dinakar Guniguntala
2005-11-10 21:04       ` Ingo Molnar
2005-11-10 21:42         ` john stultz
2005-11-11  7:38           ` Ingo Molnar
2005-11-11  8:20             ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-12  2:25 Pallipadi, Venkatesh
2005-11-12  2:34 ` john stultz

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=20051111082004.GA20977@elte.hu \
    --to=mingo@elte.hu \
    --cc=dino@in.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.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