Date: Wed, 26 May 2010 15:23:51 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: Alexander Motin <mav@freebsd.org> Cc: Andriy Gapon <avg@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: Event timers Message-ID: <AANLkTilgbP3lW90lf0PFdjbn9wIuZTnDS4fcyb2Au7X9@mail.gmail.com> In-Reply-To: <4BFD7E35.9070901@FreeBSD.org> References: <4BFAA1F3.1070206@FreeBSD.org> <4BFAAA47.5060802@freebsd.org> <4BFAB0C5.1020002@FreeBSD.org> <4BFD7E35.9070901@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
2010/5/26 Alexander Motin <mav@freebsd.org>: > Alexander Motin wrote: >> Andriy Gapon wrote: >>> on 24/05/2010 18:57 Alexander Motin said the following: >>>> I have defined several points on that way: >>>> 1*. clean low-level timer drivers from unrelated stuff, >>>> 2*. make some common code machine-independent, >>>> 3. write common driver API for event timers (alike to one we have now >>>> for time counters) to make adding more drivers possible, >>>> 4. add support for HPET as event timer in addition to time counter, >>>> 5. add support for timers in one-shot mode (LAPIC and HPET). >>> I wonder how much you have progressed for 3,4,5. >> >> Not really much yet. Learned existing code and hardware specs, have some >> thought and ready to proceed. > > Here is first approach to 3: > http://people.freebsd.org/~mav/et.20100526.patch > , - created common API, heavily refactored attimer, atrtc and lapic > drivers, written simple and formal common code. Now it is possible to > use any one or two of these three drivers for either hardclock or > statclock by just changing weights or disabling them. Tested on i386, > should work on amd64, probably broken on XEN and pc98 for now. >From my (minimal) understanding of the timer issues in FreeBSD, restructuring in this area requires a bold, fearless developer: Thanks for taking this on Alexander! Are these proposed patches made available for user testing, or mainly for developer review purposes? Is that a dumb question? :) -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTilgbP3lW90lf0PFdjbn9wIuZTnDS4fcyb2Au7X9>