From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: mikpe@csd.uu.se
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
zwane@linuxpower.ca
Subject: Re: [PATCH][2.5] Honour dont_enable_local_apic flag
Date: 01 Jun 2003 19:52:15 -0400 [thread overview]
Message-ID: <1054511535.6676.85.camel@pc> (raw)
In-Reply-To: <200306012308.h51N8K6j001404@harpo.it.uu.se>
[-- Attachment #1: Type: text/plain, Size: 2011 bytes --]
On Sun, 2003-06-01 at 19:08, mikpe@csd.uu.se wrote:
>
> Details, please. What does `cat /proc/cpuinfo` say?
Oops. Sorry. Problem is that VMware just reports the underlying (host)
system's CPU, so it will vary from (real) machine to machine. So for
instance, both my host system and my VMware virtual machine running on
it report:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 4
model name : AMD Athlon(tm) Processor
stepping : 2
cpu MHz : 796.626
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr syscall mmxext 3dnowext 3dnow
bogomips : 1589.24
With the exception of the "apic" flag (and cpu MHz values and bogomips
values differ). The above is from the host system. The VMware virtual
system has the same flags minus the apic flag because the only way to
boot it such that I can get the /proc/cpuinfo is by using the nolapic
command arg in the patch I sent earlier.
> My intention here is that we should be able to detect
> this apparently broken "CPU" by its vendor/model and
> clear cpu_has_apic for it.
Not doable by CPU identification I don't think.
> Alternatively the no_apic label in detect_init_APIC()
> could clear cpu_has_apic.
Fair enough, but what would cause the code at the no_apic label to be
executed without any of the command line arg patches proposed? We could
use Zwane's __setup() for nolapic and instead of doing:
if (dont_enable_local_apic)
return -1;
in detect_init_APIC() we can do:
if (dont_enable_local_apic)
goto no_apic;
> Hmm, obviously a 2.4 kernel.
Yes indeed. This is for testing production systems, so I need stable
kernels.
b.
--
Brian J. Murrell <brian@interlinx.bc.ca>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-01 23:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-01 23:08 [PATCH][2.5] Honour dont_enable_local_apic flag mikpe
2003-06-01 23:52 ` Brian J. Murrell [this message]
2003-06-02 4:50 ` Zwane Mwaikambo
2003-06-02 13:46 ` Brian J. Murrell
2003-06-02 14:56 ` mikpe
2003-06-02 16:20 ` Zwane Mwaikambo
2003-06-02 17:30 ` Brian J. Murrell
-- strict thread matches above, loose matches on Subject: below --
2003-06-01 23:09 mikpe
2003-06-01 11:23 mikpe
2003-06-01 16:26 ` Brian J. Murrell
2003-06-01 17:25 ` Brian J. Murrell
2003-06-01 3:30 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=1054511535.6676.85.camel@pc \
--to=brian@interlinx.bc.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=zwane@linuxpower.ca \
/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