Date: Tue, 6 Dec 2005 15:15:17 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Ruslan Ermilov <ru@FreeBSD.org> Cc: sparc64@FreeBSD.org Subject: Re: [PATCH] Re: sparc64/sparc64/exception.S Message-ID: <20051206151517.K75892@newtrinity.zeist.de> In-Reply-To: <20051206140205.GD62078@ip.net.ua>; from ru@FreeBSD.org on Tue, Dec 06, 2005 at 04:02:05PM %2B0200 References: <20051205212539.GF76163@ip.net.ua> <20051206114249.GA62078@ip.net.ua> <20051206144128.J75892@newtrinity.zeist.de> <20051206140205.GD62078@ip.net.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 06, 2005 at 04:02:05PM +0200, Ruslan Ermilov wrote: > On Tue, Dec 06, 2005 at 02:41:35PM +0100, Marius Strobl wrote: > [...] > > One probably could get away with leaving the KTR_* offset macros > > in genassym.c and just removing those exporting KTR_CT* etc. > > from <sys/ktr.h> and extending the scope of #ifndef LOCORE in > > <sys/ktr.h> so it can be included in asm source. > > However, the problem of exporting the latter set of KTR_* macros > > to the asm version of ktr(4) isn't new so I'd just go for adding > > KTR_COMPILE to genassym.c as suggested before. If you really want > > to go the route of directly using <sys/ktr.h> in asm source > > something like the patch below probably is what you want to do > > (does technically the right thing, not sure about style). > > > It works (now for both GENERIC and LINT, that is without and > with KTR defined :-). Please commit! > Which variant? Just adding KTR_COMPILE to genassym.c or the changes to use <sys/ktr.h> in asm source directly? If the latter may I refer to them as reviewed by you? Marius -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051206151517.K75892>