From: mindentropy@gmail.com (mindentropy)
To: kernelnewbies@lists.kernelnewbies.org
Subject: VMA of processes and CPU registers
Date: Mon, 25 Apr 2011 22:08:56 +0530 [thread overview]
Message-ID: <201104252208.57103.mindentropy@gmail.com> (raw)
In-Reply-To: <BANLkTinGKS22MOWu4c-s6kiL9cN8N75mMg@mail.gmail.com>
On Monday 25 Apr 2011 2:25:10 pm Prabhu nath wrote:
> I understand about Linear virtual address and Physical address. How is the
> logical address generated ? Can you please explain.
>
> Thanks,
> Prabhu
>
> On Wed, Apr 20, 2011 at 9:33 PM, mindentropy <mindentropy@gmail.com> wrote:
> > On Wednesday 20 Apr 2011 4:31:08 pm limp wrote:
> > > Thanks a lot Dace and Vladimir for your replies.
> > >
> > > First of all, I forgot to mention that I am talking for x86
> > > architecture.
> > >
> > > > The CPU registers will contain the virtual addresses. Each and every
> > > > time that the CPU tries to access a virtual memory location, then the
> > > > address will be translated by the MMU into a physical address.
> > >
> > > So, AFAIU the translation to physical memory takes place *only* when
> > > the ALU of the processor has to do some operation which has memory
> > > operands (in this case the CPU needs to deal with the *real*
> > > addresses) but not prior to that.
> >
> > The address translation happens in the following way:
> >
> > Logical Addr-->|Segmentation Unit|-->Linear Addr -->|Paging unit|-->
> > Physical
> > Addr.
> >
> > If the paging unit is not setup then the linear addr is the physical
> > addr.
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
In the segmented memory model the memory appears as segments. In this model
the program issues a logical address which comprises of a segment:offset
address. The offset selects a byte in the segment. The segmentation unit
converts it to a linear address. If the paging unit is enabled the linear
address passes through the paging unit for further translation.
Also please do not top post :)
next prev parent reply other threads:[~2011-04-25 16:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 22:56 VMA of processes and CPU registers limp
2011-04-19 23:20 ` Dave Hylands
2011-04-20 11:01 ` limp
2011-04-20 16:03 ` mindentropy
2011-04-25 8:55 ` Prabhu nath
2011-04-25 16:38 ` mindentropy [this message]
2011-04-27 4:33 ` Prabhu nath
2011-04-27 4:48 ` Mulyadi Santosa
2011-04-27 18:30 ` mindentropy
2011-04-20 17:30 ` Dave Hylands
2011-04-20 18:08 ` mindentropy
2011-04-21 1:22 ` Dave Hylands
2011-04-21 19:54 ` mindentropy
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=201104252208.57103.mindentropy@gmail.com \
--to=mindentropy@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).