From: Andrew Morton <akpm@digeo.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Christian Guggenberger
<christian.guggenberger@physik.uni-regensburg.de>,
rl@hellgate.ch, linux-kernel@vger.kernel.org,
Mikael Pettersson <mikpe@csd.uu.se>,
mingo@redhat.com
Subject: Re: Yet another IO-APIC problem (was Re: via-rhine weirdness withviakt8235 Southbridge)
Date: Thu, 14 Nov 2002 17:25:08 -0800 [thread overview]
Message-ID: <3DD44CF4.6C28CF86@digeo.com> (raw)
In-Reply-To: 3DD44B4E.3030102@pobox.com
Jeff Garzik wrote:
>
> 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)
>
> I don't see it happening, when uniprocessor mobo vendors (a) don't wire
> it up, or (b) put buggy data in their MP tables... :(
>
OK. Actually, rtc-based profiling gives perfectly grand results for
profiling userspace, and those people who want to profile their
interrupt handlers presumably know where to buy a decent motherboard.
prev parent reply other threads:[~2002-11-15 1:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20021115002822.G6981@pc9391.uni-regensburg.de>
2002-11-15 0:17 ` via-rhine weirdness with via kt8235 Southbridge Christian Guggenberger
2002-11-15 10:09 ` Erik Hensema
2002-11-15 0:55 ` Yet another IO-APIC problem (was Re: via-rhine weirdness with via kt8235 Southbridge) Jeff Garzik
2002-11-15 1:04 ` Yet another IO-APIC problem (was Re: via-rhine weirdness with viakt8235 Southbridge) Andrew Morton
2002-11-15 1:15 ` Christian Guggenberger
2002-11-15 1:21 ` John Levon
2002-11-15 1:18 ` Jeff Garzik
2002-11-15 1:25 ` Andrew Morton [this message]
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=3DD44CF4.6C28CF86@digeo.com \
--to=akpm@digeo.com \
--cc=christian.guggenberger@physik.uni-regensburg.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=mingo@redhat.com \
--cc=rl@hellgate.ch \
/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