Date: Fri, 11 Jun 2010 12:09:43 +0300 From: Alexander Motin <mav@FreeBSD.org> To: Kostik Belousov <kostikbel@gmail.com> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r208988 - in head/sys: kern sys Message-ID: <4C11FD57.2000400@FreeBSD.org> In-Reply-To: <20100611083137.GA2401@deviant.kiev.zoral.com.ua> References: <201006101614.o5AGE5Zh099383@svn.freebsd.org> <20100611083137.GA2401@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
Kostik Belousov wrote: > On Thu, Jun 10, 2010 at 04:14:05PM +0000, Alexander Motin wrote: >> Author: mav >> Date: Thu Jun 10 16:14:05 2010 >> New Revision: 208988 >> URL: http://svn.freebsd.org/changeset/base/208988 >> >> Log: >> Store interrupt trap frame into struct thread. It allows interrupt handler >> to obtain both trap frame and opaque argument submitted on registrction. >> After kernel and all drivers get used to it, legacy hack can be removed. >> >> Reviewed by: jhb@ > Just curious, why td_frame is not enough for your usage ? I believe td_frame > is currently set only by traps and syscalls, and copied on forks. I've seen that field, but I have no idea how it is used. I see a lot of usage places and not sure that none of them called inside interrupt filter. I didn't want to break something unexpected. If you sure - it is easy to change. -- Alexander Motin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C11FD57.2000400>