Date: Thu, 18 Sep 2008 00:39:41 +0400 (MSD) From: "Andrew N. Below" <defan@zenon.net> To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org Subject: Re: amd64, COMPAT_IA32 & syscall diverts Message-ID: <alpine.LNX.1.10.0809180032200.19223@defan.zenon.net> In-Reply-To: <48D14CB8.5080002@elischer.org> References: <046601c918cc$786cc8c0$970da8c0@jam.zenon.net> <48D123DD.2030701@elischer.org> <064901c918e2$803df770$970da8c0@jam.zenon.net> <48D14CB8.5080002@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 17 Sep 2008, Julian Elischer wrote: >>>> Seems like these calls are made bypassing >>>> our kernel module. >>> x86 binaries use a separate syscall table, so you need to patch >>> both tables. >> Where can I find something about that table? > the compat stuff is in /sys/compat/ia32/ > So I would start there and follow the logic. Thanks, extern struct sysent freebsd32_sysent[] is what I need. The final problem I have to solve is to find a way to determine where exactly syscall called from (64bit or compat)... -- Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.1.10.0809180032200.19223>