kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: augustocaringi@gmail.com (Augusto Mecking Caringi)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Virtual Address Space
Date: Wed, 28 Sep 2016 10:14:29 +0100	[thread overview]
Message-ID: <CADFy_4EOZ0zav+YoLBzhXv4nfKWf1pdGQSJp2_B_ok8hD3bQtg@mail.gmail.com> (raw)
In-Reply-To: <CAA2oCO=boqsqtgPbwyX_Fg53mz=Yh6G3akmud8YpQ3eJ1WvxNg@mail.gmail.com>

On Wed, Sep 28, 2016 at 6:06 AM, Madhu K <madhu.sk89@gmail.com> wrote:
> Hi All,
>
> This is to understand the Virtual address space.Basically who generates the
> virtual addresses CPU or GNU compiler?

Hi,

     In my view, the linker.

     The compiler normally generates absolute addresses (starting from
0), creating object code.

     Then the linker generates an executable by combining different
object files together and assigning virtual addresses.

     Finally, is CPU (MMU) job (with the kernel helping) to translate
these virtual addresses to physical ones.

     Best regards,

-- 
Augusto Mecking Caringi

  parent reply	other threads:[~2016-09-28  9:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28  5:06 Virtual Address Space Madhu K
2016-09-28  6:05 ` Arun Sudhilal
2016-09-28 10:11   ` Madhu K
2016-09-28 10:59     ` Prabhunath G
2016-09-28 13:32       ` Gadre Nayan
2016-09-30 16:40         ` Román Martínez
2016-10-02  2:52           ` Arshad Hussain
2016-10-03  5:12             ` Madhu K
2016-09-28  6:09 ` Greg KH
2016-09-28 10:14   ` Madhu K
2016-09-28 10:29     ` Greg KH
2016-09-28  9:14 ` Augusto Mecking Caringi [this message]
2016-09-28 10:21   ` Madhu K
2016-09-28 10:37 ` Alexander Kapshuk
2016-09-29  7:25 ` arshad hussain
2016-09-30 17:09   ` roman at mailoo.org
2016-10-01 18:02     ` piyush moghe

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=CADFy_4EOZ0zav+YoLBzhXv4nfKWf1pdGQSJp2_B_ok8hD3bQtg@mail.gmail.com \
    --to=augustocaringi@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).