From: ablacktshirt@gmail.com (walkerlala)
To: kernelnewbies@lists.kernelnewbies.org
Subject: can anyone tell me which function to call to pause the kernel
Date: Tue, 17 May 2016 20:29:12 +0800 [thread overview]
Message-ID: <573B0E98.8060602@gmail.com> (raw)
In-Reply-To: <CAGdaadbNni0YTnpfMUrTRFvph=2oSZYbi=j5uMraoPa1zTcf7w@mail.gmail.com>
On 2016?05?17? 19:41, Mulyadi Santosa wrote:
>
>
> On Mon, May 16, 2016 at 7:36 AM, walkerlala <ablacktshirt@gmail.com
> <mailto:ablacktshirt@gmail.com>> wrote:
>
> On 2016?05?16? 01:36, Mulyadi Santosa wrote:
>
>
>
> On Thu, May 12, 2016 at 9:55 PM, walkerlala
> <ablacktshirt at gmail.com <mailto:ablacktshirt@gmail.com>
> <mailto:ablacktshirt at gmail.com <mailto:ablacktshirt@gmail.com>>>
> wrote:
>
> I successfully insert some function into the kernel code
> and make it
> execute when the kernel start up, but I just can't make the
> kernel stop
> executing. Are there any functions which can pause the
> kernel so that I
> prompt the user, and let the user input a command(maybe a
> comment to
> display the current time. Something like a shell would do) and
> interact ?
> (I had checked the "sys_***" functions in this page:
> http://docs.cs.up.ac.za/programming/asm/derick_tut/syscalls.html
> but just can't find a proper one )
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> <mailto:Kernelnewbies@kernelnewbies.org>
> <mailto:Kernelnewbies@kernelnewbies.org
> <mailto:Kernelnewbies@kernelnewbies.org>>
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
> Hi...
>
> sounds like what kgdb does. But not sure if it is still
> maintained or not.
>
> btw, kernel can not be paused, actually. if you really need
> that, you
> need to run linux kernel inside virtual machine and pause the
> virtual
> machine. But doing that, you will also pause user space too :)
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com <http://the-hydra.blogspot.com>
> <http://the-hydra.blogspot.com>
> training: mulyaditraining.blogspot.com
> <http://mulyaditraining.blogspot.com>
> <http://mulyaditraining.blogspot.com>
>
>
> Hi, thanks for reply.
>
> I know using a debugger or virtual machine would help a little bit,
> but that's not interactive any more. What I want is just a
> shell-like "interactive" kernel (may be I am a little naive to think
> that ?)
>
> Why the kernel cannot be stopped ? I think, now that if the kernel
> can be interrupted, then why can't it be stopped by some mechanisms ?
>
> Regards,
>
>
>
> Hi...
>
> please add kernelnewbies to cc: list too next time :)
>
> Kernel can't be stopped, because it's actually servicing event mostly
> generated by hardware (interrupts etc) or user space (syscall etc). So
> unless you stop these two aspects to raise events, basically kernel will
> still do its works.
>
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com <http://the-hydra.blogspot.com>
> training: mulyaditraining.blogspot.com <http://mulyaditraining.blogspot.com>
Can I just disable interrupts from hardwares? I know that, at the very
beginning, the kernel disable interrupt for convenient. So I wonder
whether we can do thing like this.
Put it in another way:
when we "interact" with a Linux Desktop, there are also many programs
running underneath as daemons, but we can still do our own works without
even noting their existing. So I wonder, is there a similar way that we
can use to interact with the kernel (without using a debugger) ?
If there is, can you any one show me some examples ?
Thanks in advance
Regards,
next prev parent reply other threads:[~2016-05-17 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 14:55 can anyone tell me which function to call to pause the kernel walkerlala
2016-05-12 15:26 ` François
2016-05-15 17:36 ` Mulyadi Santosa
[not found] ` <57391618.7090506@gmail.com>
2016-05-17 11:41 ` Mulyadi Santosa
2016-05-17 12:29 ` walkerlala [this message]
2016-05-17 15:21 ` Valdis.Kletnieks at vt.edu
2016-05-18 4:53 ` walkerlala
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=573B0E98.8060602@gmail.com \
--to=ablacktshirt@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).