From: "Kasim Sinan Yildirim" <yildirim@bilmuh.ege.edu.tr>
To: linux-newbie@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Paging and system calls
Date: Mon, 28 Apr 2003 14:48:08 +0200 [thread overview]
Message-ID: <20030428124808.M37677@bilmuh.ege.edu.tr> (raw)
Hi,
I am working on a small kernel and i am examining the source code of the
linux.
Since every task has its own page tables, when task switching occurs, the
cr3 field of the TSS is put to the cr3 register which is page directory base
register.
İn my operating system, when a system call occurs, the user level code jumps
to system level code by changing its selectors to KernelCS and KernelDS. But
at this point, the cr3 register still points to the page directory of the
user process. So, the actual code that is pointed by kernel level page
directory is not equal to the user level page directory entry. As a result ,
the system fails.
How this problem is solved in Linux? Have you got any solution to my problem?
Thanks...
next reply other threads:[~2003-04-28 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 12:48 Kasim Sinan Yildirim [this message]
2003-04-28 13:14 ` Jamie Lokier
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=20030428124808.M37677@bilmuh.ege.edu.tr \
--to=yildirim@bilmuh.ege.edu.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-newbie@vger.kernel.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
all inboxes | Powered by JetHome®