From: Thomas Huth <1824744@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1824744] Re: ivshmem PCI device exposes wrong endianness on ppc64le
Date: Wed, 05 May 2021 11:27:37 -0000 [thread overview]
Message-ID: <162021405787.5783.15632134332359390114.malone@wampee.canonical.com> (raw)
In-Reply-To: 155529202334.8409.17401063591999151604.malonedeb@wampee.canonical.com
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
prev parent reply other threads:[~2021-05-05 11:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
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=162021405787.5783.15632134332359390114.malone@wampee.canonical.com \
--to=1824744@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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 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.