From: pnilesh@in.ibm.com
To: linux-mm@kvack.org
Subject: page fault in cli / sti safe or not
Date: Thu, 30 Mar 2000 10:07:09 +0530 [thread overview]
Message-ID: <CA2568B2.001A16BB.00@d73mta05.au.ibm.com> (raw)
I tried to page fault in cli () / sti() , but there was no deadlock. I
had perception that a deadlock would occur. However what might have I now
believe is that age fault always ocuur in any processes context , they will
panic in interrupt handler. So when a page fault occurs the page fault
handler is called and if the page is not found in the memory then a disk
read is scheduled the faulting process is put to sleep and schedule() is
called to run new process. The schedule () implicitly calls sti() and hence
there is no deadlock.
Please correct me if I am wrong.
Nilesh Patel
IBM Global Services India Pvt. Ltd.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next reply other threads:[~2000-03-30 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 4:37 pnilesh [this message]
2000-03-30 10:11 ` Andi Kleen
2000-03-30 21:15 ` Andrea Arcangeli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA2568B2.001A16BB.00@d73mta05.au.ibm.com \
--to=pnilesh@in.ibm.com \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox