From: tstark@linux.microsoft.com
To: virtio-comment@lists.oasis-open.org
Cc: grahamwo@microsoft.com, benhill@microsoft.com,
tstark@microsoft.com, pankaj.gupta.linux@gmail.com
Subject: [virtio-comment] [PATCH v5 0/1] virtio-pmem: Support describing pmem as shared memory region
Date: Wed, 10 Nov 2021 10:55:54 -0800 [thread overview]
Message-ID: <20211110185555.190-1-tstark@linux.microsoft.com> (raw)
From: Taylor Stark <tstark@microsoft.com>
Changes from v4 [1]:
- Clarified which fields of virtio_pmem_config are valid depending on shared
memory feature negotiation (suggested by Cornelia Huck).
Changes from v3 [1]:
- Rebased onto master now that the base virtio-pmem spec has been merged.
Changes from v2:
- Incorporated suggestions from Cornelia Huck on rewording driver initialization.
Changes from v1:
- Added in a feature bit (VIRTIO_PMEM_F_SHMEM_REGION) for controlling how the
device indicates the guest physical address ranges to the driver. This feature
directly affects control flow of the driver, since it seemed weird to have
the driver indicate support for shared memory regions, and then needing
to include an enum (or similar) informing the driver how the device
indicated guest physical address ranges. If devices want to indicate the
ranges as guest absolute addresses, they can skip negotiating the feature.
- The linux driver implementation has been updated and tested, but I'm holding
off on posting the patches to get some feedback on the new approach.
- Moved some changes to proper subsections (normative subsections).
[1] https://lists.oasis-open.org/archives/virtio-comment/202111/msg00004.html
---
This patch updates the virtio-pmem spec to add support for describing the pmem
region as a shared memory region. This is required to support virtio-pmem in
Hyper-V, since Hyper-V only allows PCI devices to operate on memory ranges
defined via BARs. When using the virtio PCI transport, shared memory regions
are described via PCI BARs.
As virtio-pmem hasn't been added to the virtio spec yet (see this issue [1]),
this patch is based off the RFC spec [2]. The linux driver implementation has
been posted at [3].
[1] https://github.com/oasis-tcs/virtio-spec/issues/78
[2] https://lists.oasis-open.org/archives/virtio-dev/201903/msg00083.html
[3] https://lore.kernel.org/nvdimm/20210715223505.GA29329@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net
Taylor Stark (1):
virtio-pmem: Support describing pmem as shared memory region
conformance.tex | 14 ++++++++++++--
virtio-pmem.tex | 40 +++++++++++++++++++++++++++++++++-------
2 files changed, 45 insertions(+), 9 deletions(-)
--
2.33.0.vfs.0.0
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next reply other threads:[~2021-11-10 18:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 18:55 tstark [this message]
2021-11-10 18:55 ` [virtio-comment] [PATCH v5 1/1] virtio-pmem: Support describing pmem as shared memory region tstark
2021-11-11 10:52 ` Cornelia Huck
2021-11-11 18:17 ` Taylor Stark
2021-11-23 16:42 ` Stefan Hajnoczi
2021-11-23 16:49 ` Cornelia Huck
2021-11-24 15:36 ` Stefan Hajnoczi
2021-11-16 0:31 ` [virtio-comment] " Pankaj Gupta
2021-11-18 17:37 ` [virtio-comment] " Halil Pasic
2021-11-21 8:08 ` Taylor Stark
2021-11-22 11:58 ` Cornelia Huck
2021-11-22 19:56 ` Halil Pasic
2021-11-23 11:10 ` Cornelia Huck
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=20211110185555.190-1-tstark@linux.microsoft.com \
--to=tstark@linux.microsoft.com \
--cc=benhill@microsoft.com \
--cc=grahamwo@microsoft.com \
--cc=pankaj.gupta.linux@gmail.com \
--cc=tstark@microsoft.com \
--cc=virtio-comment@lists.oasis-open.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 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.