From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"david.edmondson@oracle.com" <david.edmondson@oracle.com>,
"sburla@marvell.com" <sburla@marvell.com>,
Yishai Hadas <yishaih@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: Re: [virtio-comment] Re: [virtio-dev] Re: [PATCH v3 0/3] transport-pci: Introduce legacy registers access using AQ
Date: Sun, 11 Jun 2023 19:15:14 -0400 [thread overview]
Message-ID: <20230611191138-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54817172C727937B70E2FA3EDC57A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Sun, Jun 11, 2023 at 08:17:56PM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Sunday, June 11, 2023 4:09 PM
>
> > > > It's not conformant to that statement then :( It's a SHOULD which
> > > > means if you know exactly what you are doing, there could be exceptions.
> > > > In this case it's a SHOULD because it was added after 1.0 and we did
> > > > not find a way to negotiate this requirement since it's the feature negotiation
> > itself.
> > >
> > > True. May be in future such device can update the revision id.
> >
> > You can already change it but that doesn't imply anything at all, in 1.0 revisions
> > are vendor specific.
>
> I was suggesting that when such a fundamental change is done which cannot be communicated via features bit or before the reset,
> a new revision and attaching more advance/different behavior.
> This way driver knows what difference to expect for new revision.
But you don't know which revision do existing devices use:
Drivers MUST match any PCI Revision ID value.
we can come up with a mechanism, several ideas come to mind.
Before we bother, the actual need has to be understood.
--
MST
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/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Jason Wang <jasowang@redhat.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"david.edmondson@oracle.com" <david.edmondson@oracle.com>,
"sburla@marvell.com" <sburla@marvell.com>,
Yishai Hadas <yishaih@nvidia.com>,
Maor Gottlieb <maorg@nvidia.com>,
"virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
Shahaf Shuler <shahafs@nvidia.com>
Subject: [virtio-dev] Re: [virtio-comment] Re: [virtio-dev] Re: [PATCH v3 0/3] transport-pci: Introduce legacy registers access using AQ
Date: Sun, 11 Jun 2023 19:15:14 -0400 [thread overview]
Message-ID: <20230611191138-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54817172C727937B70E2FA3EDC57A@PH0PR12MB5481.namprd12.prod.outlook.com>
On Sun, Jun 11, 2023 at 08:17:56PM +0000, Parav Pandit wrote:
>
> > From: Michael S. Tsirkin <mst@redhat.com>
> > Sent: Sunday, June 11, 2023 4:09 PM
>
> > > > It's not conformant to that statement then :( It's a SHOULD which
> > > > means if you know exactly what you are doing, there could be exceptions.
> > > > In this case it's a SHOULD because it was added after 1.0 and we did
> > > > not find a way to negotiate this requirement since it's the feature negotiation
> > itself.
> > >
> > > True. May be in future such device can update the revision id.
> >
> > You can already change it but that doesn't imply anything at all, in 1.0 revisions
> > are vendor specific.
>
> I was suggesting that when such a fundamental change is done which cannot be communicated via features bit or before the reset,
> a new revision and attaching more advance/different behavior.
> This way driver knows what difference to expect for new revision.
But you don't know which revision do existing devices use:
Drivers MUST match any PCI Revision ID value.
we can come up with a mechanism, several ideas come to mind.
Before we bother, the actual need has to be understood.
--
MST
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-06-11 23:15 UTC|newest]
Thread overview: 164+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 20:36 [virtio-comment] [PATCH v3 0/3] transport-pci: Introduce legacy registers access using AQ Parav Pandit
2023-06-02 20:36 ` [virtio-dev] " Parav Pandit
2023-06-02 20:36 ` [virtio-comment] [PATCH v3 1/3] admin: Split opcode table rows with a line Parav Pandit
2023-06-02 20:36 ` [virtio-dev] " Parav Pandit
2023-06-02 20:36 ` [virtio-comment] [PATCH v3 2/3] transport-pci: Introduce legacy registers access commands Parav Pandit
2023-06-02 20:36 ` [virtio-dev] " Parav Pandit
2023-06-04 13:22 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 13:22 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 13:51 ` [virtio-comment] " Parav Pandit
2023-06-04 13:51 ` [virtio-dev] " Parav Pandit
2023-06-04 14:13 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 14:13 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 14:32 ` [virtio-comment] " Parav Pandit
2023-06-04 14:32 ` [virtio-dev] " Parav Pandit
2023-06-04 14:41 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 14:41 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 15:01 ` [virtio-comment] " Parav Pandit
2023-06-04 15:01 ` [virtio-dev] " Parav Pandit
2023-06-04 22:10 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 22:10 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 23:57 ` [virtio-comment] " Parav Pandit
2023-06-04 23:57 ` [virtio-dev] " Parav Pandit
2023-06-08 18:34 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 18:34 ` [virtio-dev] " Michael S. Tsirkin
2023-06-08 18:55 ` [virtio-comment] " Parav Pandit
2023-06-08 18:55 ` [virtio-dev] " Parav Pandit
2023-06-08 19:00 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 19:00 ` [virtio-dev] " Michael S. Tsirkin
2023-06-08 19:04 ` [virtio-comment] " Parav Pandit
2023-06-08 19:04 ` [virtio-dev] " Parav Pandit
2023-06-02 20:36 ` [virtio-comment] [PATCH v3 3/3] transport-pci: Add legacy register access conformance section Parav Pandit
2023-06-02 20:36 ` [virtio-dev] " Parav Pandit
2023-06-04 13:34 ` [virtio-comment] Re: [PATCH v3 0/3] transport-pci: Introduce legacy registers access using AQ Michael S. Tsirkin
2023-06-04 13:34 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 13:41 ` [virtio-comment] " Parav Pandit
2023-06-04 13:41 ` [virtio-dev] " Parav Pandit
2023-06-04 13:55 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 13:55 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 14:10 ` [virtio-comment] " Parav Pandit
2023-06-04 14:10 ` [virtio-dev] " Parav Pandit
2023-06-04 14:23 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 14:23 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 14:48 ` [virtio-comment] " Parav Pandit
2023-06-04 14:48 ` [virtio-dev] " Parav Pandit
2023-06-04 14:53 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 14:53 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 15:07 ` [virtio-comment] " Parav Pandit
2023-06-04 15:07 ` [virtio-dev] " Parav Pandit
2023-06-04 21:48 ` [virtio-comment] " Michael S. Tsirkin
2023-06-04 21:48 ` [virtio-dev] " Michael S. Tsirkin
2023-06-04 23:40 ` [virtio-comment] " Parav Pandit
2023-06-04 23:40 ` [virtio-dev] " Parav Pandit
2023-06-05 5:51 ` [virtio-comment] " Michael S. Tsirkin
2023-06-05 5:51 ` [virtio-dev] " Michael S. Tsirkin
2023-06-05 13:27 ` [virtio-comment] " Parav Pandit
2023-06-05 13:27 ` [virtio-dev] " Parav Pandit
2023-06-05 13:50 ` [virtio-comment] " Michael S. Tsirkin
2023-06-05 13:50 ` [virtio-dev] " Michael S. Tsirkin
2023-06-05 16:04 ` [virtio-comment] " Parav Pandit
2023-06-05 16:04 ` [virtio-dev] " Parav Pandit
2023-06-05 21:57 ` [virtio-comment] " Michael S. Tsirkin
2023-06-05 21:57 ` [virtio-dev] " Michael S. Tsirkin
2023-06-05 22:12 ` [virtio-comment] " Parav Pandit
2023-06-05 22:12 ` Parav Pandit
2023-06-06 11:56 ` [virtio-comment] " Michael S. Tsirkin
2023-06-06 11:56 ` Michael S. Tsirkin
2023-06-06 20:15 ` [virtio-comment] " Parav Pandit
2023-06-06 20:15 ` Parav Pandit
2023-06-07 2:27 ` [virtio-comment] " Jason Wang
2023-06-07 2:27 ` Jason Wang
2023-06-07 3:05 ` [virtio-comment] " Parav Pandit
2023-06-07 3:05 ` Parav Pandit
2023-06-07 6:54 ` [virtio-comment] " Jason Wang
2023-06-07 6:54 ` Jason Wang
2023-06-07 8:54 ` [virtio-comment] " Michael S. Tsirkin
2023-06-07 8:54 ` Michael S. Tsirkin
2023-06-08 14:38 ` [virtio-comment] " Parav Pandit
2023-06-08 14:38 ` Parav Pandit
2023-06-08 14:44 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 14:44 ` Michael S. Tsirkin
2023-06-08 14:53 ` [virtio-comment] " Parav Pandit
2023-06-08 14:53 ` Parav Pandit
2023-06-08 15:03 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 15:03 ` Michael S. Tsirkin
2023-06-08 15:16 ` [virtio-comment] " Parav Pandit
2023-06-08 15:16 ` Parav Pandit
2023-06-08 18:03 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 18:03 ` Michael S. Tsirkin
2023-06-08 18:11 ` [virtio-comment] " Parav Pandit
2023-06-08 18:11 ` Parav Pandit
2023-06-08 18:31 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 18:31 ` Michael S. Tsirkin
2023-06-08 19:00 ` [virtio-comment] " Parav Pandit
2023-06-08 19:00 ` Parav Pandit
2023-06-08 19:03 ` [virtio-comment] " Michael S. Tsirkin
2023-06-08 19:03 ` Michael S. Tsirkin
2023-06-08 19:12 ` [virtio-comment] " Parav Pandit
2023-06-08 19:12 ` Parav Pandit
2023-06-09 2:06 ` [virtio-comment] " Jason Wang
2023-06-09 2:06 ` Jason Wang
2023-06-09 2:29 ` [virtio-comment] " Parav Pandit
2023-06-09 2:29 ` Parav Pandit
2023-06-09 2:42 ` [virtio-comment] " Jason Wang
2023-06-09 2:42 ` Jason Wang
2023-06-09 2:53 ` [virtio-comment] " Parav Pandit
2023-06-09 2:53 ` Parav Pandit
2023-06-09 2:56 ` [virtio-comment] " Jason Wang
2023-06-09 2:56 ` Jason Wang
2023-06-09 2:58 ` [virtio-comment] " Parav Pandit
2023-06-09 2:58 ` [virtio-dev] " Parav Pandit
2023-06-09 3:02 ` Jason Wang
2023-06-09 3:02 ` [virtio-dev] " Jason Wang
2023-06-09 3:25 ` Parav Pandit
2023-06-09 3:25 ` [virtio-dev] " Parav Pandit
2023-06-09 6:27 ` Jason Wang
2023-06-09 6:27 ` [virtio-dev] " Jason Wang
2023-06-09 7:21 ` Michael S. Tsirkin
2023-06-09 7:21 ` [virtio-dev] " Michael S. Tsirkin
2023-06-09 17:11 ` Parav Pandit
2023-06-09 17:11 ` [virtio-dev] " Parav Pandit
2023-06-11 0:27 ` Michael S. Tsirkin
2023-06-11 0:27 ` [virtio-dev] " Michael S. Tsirkin
2023-06-11 2:08 ` Parav Pandit
2023-06-11 2:08 ` [virtio-dev] " Parav Pandit
2023-06-11 7:14 ` Michael S. Tsirkin
2023-06-11 7:14 ` [virtio-dev] " Michael S. Tsirkin
2023-06-11 12:54 ` Parav Pandit
2023-06-11 12:54 ` [virtio-dev] " Parav Pandit
2023-06-11 20:09 ` Michael S. Tsirkin
2023-06-11 20:09 ` [virtio-dev] " Michael S. Tsirkin
2023-06-11 20:17 ` Parav Pandit
2023-06-11 20:17 ` [virtio-dev] " Parav Pandit
2023-06-11 23:15 ` Michael S. Tsirkin [this message]
2023-06-11 23:15 ` [virtio-dev] " Michael S. Tsirkin
2023-06-26 3:46 ` Jason Wang
2023-06-26 3:46 ` [virtio-dev] " Jason Wang
2023-06-26 3:32 ` Jason Wang
2023-06-26 3:32 ` [virtio-dev] " Jason Wang
2023-06-26 3:51 ` Parav Pandit
2023-06-26 3:51 ` [virtio-dev] " Parav Pandit
2023-06-27 2:38 ` Jason Wang
2023-06-27 2:38 ` [virtio-dev] " Jason Wang
2023-06-27 3:17 ` Parav Pandit
2023-06-27 3:17 ` [virtio-dev] " Parav Pandit
2023-06-27 4:33 ` Jason Wang
2023-06-27 4:33 ` [virtio-dev] " Jason Wang
2023-06-26 3:50 ` Jason Wang
2023-06-26 3:50 ` [virtio-dev] " Jason Wang
2023-06-26 3:55 ` Parav Pandit
2023-06-26 3:55 ` [virtio-dev] " Parav Pandit
2023-06-26 10:49 ` Michael S. Tsirkin
2023-06-26 10:49 ` [virtio-dev] " Michael S. Tsirkin
2023-06-09 7:15 ` Michael S. Tsirkin
2023-06-09 7:15 ` Michael S. Tsirkin
2023-06-26 3:59 ` [virtio-comment] " Jason Wang
2023-06-26 3:59 ` Jason Wang
2023-06-26 4:04 ` [virtio-comment] " Parav Pandit
2023-06-26 4:04 ` [virtio-dev] " Parav Pandit
2023-06-27 2:42 ` Jason Wang
2023-06-27 2:42 ` [virtio-dev] " Jason Wang
2023-06-26 7:13 ` Michael S. Tsirkin
2023-06-26 7:13 ` Michael S. Tsirkin
2023-06-07 8:57 ` [virtio-comment] " Michael S. Tsirkin
2023-06-07 8:57 ` Michael S. Tsirkin
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=20230611191138-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=david.edmondson@oracle.com \
--cc=jasowang@redhat.com \
--cc=maorg@nvidia.com \
--cc=parav@nvidia.com \
--cc=sburla@marvell.com \
--cc=shahafs@nvidia.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yishaih@nvidia.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.