From: Thomas Hood <jdthood@mail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: 2.4.18-pre7 slow ... apm problem
Date: 28 Jan 2002 06:25:05 -0500 [thread overview]
Message-ID: <1012217107.746.5.camel@thanatos> (raw)
In-Reply-To: <E16V8oV-0004FV-00@the-village.bc.nu>
In-Reply-To: <E16V8oV-0004FV-00@the-village.bc.nu>
On Mon, 2002-01-28 at 05:14, Alan Cox wrote:
> Suppose vmware decides to switch between running Linux and its virtualised
> Windows OS. Can it do this during an interrupt - if so what ensures that
> vmware isnt switched to after we have done APM idle calls and slowed the
> CPU right down ?
>
> If so then I suspect vmware should be issuing APM cpu busy calls itself
Do you see a difference between VMware and other processes
in their susceptibility to this problem? If VMware runs
slowly because it gets scheduled in while the CPU is idle
and the apm driver fails to busyize the CPU, won't the same
thing happen for other processes? If so, then our idle
handling is fundamentally broken. If not, then what makes
VMware special?
next prev parent reply other threads:[~2002-01-28 11:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-28 0:15 2.4.18-pre7 slow ... apm problem Thomas Hood
2002-01-28 0:32 ` Alan Cox
2002-01-28 2:37 ` Thomas Hood
2002-01-28 10:14 ` Alan Cox
2002-01-28 11:25 ` Thomas Hood [this message]
2002-01-28 13:03 ` Stephan von Krawczynski
2002-01-28 13:18 ` Alan Cox
2002-01-28 16:19 ` Thomas Hood
2002-01-28 3:22 ` Thomas Hood
2002-01-28 20:11 ` Jeff Chua
2002-01-28 20:28 ` Thomas Hood
2002-01-28 22:20 ` Alan Cox
2002-01-29 12:36 ` Jeff Chua
2002-01-30 1:12 ` Thomas Hood
2002-01-30 9:22 ` Jeff Chua
2002-01-28 21:14 ` Thomas Hood
2002-01-28 21:17 ` Jeff Chua
2002-01-28 23:09 ` Stephan von Krawczynski
2002-01-29 13:01 ` Jeff Chua
-- strict thread matches above, loose matches on Subject: below --
2002-01-29 18:53 Petr Vandrovec
2002-01-29 22:47 ` Stephan von Krawczynski
2002-01-30 0:44 ` Jeff Chua
2002-01-30 5:50 ` Stephen Rothwell
2002-01-30 9:27 ` Jeff Chua
2002-02-01 13:20 ` Jeff Chua
2002-01-28 23:22 Petr Vandrovec
2002-01-27 10:08 Jeff Chua
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=1012217107.746.5.camel@thanatos \
--to=jdthood@mail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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