From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: local apic timer ints not working with vmware: nolocalapic
Date: Sat, 31 May 2003 00:41:26 -0400 [thread overview]
Message-ID: <pan.2003.05.31.04.41.25.903565@interlinx.bc.ca> (raw)
In-Reply-To: pan.2003.05.31.03.38.16.701826@interlinx.bc.ca
On Fri, 30 May 2003 23:38:16 -0400, Brian J. Murrell wrote:
>
> I will take another stab at all of this tomorrow to double-verify what I
> am saying here regarding the use of local APIC timer interrupts even if
> the local apic usage flag is set to disable (dont_enable_local_apic = 1).
Just to confirm now, I have modified Zwane's patch add another kernel arg,
[no]locapictimer, which deals with dont_use_local_apic_timer in the same
way his patch deals with the dont_enable_local_apic flag, and indeed, a
kernel booted with "nolapic" does hang in the APIC timer calibration
however a kernel booted with "nolocapictimer" does not.
Is it really valid to go and try to calibrate the APIC timer if it was
disabled by the user, or even DMI?
b.
next prev parent reply other threads:[~2003-05-31 4:28 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 ` local apic timer ints not working with vmware: nolocalapic brian
2003-05-28 17:42 ` 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 [this message]
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=pan.2003.05.31.04.41.25.903565@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