Date: Sun, 10 Apr 2005 23:58:02 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Scott Long <scottl@samsco.org>, Doug White <dwhite@gumbysoft.com>, freebsd-current@freebsd.org Subject: Re: Potential source of interrupt aliasing Message-ID: <200504110658.j3B6w2nb048552@apollo.backplane.com> References: <20050406233405.O47071@carver.gumbysoft.com> <200504081656.51917.jhb@FreeBSD.org> <20050410152946.W82708@carver.gumbysoft.com> <20050410172818.D82708@carver.gumbysoft.com> <200504110231.j3B2VOYr047361@apollo.backplane.com> <425A10DD.70500@samsco.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hmm. I can think of two solutions that avoid masking:
* Change the trigger mode from level to edge as a means of masking the
interrupt, then change it back to level triggered to unmask. This
would be done in the IO APIC.
* Change the delivery mode to low-priority for the interrupt that occured
and use the priority field to mask the interrupt to the cpu. This
would be done in the IO APIC with the LAPIC's TPR set appropriately.
These are off-the-cuff ideas. I don't know how easy or hard it would be
to implement (yet). But, certainly, changing the trigger mode can't be
any more complicated then messing around with the mask.
-Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200504110658.j3B6w2nb048552>