qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: Brijesh Singh <brijesh.singh@amd.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Jason Wang <jasowang@redhat.com>,
	Daniel Henrique Barboza <danielhb413@gmail.com>,
	qemu-devel@nongnu.org, Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [RFC PATCH 1/1] virtio: fix feature negotiation for ACCESS_PLATFORM
Date: Mon, 07 Feb 2022 16:21:31 +0100	[thread overview]
Message-ID: <87v8xqvh1g.fsf@redhat.com> (raw)
In-Reply-To: <20220207160516.2aead931.pasic@linux.ibm.com>

On Mon, Feb 07 2022, Halil Pasic <pasic@linux.ibm.com> wrote:

> On Mon, 07 Feb 2022 14:41:58 +0100
> Cornelia Huck <cohuck@redhat.com> wrote:

>> OTOH, the decision to make it mandatory is certainly sound, and covered
>> by the spec. As the driver must be prepared for the device failing to
>> accept FEATURES_OK, we can make it mandatory here -- we should just not
>> say that it is considered mandatory from a spec standpoint. The spec
>> allows to make it mandatory, and we make it mandatory in our
>> implementation.
>
> Right. Was never my intention to say that it is considered mandatory
> by the spec. I guess the spec considers it less optional than the
> run of the mill features.
>
> Should I change the first sentence to something like "Unlike most virtio
> features ACCESS_PATFORM is considered mandatory by QEMU, i.e. the driver
> must accept it if offered by the device."

If you do s/PATFORM/PLATFORM/ :), yes. That's a much shorter way of
expressing what I had been trying to argue in my reply :)



  reply	other threads:[~2022-02-07 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 16:45 [RFC PATCH 1/1] virtio: fix feature negotiation for ACCESS_PLATFORM Halil Pasic
2022-02-07 11:46 ` Daniel Henrique Barboza
2022-02-07 13:41   ` Cornelia Huck
2022-02-07 14:01     ` Daniel Henrique Barboza
2022-02-07 15:05     ` Halil Pasic
2022-02-07 15:21       ` Cornelia Huck [this message]
2022-02-07 15:42         ` Halil Pasic
2022-02-07 16:23       ` Michael S. Tsirkin
2022-02-07 14:46   ` Halil Pasic
2022-02-07 19:46     ` Daniel Henrique Barboza
2022-02-08  1:27       ` Halil Pasic

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=87v8xqvh1g.fsf@redhat.com \
    --to=cohuck@redhat.com \
    --cc=brijesh.singh@amd.com \
    --cc=danielhb413@gmail.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).