From: Elena Afanasova <eafanasova@gmail.com>
To: kvm@vger.kernel.org
Cc: stefanha@redhat.com, jag.raman@oracle.com,
elena.ufimtseva@oracle.com,
Elena Afanasova <eafanasova@gmail.com>
Subject: [RFC v2 0/4] Introduce MMIO/PIO dispatch file descriptors (ioregionfd)
Date: Thu, 28 Jan 2021 21:32:19 +0300 [thread overview]
Message-ID: <cover.1611850290.git.eafanasova@gmail.com> (raw)
This patchset introduces a KVM dispatch mechanism which can be used
for handling MMIO/PIO accesses over file descriptors without returning
from ioctl(KVM_RUN). This allows device emulation to run in another task
separate from the vCPU task.
This is achieved through KVM vm ioctl for registering MMIO/PIO regions and
a wire protocol that KVM uses to communicate with a task handling an
MMIO/PIO access.
TODOs:
* Implement KVM_EXIT_IOREGIONFD_FAILURE
* Add non-x86 arch support
* Add kvm-unittests
Elena Afanasova (4):
KVM: add initial support for KVM_SET_IOREGION
KVM: x86: add support for ioregionfd signal handling
KVM: add support for ioregionfd cmds/replies serialization
KVM: enforce NR_IOBUS_DEVS limit if kmemcg is disabled
arch/x86/kvm/Kconfig | 1 +
arch/x86/kvm/Makefile | 1 +
arch/x86/kvm/x86.c | 216 ++++++++++++++-
include/kvm/iodev.h | 14 +
include/linux/kvm_host.h | 34 +++
include/uapi/linux/ioregion.h | 32 +++
include/uapi/linux/kvm.h | 23 ++
virt/kvm/Kconfig | 3 +
virt/kvm/eventfd.c | 25 ++
virt/kvm/eventfd.h | 14 +
virt/kvm/ioregion.c | 479 ++++++++++++++++++++++++++++++++++
virt/kvm/ioregion.h | 15 ++
virt/kvm/kvm_main.c | 68 ++++-
13 files changed, 905 insertions(+), 20 deletions(-)
create mode 100644 include/uapi/linux/ioregion.h
create mode 100644 virt/kvm/eventfd.h
create mode 100644 virt/kvm/ioregion.c
create mode 100644 virt/kvm/ioregion.h
--
2.25.1
next reply other threads:[~2021-01-28 18:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 18:32 Elena Afanasova [this message]
2021-01-28 18:32 ` [RFC v2 2/4] KVM: x86: add support for ioregionfd signal handling Elena Afanasova
2021-01-30 16:58 ` Stefan Hajnoczi
2021-02-03 14:00 ` Elena Afanasova
2021-02-09 6:21 ` Jason Wang
2021-02-09 14:49 ` Stefan Hajnoczi
2021-02-10 19:06 ` Elena Afanasova
2021-02-09 6:26 ` Jason Wang
2021-01-28 18:32 ` [RFC v2 3/4] KVM: add support for ioregionfd cmds/replies serialization Elena Afanasova
2021-01-30 18:54 ` Stefan Hajnoczi
2021-02-03 14:10 ` Elena Afanasova
2021-01-28 18:32 ` [RFC v2 4/4] KVM: enforce NR_IOBUS_DEVS limit if kmemcg is disabled Elena Afanasova
2021-01-29 18:48 ` [RESEND RFC v2 1/4] KVM: add initial support for KVM_SET_IOREGION Elena Afanasova
2021-01-30 15:04 ` Stefan Hajnoczi
2021-02-04 13:03 ` Cornelia Huck
2021-02-05 18:39 ` Elena Afanasova
2021-02-08 11:49 ` Cornelia Huck
2021-02-08 6:21 ` Jason Wang
2021-02-09 14:59 ` Stefan Hajnoczi
2021-02-18 6:17 ` Jason Wang
2021-02-10 19:31 ` Elena Afanasova
2021-02-11 14:59 ` Stefan Hajnoczi
2021-02-17 23:05 ` Elena Afanasova
2021-02-18 6:22 ` Jason Wang
2021-02-18 6:20 ` Jason Wang
2021-01-30 14:56 ` [RFC v2 0/4] Introduce MMIO/PIO dispatch file descriptors (ioregionfd) Stefan Hajnoczi
2021-02-02 14:59 ` Stefan Hajnoczi
2021-02-08 6:02 ` Jason Wang
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=cover.1611850290.git.eafanasova@gmail.com \
--to=eafanasova@gmail.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=stefanha@redhat.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).