On 01.07.19 14:59, Ralf Ramsauer wrote:
Hi,
On 6/27/19 9:06 AM, Jan Kiszka wrote:
On 25.06.19 19:25, Ralf Ramsauer wrote:
Hi,
for the completeness sake: it's about ivshmem-net. The PCI device shows
up in the root cell and can be discovered via lspci, but the driver
fails while probing with
[17061.414176] ivshmem-net 0000:00:01.0: enabling device (0000 -> 0002)
[17061.420598] ivshmem-net 0000:00:01.0: invalid IVPosition -1
The register read-out failed. Maybe a mismatch between driver and
Jailhouse version: Which revisions are you using on both sides?
siemens/4.19-rt vs. jailhouse/next. Should match.
The bar_mask was copied over from the qemu demo. Other than that, the
only thing that changed is the bdf. We simply chose a free one on our
system.
The memory region behin ivshmem is high memory above 32-bit. I
instrumented and checked the code, but that shouldn't be a problem.
This is rather related to the MMIO register access. Check if reading that
ID/IVPos register actually triggers a VM exit. I suspect it doesn't.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/81c3353e-88f9-5908-ef76-bbc8f28c7613%40siemens.com.
For more options, visit https://groups.google.com/d/optout.
