mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	torvalds@linux-foundation.org, Matthew Wilcox <matthew@wil.cx>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: RFC: [PATCH] resource: ensure MMIO exclusivity for device drivers
Date: Mon, 27 Oct 2008 16:31:58 +0100	[thread overview]
Message-ID: <20081027153158.GJ5704@elte.hu> (raw)
In-Reply-To: <20081022205656.184929ed@infradead.org>


* Arjan van de Ven <arjan@infradead.org> wrote:

> 
> From: Arjan van de Ven <arjan@linux.intel.com>
> Date: Wed, 22 Oct 2008 19:55:31 -0700
> Subject: [PATCH] resource: ensure MMIO exclusivity for device drivers
> 
> Device drivers that use pci_request_regions() (and similar APIs) have a
> reasonable expectation that they are the only ones accessing their device.
> As part of the e1000e hunt, we were afraid that some userland (X or some
> bootsplash stuff) was mapping the MMIO region that the driver thought it
> had exclusively via /dev/mem or via various sysfs resource mappings.
> 
> This patch adds the option for device drivers to cause their reserved
> regions to be on the "banned from /dev/mem use" list, so now both kernel memory
> and device-exclusive MMIO regions are banned.
> NOTE: This is only active when CONFIG_STRICT_DEVMEM is set.
> 
> In addition to the config option, a kernel parameter iomem=relaxed is
> provided for the cases where developers want to diagnose, in the field,
> drivers issues from userspace despite the drivers explicit request.
> 
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>

the concept looks fine to me - the stricter we are in this area the 
better IMO. Unless there are objections, i guess it's best to do this 
via the PCI tree?

	Ingo

      reply	other threads:[~2008-10-27 15:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23  3:56 Arjan van de Ven
2008-10-27 15:31 ` Ingo Molnar [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=20081027153158.GJ5704@elte.hu \
    --to=mingo@elte.hu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=arjan@infradead.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=torvalds@linux-foundation.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

Powered by JetHome