From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] what about SGI IA64 io address map
Date: Mon, 24 Jun 2002 21:29:25 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905719@msgid-missing> (raw)
On Mon, Jun 24, 2002 at 09:13:43PM +0800, Barry Wu wrote:
> Hi, all, I am new to Intel Itanium. I do not know
> if io address is special linux. For example, in mips
> io virtual address can be converted directly to
> physics address by K1seg. I read Itanium system
> architecture and find that all virtual address have
> to pass TLB transation. Am I right?
Right. Though region 7 for linux/ia64 is kind of like k1seg in mips,
and like mips, there's a dedicated translation register setup for it.
> I read include/asm-ia64/sn/sn2/addrs.h and find
> that SGI IA64 address is composed of
> node-id + node offset
Yes.
> If all virtual address have to convert by TLB, then
> I think SGI Itanium virtual address have to use
> TR register. But Itanium only has 48 DTR and if
> we use node-id as part of physics address, then
> each node we have to use a DTR, then SGI IA64 system
> have no too DTR to convert this address. The efficiency
> must be slow for IO address. I do not know if it is
> correct. If someone knows, please give me a reply.
Only one TR is used for mapping I/O space--the one for region 6, which
is uncached direct mapped memory. Additionaly, I/O space accesses
should only be done through the readX/writeX functions, which can do
things like make sure I/O is coherent and ordered properly.
Was there any particular code snippet that you were confused about?
It might be easier to explain things in that context.
Jesse
next reply other threads:[~2002-06-24 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-24 21:29 Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-24 13:13 [Linux-ia64] what about SGI IA64 io address map Barry Wu
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=marc-linux-ia64-105590701905719@msgid-missing \
--to=jbarnes@sgi.com \
--cc=linux-ia64@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.