Re: Resource assignment oddities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 2013-05-21 at 11:28 -0600, Bjorn Helgaas wrote:
> On Thu, May 16, 2013 at 11:36 PM, Benjamin Herrenschmidt
> <benh@xxxxxxxxxxxxxxxxxxx> wrote:
> > On Tue, 2013-05-07 at 15:21 -0700, Yinghai Lu wrote:
> >> I just sent v3, please test that.
> >>
> >> That should be less invasive for v3.10. As it will skip adding faile
> >> resource to failed list when the resource is IORESOURCE_IO, and bus
> >> does not have IORESOURCE_IO.
> >
> > Any news about merging this ?
> 
> I'm starting to look at this.  Do you think this is v3.10 material?
> My first impression is that it seems pretty large for that.

Well, it's problematic for us, the assignment fails here or there on
some of our new systems with the new code multi-pass code for memory due
to the lack of IO which is nasty at best.

We were hoping we could get 3.10 to support those machines since that's
apparently what a well known enterprise distro will pickup (and trying
to get them to pickup backport can be complete hell).

Cheers,
Ben.




--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux