From: Cornelia Huck <cohuck@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: David Hildenbrand <david@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, "Wang,
Wei W" <wei.w.wang@intel.com>
Subject: Re: [virtio-comment] [PATCH v3 2/3] content: Document balloon feature page poison
Date: Wed, 27 May 2020 08:06:10 +0200 [thread overview]
Message-ID: <20200527080610.100af355.cohuck@redhat.com> (raw)
In-Reply-To: <CAKgT0UfLwxomhqcNY2n-CsX7U_iMU-5UcyAKFVzmMaZtdJ722w@mail.gmail.com>
On Tue, 26 May 2020 20:20:21 -0700
Alexander Duyck <alexander.duyck@gmail.com> wrote:
> On Tue, May 26, 2020 at 8:38 AM Cornelia Huck <cohuck@redhat.com> wrote:
> >
> > On Tue, 26 May 2020 17:28:00 +0200
> > David Hildenbrand <david@redhat.com> wrote:
> >
> > > On 26.05.20 16:50, Alexander Duyck wrote:
> > > > On Tue, May 26, 2020 at 1:24 AM David Hildenbrand <david@redhat.com> wrote:
> >
> > > >> Still wondering what to do with free page hinting ... in the meantime
> > > >> I'll have a look at free page reporting :)
> > > >
> > > > The problem is it is already out there so I worry we wouldn't ever be
> > > > able to get rid of it. At most we could deprecate it, but we are still
> > > > stuck with it consuming bit resources and such.
> > >
> > > Yeah, that's not an issue, they will simply turn to dead bits with
> > > minimal documentation. I just don't see us fixing/supporting that
> > > feature, really. Let's see what @MST things when he has time to look
> > > into this.
> > >
> >
> > If free page hinting is broken enough that we don't want anybody to try
> > implementing it, we maybe could:
> >
> > - reserve the feature bit,
> > - say that the device SHOULD NOT offer it,
> > - say that the driver SHOULD NOT accept it?
> >
> > Would avoid conflicts, and tell implementors that they should not
> > bother. (We can then proceed to start deprecating the Linux/QEMU
> > implementations.)
>
> What I might do is just try to work around it for now. I might
> re-order my patches so that I can push the page poison and free page
> reporting bits with the free page hinting changes at the end of the
> set. That way if we decide to take a different route then we can
> always go back and change that later and it won't have an impact on
> the earlier changes.
Maybe:
- only add the hinting feature bit as reserved,
- document page poison and free page reporting,
- and then think about what to do with the hinting?
Just to make it clear that there is another feature bit out there; but
maybe that is overkill and we should just go ahead with patches 2/3 for
now.
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:[~2020-05-27 6:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 2:02 [virtio-comment] [PATCH v3 0/3] virtio-spec: Add documentation for recently added balloon features Alexander Duyck
2020-05-20 2:02 ` [virtio-comment] [PATCH v3 1/3] content: Document balloon feature free page hints Alexander Duyck
2020-05-20 2:02 ` [virtio-comment] [PATCH v3 2/3] content: Document balloon feature page poison Alexander Duyck
2020-05-20 9:27 ` David Hildenbrand
2020-05-20 16:25 ` Alexander Duyck
2020-05-26 8:24 ` David Hildenbrand
2020-05-26 14:50 ` Alexander Duyck
2020-05-26 15:28 ` David Hildenbrand
2020-05-26 15:38 ` Cornelia Huck
2020-05-27 3:20 ` Alexander Duyck
2020-05-27 6:06 ` Cornelia Huck [this message]
2020-05-27 6:14 ` [virtio-comment] Re: [virtio-dev] " Wei Wang
2020-05-27 12:08 ` David Hildenbrand
2020-05-20 2:02 ` [virtio-comment] [PATCH v3 3/3] content: Document balloon feature free page reporting Alexander Duyck
2020-05-26 9:05 ` David Hildenbrand
2020-05-26 14:42 ` Alexander Duyck
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=20200527080610.100af355.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=wei.w.wang@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