Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: tstark@linux.microsoft.com
To: virtio-comment@lists.oasis-open.org
Cc: grahamwo@microsoft.com, benhill@microsoft.com, mst@redhat.com,
	pankaj.gupta@ionos.com, Taylor Stark <tstark@microsoft.com>
Subject: [virtio-comment] [PATCH 0/1] virtio-pmem: Support PCI BAR-relative addresses
Date: Wed, 21 Jul 2021 13:59:38 -0700	[thread overview]
Message-ID: <20210721205939.20746-1-tstark@linux.microsoft.com> (raw)

From: Taylor Stark <tstark@microsoft.com>

This patch updates the virtio-pmem spec to add support for describing the pmem
region via PCI BARs. 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.

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

<Apologies for the resend - forgot to subscribe to virtio-comment so my original mail bounced>

Taylor Stark (1):
  virtio_pmem: Support PCI BAR-relative addresses

 virtio-pmem.tex | 22 +++++++++++++++++-----
 1 file changed, 17 insertions(+), 5 deletions(-)

-- 
2.31.0.vfs.0.1


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/


             reply	other threads:[~2021-07-21 21:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 20:59 tstark [this message]
2021-07-21 20:59 ` [virtio-comment] [PATCH 1/1] virtio-pmem: Support PCI BAR-relative addresses tstark
2021-07-22 11:24   ` Cornelia Huck
2021-07-22 23:26     ` Taylor Stark
2021-07-23  6:59       ` Cornelia Huck
2021-07-23  7:01       ` David Hildenbrand
2021-07-23 18:38         ` Taylor Stark
2021-07-23 19:18           ` David Hildenbrand
2021-07-27  4:21             ` Taylor Stark
2021-07-22 11:14 ` [virtio-comment] [PATCH 0/1] " Cornelia Huck
2021-07-22 11:30   ` Pankaj Gupta
2021-07-22 11:41     ` 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=20210721205939.20746-1-tstark@linux.microsoft.com \
    --to=tstark@linux.microsoft.com \
    --cc=benhill@microsoft.com \
    --cc=grahamwo@microsoft.com \
    --cc=mst@redhat.com \
    --cc=pankaj.gupta@ionos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox