From: Zoltan MENYHART <Zoltan.Menyhart@m6net.fr>
To: linux-ia64@vger.kernel.org
Subject: Mapping addresses 0xe000... and 0xc000...
Date: Thu, 15 Jan 2004 22:31:50 +0000 [thread overview]
Message-ID: <400714D6.2080609@m6net.fr> (raw)
I guess most of my problems with "IA64_LOG_NEXT_BUFFER()",
"salinfo_log_wakeup()", the KDB, unwinding the interrupted CPU's stack,
etc. are related to the mapping of the addresses 0xe000... and 0xc000...
As far as I can see, when I touch such an address that is not mapped
by any TR or TC entry (the walker is off for these address ranges), then
the low level translation fault handler automatically inserts a new TC
entry that maps the address in the usual way.
Yet an alternate translation fault vector is used if the PSR.ic is off
(interrupts are disabled), and this handler does not map automatically
the addresses 0xe000... and 0xc000...
We are obliged to take locks and to disable interrupts, see e.g.
"IA64_LOG_NEXT_BUFFER()", the KDB.
Is it a VMM design issue not to allow automatic address mapping
if the PSR.ic is off ? Should not we revise it :-) ?
Zoltan Menyhart
next reply other threads:[~2004-01-15 22:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 22:31 Zoltan MENYHART [this message]
2004-01-15 23:15 ` Mapping addresses 0xe000... and 0xc000 David Mosberger
2004-01-16 6:52 ` Christian Hildner
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=400714D6.2080609@m6net.fr \
--to=zoltan.menyhart@m6net.fr \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox