From: Alexey Korolev <alexey.korolev@endace.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: sfd@endace.com, yamahata@valinux.co.jp, seabios@seabios.org,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [BUG] [Seabios] PCI 64bit BARs on Win2008 - unable to start the device. (ACPI lacks the _DSM method)
Date: Mon, 5 Dec 2011 17:29:13 +1300 [thread overview]
Message-ID: <4EDC4899.2080101@endace.com> (raw)
In-Reply-To: <4ED767DF.7060707@redhat.com>
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 see bar 1, addr 0 in seabios log.
Sorry that I haven't specified all this initially. I just want to make
64bit PCI bar working properly. Linux guests works correctly (except
early versions - not investigated this yet). At the moment I have some
issues with windows which relies on ACPI _CRS.
Thanks,
Alexey
> Hi,
>
>>> PCI: map device bus 0, bfd 0x28
>>> bar 0, addr febe0000, size 10000 [mem]
>>> bar 1, addr 0, size 20000000 [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 @ 0xe0000000.
> ... and it should also have figured it is prefetchable memory. Was pci
> config space messed up somehow? What does 'lspci -v' say once you've
> booted the machine with linux?
>
> What qemu version you are running?
> What kind of device is this?
> Emulated? Code somewhere?
> Or a real device passed through to the guest?
>
> cheers,
> Gerd
next prev parent reply other threads:[~2011-12-05 4:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 1:04 [Qemu-devel] [BUG] [Seabios] PCI 64bit BARs on Win2008 - unable to start the device. (ACPI lacks the _DSM method) Alexey Korolev
2011-11-30 7:49 ` Michael S. Tsirkin
2011-12-01 5:19 ` Alexey Korolev
2011-12-01 11:25 ` Gerd Hoffmann
2011-12-01 11:41 ` Gerd Hoffmann
2011-12-05 4:29 ` Alexey Korolev [this message]
2011-12-12 8:10 ` Gerd Hoffmann
2011-12-13 4:19 ` Alexey Korolev
2011-12-14 4:30 ` Alexey Korolev
2011-12-14 5:10 ` Kevin O'Connor
2011-12-15 8:48 ` Gerd Hoffmann
2011-12-16 4:41 ` Alexey Korolev
2011-12-16 9:23 ` Gerd Hoffmann
2011-12-01 5:49 ` Alexey Korolev
2011-12-01 10:17 ` Michael S. Tsirkin
2011-12-05 4:20 ` Alexey Korolev
2011-12-05 6:31 ` Michael S. Tsirkin
2011-12-06 4:23 ` Alexey Korolev
2011-12-13 11:11 ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2011-12-14 4:31 ` Alexey Korolev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EDC4899.2080101@endace.com \
--to=alexey.korolev@endace.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
--cc=sfd@endace.com \
--cc=yamahata@valinux.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).