Date: Sun, 11 Jul 2010 18:05:47 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: mdf@FreeBSD.org Cc: Dimitry Andric <dimitry@andric.com>, FreeBSD Hackers <hackers@freebsd.org> Subject: Re: strange problem with int64_t variables Message-ID: <4C39EBDB.2070804@FreeBSD.org> In-Reply-To: <AANLkTil_AEicC4sWD2M7-FwTl2OO5KKGk3P7TVynh2wP@mail.gmail.com> References: <4C39D92F.4050605@FreeBSD.org> <4C39DB09.6010808@andric.com> <4C39DBFF.2000307@FreeBSD.org> <AANLkTil_AEicC4sWD2M7-FwTl2OO5KKGk3P7TVynh2wP@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 2010.07.11. 17:33, mdf@FreeBSD.org escreveu:
> What does struct killjob_args look like?
>
It's just what make sysent generated:
+struct killjob_args {
+ char jid_l_[PADL_(__jid_t)]; __jid_t jid; char jid_r_[PADR_(__jid_t)];
+ char signal_l_[PADL_(int)]; int signal; char signal_r_[PADR_(int)];
+};
> Is this syscall defined in a module, or an addition to the kernel's
> syscalls.master?
>
In syscalls.master:
+ { AS(makenewjob_args), (sy_call_t *)makenewjob, AUE_NULL, NULL, 0, 0, 0, SY_THR_STATIC }, /* 523 = makenewjob */
+ { AS(killjob_args), (sy_call_t *)killjob, AUE_NULL, NULL, 0, 0, 0, SY_THR_STATIC }, /* 524 = killjob */
+ { 0, (sy_call_t *)getjid, AUE_NULL, NULL, 0, 0, 0, SY_THR_STATIC }, /* 525 = getjid */
+ { AS(getjlimit_args), (sy_call_t *)getjlimit, AUE_NULL, NULL, 0, 0, 0, SY_THR_STATIC }, /* 526 = getjlimit */
+ { AS(setjlimit_args), (sy_call_t *)setjlimit, AUE_NULL, NULL, 0, 0, 0, SY_THR_STATIC }, /* 527 = setjlimit */
> Is the user-space 32-bit or 64-bit? What about the kernel?
>
Both are 32-bit.
Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C39EBDB.2070804>