qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [PATCH v2 0/2] ivshmem: fix misconfig of not_legacy_32bit
@ 2016-11-15 10:45 Zhuangyanying
  2016-11-15 10:45 ` [Qemu-devel] [PATCH v2 1/2] " Zhuangyanying
  2016-11-15 10:45 ` [Qemu-devel] [PATCH v2 2/2] ivshmem: set not_legacy_32bit to 1 for ivshmem_doorbell and ivshmem-plain Zhuangyanying
  0 siblings, 2 replies; 7+ messages in thread
From: Zhuangyanying @ 2016-11-15 10:45 UTC (permalink / raw)
  To: marcandre.lureau, armbru, pbonzini, mst, arei.gonglei
  Cc: qemu-devel, qemu-stable, ZhuangYanying

From: ZhuangYanying <ann.zhuangyanying@huawei.com>

Recently, I tested ivshmem, found that use64, that is not_legacy_32bit 
implementation is odd, or even the opposite.
Previous use64 = ivshmem_64bit = 1, then attr |= PCI_BASE_ADDRESS_MEM_TYPE_64, 
ivshmem support 1G and above packaged into bar2, presented to the virtual 
machine.
But after commit 5400c02, PCI_BASE_ADDRESS_MEM_TYPE_64 is configured 
while not_legacy_32bit = 0, that is the legacy model.

ZhuangYanying (2):
  hw/misc/ivshmem: fix misconfig of not_legacy_32bit
  hw/misc/ivshmem: set not_legacy_32bit to 1 for ivshmem_doorbell and
    ivshmem-plain

 hw/misc/ivshmem.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

-- 
1.8.3.1

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2016-11-17 10:55 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-15 10:45 [Qemu-devel] [PATCH v2 0/2] ivshmem: fix misconfig of not_legacy_32bit Zhuangyanying
2016-11-15 10:45 ` [Qemu-devel] [PATCH v2 1/2] " Zhuangyanying
2016-11-15 10:48   ` Marc-André Lureau
2016-11-17 10:55   ` Markus Armbruster
2016-11-15 10:45 ` [Qemu-devel] [PATCH v2 2/2] ivshmem: set not_legacy_32bit to 1 for ivshmem_doorbell and ivshmem-plain Zhuangyanying
2016-11-15 10:49   ` Marc-André Lureau
2016-11-16  0:50   ` Gonglei (Arei)

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).