From: Paul Bolle <pebolle@tiscali.nl>
To: Steven Newbury <steve@snewbury.org.uk>
Cc: David Airlie <airlied@linux.ie>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: agp/intel: can't ioremap flush page - no chipset flushing
Date: Sun, 09 Feb 2014 14:25:44 +0100 [thread overview]
Message-ID: <1391952344.25424.4.camel@x220> (raw)
In-Reply-To: <1391951759.6036.7.camel@artifact>
On Sun, 2014-02-09 at 13:15 +0000, Steven Newbury wrote:
> PCI resource allocation is undergoing some changes at the moment, it's
> definitely a bug if the Flush Page isn't getting allocated. I'm looking
> forward to hopefully getting pci_bus_alloc_resource_fit() behaviour in
> mainline, it will provide much better resource allocation in the 32 bit
> PCI address space, and prevent problems like this from cropping up.
>
> See Yinghai Lu's for-pci-res-alloc branch.
>
> I've been carrying the changes in my local tree, but right now the
> upstream PCI changes are quite extensive. He's planning on rebasing the
> branch soon.
Does this mean I might be better of not bisecting this just yet? Or are
these changes targeted at v3.15 (or later)?
Paul Bolle
WARNING: multiple messages have this Message-ID (diff)
From: Paul Bolle <pebolle@tiscali.nl>
To: Steven Newbury <steve@snewbury.org.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset flushing
Date: Sun, 09 Feb 2014 14:25:44 +0100 [thread overview]
Message-ID: <1391952344.25424.4.camel@x220> (raw)
In-Reply-To: <1391951759.6036.7.camel@artifact>
On Sun, 2014-02-09 at 13:15 +0000, Steven Newbury wrote:
> PCI resource allocation is undergoing some changes at the moment, it's
> definitely a bug if the Flush Page isn't getting allocated. I'm looking
> forward to hopefully getting pci_bus_alloc_resource_fit() behaviour in
> mainline, it will provide much better resource allocation in the 32 bit
> PCI address space, and prevent problems like this from cropping up.
>
> See Yinghai Lu's for-pci-res-alloc branch.
>
> I've been carrying the changes in my local tree, but right now the
> upstream PCI changes are quite extensive. He's planning on rebasing the
> branch soon.
Does this mean I might be better of not bisecting this just yet? Or are
these changes targeted at v3.15 (or later)?
Paul Bolle
next prev parent reply other threads:[~2014-02-09 13:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 19:06 agp/intel: can't ioremap flush page - no chipset flushing Paul Bolle
2014-02-08 19:59 ` Daniel Vetter
2014-02-08 19:59 ` Daniel Vetter
2014-02-08 20:22 ` Paul Bolle
2014-02-09 0:02 ` Daniel Vetter
2014-02-09 0:02 ` Daniel Vetter
2014-02-09 13:15 ` Steven Newbury
2014-02-09 13:15 ` [Intel-gfx] " Steven Newbury
2014-02-09 13:25 ` Paul Bolle [this message]
2014-02-09 13:25 ` Paul Bolle
2014-02-09 13:32 ` Steven Newbury
2014-02-09 13:32 ` [Intel-gfx] " Steven Newbury
2014-02-10 21:33 ` Bjorn Helgaas
2014-02-10 21:33 ` [Intel-gfx] " Bjorn Helgaas
2014-03-06 20:25 ` Paul Bolle
2014-03-06 20:25 ` [Intel-gfx] " Paul Bolle
2014-03-06 21:38 ` Bjorn Helgaas
2014-03-06 21:38 ` [Intel-gfx] " Bjorn Helgaas
2014-03-07 20:33 ` Bjorn Helgaas
2014-03-07 20:33 ` [Intel-gfx] " Bjorn Helgaas
2014-03-07 9:48 ` Paul Bolle
2014-03-07 9:48 ` [Intel-gfx] " Paul Bolle
2014-03-07 16:55 ` Bjorn Helgaas
2014-03-07 16:55 ` [Intel-gfx] " Bjorn Helgaas
2014-03-07 17:16 ` Paul Bolle
2014-03-07 17:16 ` [Intel-gfx] " Paul Bolle
2014-03-07 20:40 ` Bjorn Helgaas
2014-03-07 20:40 ` [Intel-gfx] " Bjorn Helgaas
2014-03-07 21:03 ` Paul Bolle
2014-03-07 21:03 ` [Intel-gfx] " Paul Bolle
2014-03-07 22:07 ` Bjorn Helgaas
2014-03-07 22:07 ` [Intel-gfx] " Bjorn Helgaas
2014-03-08 14:12 ` Bjorn Helgaas
2014-03-08 14:12 ` [Intel-gfx] " Bjorn Helgaas
2014-03-08 14:44 ` Paul Bolle
2014-03-08 14:44 ` [Intel-gfx] " Paul Bolle
2014-03-10 18:24 ` Bjorn Helgaas
2014-03-10 18:24 ` Bjorn Helgaas
2014-03-10 23:45 ` [Intel-gfx] " Paul Bolle
2014-03-10 23:45 ` Paul Bolle
2014-03-11 0:07 ` [Intel-gfx] " Bjorn Helgaas
2014-03-11 0:07 ` Bjorn Helgaas
2014-03-11 0:15 ` [Intel-gfx] " Paul Bolle
2014-03-11 2:07 ` Bjorn Helgaas
2014-03-11 9:20 ` Paul Bolle
2014-03-11 9:20 ` Paul Bolle
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=1391952344.25424.4.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=airlied@linux.ie \
--cc=bhelgaas@google.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steve@snewbury.org.uk \
--cc=yinghai@kernel.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 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.