From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Willy Tarreau <w@1wt.eu>
Cc: "Jason Gunthorpe" <jgunthorpe@obsidianresearch.com>,
"Neil Greatorex" <neil@fatboyfat.co.uk>,
"Matthew Minter" <matthew_minter@xyratex.com>,
"Gerlando Falauto" <gerlando.falauto@keymile.com>,
linux-arm-kernel@lists.infradead.org,
"Jason Cooper" <jason@lakedaemon.net>,
"Gregory Clément" <gregory.clement@free-electrons.com>,
"Ezequiel Garcia" <ezequiel.garcia@free-electrons.com>,
"Andrew Lunn" <andrew@lunn.ch>,
linux-pci@vger.kernel.org, "Tawfik Bayouk" <tawfik@marvell.com>,
"Lior Amsalem" <alior@marvell.com>
Subject: Re: Fixing PCIe issues on Armada XP
Date: Thu, 10 Apr 2014 20:02:22 +0200 [thread overview]
Message-ID: <20140410200222.27cab16e@skate> (raw)
In-Reply-To: <20140410171000.GF25890@1wt.eu>
Dear Willy Tarreau,
On Thu, 10 Apr 2014 19:10:00 +0200, Willy Tarreau wrote:
> Thanks for putting all this online.
>
> I have a minor comment below :
>
> > * 2 patches on the pci-mvebu driver. One from Willy Tarreau to fix the
> > off by one on the sizes. And another one from me which splits the
> > PCI BAR into power-of-two sized chunks, in order to create valid
> > MBus windows.
>
> As suggested by Jason, this one should be merged before his that's just
> before, to ensure that it will not cause a regression.
Ok, will change this, thanks.
> > I've tested this with my IGB card which needs a 9 MB
> > BAR (so 8 MB + 1 MB needed), and I've also faked the code to code to
> > simulate a 11.5 MB BAR (so 8 + 2 + 1 + 0.5 MB), and it worked. I
> > also checked that if we have an error when creating one of the
> > windows, then all the previous windows needed for the current BAR
> > are properly removed.
>
> Really cool, I'm going to test that on a few PCIe cards and will report
> the results here. How can we check the number of mbus windows in use ?
# cat /sys/kernel/debug/mvebu-mbus/devices
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-10 18:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 16:19 Fixing PCIe issues on Armada XP Thomas Petazzoni
2014-04-10 16:57 ` Jason Gunthorpe
2014-04-10 18:01 ` Thomas Petazzoni
2014-04-10 20:12 ` Jason Gunthorpe
2014-04-10 21:04 ` Thomas Petazzoni
2014-04-10 21:56 ` Neil Greatorex
2014-04-10 22:06 ` Jason Gunthorpe
2014-04-10 22:15 ` Neil Greatorex
2014-04-11 10:23 ` Thomas Petazzoni
2014-04-11 16:31 ` Jason Gunthorpe
2014-04-11 17:21 ` Matthew Minter
2014-04-11 17:29 ` Jason Gunthorpe
2014-04-18 13:02 ` Thomas Petazzoni
2014-04-22 17:34 ` Jason Gunthorpe
2014-04-18 12:58 ` Thomas Petazzoni
2014-04-22 17:56 ` Jason Gunthorpe
2014-04-10 17:10 ` Willy Tarreau
2014-04-10 18:02 ` Thomas Petazzoni [this message]
2014-04-10 23:13 ` Willy Tarreau
2014-04-10 23:40 ` Jason Gunthorpe
2014-04-11 6:23 ` Willy Tarreau
2014-04-10 18:20 ` Neil Greatorex
2014-04-10 21:07 ` Thomas Petazzoni
2014-04-11 14:32 ` Thomas Petazzoni
2014-04-11 15:57 ` Neil Greatorex
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=20140410200222.27cab16e@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gerlando.falauto@keymile.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew_minter@xyratex.com \
--cc=neil@fatboyfat.co.uk \
--cc=tawfik@marvell.com \
--cc=w@1wt.eu \
/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).