From: Markus Armbruster <armbru@redhat.com>
To: Zhuangyanying <ann.zhuangyanying@huawei.com>
Cc: marcandre.lureau@redhat.com, pbonzini@redhat.com, mst@redhat.com,
arei.gonglei@huawei.com, qemu-devel@nongnu.org,
qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] ivshmem: Fix 64 bit memory bar configuration
Date: Thu, 17 Nov 2016 14:27:50 +0100 [thread overview]
Message-ID: <87bmxegrs9.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <1479385863-7648-1-git-send-email-ann.zhuangyanying@huawei.com> (Zhuangyanying's message of "Thu, 17 Nov 2016 20:31:03 +0800")
Zhuangyanying <ann.zhuangyanying@huawei.com> writes:
> From: Zhuang Yanying <ann.zhuangyanying@huawei.com>
>
> Device ivshmem property use64=0 is designed to make the device
> expose a 32 bit shared memory BAR instead of 64 bit one. The
> default is a 64 bit BAR, except pc-1.2 and older retain a 32 bit
> BAR. A 32 bit BAR can support only up to 1 GiB of shared memory.
>
> This worked as designed until commit 5400c02 accidentally flipped
> its sense: since then, we misinterpret use64=0 as use64=1 and vice
> versa. Worse, the default got flipped as well. Devices
> ivshmem-plain and ivshmem-doorbell are not affected.
>
> Fix by restoring the test of IVShmemState member not_legacy_32bit
> that got messed up in commit 5400c02. Also update its
> initialization for devices ivhsmem-plain and ivshmem-doorbell.
> Without that, they'd regress to 32 bit BARs.
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Zhuang Yanying <ann.zhuangyanying@huawei.com>
> Reviewed-by: Gonglei <arei.gonglei@huawei.com>
> Reviewed-by: Marc-Andr. Lureau <marcandre.lureau@redhat.com>
Commit message should not be indented, and Marc-André's name got
mangled. Both could be touched up on commit.
Thanks again for cleaning up my mess.
Reviewed-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2016-11-17 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 12:31 [Qemu-devel] [PATCH v3] ivshmem: Fix 64 bit memory bar configuration Zhuangyanying
2016-11-17 13:27 ` Markus Armbruster [this message]
2016-11-17 16:45 ` Michael S. Tsirkin
2016-11-18 15:27 ` Michael S. Tsirkin
2016-11-18 15:30 ` Michael S. Tsirkin
2016-11-18 17:30 ` Paolo Bonzini
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=87bmxegrs9.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=ann.zhuangyanying@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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.