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 <[email protected]> wrote:
> 
> > On Fri 2007-12-14 15:33:28, Ingo Molnar wrote:
> > > 
> > > * Alan Cox <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Ingo Molnar <[email protected]>

• References:
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "David P. Reed" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Alan Cox <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "David P. Reed" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "linux-os (Dick Johnson)" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "David P. Reed" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: "linux-os (Dick Johnson)" <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Alan Cox <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Ingo Molnar <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Pavel Machek <[email protected]>
  • Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
    • From: Alan Cox <[email protected]>

• Prev by Date: Re: [PATCH 4/8] unify paravirt parts of system.h
• Next by Date: Re: [RFC PATCH 08/12] PAT 64b: coherent mmap and sysfs bin ioctl
• Previous by thread: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
• Next by thread: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]