Re: [PATCH] x86: provide a DMI based port 0x80 I/O delay override

[Robert Hancock]

Ingo Molnar wrote:
> * Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote:
>
> > > i dont get your last point. Firstly, we do an "outb $0x80" not an 
> > > inb.
> > outb not inb sorry yes
> >
> > > Secondly, outb $0x80 has no PCI posting side-effects AFAICS. 
> > > Thirdly,
> > It does. The last mmio write cycle to the bridge gets pushed out 
> > before the 0x80 cycle goes to the PCI bridge, times out and goes to 
> > the LPC bus.
>
> ok. Is it more of a "gets flushed due to timing out", or a 
> specified-for-sure POST flushing property of all out 0x80 cycles going 
> to the PCI bridge? I thought PCI posting policy is up to the CPU, it can 
> delay PCI space writes arbitrarily (within reasonable timeouts) as long 
> as no read is done from the _same_ IO space address. Note that the port 
> 0x80 cycle is neither a read, nor for the same address.

There's no guarantee in the spec that any IO access will flush pending 
MMIO writes. However, I suspect in the majority of implementations 
(perhaps all), it indeed does.

--
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@xxxxxxxxxxxxx
Home Page: http://www.roberthancock.com/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/