On 12/16/11 05:41, Alexey Korolev wrote:
>>> I wonder if there any particular reason to separate prefetchable a
>>> non-prefetchable memory regions in pciinit? Extra two more regions would
>>> make code more complex.
>> Oh yes, there is. Which reminds me that the whole thing isn't that easy
>> unf
I wonder if there any particular reason to separate prefetchable a
non-prefetchable memory regions in pciinit? Extra two more regions would
make code more complex.
Oh yes, there is. Which reminds me that the whole thing isn't that easy
unfortunaly ...
The reason are pci bridges. They have two
On 12/14/11 05:30, Alexey Korolev wrote:
> Hi,
>>>
>>> It shouldn't be that hard to add the latter though. seabios needs two
>>> more pci_region_type (PCI_REGION_TYPE_MEM_64 and
>>> PCI_REGION_TYPE_PREFMEM_64) to track and map 64bit bars separately. And
>>> a address space window where it can map
On Wed, Dec 14, 2011 at 05:30:23PM +1300, Alexey Korolev wrote:
> Hi,
> >>
> >>It shouldn't be that hard to add the latter though. seabios needs two
> >>more pci_region_type (PCI_REGION_TYPE_MEM_64 and
> >>PCI_REGION_TYPE_PREFMEM_64) to track and map 64bit bars separately. And
> >>a address space
Hi,
It shouldn't be that hard to add the latter though. seabios needs two
more pci_region_type (PCI_REGION_TYPE_MEM_64 and
PCI_REGION_TYPE_PREFMEM_64) to track and map 64bit bars separately. And
a address space window where it can map 64bit bars to.
Right. This is a thing I'm thinking about no
Hi Gerd,
I'd strongly suggest to move forward to qemu 1.0. Memory region
handling has seen a major rewrite in 1.0 (memory api patches by avi).
Chances are good that the 64bit bar bugs in qemu have been fixed meanwhile.
Thanks, will try it. Hope it will be better.
I have experimental patches
On 12/05/11 05:29, Alexey Korolev wrote:
> Hi Gerd,
>
> We have very early prototype of data acquisition device, with quite
> large MMIO buffer. It is an emulated device.
> We are running the 0.15 release.
> 0.15 doesn't work correctly with 64bit BARs so I've already added some
> hacks to Seabios
On 05/12/11 19:31, Michael S. Tsirkin wrote:
On Mon, Dec 05, 2011 at 05:20:32PM +1300, Alexey Korolev wrote:
Hi Michael,
Thank you for good advice, you are right. When I added new range
above 4GB in _CRS the problem has gone.
QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed,
Non
On Mon, Dec 05, 2011 at 05:20:32PM +1300, Alexey Korolev wrote:
> Hi Michael,
>
> Thank you for good advice, you are right. When I added new range
> above 4GB in _CRS the problem has gone.
> QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed,
> NonCacheable, ReadWrite,
>
Hi Gerd,
We have very early prototype of data acquisition device, with quite
large MMIO buffer. It is an emulated device.
We are running the 0.15 release.
0.15 doesn't work correctly with 64bit BARs so I've already added some
hacks to Seabios to let OS to choose the memory region.
Thus you se
Hi Michael,
Thank you for good advice, you are right. When I added new range above
4GB in _CRS the problem has gone.
QWordMemory (ResourceProducer, PosDecode, MinFixed, MaxFixed,
NonCacheable, ReadWrite,
0x, // Address Space Granularity
Hi,
>> PCI: map device bus 0, bfd 0x28
>> bar 0, addr febe, size 1 [mem]
>> bar 1, addr 0, size 2000 [mem]
>
> Somehow seabios didn't recognise the bar correctly it seems (both 512
> and 256 MB cases look the same). For the 256 MB case seabios should
> have mapped the bar @ 0xe
Hi,
> Ok Here are logs the faulty device is: 00:05.0.
> In the first case the BAR1 size is 512MB and it fails in Windows (Linux
> is fine, the kernel enumerates the bus and assigns the resource above 4GB),
> In the second case the BAR1 size is 256M and works fine.
> === PCI new allocation pass
On Thu, Dec 01, 2011 at 06:49:54PM +1300, Alexey Korolev wrote:
> Isaku san,
>
> I've just added you to discussion.
> There are some issues with PCI 64bit support in Windows. Windows
> fails to assign the resource if it doesn't fit in first 4GB window.
>
> I really don't know why it happens.
> On
Isaku san,
I've just added you to discussion.
There are some issues with PCI 64bit support in Windows. Windows fails
to assign the resource if it doesn't fit in first 4GB window.
I really don't know why it happens.
One of the possibilities is related to lack of _DSM method in ACPI.
Another gu
On Wed, Nov 30, 2011 at 02:04:08PM +1300, Alexey Korolev wrote:
Hi,
We have got some issues with 64bit PCI devices support under Windows guests.
Windows fails to start any PCI devices with 64bit BARs when size
exceeds 512MB with error code 12 (can't allocate resources). In
other words it fails
On Wed, Nov 30, 2011 at 02:04:08PM +1300, Alexey Korolev wrote:
> Hi,
>
> We have got some issues with 64bit PCI devices support under Windows guests.
> Windows fails to start any PCI devices with 64bit BARs when size
> exceeds 512MB with error code 12 (can't allocate resources). In
> other words
Hi,
We have got some issues with 64bit PCI devices support under Windows guests.
Windows fails to start any PCI devices with 64bit BARs when size exceeds
512MB with error code 12 (can't allocate resources). In other words it
fails when the PCI memory region is located above 4GB.
I tried to in
18 matches
Mail list logo
