From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] heads up: i/o mmu related changes
Date: Tue, 10 Jun 2003 08:07:18 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723706202@msgid-missing> (raw)
I justed checked in a changeset
(davidm@tiger.hpl.hp.com|ChangeSet|20030610070955|57077) to make the
kernel work better for machines with I/O MMU. This should fix the
long-standing bug where IDE disks on machines with memory above 4GB
would MCA if the machine has an I/O MMU.
The trick was to make PCI_DMA_BUS_IS_PHYS a variable which is set at
runtime. Machines with I/O MMUs or machines with PCI buses which live
in separate address spaces MUST clear this variable. I updated the
code for the zx1 I/O MMU. I didn't touch the SGI I/O MMU code,
though, as I wouldn't be able to test it. Also, it would be good if
someone could test whether IDE disks work fine on machines with
Intel-chipsets and memory above 4GB.
--david
next reply other threads:[~2003-06-10 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 8:07 David Mosberger [this message]
2003-06-10 17:36 ` [Linux-ia64] heads up: i/o mmu related changes David Mosberger
2003-06-10 18:37 ` Jesse Barnes
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-105590723706202@msgid-missing \
--to=davidm@napali.hpl.hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox