Date: Sun, 16 Mar 2008 14:52:59 -0400 From: Andrew Gallatin <gallatin@cs.duke.edu> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/amd64/amd64 intr_machdep.c src/sys/amd64/include intr_machdep.h src/sys/arm/arm intr.c src/sys/i386/i386 intr_machdep.c src/sys/i386/include intr_machdep.h src/sys/ia64/ia64 interrupt.c src/sys/kern kern_intr.c ... Message-ID: <20080316145259.A37148@grasshopper.cs.duke.edu> In-Reply-To: <200803141941.m2EJfmL2020579@repoman.freebsd.org>; from jhb@FreeBSD.org on Fri, Mar 14, 2008 at 07:41:25PM %2B0000 References: <200803141941.m2EJfmL2020579@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin [jhb@FreeBSD.org] wrote: > MI code can currently (ab)use this by doing: > > intr_bind(rman_get_start(irq_res), cpu); > > however, I plan to add a truly MI interface (probably a bus_bind_intr(9)) Thank you very much for this! Do you plan to add a generic adminstrative interface to bind interrupts, or may I add a driver specific sysctl to bind mxge's interrupts in mxge? If you plan to add a generic administrative interface, I think we also need to add a way for drivers to label their interrupts so that an administrator can differentiate between the different MSI-X vectors. Thanks again, Drew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080316145259.A37148>