From: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Jason Cooper <jason@lakedaemon.net>,
Bjorn Helgaas <bhelgaas@google.com>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled
Date: Mon, 30 Jan 2017 09:51:46 -0700 [thread overview]
Message-ID: <20170130165146.GA29502@obsidianresearch.com> (raw)
In-Reply-To: <20170130154136.GR20550@bhelgaas-glaptop.roam.corp.google.com>
On Mon, Jan 30, 2017 at 09:41:36AM -0600, Bjorn Helgaas wrote:
> On Mon, Dec 12, 2016 at 11:30:20AM -0700, Jason Gunthorpe wrote:
> > The PCI core will write to the bridge window config multiple times
> > while they are enabled. This can lead to mbus failures like:
> >
> > mvebu_mbus: cannot add window '4:e8', conflicts with another window
> > mvebu-pcie mbus:pex@e0000000: Could not create MBus window at [mem 0xe0000000-0xe00fffff]: -22
> >
> > For me this is happening during a hotplug cycle. The PCI core is
> > not changing the values, just writing them twice while active.
> >
> > The patch addresses the general case of any change to an active window,
> > but not atomically. The code is slightly refactored so io and mem
> > can share more of the window logic.
> >
> > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
>
> Applied with Jason C's ack to pci/host-mvebu for v4.11, thanks!
Thank you for keeping on top of this Bjorn!
Jason
WARNING: multiple messages have this Message-ID (diff)
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled
Date: Mon, 30 Jan 2017 09:51:46 -0700 [thread overview]
Message-ID: <20170130165146.GA29502@obsidianresearch.com> (raw)
In-Reply-To: <20170130154136.GR20550@bhelgaas-glaptop.roam.corp.google.com>
On Mon, Jan 30, 2017 at 09:41:36AM -0600, Bjorn Helgaas wrote:
> On Mon, Dec 12, 2016 at 11:30:20AM -0700, Jason Gunthorpe wrote:
> > The PCI core will write to the bridge window config multiple times
> > while they are enabled. This can lead to mbus failures like:
> >
> > mvebu_mbus: cannot add window '4:e8', conflicts with another window
> > mvebu-pcie mbus:pex at e0000000: Could not create MBus window at [mem 0xe0000000-0xe00fffff]: -22
> >
> > For me this is happening during a hotplug cycle. The PCI core is
> > not changing the values, just writing them twice while active.
> >
> > The patch addresses the general case of any change to an active window,
> > but not atomically. The code is slightly refactored so io and mem
> > can share more of the window logic.
> >
> > Signed-off-by: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
>
> Applied with Jason C's ack to pci/host-mvebu for v4.11, thanks!
Thank you for keeping on top of this Bjorn!
Jason
next prev parent reply other threads:[~2017-01-30 16:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 18:30 [PATCH] PCI: mvebu: Handle changes to the bridge windows while enabled Jason Gunthorpe
2016-12-12 18:30 ` Jason Gunthorpe
2017-01-11 18:30 ` Bjorn Helgaas
2017-01-11 18:30 ` Bjorn Helgaas
2017-01-11 18:30 ` Bjorn Helgaas
2017-01-28 21:17 ` Bjorn Helgaas
2017-01-28 21:17 ` Bjorn Helgaas
2017-01-28 21:17 ` Bjorn Helgaas
2017-01-30 14:34 ` Jason Cooper
2017-01-30 14:34 ` Jason Cooper
2017-01-30 14:34 ` Jason Cooper
2017-01-30 15:41 ` Bjorn Helgaas
2017-01-30 15:41 ` Bjorn Helgaas
2017-01-30 15:41 ` Bjorn Helgaas
2017-01-30 16:51 ` Jason Gunthorpe [this message]
2017-01-30 16:51 ` Jason Gunthorpe
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=20170130165146.GA29502@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=bhelgaas@google.com \
--cc=gregory.clement@free-electrons.com \
--cc=helgaas@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=thomas.petazzoni@free-electrons.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.