From: brian@interlinx.bc.ca
To: linux-kernel@vger.kernel.org
Subject: Re: local apic timer ints not working with vmware: nolocalapic
Date: Wed, 28 May 2003 13:34:33 -0400 [thread overview]
Message-ID: <20030528173432.GA21379@linux.interlinx.bc.ca> (raw)
In-Reply-To: <2C8EEAE5E5C@vcnet.vc.cvut.cz>
[-- Attachment #1: Type: text/plain, Size: 762 bytes --]
On Wed, May 28, 2003 at 11:56:29AM +0200, Petr Vandrovec wrote:
>
> Just get VMware 3 or 4
Unfortunately, I cannot currently afford to buy (outright -- there is
no upgrade path from 2 to 4) a newer version of VMware. Really, other
than this issue of the local APIC timer, I don't really need or care
to have a newer version of VMware anyway.
> - they (properly) emulate APIC timer and you'll
> get information that host bus is running at 66.xxxx MHz. With VMware 2
> you have to boot with noapic.
If only this worked. I tried noapic, but it still tries to use the
local APIC timer interrupts. noapic seems to only disable IO-APIC.
That is why I was "proposing" a new kernel command line arg,
"nolocalapic".
b.
--
Brian J. Murrell
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-28 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 9:56 local apic timer ints not working with vmware: nolocala Petr Vandrovec
2003-05-28 17:34 ` brian [this message]
2003-05-28 17:42 ` local apic timer ints not working with vmware: nolocalapic Zwane Mwaikambo
2003-05-30 22:14 ` Brian J. Murrell
2003-05-30 23:23 ` Zwane Mwaikambo
2003-05-31 3:38 ` Brian J. Murrell
2003-05-31 4:41 ` Brian J. Murrell
2003-05-31 6:50 ` Zwane Mwaikambo
2003-05-31 15:21 ` Brian J. Murrell
2003-06-03 11:47 ` Maciej W. Rozycki
2003-06-05 3:04 ` Zwane Mwaikambo
2003-06-05 12:19 ` Maciej W. Rozycki
2003-06-05 17:54 ` Zwane Mwaikambo
2003-06-09 11:57 ` Maciej W. Rozycki
2003-06-10 1:17 ` Zwane Mwaikambo
2003-06-10 11:20 ` Maciej W. Rozycki
2003-05-31 7:03 ` Zwane Mwaikambo
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=20030528173432.GA21379@linux.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox