From: Cornelia Huck <cohuck@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Jean-Philippe Brucker <jean-philippe@linaro.org>,
virtio-dev@lists.oasis-open.org, eric.auger@redhat.com,
sebastien.boeuf@intel.com, kevin.tian@intel.com
Subject: [virtio-dev] Re: [PATCH] virtio-iommu: Rework the bypass feature
Date: Wed, 06 Oct 2021 08:45:12 +0200 [thread overview]
Message-ID: <877deq1wjr.fsf@redhat.com> (raw)
In-Reply-To: <20211005174532-mutt-send-email-mst@kernel.org>
On Tue, Oct 05 2021, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Tue, Oct 05, 2021 at 06:57:50PM +0200, Cornelia Huck wrote:
>> On Thu, Sep 30 2021, Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:
>> > \item[VIRTIO_IOMMU_F_BYPASS (3)]
>> > - When not attached to a domain, endpoints downstream of the IOMMU
>> > - can access the guest-physical address space.
>> > + This feature is deprecated.
>>
>> "and must not be negotiated." ?
>>
>> Not sure if we should add normative statements for that.
>
> We can't just make existing art de jure illegal.
>
> So SHOULD NOT and yes needs confirmance statements.
> Given documentation is already there why remove it?
Right, let's make that SHOULD NOT.
---------------------------------------------------------------------
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:[~2021-10-06 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-30 16:35 [PATCH] virtio-iommu: Rework the bypass feature Jean-Philippe Brucker
2021-10-05 16:57 ` [virtio-dev] " Cornelia Huck
2021-10-05 21:49 ` Michael S. Tsirkin
2021-10-06 6:45 ` Cornelia Huck [this message]
2021-10-06 12:53 ` [virtio-dev] " Eric Auger
2021-10-07 17:46 ` Jean-Philippe Brucker
2021-10-31 15:50 ` Eric Auger
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=877deq1wjr.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=kevin.tian@intel.com \
--cc=mst@redhat.com \
--cc=sebastien.boeuf@intel.com \
--cc=virtio-dev@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