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
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 wor
o try?
Thanks,
Alexey
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
egion.
Do you have any ideas what can be done to solve this problem?
Regards,
Alexey
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 reso
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
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
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
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
2. Get a range toward the upper end of the memory, around 1<<40
Yes. This solution works great. And this is very simple as well. Just
wondering if it will be good as a complete solution?
I would have tried this first too ;)
Care to share the patches so we can review& merge them?
No worries.
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
HI,
Current version of Seabios is causing blue screen on Windows2003 when 64bit PCI
resource is present and occupies high memory.
BSOD Error code is: 0x00A5 (0x02, 0xfADF6A446880, 0x1,
0xFADFAA34690)
The issue is localized, it is related to presence of 64bit resource in _CRS
metho
Hi Kevin,
>Unfortunately, it's very difficult to debug acpi issues on Windows.
>Gerd's been on vacation this week - so, lets give him a chance to look
>at it when he gets back. If it can't be resolved, we'll need to
>revert the patch that broke Win2003.
Thank you for your reply.
Right - acpi iss
The 64bit range can be used only if BAR has PCI_BASE_ADDRESS_MEM_TYPE_64
attribute and the given region doesn't fit in first 4GB. The patch has been
tested on Linux and BSD guest OS's and it appears to work fine.
Signed-off-by Alexey Korolev
Hi,
> Hi.
> The current BAR allocation doesn't check overflow and some patches
> are floating around which aren't merged yet.
> There are several issues.
>
> - overflow check
> This should be fixed.
> Some patches are proposed. None hasn't been merged yet.
> Your patch also addresses this is
101 - 114 of 114 matches
Mail list logo
