From: Stephen Warren <swarren@wwwdotorg.org>
To: Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc: sudeep.dutt@intel.com, ashutosh.dixit@intel.com,
gregkh@linuxfoundation.org, arnd@arndb.de,
linux-kernel@vger.kernel.org,
Vincent Whitchurch <rabinv@axis.com>,
"ABRAHAM, KISHON VIJAY" <kishon@ti.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
linux-ntb@googlegroups.com, Jon Mason <jdmason@kudzu.us>,
Dave Jiang <dave.jiang@intel.com>,
Allen Hubbe <allenbh@gmail.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/8] Virtio-over-PCIe on non-MIC
Date: Fri, 18 Jan 2019 16:49:16 -0700 [thread overview]
Message-ID: <e22d901d-f92f-90a4-eaa5-a350e3f817f1@wwwdotorg.org> (raw)
In-Reply-To: <20190116163253.23780-1-vincent.whitchurch@axis.com>
On 1/16/19 9:32 AM, Vincent Whitchurch wrote:
> The Virtio-over-PCIe framework living under drivers/misc/mic/vop implements a
> generic framework to use virtio between two Linux systems, given shared memory
> and a couple of interrupts. It does not actually require the Intel MIC
> hardware, x86-64, or even PCIe for that matter. This patch series makes it
> buildable on more systems and adds a loopback driver to test it without special
> hardware.
>
> Note that I don't have access to Intel MIC hardware so some testing of the
> patchset (especially the patch "vop: Use consistent DMA") on that platform
> would be appreciated, to ensure that the series does not break anything there.
So a while ago I took a look at running virtio over PCIe. I found virtio
basically had two parts:
1) The protocol used to enumerate which virtio devices exist, and
perhaps configure them.
2) The ring buffer protocol that actually transfers the data.
I recall that data transfer was purely based on simple shared memory and
interrupts, and hence could run over PCIe (e.g. via the PCIe endpoint
subsystem in the kernel) without issue.
However, the enumeration/configuration protocol requires the host to be
able to do all kinds of strange things that can't possibly be emulated
over PCIe; IIRC the configuration data contains "registers" that when
written select the data other "registers" access. When the virtio device
is exposed by a hypervisor, and all the accesses are emulated
synchronously through a trap, this is easy enough to implement. However,
if the two ends of this configuration parsing are on different ends of a
PCIe bus, there's no way this can work.
Are you thinking of doing something different for
enumeration/configuration, and just using the virtio ring buffer
protocol over PCIe?
I did post asking about this quite a while back, but IIRC I didn't
receive much of a response. Yes, here it is:
> https://lists.linuxfoundation.org/pipermail/virtualization/2018-March/037276.html
"virtio over SW-defined/CPU-driven PCIe endpoint"
next prev parent reply other threads:[~2019-01-18 23:49 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 16:32 [PATCH 0/8] Virtio-over-PCIe on non-MIC Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 1/8] vop: Use %z for size_t Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 2/8] vop: Cast pointers to uintptr_t Vincent Whitchurch
2019-01-16 17:39 ` Joe Perches
2019-01-22 10:41 ` Greg KH
2019-01-16 16:32 ` [PATCH 3/8] vop: Add definition of readq/writeq if missing Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 4/8] vop: Allow building on more systems Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 5/8] vop: vringh: Do not crash if no DMA channel Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 6/8] vop: Fix handling of >32 feature bits Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 7/8] vop: Use consistent DMA Vincent Whitchurch
2019-01-16 16:32 ` [PATCH 8/8] vop: Add loopback Vincent Whitchurch
2019-01-16 17:07 ` [PATCH 0/8] Virtio-over-PCIe on non-MIC Arnd Bergmann
2019-01-17 10:54 ` Vincent Whitchurch
2019-01-17 12:39 ` Arnd Bergmann
2019-01-17 15:15 ` Christoph Hellwig
2019-01-17 15:19 ` Christoph Hellwig
2019-01-17 15:31 ` Arnd Bergmann
2019-01-17 15:19 ` Vincent Whitchurch
2019-01-17 15:21 ` Christoph Hellwig
2019-01-17 15:32 ` Vincent Whitchurch
2019-01-17 15:46 ` Christoph Hellwig
2019-01-17 16:18 ` Arnd Bergmann
2019-01-17 15:53 ` Arnd Bergmann
2019-01-17 16:26 ` Vincent Whitchurch
2019-01-17 16:34 ` Arnd Bergmann
2019-01-17 22:17 ` Logan Gunthorpe
2019-01-18 23:49 ` Stephen Warren [this message]
2019-01-21 16:25 ` Vincent Whitchurch
2019-01-22 10:45 ` Greg KH
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=e22d901d-f92f-90a4-eaa5-a350e3f817f1@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=allenbh@gmail.com \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=dave.jiang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jdmason@kudzu.us \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntb@googlegroups.com \
--cc=linux-pci@vger.kernel.org \
--cc=rabinv@axis.com \
--cc=sudeep.dutt@intel.com \
--cc=vincent.whitchurch@axis.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 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.