Re: what is the state of current after an mm_fault occurs?

jeff shia <tshxiayu@gmail.com> wrote:
>
> en,

Please see http://www.zip.com.au/~akpm/linux/patches/stuff/top-posting.txt

>  You mean in some pagefault place we do schedule()?

We used to - that should no longer be the case.  The TASK_RUNNING thing is
probably redundant now.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: what is the state of current after an mm_fault occurs?
  - From: Christoph Lameter <clameter@engr.sgi.com>

References:
- what is the state of current after an mm_fault occurs?
  - From: jeff shia <tshxiayu@gmail.com>
- Re: what is the state of current after an mm_fault occurs?
  - From: Andrew Morton <akpm@osdl.org>
- Re: what is the state of current after an mm_fault occurs?
  - From: jeff shia <tshxiayu@gmail.com>

Prev by Date: Re: [patch 00/21] mutex subsystem, -V14
Next by Date: Re: mouse issues in 2.6.15-rc5-mm series
Previous by thread: Re: what is the state of current after an mm_fault occurs?
Next by thread: Re: what is the state of current after an mm_fault occurs?
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]