linux-kernel - Re: [Intel-gfx] agp/intel: can't ioremap flush page

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1391952344.25424.4.camel@x220>
Date:	Sun, 09 Feb 2014 14:25:44 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Steven Newbury <steve@...wbury.org.uk>
Cc:	Daniel Vetter <daniel.vetter@...ll.ch>,
	David Airlie <airlied@...ux.ie>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Yinghai Lu <yinghai@...nel.org>
Subject: Re: [Intel-gfx] agp/intel: can't ioremap flush page - no chipset
 flushing

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/