From mboxrd@z Thu Jan 1 00:00:00 1970 From: bhat.srivatsa@gmail.com (Srivatsa Bhat) Date: Thu, 23 Feb 2012 16:42:51 +0530 Subject: Iterating through all the processes in a module In-Reply-To: <20120222145309.GA25682@kroah.com> References: <20120207191702.GA9172@kroah.com> <20120222145309.GA25682@kroah.com> Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org On Wed, Feb 22, 2012 at 8:23 PM, Greg KH wrote: > > A: No. > Q: Should I include quotations after my reply? > > http://daringfireball.net/2007/07/on_top > > On Wed, Feb 22, 2012 at 02:07:22PM +0100, Arokux B. wrote: > > Dear Greg, > > > > thank you very much for your quick reply. > > > > Having my code as a module I can trigger its execution (load a module) > > and disable it (unload a module). How can I achieve this if the code > > is inside the kernel? One possibility I see is adding an entry in the > > procfs. > > I don't see what procfs has to do with this, please explain. > > And as you said this was for "learning purposes", then just build it > into the kernel, there's no need for it to be a module. > > Heh, you can just put back the relevant parts of what commit c59923a15c12d2b3597af913bf234a0ef264a38b removed and then do what you want as a module, if it is for learning purposes :-) Regards, Srivatsa S. Bhat -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20120223/52b52959/attachment.html