Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Alexey Korolev
>> >There are two main things we can do: >> >1. Make the 64 bit device only use the low 32 bit >> It was my first implementation. Unfortunately older versions of >> Linux (Like 2.6.18) hang during startup with this. >> As far as I remember it was qemu-0.15 so may be 1.0 have no such an >> issue.

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Kevin O'Connor
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote: > On 29/12/11 00:43, Michael S. Tsirkin wrote: > >On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: > >>All devices behind a bridge need to have all their regions consecutive and > >>not overlapping with all the normal me

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Kevin O'Connor
On Fri, Dec 30, 2011 at 06:10:13PM +1300, Alexey Korolev wrote: > On 30/12/11 05:21, Michael S. Tsirkin wrote: > >On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote: > >>>Can't figure this out. What does this do? > >>Bios will panic if it founds prefmem BARs in both 32bit and 64bit area

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Alexey Korolev
On 30/12/11 05:21, Michael S. Tsirkin wrote: On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote: Can't figure this out. What does this do? Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas. That's not good, it's a legal configuration. To be more complete : Bi

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Alexey Korolev
On 30/12/11 05:21, Michael S. Tsirkin wrote: On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote: Can't figure this out. What does this do? Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas. That's not good, it's a legal configuration. To be more complete : Bi

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Kevin O'Connor
On Wed, Dec 28, 2011 at 01:43:02PM +0200, Michael S. Tsirkin wrote: > On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: > > All devices behind a bridge need to have all their regions consecutive and > > not overlapping with all the normal memory ranges. > > Since prefetchable memory i

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Alexey Korolev
On 30/12/11 05:18, Michael S. Tsirkin wrote: On Thu, Dec 29, 2011 at 06:40:26PM +1300, Alexey Korolev wrote: On 29/12/11 00:43, Michael S. Tsirkin wrote: On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: All devices behind a bridge need to have all their regions consecutive and n

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Michael S. Tsirkin
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote: > >Can't figure this out. What does this do? > Bios will panic if it founds prefmem BARs in both 32bit and 64bit areas. That's not good, it's a legal configuration. > Otherwise we will pick one which exists or 32bit one if both are n

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Michael S. Tsirkin
On Thu, Dec 29, 2011 at 06:41:36PM +1300, Alexey Korolev wrote: > On 29/12/11 00:43, Michael S. Tsirkin wrote: > >On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: > >>All devices behind a bridge need to have all their regions consecutive and > >>not overlapping with all the normal me

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-29 Thread Michael S. Tsirkin
On Thu, Dec 29, 2011 at 06:40:26PM +1300, Alexey Korolev wrote: > On 29/12/11 00:43, Michael S. Tsirkin wrote: > >On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: > >>All devices behind a bridge need to have all their regions consecutive and > >>not overlapping with all the normal me

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-28 Thread Alexey Korolev
On 29/12/11 00:43, Michael S. Tsirkin wrote: On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: All devices behind a bridge need to have all their regions consecutive and not overlapping with all the normal memory ranges. Since prefetchable memory is described by one record, we must

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-28 Thread Alexey Korolev
On 29/12/11 00:43, Michael S. Tsirkin wrote: On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: All devices behind a bridge need to have all their regions consecutive and not overlapping with all the normal memory ranges. Since prefetchable memory is described by one record, we must

Re: [Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-28 Thread Michael S. Tsirkin
On Wed, Dec 28, 2011 at 06:35:55PM +1300, Alexey Korolev wrote: > All devices behind a bridge need to have all their regions consecutive and > not overlapping with all the normal memory ranges. > Since prefetchable memory is described by one record, we must avoid the > situations > when 32bit and

[Qemu-devel] [PATCH 3/3] Changes related to secondary buses and 64bit regions

2011-12-27 Thread Alexey Korolev
All devices behind a bridge need to have all their regions consecutive and not overlapping with all the normal memory ranges. Since prefetchable memory is described by one record, we must avoid the situations when 32bit and 64bit prefetchable regions are present within one secondary bus. Signed-