checkpointing a process using linux kernel programming
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
checkpointing a process using linux kernel programming
I am doing a project in linux kernel programming in which i want to checkpoint a process which is running at different interval of time and restoring it when needed please if any one has any idea about how to go about in this project please help me in doing my project.
Well, we don't want to tell you how to do it, but you know, Linux does this sort of thing on a grand scale when it "suspends" .. as when a laptop user closes the lid. That should give you some good code to study.
That might be a bit high-tech for here. But most such things are handled using kernel modules.
Also... "checkpoint / restart" is often something that an application does for itself, perhaps in response to a signal. The application saves its own state into some file, and knows how to restore that state later.
This approach has the advantage of being a "designed-in" characteristic of the application itself. The application, upon receiving the order to checkpoint, brings itself to a good stopping-place, then saves the checkpoint information. Should it then need to restart from that checkpoint, it once again brings itself to that same "good stopping-place," then restores (and validates!) the checkpoint image. It does this with the one advantage that the kernel does not have: the application knows very intimately what it is doing and why. The kernel doesn't. The kernel must view "every application" as basically a generic thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.