From: Bjorn Helgaas <helgaas@kernel.org>
To: "Koehrer Mathias (ETAS/ESW5)" <mathias.koehrer@etas.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
"hjk@hansjkoch.de" <hjk@hansjkoch.de>
Subject: Re: [PATCH] Extending kernel option pci=resource_alignment to be able to specify PCI device/vendor IDs
Date: Mon, 8 Aug 2016 09:01:27 -0500 [thread overview]
Message-ID: <20160808140127.GA14630@localhost> (raw)
In-Reply-To: <9224b5d57cf14c5da4979251742b838b@FE-MBX1012.de.bosch.com>
On Mon, Aug 08, 2016 at 07:39:01AM +0000, Koehrer Mathias (ETAS/ESW5) wrote:
> Hi Bjorn,
>
> > On Tue, Jun 07, 2016 at 02:24:17PM +0000, Koehrer Mathias (ETAS/ESW5) wrote:
> > > 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 boards are in
> > > use as the specification of the cards has to be done via PCI
> > > bus/slot/function number which might change e.g. by adding another board.
> > > This patch extends the kernel option "pci=resource_alignment" to allow
> > > to specify the relevant boards via PCI device/vendor (and subdevice/subvendor)
> > ids.
> > > The specification of the devices via device/vendor is indicated by a
> > > leading string "pci:" as argument to "pci=resource_alignment".
> > > The format of the specification is
> > > pci:<vendor>:<device>[:<subvendor>:<subdevice>]
> > >
> > > Signed-off-by: Mathias Koehrer <mathias.koehrer@etas.com>
> > >
> > > ---
> > > Documentation/kernel-parameters.txt | 2 +
> > > drivers/pci/pci.c | 66 +++++++++++++++++++++++++-----------
> > > 2 files changed, 49 insertions(+), 19 deletions(-)
> > >
> > > Index: linux-4.7-rc1/Documentation/kernel-parameters.txt
> > >
> > ============================================================
> > =======
> > > --- linux-4.7-rc1.orig/Documentation/kernel-parameters.txt
> > > +++ linux-4.7-rc1/Documentation/kernel-parameters.txt
> > > @@ -2998,6 +2998,8 @@ bytes respectively. Such letter suffixes
> > > resource_alignment=
> > > Format:
> > > [<order of
> > align>@][<domain>:]<bus>:<slot>.<func>[; ...]
> > > + [<order of align>@]pci:<vendor>:<device>\
> > > + [:<subvendor>:<subdevice>][; ...]
> >
> > Can you include a little example here so we know whether to use "pci:8086:1234" or
> > "pci:0x8086:0x1234"?
> >
> > Bjorn
>
> I have provided an example and extended the docu (sent in http://marc.info/?l=linux-pci&m=146657769505684&w=2 and http://marc.info/?l=linux-pci&m=146918412704107&w=2 ).
> It would be great if you could comment on the modified patch...
It looks like I applied the patch, but I forgot to include the updated
documentation. Can you confirm that? If you send a documentation
patch to add the example, I can add that.
Bjorn
next prev parent reply other threads:[~2016-08-08 14:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 7:39 [PATCH] Extending kernel option pci=resource_alignment to be able to specify PCI device/vendor IDs Koehrer Mathias (ETAS/ESW5)
2016-08-08 14:01 ` Bjorn Helgaas [this message]
2016-08-09 8:33 ` [PATCH] Extending kernel option pci=resource_alignment to be able to specify PCI device/vendor IDs - Documentation Mathias Koehrer
-- strict thread matches above, loose matches on Subject: below --
2016-06-09 12:40 [PATCH] Extending kernel option pci=resource_alignment to be able to specify PCI device/vendor IDs Koehrer Mathias (ETAS/ESW5)
2016-06-09 16:12 ` gregkh
2016-06-08 6:14 Koehrer Mathias (ETAS/ESW5)
2016-06-07 14:24 Koehrer Mathias (ETAS/ESW5)
2016-06-07 14:32 ` gregkh
2016-06-21 22:00 ` Bjorn Helgaas
2016-06-21 22:04 ` Bjorn Helgaas
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=20160808140127.GA14630@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hjk@hansjkoch.de \
--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 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.