From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] mmap crashes system after mapping PCI device into user space and reading and writin
Date: Wed, 09 Apr 2003 17:33:59 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705448@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705441@msgid-missing>
>>>>> On Tue, 8 Apr 2003 17:59:56 -0400, "Mike Fox" <mfox@annapmicro.com> said:
Mike> Hi, I am running kernel version 2.4.19 and I am getting a
Mike> system crash when I mmap my PCI device into user space and
Mike> access it.
One thing you need to be careful about is memory attribute aliasing.
The CPU (or platform chips) can MCA if you try to access the same
physical location with different memory attributes (e.g., cached vs.
uncached). Also, keep in mind that the kernel uses a 64MB page size
for the identity-mapped regions (regions 6 and 7). This means that
you cannot map stuff requiring different attributes within the same
64MB page. I kind of doubt this is what's causing the problem for
you, but since you didn't give any details about the hw you're trying
to map, it's hard to be more specific.
As others have pointed out, it's of course also important to verify
that you access I/O space uncached.
--david
next prev parent reply other threads:[~2003-04-09 17:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 21:59 [Linux-ia64] mmap crashes system after mapping PCI device into user space and reading and writing Mike Fox
2003-04-09 0:42 ` [Linux-ia64] mmap crashes system after mapping PCI device into user space and reading and writin Grant Grundler
2003-04-09 5:36 ` Mike Fox
2003-04-09 6:20 ` Grant Grundler
2003-04-09 8:57 ` [Linux-ia64] mmap crashes system after mapping PCI device into user Christian Hinkelbein
2003-04-09 17:33 ` David Mosberger [this message]
2003-04-09 17:45 ` [Linux-ia64] mmap crashes system after mapping PCI device into user space and reading and writin David Mosberger
2003-04-09 23:53 ` Mike Fox
2003-04-10 0:44 ` David Mosberger
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-105590723705448@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