The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Ben Johnson <ben@blarg.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linear vs. logical addresses?  how does cpu interpret kernel addrs?
Date: Tue, 16 Sep 2003 17:54:46 -0700	[thread overview]
Message-ID: <20030917005446.GW4306@holomorphy.com> (raw)
In-Reply-To: <1562370000.1063759683@[10.10.2.4]>

At some point in the past, someone had their attribution stripped from:
>> 1) When I am referencing a pointer in the kernel, is the value of that
>> pointer variable interpreted by the cpu as a logical or linear address?
>> 2) if I have two overlapping data/stack segments presently selected,
>> each with a different base, how does the cpu know which segment/base
>> address to use to get the linear address?

On Tue, Sep 16, 2003 at 05:48:04PM -0700, Martin J. Bligh wrote:
> IIRC, all the base segments are 0, so none of this matters ;-)

2.0.x used such things as the segment bits, hardware tasking, and so on.


-- wli

  reply	other threads:[~2003-09-17  0:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-16 22:47 linear vs. logical addresses? how does cpu interpret kernel addrs? Ben Johnson
2003-09-17  0:48 ` Martin J. Bligh
2003-09-17  0:54   ` William Lee Irwin III [this message]
2003-09-17  0:58     ` Martin J. Bligh
2003-09-17  1:44       ` Ben Johnson
2003-09-17  1:55         ` William Lee Irwin III
2003-09-17  2:07           ` Ben Johnson
2003-09-17  2:10             ` William Lee Irwin III
2003-09-17  2:32               ` Ben Johnson
2003-09-17  2:10         ` Felipe Alfaro Solana
2003-09-17 11:39 ` Richard B. Johnson
2003-09-17 19:42   ` Ben Johnson
2003-09-17 20:05     ` Richard B. Johnson
2003-09-17 20:44       ` 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=20030917005446.GW4306@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=ben@blarg.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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