From: Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
To: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Volodymyr Babchuk" <Volodymyr_Babchuk@epam.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Roger Pau Monné" <roger.pau@citrix.com>, "Wei Liu" <wl@xen.org>,
"George Dunlap" <george.dunlap@citrix.com>,
"Julien Grall" <julien@xen.org>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Paul Durrant" <paul@xen.org>
Subject: [PATCH v2 0/4] vpci: first series in preparation for vpci on ARM
Date: Mon, 18 Jul 2022 21:15:39 +0000 [thread overview]
Message-ID: <20220718211521.664729-1-volodymyr_babchuk@epam.com> (raw)
Hello all,
While Oleksandr Andrushchenko is busy with more important matters, I
want to continue his work on preparing different Xen subsystems to
support PCI on ARM platform.
This patch series are mostly focused on next take of PCI locking
rework. It introduces reentrant read/write locking mechanism for
pcidevs, which will be immediatelly used to decouple readers and
writers in the PCI code. There are also some minor changes to a
related vpci code.
Oleksandr Andrushchenko (3):
pci: add rwlock to pcidevs_lock machinery
vpci: restrict unhandled read/write operations for guests
vpci: use pcidevs locking to protect MMIO handlers
Volodymyr Babchuk (1):
vpci: include xen/vmap.h to fix build on ARM
xen/arch/x86/hvm/vmsi.c | 46 +++++++++++++++++--------
xen/arch/x86/irq.c | 8 ++---
xen/arch/x86/msi.c | 16 ++++-----
xen/drivers/passthrough/pci.c | 65 +++++++++++++++++++++++++++++++----
xen/drivers/vpci/header.c | 24 +++++++++++--
xen/drivers/vpci/msi.c | 21 +++++++----
xen/drivers/vpci/msix.c | 55 +++++++++++++++++++++++++----
xen/drivers/vpci/vpci.c | 29 +++++++++++++---
xen/include/xen/pci.h | 11 +++++-
xen/include/xen/vpci.h | 2 +-
10 files changed, 223 insertions(+), 54 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-18 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 21:15 Volodymyr Babchuk [this message]
2022-07-18 21:15 ` [PATCH v2 1/4] pci: add rwlock to pcidevs_lock machinery Volodymyr Babchuk
2022-07-19 6:20 ` Wei Chen
2022-07-20 18:43 ` Volodymyr Babchuk
2022-07-18 21:15 ` [PATCH v2 2/4] vpci: restrict unhandled read/write operations for guests Volodymyr Babchuk
2022-07-18 21:15 ` [PATCH v2 3/4] vpci: use pcidevs locking to protect MMIO handlers Volodymyr Babchuk
2022-08-01 11:40 ` Jan Beulich
2022-08-09 20:33 ` Volodymyr Babchuk
2022-08-10 6:46 ` Jan Beulich
2022-07-18 21:15 ` [PATCH v2 4/4] vpci: include xen/vmap.h to fix build on ARM Volodymyr Babchuk
2022-07-19 6:07 ` Jan Beulich
2022-07-19 10:32 ` Volodymyr Babchuk
2022-07-19 10:40 ` Jan Beulich
2022-10-21 14:32 ` Oleksandr
2022-10-21 14:40 ` Henry Wang
2022-10-21 14:56 ` Bertrand Marquis
2022-10-22 0:50 ` Henry Wang
2022-10-24 6:34 ` Jan Beulich
2022-10-27 8:28 ` Roger Pau Monné
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=20220718211521.664729-1-volodymyr_babchuk@epam.com \
--to=volodymyr_babchuk@epam.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=paul@xen.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 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).