On Fri, 2010-01-15 at 17:24 -0800, Daniel (Youngwhan) Song wrote:
> I am reading "Understanding the Linux Kernel" in chapter 3 of
> describing process, and trying to understand the terms of three of
> Process, Lightweight Process and Thread.
>
> Please, confirm if my understanding is correct.
>
>
On Thu, 2010-01-14 at 17:48 -0800, Daniel (Youngwhan) Song wrote:
> Hi,
>
> Could somebody help me to understand the reason why the linux kernel
> does not allow the access to a file in the device driver? For example,
> for debugging purpose, if a device driver want to log some data in a
> file by
On Mon, 2010-01-11 at 15:01 +0530, Pete wrote:
> After going through this thread, I just tried out the following simple
> code:
>
> int main (void) {
>
> int pid;
>
> int *testVar = (int *) malloc (sizeof (int));
>
> *testVar = 10;
>
> printf ("%d [%d] Main \n", *testVar, testVar);
>
> pid=
On Mon, 2009-12-07 at 05:36 -0500, Robert P. J. Day wrote:
> something i'm reading claims that softirqs are used directly (that
> is, not simply to support tasklets) in only the networking and block
> devices subsystems. anyone know offhand any other places they're
> used? i can run a grep shortl
On Sun, 2009-11-15 at 17:26 -0800, Daniel (Youngwhan) Song wrote:
> Hi,
>
> I am just curious that if it is possible to launch user application,
> say, "ls" or "ps", in kernel space.
>
Following facilitates calling a user space function from a kernel
module:
int call_usermodehelper(char *path,
On Wed, 2009-10-21 at 11:09 +0530, Siddu wrote:
>
>
> On Wed, Oct 21, 2009 at 8:32 AM, Rick Brown
> wrote:
> Hi,
>
> Firstly, I'm trying to understand what exactly characterizes a
> procesor or an operating system as 32bit / 64 bit. I've read
> that it
>
> >
> > Lastly, is it allowable to schedule / sleep immediately after a call
> > to preempt_disable()?
>
> No I guess kernel will panic with some error like , "scheduling while
> in Atomic Context".
Sorry, I somehow missed out reading this. Can you let me know why its
not possible to schedule wi
> Firstly, Does preempt_disable() disable the preemption on all the
> processors or on just the local processor?
Only on the local cpu. This is for disabling preemption and protecting your
critical section
for per-cpu kernel space process context data.
> Lastly, is it allowable to schedule / sle
> BTW, ptrace is about when the process to be debugged is started from
> within gdb process. PArent process debugging the child process.
>
> How does gdb attach to a process that it has not started, in other
> words, how does it attach to a process that is not its child?
While 'gdb attach' tells
> module for every filesytem. I feel looking at the codes may help me
> appreciate the filesystems better. I searched the kernel tree and even
> googled for such code, but I feel I am yet not proficient enough to
> get anything. Hope you guys can help me out.
To start off, I would suggest the run
> I need to do lot of small allocations (around 70-80 bytes) from a
> critical region
> while holding a spinlock. Total number of such allocation could go
> upto tens of
> thousands in few hours. So all these allocations use GFP_ATOMIC flag
> instead of
> GFP_KERNEL. As per my understanding, GFP_A
On Wed, 2009-09-23 at 23:28 -0400, CP YEH wrote:
> Hi,
>
> I am just wondering how the kernel manages user space stack for
> different threads.
>
> I tried to follow the code and noticed that if CLONE_VM is specified,
> the kernel simply points mm to parent's mm. I suppose pthread does
> specify
12 matches
Mail list logo
