From: Pavel Machek <pavel@suse.cz>
To: Tony Hoyle <tmh@magenta-netlogic.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ACPI slowdown...
Date: Sun, 11 Feb 2001 23:04:48 +0100 [thread overview]
Message-ID: <20010211230448.J3748@bug.ucw.cz> (raw)
In-Reply-To: <3A818BC4.7020007@magenta-netlogic.com> <3A81920A.90601@magenta-netlogic.com>
In-Reply-To: <3A81920A.90601@magenta-netlogic.com>; from Tony Hoyle on Wed, Feb 07, 2001 at 06:20:58PM +0000
Hi!
> Tony Hoyle wrote:
>
> I'm talking to myself :-)
>
> OK I see that safe_halt() will re-enable interrupts. However this is only
> called in S1. If your machine gets as far as S3 you have...
>
> for (;;) {
> unsigned long time;
> unsigned long diff;
>
> __cli();
> if (current->need_resched)
> goto out;
> if (acpi_bm_activity())
> goto sleep2;
>
> time = acpi_read_pm_timer();
> inb(acpi_pblk + ACPI_P_LVL3);
> /* Dummy read, force synchronization with the PMU */
> acpi_read_pm_timer();
> diff = acpi_compare_pm_timers(time, acpi_read_pm_timer());
>
> __sti();
> if (diff < acpi_c3_exit_latency)
> goto sleep2;
> }
>
> There is no halt here... the interrupts are enabled for only a couple of
> instructions (one comparison and a jump) before being disabled again.
> It seems to me if the computer gets into S3 it'll effectively die until
> some kind of busmaster device wakes it up (DMA?).
No.
If interrupts come in cli-ed section, it will be postponed until
sti. It then comes, and sets need_resched and recovers.
Pavel
--
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-12 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 17:54 ACPI slowdown Tony Hoyle
2001-02-07 18:20 ` Tony Hoyle
2001-02-11 22:04 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-07 19:34 Grover, Andrew
2001-02-08 0:23 ` Tony Hoyle
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=20010211230448.J3748@bug.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tmh@magenta-netlogic.com \
/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