From: Cornelia Huck <cohuck@redhat.com>
To: Pankaj Gupta <pankaj.gupta@ionos.com>
Cc: Taylor Stark <tstark@linux.microsoft.com>,
virtio-comment@lists.oasis-open.org, grahamwo@microsoft.com,
benhill@microsoft.com, "Michael S . Tsirkin" <mst@redhat.com>,
Taylor Stark <tstark@microsoft.com>
Subject: Re: [virtio-comment] [PATCH 0/1] virtio-pmem: Support PCI BAR-relative addresses
Date: Thu, 22 Jul 2021 13:41:21 +0200 [thread overview]
Message-ID: <87h7gm7ezi.fsf@redhat.com> (raw)
In-Reply-To: <CALzYo309tuJLLhVGdGc6RxOgQr5Y_ZtEsS=xG9Uu8G5_b42S7Q@mail.gmail.com>
On Thu, Jul 22 2021, Pankaj Gupta <pankaj.gupta@ionos.com> wrote:
> Hi Cornelia,
>
>> > 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].
>>
>> What's the general status of the pmem spec? I had pinged in the issue,
>> but I have not seen any progress.
>
> Appologies for missing your ping (As I was down for some time). I will
> try to post the
> virtio-pmem spec new version in coming week.
Thanks, that's good news!
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/
prev parent reply other threads:[~2021-07-22 11:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 20:59 [virtio-comment] [PATCH 0/1] virtio-pmem: Support PCI BAR-relative addresses tstark
2021-07-21 20:59 ` [virtio-comment] [PATCH 1/1] " 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 [this message]
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=87h7gm7ezi.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=benhill@microsoft.com \
--cc=grahamwo@microsoft.com \
--cc=mst@redhat.com \
--cc=pankaj.gupta@ionos.com \
--cc=tstark@linux.microsoft.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