linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"bhelgaas@google.com" <bhelgaas@google.com>,
	"hjk@hansjkoch.de" <hjk@hansjkoch.de>
Subject: Re: [PATCH] Introducing kernel option to force all PCI memory resources to be page aligned. Fixes issues with uio based drivers.
Date: Mon, 6 Jun 2016 08:26:45 -0700	[thread overview]
Message-ID: <20160606152645.GA7605@kroah.com> (raw)
In-Reply-To: <a2e2c02820fd495e845a9cf9340a30e3@FE-MBX1012.de.bosch.com>

On Mon, Jun 06, 2016 at 02:59:47PM +0000, Koehrer Mathias (ETAS/ESW5) wrote:
> Hi Greg,
> 
> thanks for the response.
> > > Some uio based PCI drivers (e.g. uio_cif) do not work if the assigned
> > > PCI memory resources are not page aligned.
> > > By using the kernel option "pci=resource_alignment" it is possible to
> > > force single PCI boards to use page alignment for their memory resources.
> > > However, this is fairly cumbersome if multiple of these cards are in use.
> > > This patch adds another kernel option "pci=resources_page_aligned"
> > > that allows to set the default alignment of PCI memory resources to be
> > > page aligned.
> > > Overwriting of this default alignment via "pci=resource_alignment" is
> > > still possible.
> > 
> > This seems like a very large hammer for a very specific problem with a card
> > that seems to be not-in-spec (I can't find anywhere that requires resources to
> > be "page" aligned in the PCI spec).  Why not fix the firmware in these cards?
> The issue is not the firmware. The issue is that the Linux uio driver (here: uio_cif)
> does not work as uio_mmap() -> uio_mmap_physical() does not do a mmap 
> on physical memory that is not page aligned...

Then why not fix the uio_cif driver?

greg k-h

  reply	other threads:[~2016-06-06 15:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-06 14:59 [PATCH] Introducing kernel option to force all PCI memory resources to be page aligned. Fixes issues with uio based drivers Koehrer Mathias (ETAS/ESW5)
2016-06-06 15:26 ` gregkh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-06-08  8:32 Koehrer Mathias (ETAS/ESW5)
2016-06-07  6:51 Koehrer Mathias (ETAS/ESW5)
2016-06-07 14:31 ` gregkh
2016-06-06  6:53 Koehrer Mathias (ETAS/ESW5)
2016-06-06 14:46 ` gregkh

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=20160606152645.GA7605@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bhelgaas@google.com \
    --cc=hjk@hansjkoch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mathias.koehrer@etas.com \
    /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).