Re: Weird PCI interrupt delivery problem (resolution, sort of)
- From: Craig Boston <craig@xxxxxxxxxxxxxx>
- Date: Tue, 24 Jan 2006 18:34:05 -0600
On Tue, Jan 24, 2006 at 10:43:49AM -0500, John Baldwin wrote:
> What if you do a read of the lapic before the write? Maybe doing 'x =
> lapic->eoi; lapic->eoi = 0;'?
Reading the lapic before the write has no effect.
Reading the lapic after the write makes it work.
Craig
_______________________________________________
freebsd-hackers@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Weird PCI interrupt delivery problem (resolution, sort of)
- From: John Baldwin
- Re: Weird PCI interrupt delivery problem (resolution, sort of)
- References:
- Weird PCI interrupt delivery problem (resolution, sort of)
- From: Craig Boston
- Re: Weird PCI interrupt delivery problem (resolution, sort of)
- From: John Baldwin
- Re: Weird PCI interrupt delivery problem (resolution, sort of)
- From: Craig Boston
- Re: Weird PCI interrupt delivery problem (resolution, sort of)
- From: John Baldwin
- Weird PCI interrupt delivery problem (resolution, sort of)
- Prev by Date: CPU/case/disk temperature sensors for Dell PowerEdge 2850
- Next by Date: KTR not working !!
- Previous by thread: Re: Weird PCI interrupt delivery problem (resolution, sort of)
- Next by thread: Re: Weird PCI interrupt delivery problem (resolution, sort of)
- Index(es):