From: Amol Mohite <amol@m-net.arbornet.org>
To: linux-mm@kvack.org
Subject: Somw questions [ MAYBE OFFTOPIC ]
Date: Thu, 1 Apr 1999 04:16:51 -0500 (EST) [thread overview]
Message-ID: <Pine.BSI.3.96.990401041607.28014A-100000@m-net.arbornet.org> (raw)
Hi!
These might be newbie like qs., but I would really appreciate it if anyone
could answer them.
1) How does the processor notify the OS of a pagefault ? or a null pointer
exception ?
Now null pointer exception I know, is done using the expand down
attribute in descriptor. However, when the processor gp faults, how does
it know it is a null pointer exception ?
Where does it store the program counter ?
2) How are the following exceptions handled ;
TLB Refill
TLB Invalid
TLB Modify ?
3) How does the processor differentiate between entries (PTE) in the TLB
belonging to different processes ? Is it a bit in this ?
4) Why is the vm_area_structs maintained as a circular list, AVL tree and
as a doubly linked list ?
Why an AVL tree ? Any specific reason ?
5) What is the difference between SIGSEGV and a SIGBUS ?
6) How does the processor signal memory access inan illegal way (i.e.
trying write access to memory when this is not allowed )
7) How does linux handle malloc function ?
I would really appreciate it if anyone could answer these.
Please cc any answers to me as I am not on this list.
Thanks a lot.
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next reply other threads:[~1999-04-01 9:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-01 9:16 Amol Mohite [this message]
1999-04-02 9:35 ` ralf
1999-04-02 18:56 ` Chris Atenasio
1999-04-05 9:12 ` Amol Mohite
1999-04-06 10:55 ` ralf
1999-04-06 22:51 ` Stephen C. Tweedie
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=Pine.BSI.3.96.990401041607.28014A-100000@m-net.arbornet.org \
--to=amol@m-net.arbornet.org \
--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