6 March 2009 5:04 PM
To: micro...@virginbroadband.com.au
Cc: Kernelnewbies
Subject: Re: About Kernel preemption and kernel mode stack
Hi!
On 12:15 Fri 06 Mar , micro...@virginbroadband.com.au wrote:
...
> In this case it's common to use co-operative scheduling. This means that
>
Hi!
On 12:15 Fri 06 Mar , micro...@virginbroadband.com.au wrote:
...
> In this case it's common to use co-operative scheduling. This means that
> when a task does not need further execution, it must relinquish control
> back to the scheduler. I personally find this a real pig to program like
>
Hi!
On 19:06 Thu 05 Mar , sahlot arvind wrote:
> Got it!.I have another question:
> What are the exact steps when I press a key? Assume only one shell is
> running and I press 'd':
> 1. processor will get interrupted.
> 2. it will jump to the common interrupt handler
> 3. common interrupt han
2009/3/6
> > Anyway in any case how does shell get the 'd' or anything from the
> > keyboard?
> > What are the exact steps?
>
> I'm a Linux kernel newbie, (although I have heavy embedded MCU coding
> background) but I can help with the general approach of this scenario.
> First, it's important to
> Anyway in any case how does shell get the 'd' or anything from the
> keyboard?
> What are the exact steps?
I'm a Linux kernel newbie, (although I have heavy embedded MCU coding
background) but I can help with the general approach of this scenario.
First, it's important to note that any interrupt
Got it!.I have another question:
What are the exact steps when I press a key? Assume only one shell is
running and I press 'd':
1. processor will get interrupted.
2. it will jump to the common interrupt handler
3. common interrupt handler will save the context of shell and will call the
appropriat
Hi!
On 13:00 Thu 05 Mar , Pranav Peshwe wrote:
> On Thu, Mar 5, 2009 at 11:48 AM, Michael Blizek <
> mic...@michaelblizek.twilightparadox.com> wrote:
>
> > Hi!
> >
> > On 23:47 Wed 04 Mar , sahlot arvind wrote:
> > > Hi All,
...
> > > 2. If kernel is not preemptible then do we really ne
On Thu, Mar 5, 2009 at 11:48 AM, Michael Blizek <
mic...@michaelblizek.twilightparadox.com> wrote:
> Hi!
>
> On 23:47 Wed 04 Mar , sahlot arvind wrote:
> > Hi All,
> >
> > Just had couple of questions:
> >
> > 1. kernel is preemptible if we are running in kernel mode and not holding
> > any lo
Hi!
On 23:47 Wed 04 Mar , sahlot arvind wrote:
> Hi All,
>
> Just had couple of questions:
>
> 1. kernel is preemptible if we are running in kernel mode and not holding
> any lock. What if we preempt the kernel even when we are holding lock?
> Assuming process A and B are trying to execute t
Hi All,
Just had couple of questions:
1. kernel is preemptible if we are running in kernel mode and not holding
any lock. What if we preempt the kernel even when we are holding lock?
Assuming process A and B are trying to execute the same kernel path. So what
if something like this happens:
A get
10 matches
Mail list logo
