Re: PCI bridge range sizing bug

2007-05-15 Thread Ivan Kokshaysky
On Mon, May 14, 2007 at 10:45:43AM -0700, Jesse Barnes wrote: > Any update on this, Ivan? Maybe I missed your post, but I haven't seen > anything yet... No, I didn't post anything, sorry. This turned out to be not as trivial as I thought - I've played with that code on amd64, and results were

Re: PCI bridge range sizing bug

2007-05-15 Thread Ivan Kokshaysky
On Mon, May 14, 2007 at 10:45:43AM -0700, Jesse Barnes wrote: Any update on this, Ivan? Maybe I missed your post, but I haven't seen anything yet... No, I didn't post anything, sorry. This turned out to be not as trivial as I thought - I've played with that code on amd64, and results were

Re: PCI bridge range sizing bug

2007-05-14 Thread Jesse Barnes
On Friday, April 20, 2007 1:30 pm Ivan Kokshaysky wrote: > On Fri, Apr 20, 2007 at 11:28:42AM -0700, Linus Torvalds wrote: > > Actually, I would suggest we not do it automatically (because the > > need for it is just so low, and the downsides are potentially huge > > - there are just too many

Re: PCI bridge range sizing bug

2007-05-14 Thread Jesse Barnes
On Friday, April 20, 2007 1:30 pm Ivan Kokshaysky wrote: On Fri, Apr 20, 2007 at 11:28:42AM -0700, Linus Torvalds wrote: Actually, I would suggest we not do it automatically (because the need for it is just so low, and the downsides are potentially huge - there are just too many resources

Re: PCI bridge range sizing bug

2007-04-20 Thread Rik van Riel
Jesse Barnes wrote: On Friday, April 20, 2007 11:28 am Linus Torvalds wrote: On Fri, 20 Apr 2007, Jesse Barnes wrote: Sounds good, hopefully reassigning the bridge resources won't cause too much trouble. Do you have time to hack this up? If not, I could give it a try, as long as ajax is

Re: PCI bridge range sizing bug

2007-04-20 Thread Jesse Barnes
On Friday, April 20, 2007 11:28 am Linus Torvalds wrote: > On Fri, 20 Apr 2007, Jesse Barnes wrote: > > Sounds good, hopefully reassigning the bridge resources won't cause > > too much trouble. Do you have time to hack this up? If not, I > > could give it a try, as long as ajax is willing to

Re: PCI bridge range sizing bug

2007-04-20 Thread Ivan Kokshaysky
On Fri, Apr 20, 2007 at 11:28:42AM -0700, Linus Torvalds wrote: > Actually, I would suggest we not do it automatically (because the need for > it is just so low, and the downsides are potentially huge - there are just > too many resources that are "hidden" from us through ACPI tricks and >

Re: PCI bridge range sizing bug

2007-04-20 Thread Linus Torvalds
On Fri, 20 Apr 2007, Jesse Barnes wrote: > > Sounds good, hopefully reassigning the bridge resources won't cause too > much trouble. Do you have time to hack this up? If not, I could give > it a try, as long as ajax is willing to test... Actually, I would suggest we not do it automatically

Re: PCI bridge range sizing bug

2007-04-20 Thread Jesse Barnes
On Friday, April 20, 2007 2:23 am Ivan Kokshaysky wrote: > On Thu, Apr 19, 2007 at 05:19:20PM -0700, Linus Torvalds wrote: > > I think we used to *never* assign PCI bus resources on x86, but > > that thing got fixed some time ago. Now I think we only re-assign > > them if they were unassigned *or*

Re: PCI bridge range sizing bug

2007-04-20 Thread Ivan Kokshaysky
On Thu, Apr 19, 2007 at 05:19:20PM -0700, Linus Torvalds wrote: > I think we used to *never* assign PCI bus resources on x86, but that thing > got fixed some time ago. Now I think we only re-assign them if they were > unassigned *or* if the assignment wasn't working before. But I'm not 100% >

Re: PCI bridge range sizing bug

2007-04-20 Thread Ivan Kokshaysky
On Thu, Apr 19, 2007 at 05:19:20PM -0700, Linus Torvalds wrote: I think we used to *never* assign PCI bus resources on x86, but that thing got fixed some time ago. Now I think we only re-assign them if they were unassigned *or* if the assignment wasn't working before. But I'm not 100% sure

Re: PCI bridge range sizing bug

2007-04-20 Thread Jesse Barnes
On Friday, April 20, 2007 2:23 am Ivan Kokshaysky wrote: On Thu, Apr 19, 2007 at 05:19:20PM -0700, Linus Torvalds wrote: I think we used to *never* assign PCI bus resources on x86, but that thing got fixed some time ago. Now I think we only re-assign them if they were unassigned *or* if the

Re: PCI bridge range sizing bug

2007-04-20 Thread Linus Torvalds
On Fri, 20 Apr 2007, Jesse Barnes wrote: Sounds good, hopefully reassigning the bridge resources won't cause too much trouble. Do you have time to hack this up? If not, I could give it a try, as long as ajax is willing to test... Actually, I would suggest we not do it automatically

Re: PCI bridge range sizing bug

2007-04-20 Thread Ivan Kokshaysky
On Fri, Apr 20, 2007 at 11:28:42AM -0700, Linus Torvalds wrote: Actually, I would suggest we not do it automatically (because the need for it is just so low, and the downsides are potentially huge - there are just too many resources that are hidden from us through ACPI tricks and having

Re: PCI bridge range sizing bug

2007-04-20 Thread Jesse Barnes
On Friday, April 20, 2007 11:28 am Linus Torvalds wrote: On Fri, 20 Apr 2007, Jesse Barnes wrote: Sounds good, hopefully reassigning the bridge resources won't cause too much trouble. Do you have time to hack this up? If not, I could give it a try, as long as ajax is willing to test...

Re: PCI bridge range sizing bug

2007-04-20 Thread Rik van Riel
Jesse Barnes wrote: On Friday, April 20, 2007 11:28 am Linus Torvalds wrote: On Fri, 20 Apr 2007, Jesse Barnes wrote: Sounds good, hopefully reassigning the bridge resources won't cause too much trouble. Do you have time to hack this up? If not, I could give it a try, as long as ajax is

Re: PCI bridge range sizing bug

2007-04-19 Thread Linus Torvalds
On Thu, 19 Apr 2007, Greg KH wrote: > On Thu, Apr 19, 2007 at 04:11:50PM -0700, Jesse Barnes wrote: > > On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: > > > So I'm attempting to do something fairly heinous (X server across > > > five video cards), and I hit a fun bug in bridge range

Re: PCI bridge range sizing bug

2007-04-19 Thread Greg KH
On Thu, Apr 19, 2007 at 04:11:50PM -0700, Jesse Barnes wrote: > On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: > > So I'm attempting to do something fairly heinous (X server across > > five video cards), and I hit a fun bug in bridge range setup. See > > attached lspci and dmesg, but the

Re: PCI bridge range sizing bug

2007-04-19 Thread Jesse Barnes
On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: > So I'm attempting to do something fairly heinous (X server across > five video cards), and I hit a fun bug in bridge range setup. See > attached lspci and dmesg, but the short of it is I've got two VGA > chips on one card behind a bridge,

Re: PCI bridge range sizing bug

2007-04-19 Thread Jesse Barnes
On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: So I'm attempting to do something fairly heinous (X server across five video cards), and I hit a fun bug in bridge range setup. See attached lspci and dmesg, but the short of it is I've got two VGA chips on one card behind a bridge, which

Re: PCI bridge range sizing bug

2007-04-19 Thread Greg KH
On Thu, Apr 19, 2007 at 04:11:50PM -0700, Jesse Barnes wrote: On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: So I'm attempting to do something fairly heinous (X server across five video cards), and I hit a fun bug in bridge range setup. See attached lspci and dmesg, but the short

Re: PCI bridge range sizing bug

2007-04-19 Thread Linus Torvalds
On Thu, 19 Apr 2007, Greg KH wrote: On Thu, Apr 19, 2007 at 04:11:50PM -0700, Jesse Barnes wrote: On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: So I'm attempting to do something fairly heinous (X server across five video cards), and I hit a fun bug in bridge range setup. See