From: Cornelia Huck <cohuck@redhat.com>
To: Taylor Stark <tstark@linux.microsoft.com>
Cc: virtio-comment@lists.oasis-open.org, grahamwo@microsoft.com,
benhill@microsoft.com, mst@redhat.com, pankaj.gupta@ionos.com,
Taylor Stark <tstark@microsoft.com>
Subject: Re: [virtio-comment] [PATCH 1/1] virtio-pmem: Support PCI BAR-relative addresses
Date: Fri, 23 Jul 2021 08:59:51 +0200 [thread overview]
Message-ID: <875yx17bx4.fsf@redhat.com> (raw)
In-Reply-To: <20210722232626.GA32055@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Thu, Jul 22 2021, Taylor Stark <tstark@linux.microsoft.com> wrote:
> On Thu, Jul 22, 2021 at 01:24:17PM +0200, Cornelia Huck wrote:
>> On Wed, Jul 21 2021, tstark@linux.microsoft.com wrote:
>>
>> > From: Taylor Stark <tstark@microsoft.com>
>> >
>> > Update the virtio-pmem RFC spec to add support for describing the pmem region
>> > via PCI BARs. Shared memory windows are used to accomplish this, similar to
>> > virtio-fs and virtio-gpu. 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.
>>
>> Given that we already have pmem support out there (even though the spec
>> has not been included yet, should this get a feature?
>
> I wasn't sure if we needed to handle backwards compatibility given that pmem
> hasn't been merged into the spec yet. If we do, then yes I think it makes sense
> to add a feature bit. How about VIRTIO_PMEM_F_SHMEM_REGION?
Sounds good to me.
>> Also, requirements belong in a normative section; it's better to just
>> describe textually what the driver needs to do here and split out the
>> normative statements.
>
> Will do (ditto for your other comments). Thanks for the suggestions. It's
> a learning process for me - had to go and lookup what normative meant.. :)
If you have any further questions (or any suggestions how we can make
this easier for newcomers), feel free to follow up :)
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 prev parent reply other threads:[~2021-07-23 7:00 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 [this message]
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=875yx17bx4.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 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.