public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: "David P. Reed" <dpreed@reed.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Dmitry Torokhov <dtor_core@ameritech.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: use explicit timing delay for pit accesses in kernel and pcspkr driver
Date: Mon, 18 Feb 2008 22:59:49 +0100	[thread overview]
Message-ID: <47B9FFD5.6040801@keyaccess.nl> (raw)
In-Reply-To: <47B9FC3A.2010508@zytor.com>

On 18-02-08 22:44, H. Peter Anvin wrote:
> Rene Herman wrote:
>>
>> I mean that before the linux kernel used a port 0x80 write as an I/O 
>> delay it used a short jump (two in a row actually...) as such and this 
>> was at the time that it actually ran on the old legacy stuff that is 
>> of most concern here.
>>
>> No, if I'm not mistaken, those two jumps are actually what the 
>> udelay() is going to do anyway as part of delay_loop() at that early 
>> stage so that even before loops_per_jiffy calibration, I believe we 
>> should still be okay.
>>
> 
> That doesn't make any sense at all.  The whole point why the two jumps 
> were obsoleted with the P5 (or even late P4, if I'm not mistaken) was 
> because they were utterly insufficient when the CPU ran at something 
> much higher than the external speed.

Yes, but generally not any P5+ system is going to need the PIT delay in the 
first place meaning it just doesn't matter. There were the VIA issues with 
the PIC but unless I missed it not with the PIT.

That's the point. It's fairly unclean to say udelay(2) and then not delay 
for 2 microseconds but you _have_ done the two short jumps meaning 386 and 
486 systems are okay and later systems were okay to start with.

Rene.

  reply	other threads:[~2008-02-18 21:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-18 18:58 [PATCH] x86: use explicit timing delay for pit accesses in kernel and pcspkr driver David P. Reed
2008-02-18 20:17 ` Alan Cox
2008-02-18 20:38 ` Rene Herman
2008-02-18 20:43   ` H. Peter Anvin
2008-02-18 21:04     ` Rene Herman
2008-02-18 21:05       ` Rene Herman
2008-02-18 21:44       ` H. Peter Anvin
2008-02-18 21:59         ` Rene Herman [this message]
2008-02-18 22:01           ` H. Peter Anvin
2008-02-18 22:07             ` Rene Herman
2008-02-18 22:32               ` Rene Herman
2008-02-18 22:44                 ` H. Peter Anvin
2008-02-20 12:06                   ` Rene Herman
2008-02-20 17:05                     ` H. Peter Anvin
2008-02-20 17:09                       ` Rene Herman
2008-02-20 20:13                         ` [linux-kernel] " David P. Reed
2008-02-21  6:21                           ` Rene Herman
2008-02-18 22:43               ` H. Peter Anvin
2008-02-19  9:46 ` Ingo Molnar

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=47B9FFD5.6040801@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dpreed@reed.com \
    --cc=dtor_core@ameritech.net \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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