Date: Fri, 16 Jan 2015 09:19:13 -0700 From: Ian Lepore <ian@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arm@freebsd.org Subject: Re: interrupt framework Message-ID: <1421425153.14601.289.camel@freebsd.org> In-Reply-To: <6E33C7B5-F784-4604-9F09-9FEDB1EFBE56@bsdimp.com> References: <CAFHCsPX5kG_v-F-cjpyMQsT_b386eok=mqWW0%2BEUb_4-_1Otnw@mail.gmail.com> <20150115192624.122066dd@bender.lan> <CAFHCsPW5q=jMsehuYro7V5g56pMXK1tENP-_ibpg0q76LLWxJQ@mail.gmail.com> <20150116120315.7f343f66@bender.lan> <6E33C7B5-F784-4604-9F09-9FEDB1EFBE56@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2015-01-16 at 08:34 -0700, Warner Losh wrote: > > On Jan 16, 2015, at 5:03 AM, Andrew Turner <andrew@fubar.geek.nz> wro= te: > >=20 > > On Fri, 16 Jan 2015 12:44:22 +0100 > > Svatopluk Kraus <onwahe@gmail.com> wrote: > > ... > >> It's just a few things from quick look now which are different in ou= r > >> design. However, my intention is not read our code on behalf of you.= I > >> still think that our design is more general mainly and can serve for > >> interrupt controllers better. > >=20 > > I was asking on the differences as I'm already in the process of > > importing the arm_intrng project branch as I need something like it o= n > > arm64. It is also based on the same code from Jakub and Ian, I haven'= t > > looked at changing the design, just cleaning up the code to import in= to > > head. > >=20 > > I would be happy to merge your code instead, along with my existing > > cleanups, however I would need to know why I should spend time on it = as > > opposed to the current development branch. If we do decide to with yo= ur > > change I would like to import it into the arm_intrng project branch > > first to assist the import into head. >=20 > My first look at Svatopluk=A2s code and summaries, on its surface it se= ems > to be a simpler, more generalized and more effective design than intern. > It avoids some additional overhead that=A2s always troubled me about in= tern > that I=A2ve not had the time to make good suggestions to overcome. It l= ooks > (again on its surface) easier to bring to all the architectures as well. >=20 > I haven=A2t tried to use the code so I can=A2t comment on its stability= . So of course > I can=A2t measure the differences in interrupt latencies between the tw= o. Both of > these factors would be the kind of data that would help drive the decis= ion of which > one to adapt. >=20 > Warner I haven't looked at Svata's work recently, but in general he started with the same sources that are now in the intrng branch and finished work I was in the middle of (redoing IPI stuff) when I had to set it aside. Based on other work done recently by Svata and Michal, I can only imagine that they've improved on Jakub's and my earlier effort. My main concern for importing anything (Svata's version or the current intrng branch) is for the Marvell code. It's the one that's a bit different than other modern arm systems, for example it's the reason we had the somewhat strange design for handling IPIs in the current code. Unfortunately, I think none of us have hardare for testing except the folks at Semihalf. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1421425153.14601.289.camel>