<div dir="ltr"><br><div>Hi Greg,</div><div><br></div><div>You have misunderstood the question. That, too, because me being too brief.</div><div><br></div><div>What I tried to mean is NOT to test the syscall after the modified kernel is compiled and booted. That's easy.</div>
<div><br></div><div>To add the syscall to the kernel, one needs to drop a C code implementing the body of the call itself to some appropriate location of the kernel source tree. Isn't it so? I am doing that for the first time and want to be sure that the compilation, especially the includes work. Otherwise, the kernel compilation may throw an error midway, thereby wasting my time.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 4 June 2014 09:22, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com" target="_blank">greg@kroah.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Jun 04, 2014 at 08:52:31AM +0530, Dipanjan Das wrote:<br>
><br>
> Hi,<br>
><br>
> While adding a syscall, how do I test the syscall code itself? If I simply try<br>
> to compile the C file individually, will the compiler be able find the<br>
> includes?<br>
<br>
Did you try:<br>
man 2 syscall<br>
<br>
greg k-h<br>
</blockquote></div><br></div>