Re: [ 37/38] PCI : ability to relocate assigned pci-resources

[Greg Kroah-Hartman]

On Sat, Nov 24, 2012 at 09:41:41AM +0800, Ram Pai wrote:
> On Fri, Nov 23, 2012 at 11:29:20AM -0200, Herton Ronaldo Krzesinski wrote:
> > On Wed, Nov 21, 2012 at 04:40:20PM -0800, Greg Kroah-Hartman wrote:
> > > 3.0-stable review patch.  If anyone has any objections, please let me know.
> > > 
> > > ------------------
> > > 
> > > From: Ram Pai <linuxram@xxxxxxxxxx>
> > > 
> > > commit 2bbc6942273b5b3097bd265d82227bdd84b351b2 upstream.
> > > 
> > > Currently pci-bridges are allocated enough resources to satisfy their immediate
> > > requirements.  Any additional resource-requests fail if additional free space,
> > > contiguous to the one already allocated, is not available. This behavior is not
> > > reasonable since sufficient contiguous resources, that can satisfy the request,
> > > are available at a different location.
> > > 
> > > This patch provides the ability to expand and relocate a allocated resource.
> > > 
> > > 	v2: Changelog: Fixed size calculation in pci_reassign_resource()
> > > 	v3: Changelog : Split this patch. The resource.c changes are already
> > > 			upstream. All the pci driver changes are in here.
> > > 
> > > Signed-off-by: Ram Pai <linuxram@xxxxxxxxxx>
> > > Signed-off-by: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
> > > Cc: Andrew Worsley <amworsley@xxxxxxxxx>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> > 
> > This change is said to bring a regression:
> > http://comments.gmane.org/gmane.linux.kernel.pci/11666
> > 
> > fixed by:
> > commit 47ea91b4052d9e94b9dca5d7a3d947fbebd07ba9
> > Resource: fix wrong resource window calculation
> > 
> > Which wasn't applied with this series for 3.0.
> 
> You are right.  We need to apply that fix along with this patch.

Thanks, now added to the tree.

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