linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "pascal@pabr.org" <pascal@pabr.org>
To: linux-mips@linux-mips.org
Subject: Re: Warning about add_wired_entry
Date: Mon, 07 Dec 2009 16:41:04 +0100	[thread overview]
Message-ID: <hfj7mr$lde$1@ger.gmane.org> (raw)
In-Reply-To: <20091207150236.GD19269@linux-mips.org>

Ralf Baechle wrote:
> The kernel does not reserve any address space for use by add_wired_entry().
> In other words there is the possibility that vmalloc, ioremap or other
> kernel APIs will use the same address space resulting in a crash or worse.

Thanks, I was not aware of that.

But what is the alternative ?  I have an Alchemy 1550 board with
an ethernet chip at 0xD-1000-0000, and last time I tried, enabling
  CONFIG_64BIT_PHYS_ADDR,
  CONFIG_ARCH_PHYS_ADDR_T_64BIT and
  CONFIG_PHYS_ADDR_T_64BIT
did not seem to allow access to the 36-bit I/O address space
through the platform_get_resource/request_mem_region machinery.
Is this supposed to work now ?

Pascal

      reply	other threads:[~2009-12-07 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 15:02 Warning about add_wired_entry Ralf Baechle
2009-12-07 15:41 ` pascal [this message]

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='hfj7mr$lde$1@ger.gmane.org' \
    --to=pascal@pabr.org \
    --cc=linux-mips@linux-mips.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;
as well as URLs for NNTP newsgroup(s).