From: John Levon <levon@movementarian.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
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 with viakt8235 Southbridge)
Date: Fri, 15 Nov 2002 01:21:11 +0000 [thread overview]
Message-ID: <20021115012111.GB15619@compsoc.man.ac.uk> (raw)
In-Reply-To: <3DD4481F.72627800@digeo.com>
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.
next prev parent reply other threads:[~2002-11-15 1:14 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 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:18 ` Jeff Garzik
2002-11-15 1:25 ` Yet another IO-APIC problem (was Re: via-rhine weirdness withviakt8235 Southbridge) Andrew Morton
2002-11-15 1:21 ` John Levon [this message]
2002-11-15 10:09 ` via-rhine weirdness with via kt8235 Southbridge Erik Hensema
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=20021115012111.GB15619@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=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
Powered by JetHome