Date: Mon, 19 Jan 2015 18:15:49 +0100 From: Svatopluk Kraus <onwahe@gmail.com> To: freebsd-arm@freebsd.org Subject: Re: interrupt framework Message-ID: <CAFHCsPWyEAGnSErw_24FEENw_Luce-puRFekGe74=PvvofYXfQ@mail.gmail.com> In-Reply-To: <54BC49CB.4020504@freebsd.org> References: <CAFHCsPX5kG_v-F-cjpyMQsT_b386eok=mqWW0%2BEUb_4-_1Otnw@mail.gmail.com> <54B7EB67.6010702@freebsd.org> <20150118203021.3ecac737@bender.lan> <54BC49CB.4020504@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Considering that our work could be the framework and even for more archs, I like to ask what should be optimalized? (1) The framework is based on an interrupt source structure. Should it be transparent for controllers with a set of interface functions or should it be public for them? (2) We are using KOBJ methods as controller's interface now. However, there is a table of functions used in i386 arch. (3) Could be the new INTR_SOLO method how to handle an interrupt useful for other archs? If so, it will be nice to try to import it somehow to MI interrupt event in kern_intr.c. For example, there is a timer interrupt in i386 arch which is handled without MI interrupt framework to be really fast. Svata
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFHCsPWyEAGnSErw_24FEENw_Luce-puRFekGe74=PvvofYXfQ>