summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1824744
diff options
context:
space:
mode:
Diffstat (limited to 'results/scraper/launchpad-without-comments/1824744')
-rw-r--r--results/scraper/launchpad-without-comments/18247447
1 files changed, 7 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1824744 b/results/scraper/launchpad-without-comments/1824744
new file mode 100644
index 000000000..6dcc12701
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1824744
@@ -0,0 +1,7 @@
+ivshmem PCI device exposes wrong endianness on ppc64le
+
+On a ppc64le host with a ppc64le guest running on QEMU 3.1.0 when an ivshmem device is used, the ivshmem device appears to expose the wrong endianness for the values in BAR 0.
+
+For example, when the guest is assigned an ivshmem device ID of 1, the IVPosition register (u32, offset 8 in BAR 0) returns 0x1000000 instead of 0x1. I tested on an x86_64 machine and the IVPosition reads 0x1 as expected.
+
+It seems possible that there's a ppc64*==bigendian assumption somewhere that is erroneously affecting ppc64le.
\ No newline at end of file