All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan C. Kleinsorge" <wobble@gmx.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Timed wait/sleep
Date: Sat, 07 Jul 2007 12:29:18 +0200	[thread overview]
Message-ID: <468F6AFE.20806@gmx.de> (raw)
In-Reply-To: <8c0c43de0707061521s25f22cd8t38f3299b56604e94@mail.gmail.com>

For i/o delays on x86, Linux uses a sequence of outp(0x80). 0x80 is
usually unsed.
One to three times should be quite sufficient.

Jan

ex Roman wrote:
> On 06 Jul 2007 17:04:19 -0500, Haudy Kazemi <kaze0010@umn.edu> wrote:
>> On Jul 6 2007, Alex Roman wrote:
>> I'd avoid straight loops...with those you run into processor speed
>> issues...runs too fast on new CPUs, runs too slow on old hardware. Of
>> course I guess you could calibrate some straight loops to the RTC,
>> and then
>> use the loops rather than polling the RTC periodically, but I don't
>> think
>> the extra level of complication would provide any real benefit.
>
> Yes, I am reluctant to use loops for that reason.
>
> I could definitely do a simple read RTC in a loop until the time
> difference from when I started the loop is what I want it to be...
>
> I'll try to get that working, but I am open to other suggestions as well!
>
>
> Thanks!
>




  reply	other threads:[~2007-07-07 10:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 21:57 Timed wait/sleep Alex Roman
2007-07-06 22:04 ` Haudy Kazemi
2007-07-06 22:21   ` Alex Roman
2007-07-07 10:29     ` Jan C. Kleinsorge [this message]
2007-07-22 13:48 ` Marco Gerards
2007-07-22 21:38   ` Alex Roman
2007-07-22 22:33     ` Jeroen Dekkers
  -- strict thread matches above, loose matches on Subject: below --
2007-07-07  6:47 Amin Azez

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=468F6AFE.20806@gmx.de \
    --to=wobble@gmx.de \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.