linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joseph A Knapka <jknapka@earthlink.net>
To: Sanket Rathi <sanket.rathi@cdac.ernet.in>
Cc: linux-mm@kvack.org
Subject: Re: How CPU(x86) resolve kernel address
Date: Fri, 05 Apr 2002 10:07:08 +0000	[thread overview]
Message-ID: <3CAD774C.3010908@earthlink.net> (raw)
In-Reply-To: <Pine.GSO.4.10.10204051648440.18364-100000@mailhub.cdac.ernet.in>

Sanket Rathi wrote:

> I read all about the memory management in linux. all thing are clear to me
> like there is 3GB space for user procee and 1GB for kernel and thats why
> kernel address always greater then 0xC0000000. But one thing is not clear
> that is for kernel address there is no page table,


Yes there is. Look for swapper_pg_dir. It maps physical address
N to virtual address PAGE_OFFSET+N.

> actually there is no
> need because this is one to one mapping to physical memory but who resolve
> kernel address to actual physical address how CPU(X86) perform this task
> because when we do DMA we have to give actual physical address by
> virt_to_phys() so what is the mechanism by which CPU translate kernel
> address into physical address ( Somewhere i heard that CPU ignore some of
> the upper bits of address if so then how much bits and why).


I don't think so. Kernel and user addresses all pass through
the virtual mapping mechanism. virt_to_phys() just subtracts
PAGE_OFFSET from the kernel virtual address to arrive at the
physical address

Cheers,


-- Joe
   Using open-source software: free.
   Pissing Bill Gates off: priceless.

--
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-mm.org/

  reply	other threads:[~2002-04-05 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-05 11:27 Sanket Rathi
2002-04-05 10:07 ` Joseph A Knapka [this message]
2002-04-05 17:06 ` Ravi
2002-04-07 21:00 ` Eric W. Biederman

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=3CAD774C.3010908@earthlink.net \
    --to=jknapka@earthlink.net \
    --cc=linux-mm@kvack.org \
    --cc=sanket.rathi@cdac.ernet.in \
    /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