From: pranjas@gmail.com (Pranay Srivastava)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system call
Date: Thu, 7 Apr 2016 13:08:21 +0530 [thread overview]
Message-ID: <CA+aCy1Eh1c0wG1FKwC9AfvW6G_Q=ouOexYeJKLwyvrAW63G5Cw@mail.gmail.com> (raw)
In-Reply-To: <CAKfJ7KKpQKt1OBv30KXVKjcGiMvWq-cGirLCoUwMbTo3-v6baA@mail.gmail.com>
Nitin
On Thu, Apr 7, 2016 at 11:53 AM, Nitin Varyani <varyani.nitin1@gmail.com> wrote:
>
> Hi,
> I want to implement a system call as explained in Linux kernel development by Robert Love.
>
> He does three things
> adding entry to entry.S
> adding entry to asm/unistd.h
> and adding the system call code to sched.c
>
>
> and then make + make install
>
> I do not want to implement for all architectures but only for my PC which is 64 bit. I am not able to locate files entry. S and unistd.h which he is telling in his tutorial.
> Please help me out to figure out the exact steps. Please also mention the linux kernel version I should use.
>
Please refer this. I wrote this quite a while back but should be good to go.
http://codewithkernel.blogspot.my/2014/06/adding-new-system-call-in-linux-x86-and.html
> Nitin
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
---P.K.S
next prev parent reply other threads:[~2016-04-07 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 6:23 system call Nitin Varyani
2016-04-07 6:30 ` Giedrius Statkevičius
2016-04-07 6:45 ` Sharath Chandra
2016-04-07 7:38 ` Pranay Srivastava [this message]
2016-04-09 11:33 ` Nitin Varyani
2016-04-09 14:09 ` Pranay Srivastava
2016-04-09 14:21 ` Nitin Varyani
2016-04-09 14:34 ` Pranay Srivastava
2016-04-09 14:41 ` Nitin Varyani
2016-04-09 14:46 ` Pranay Srivastava
-- strict thread matches above, loose matches on Subject: below --
2011-06-11 9:39 Venkateswarlu P
2011-06-11 9:58 ` Rajat Sharma
2011-06-11 17:59 ` Javier Martinez Canillas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+aCy1Eh1c0wG1FKwC9AfvW6G_Q=ouOexYeJKLwyvrAW63G5Cw@mail.gmail.com' \
--to=pranjas@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).