qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: zanghongyong@huawei.com
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Cc: wusongwei@huawei.com, hanweidong@huawei.com,
	louzhengwei@huawei.com, xiaowei.yang@huawei.com,
	zanghongyong@huawei.com, avi@redhat.com, cam@cs.ualberta.ca
Subject: [Qemu-devel] [PATCH v3 0/3] ivshmem: add a new PIO BAR4(Doorbell) besides MMIO BAR0 to reduce notification time
Date: Tue, 13 Dec 2011 09:42:45 +0800	[thread overview]
Message-ID: <1323740568-17692-1-git-send-email-zanghongyong@huawei.com> (raw)

From: Hongyong Zang <zanghongyong@huawei.com>

This patch series, adds a PIO BAR4 for guest notifying qemu. And the new
notification way of PIO BAR4 reduces 30% time in comparison with the original
MMIO BAR0 way.
Meantime, this patch adds a memory API named kvm_set_ioeventfd_pio_long which
is about ioeventfd for PIO long. Also, this patch introduces a new feature
named IVSHMEM_PIO_NOTIFY to make PIO BAR4 disappeared for compatible with
machine type pc-1.0 or blow.

Notes: the patch series are based on the former patch "[PATCH] ivshmem: fix
guest unable to start with ioeventfd".

In v3, some changes come from Avi and Cam's comments:
  -split the v2 patch to an infrastructure patch(memory API) and an ivshmem patch
  -change BAR3 to BAR4 so that the shared memory region could be made a 64-bit
    BAR(take BAR2 and BAR3)
  -make BAR4 disappeared for compatible with machine type pc-1.0 or blow
  -update the ivshmem spec


Hongyong Zang (3):
  memory: add a memory API about ioeventfd for PIO long
  ivshmem: add a new PIO BAR4(Doorbell) to reduce notification time
  ivshmem: update the spec

 docs/specs/ivshmem_device_spec.txt |    8 ++++++--
 hw/ivshmem.c                       |   34 ++++++++++++++++++++++++++++++++--
 hw/pc_piix.c                       |   28 ++++++++++++++++++++++++++++
 kvm-all.c                          |   23 +++++++++++++++++++++++
 kvm-stub.c                         |    5 +++++
 kvm.h                              |    1 +
 memory.c                           |   20 ++++++++++++++++----
 7 files changed, 111 insertions(+), 8 deletions(-)

             reply	other threads:[~2011-12-13  2:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13  1:42 zanghongyong [this message]
2011-12-13  1:42 ` [Qemu-devel] [PATCH v3 1/3] memory: add a memory API about ioeventfd for PIO long zanghongyong
2011-12-13  1:42 ` [Qemu-devel] [PATCH v3 2/3] ivshmem: add a new PIO BAR4(Doorbell) to reduce notification time zanghongyong
2011-12-13  1:42 ` [Qemu-devel] [PATCH v3 3/3] ivshmem: update the spec zanghongyong

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=1323740568-17692-1-git-send-email-zanghongyong@huawei.com \
    --to=zanghongyong@huawei.com \
    --cc=avi@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --cc=hanweidong@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=louzhengwei@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wusongwei@huawei.com \
    --cc=xiaowei.yang@huawei.com \
    /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 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).