2002-11-15 00:57:46

by Andrew Morton

[permalink] [raw]
Subject: Re: Yet another IO-APIC problem (was Re: via-rhine weirdness with viakt8235 Southbridge)

Jeff Garzik wrote:
>
> ...
> IMO we should just take out UP IOAPIC support in the kernel, or put a
> big fat warning in the kernel config _and_ at boot...
>

It would be nice to get it working, because oprofile needs it.

(Well, oprofile can use the rtc, but then it doesn't profile
ints-off code)


2002-11-15 01:08:46

by Christian Guggenberger

[permalink] [raw]
Subject: Re: Yet another IO-APIC problem (was Re: via-rhine weirdness with viakt8235 Southbridge)

On 15 Nov 2002 02:04:31 Andrew Morton wrote:
> Jeff Garzik wrote:
> >
> > ...
> > IMO we should just take out UP IOAPIC support in the kernel, or put a
> > big fat warning in the kernel config _and_ at boot...
> >
>
> It would be nice to get it working, because oprofile needs it.
>
> (Well, oprofile can use the rtc, but then it doesn't profile
> ints-off code)
>

so, is there anything I could do for you in that IO-APIC case ? Especially in
my via-rhine case? As I mentioned in my previous mail, would some via-diag,
mii-diag outputs (what options) be helpful for you?

Christian

2002-11-15 01:14:26

by John Levon

[permalink] [raw]
Subject: Re: Yet another IO-APIC problem (was Re: via-rhine weirdness with viakt8235 Southbridge)

On Thu, Nov 14, 2002 at 05:04:31PM -0800, Andrew Morton wrote:

> It would be nice to get it working, because oprofile needs it.

That's the local APIC (CONFIG_X86_UP_APIC) not IO-APIC
(CONFIG_X86_UP_IOAPIC). They should be separate, and it's been a while
since I've tested it, but CONFIG_X86_UP_IOAPIC=n should still work OK

regards
john
--
Khendon's Law: If the same point is made twice by the same person,
the thread is over.