From: Peter Xu <peterx@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"yi.y.sun@linux.intel.com" <yi.y.sun@linux.intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mst@redhat.com" <mst@redhat.com>
Subject: Re: [PATCH V2 1/4] intel-iommu: don't warn guest errors when getting rid2pasid entry
Date: Thu, 21 Apr 2022 20:13:15 -0400 [thread overview]
Message-ID: <YmHzG4/pAqD9MLE1@xz-m1.local> (raw)
In-Reply-To: <CACGkMEt9J6Jcy7+EmgFm-JTTqd82ONt_aOYRsxnTke2ZNSaA7A@mail.gmail.com>
On Wed, Mar 30, 2022 at 04:36:36PM +0800, Jason Wang wrote:
> > If not, do we want to apply this version scheme only when it
> > reaches the production quality or also in the experimental phase?
>
> Yes. E.g if we think scalable mode is mature, we can enable 3.0.
Sorry to come back to the discussion late..
I'd say unless someone (or some organization) strongly ask for a stable
interface for scalable mode (better with some developer looking after it
along with the organization), until then we start with versioning.
Otherwise I hope we can be free to break the interface assuming things are
still evolving, just like the spec.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2022-04-22 0:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 5:54 [PATCH V2 0/4] PASID support for Intel IOMMU Jason Wang
2022-03-21 5:54 ` [PATCH V2 1/4] intel-iommu: don't warn guest errors when getting rid2pasid entry Jason Wang
2022-03-24 8:21 ` Tian, Kevin
2022-03-28 2:27 ` Jason Wang
2022-03-28 8:53 ` Yi Liu
2022-03-29 4:52 ` Jason Wang
2022-03-30 8:16 ` Tian, Kevin
2022-03-30 8:36 ` Jason Wang
2022-04-02 7:33 ` Tian, Kevin
2022-04-06 3:33 ` Jason Wang
2022-04-06 3:41 ` Tian, Kevin
2022-04-22 0:13 ` Peter Xu [this message]
2022-04-22 6:24 ` Jason Wang
2022-04-22 7:57 ` Michael S. Tsirkin
2022-03-21 5:54 ` [PATCH V2 2/4] intel-iommu: drop VTDBus Jason Wang
2022-04-22 1:17 ` Peter Xu
2022-04-22 6:26 ` Jason Wang
2022-04-22 12:55 ` Peter Xu
2022-03-21 5:54 ` [PATCH V2 3/4] intel-iommu: convert VTD_PE_GET_FPD_ERR() to be a function Jason Wang
2022-03-24 8:26 ` Tian, Kevin
2022-03-28 2:27 ` Jason Wang
2022-04-22 13:08 ` Peter Xu
2022-03-21 5:54 ` [PATCH V2 4/4] intel-iommu: PASID support Jason Wang
2022-03-24 8:53 ` Tian, Kevin
2022-03-28 2:31 ` Jason Wang
2022-03-28 6:47 ` Tian, Kevin
2022-03-29 4:46 ` Jason Wang
2022-03-30 8:00 ` Tian, Kevin
2022-03-30 8:32 ` Jason Wang
2022-04-02 7:27 ` Tian, Kevin
2022-04-06 3:31 ` Jason Wang
2022-04-22 15:03 ` Peter Xu
2022-04-23 16:51 ` Michael S. Tsirkin
2022-03-28 7:03 ` Tian, Kevin
2022-03-29 4:48 ` Jason Wang
2022-03-30 8:02 ` Tian, Kevin
2022-03-30 8:31 ` Jason Wang
2022-04-02 7:24 ` Tian, Kevin
2022-04-06 3:31 ` Jason Wang
2022-03-28 8:45 ` Yi Liu
2022-03-29 4:54 ` Jason Wang
2022-04-01 13:42 ` Yi Liu
2022-04-02 1:52 ` Jason Wang
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=YmHzG4/pAqD9MLE1@xz-m1.local \
--to=peterx@redhat.com \
--cc=jasowang@redhat.com \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yi.l.liu@intel.com \
--cc=yi.y.sun@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).