kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: pranjas@gmail.com (Pranay Srivastava)
To: kernelnewbies@lists.kernelnewbies.org
Subject: system call
Date: Sat, 9 Apr 2016 20:04:56 +0530	[thread overview]
Message-ID: <CA+aCy1EmXaEsrNEA7wLkXercGZ7N4=M3Pav8-nSSraK7cNU_1A@mail.gmail.com> (raw)
In-Reply-To: <CAKfJ7KKBPzzimZjwLwMP1GrOp9e1huh9K0BgsBToy+Oe8G1iQg@mail.gmail.com>

On Sat, Apr 9, 2016 at 7:51 PM, Nitin Varyani <varyani.nitin1@gmail.com> wrote:
> I have a 64 bit machine
>

Before changing the source try to build, install and boot your kernel.
I'm sure there are some extra steps you might need to perform to boot your
compiled kernel. Which distro are you using? I used OpenSuse for this work.


> I am changing linux 3.5.4 source tree.
>
> I modified syscall_64.tbl
> I had put your code in linux_3.5.4/arch/x86/pks_first/pks_first_call.c
>
> Then, I created pks_first/Makefile
>
> Modified the arch/x86/Kbuild
>
> Modified include/linux/syscalls.h
>
>
> I ran "make menuconfig" and then simply exit.
>
> Then I ran
>
> "make"
>
> I saw that pks_first_call.o was created
>
> I then ran
>
> "make modules_install"
> "make install"
>
> After then I restarted my system and booted linux 3.5.4. But it was stuck
> half way.
>
> On Sat, Apr 9, 2016 at 7:39 PM, Pranay Srivastava <pranjas@gmail.com> wrote:
>>
>> Hi Nitin
>>
>> On Sat, Apr 9, 2016 at 5:03 PM, Nitin Varyani <varyani.nitin1@gmail.com>
>> wrote:
>> > Neither of the solution is working.
>> > @ Pranay: kernel is not booting after making the changes you have
>> > mentioned.
>> > somethings like
>> > "dropping to shell
>> > initramfs:"
>> > is displayed on booting.
>>
>> I don't think this is related to the changes you made. I would advise
>> you just build the sources for your
>> distro and try to get to boot the kernel you compiled. Perhaps some
>> steps you might have missed specific to your
>> distro?
>>
>> >
>> >
>> > On Thu, Apr 7, 2016 at 1:08 PM, Pranay Srivastava <pranjas@gmail.com>
>> > wrote:
>> >>
>> >> 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
>> >
>> >
>>
>>
>>
>> --
>>         ---P.K.S
>
>



-- 
        ---P.K.S

  reply	other threads:[~2016-04-09 14:34 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
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 [this message]
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+aCy1EmXaEsrNEA7wLkXercGZ7N4=M3Pav8-nSSraK7cNU_1A@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).