[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071217002827.GG5692@elf.ucw.cz>
Date: Mon, 17 Dec 2007 01:28:27 +0100
From: Pavel Machek <pavel@....cz>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Ingo Molnar <mingo@...e.hu>, unlisted-recipients: no@...is.elte.hu,
To-header@...is.elte.hu, on@...is.elte.hu, "input <"@elvis.elte.hu,
; Rene Herman <rene.herman@...access.nl>,
Paul Rolland <rol@...917.net>,
"H. Peter Anvin" <hpa@...or.com>, Krzysztof Halasa <khc@...waw.pl>,
Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, rol@...be.net
Subject: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64
with MCP51 laptops
On Mon 2007-12-17 00:03:01, Alan Cox wrote:
> On Sun, 16 Dec 2007 22:26:33 +0100
> Pavel Machek <pavel@....cz> wrote:
>
> > On Fri 2007-12-14 15:33:28, Ingo Molnar wrote:
> > >
> > > * Alan Cox <alan@...rguk.ukuu.org.uk> wrote:
> > >
> > > > There is another reason we can't just do a dumb changeover - two
> > > > actually
> > > >
> > > > #1: Some drivers are using inb_p/outb_p in PCI cases which are going
> > > > #to cause PCI posting changes. Most are probably just wrong in the
> > > > #first place but they need hand checking
> > >
> > > hm, any intelligent way to force PCI posting? I guess not.
> > >
> > > here's a list of candidate drivers (match the out*_p() pattern and do
> > > pci)
> > >
> > > ./char/epca.c
> > > ./char/sonypi.c
> > > ./scsi/megaraid.c
> > > ./ide/pci/serverworks.c
> > > ./ide/pci/cmd640.c
> > > ./input/mouse/pc110pad.c
>
> You are missing some watchdogs at least ?
I snipped them, I only wanted to comment that pc110pad.c looks like
legitimate use of outb_p().
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists