From: Pavel Machek <pavel@ucw.cz>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
Jean Delvare <jdelvare@suse.de>,
LKML <linux-kernel@vger.kernel.org>, Tejun Heo <htejun@gmail.com>,
Tom Long Nguyen <tom.l.nguyen@intel.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: PCI MSI breaks when booting with nosmp
Date: Tue, 22 Apr 2008 23:25:48 +0200 [thread overview]
Message-ID: <20080422212548.GC6004@elf.ucw.cz> (raw)
In-Reply-To: <480CEEA2.1040106@firstfloor.org>
On Mon 2008-04-21 21:44:34, Andi Kleen wrote:
> Pavel Machek wrote:
> > On Mon 2008-04-21 20:45:05, Andi Kleen wrote:
> >> Jesse Barnes <jbarnes@virtuousgeek.org> writes:
> >>> Ok, I see this too on my desktop machine. It looks like we're not getting
> >>> interrupts setup correctly in the nosmp case. Still digging through to see
> >>> why though...
> >> NoSMP disables the io-apic and a lot of modern systems don't work
> >> without APIC.
> >
> > Are you sure? I still boot DOS on very recent boxes, and they seem to
> > work. How can PC-compatible machine require an APIC?
>
> The machine doesn't, but the drivers do. DOS likely doesn't use all
> hardware.
Should we be fixing drivers?
Do drivers even know? I'd expect core code in arch/x86 to shield
details of interrupt routing from them..
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-04-22 21:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 19:40 PCI MSI breaks when booting with nosmp Jean Delvare
2008-04-17 20:08 ` Jesse Barnes
2008-04-17 20:25 ` Jean Delvare
2008-04-21 17:43 ` Jesse Barnes
2008-04-21 18:45 ` Andi Kleen
2008-04-21 19:06 ` Jesse Barnes
2008-04-21 19:35 ` Jesse Barnes
2008-04-21 19:41 ` Andi Kleen
2008-04-21 19:43 ` Pavel Machek
2008-04-21 19:44 ` Andi Kleen
2008-04-22 21:25 ` Pavel Machek [this message]
2008-04-22 23:07 ` Jesse Barnes
2008-04-21 20:20 ` Jean Delvare
2008-04-21 20:40 ` Jesse Barnes
2008-04-21 20:46 ` Andi Kleen
2008-04-21 20:48 ` Jean Delvare
2008-04-21 21:09 ` Andi Kleen
2008-04-21 21:14 ` Jesse Barnes
2008-04-22 13:27 ` Jean Delvare
2008-04-22 15:50 ` Jesse Barnes
2008-04-23 14:38 ` Jean Delvare
2008-04-23 15:12 ` Jesse Barnes
2008-04-23 18:13 ` Maciej W. Rozycki
2008-04-23 18:23 ` Jesse Barnes
2008-04-23 18:32 ` Jesse Barnes
2008-04-23 18:32 ` Jean Delvare
2008-04-23 18:38 ` Maciej W. Rozycki
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=20080422212548.GC6004@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=andi@firstfloor.org \
--cc=htejun@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jdelvare@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=rdunlap@xenotime.net \
--cc=tom.l.nguyen@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.