All of lore.kernel.org
 help / color / mirror / Atom feed
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:45:45 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705449@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705441@msgid-missing>

>>>>> On Wed, 9 Apr 2003 01:36:33 -0400, "Mike Fox" <mfox@annapmicro.com> said:

  Mike> In the driver I am basically doing this in my mmap entry point:

  Mike>   vma-> vm_page_prot = pgprot_noncached(vma->vm_page_prot);
  Mike>   vma-> vm_flags |= VM_IO;

  Mike> /*
  Mike> * this maps the physical memory to the user
  Mike> */
  Mike> if (remap_page_range(vma->vm_start, offset, vma->vm_end-vma->vm_start, vma->vm_page_prot))
  Mike> {
  Mike>     return -EAGAIN;
  Mike> }

This is basically what drivers/char/mem.c is doing, so there is
nothing obviously wrong here.

	--david


  parent reply	other threads:[~2003-04-09 17:45 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 ` [Linux-ia64] mmap crashes system after mapping PCI device into user space and reading and writin David Mosberger
2003-04-09 17:45 ` David Mosberger [this message]
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-105590723705449@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 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.