* [Qemu-devel] [Bug 1824744] [NEW] ivshmem device PCI device exposes wrong endianness on ppc64le
@ 2019-04-15 1:33 ` shawn via Qemu-devel
0 siblings, 0 replies; 5+ messages in thread
From: shawn @ 2019-04-15 1:33 UTC (permalink / raw)
To: qemu-devel
Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: ppc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Title:
ivshmem device PCI device exposes wrong endianness on ppc64le
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824744/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Qemu-devel] [Bug 1824744] [NEW] ivshmem device PCI device exposes wrong endianness on ppc64le
@ 2019-04-15 1:33 ` shawn via Qemu-devel
0 siblings, 0 replies; 5+ messages in thread
From: shawn via Qemu-devel @ 2019-04-15 1:33 UTC (permalink / raw)
To: qemu-devel; +Cc: shawn
Public bug reported:
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.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: ppc
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Title:
ivshmem device PCI device exposes wrong endianness on ppc64le
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824744/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Qemu-devel] [Bug 1824744] Re: ivshmem PCI device exposes wrong endianness on ppc64le
@ 2019-04-15 2:00 ` shawn via Qemu-devel
0 siblings, 0 replies; 5+ messages in thread
From: shawn @ 2019-04-15 2:00 UTC (permalink / raw)
To: qemu-devel
** Summary changed:
- ivshmem device PCI device exposes wrong endianness on ppc64le
+ ivshmem PCI device exposes wrong endianness on ppc64le
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Title:
ivshmem PCI device exposes wrong endianness on ppc64le
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824744/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Qemu-devel] [Bug 1824744] Re: ivshmem PCI device exposes wrong endianness on ppc64le
@ 2019-04-15 2:00 ` shawn via Qemu-devel
0 siblings, 0 replies; 5+ messages in thread
From: shawn via Qemu-devel @ 2019-04-15 2:00 UTC (permalink / raw)
To: qemu-devel; +Cc: shawn
** Summary changed:
- ivshmem device PCI device exposes wrong endianness on ppc64le
+ ivshmem PCI device exposes wrong endianness on ppc64le
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Title:
ivshmem PCI device exposes wrong endianness on ppc64le
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824744/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
* [Bug 1824744] Re: ivshmem PCI device exposes wrong endianness on ppc64le
2019-04-15 1:33 ` shawn via Qemu-devel
(?)
(?)
@ 2021-05-05 11:27 ` Thomas Huth
-1 siblings, 0 replies; 5+ messages in thread
From: Thomas Huth @ 2021-05-05 11:27 UTC (permalink / raw)
To: qemu-devel
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/168
** Changed in: qemu
Status: New => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #168
https://gitlab.com/qemu-project/qemu/-/issues/168
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1824744
Title:
ivshmem PCI device exposes wrong endianness on ppc64le
Status in QEMU:
Expired
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1824744/+subscriptions
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2021-05-05 11:44 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-04-15 1:33 [Qemu-devel] [Bug 1824744] [NEW] ivshmem device PCI device exposes wrong endianness on ppc64le shawn
2019-04-15 1:33 ` shawn via Qemu-devel
2019-04-15 2:00 ` [Qemu-devel] [Bug 1824744] Re: ivshmem " shawn
2019-04-15 2:00 ` shawn via Qemu-devel
2021-05-05 11:27 ` Thomas Huth
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.