From: Cornelia Huck <cohuck@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: virtio-comment@lists.oasis-open.org,
"Michael S. Tsirkin" <mst@redhat.com>,
David Hildenbrand <david@redhat.com>,
virtio-dev@lists.oasis-open.org, "Wang,
Wei W" <wei.w.wang@intel.com>
Subject: [virtio-comment] Re: [PATCH 1/3] content: Document balloon feature free page hints
Date: Mon, 11 May 2020 17:50:36 +0200 [thread overview]
Message-ID: <20200511175036.53640bfc.cohuck@redhat.com> (raw)
In-Reply-To: <CAKgT0UcE24vBfQZDpNNMh0FMAkAN0SyZzPMnfznmXbJth-fVYQ@mail.gmail.com>
On Mon, 11 May 2020 08:22:02 -0700
Alexander Duyck <alexander.duyck@gmail.com> wrote:
> On Mon, May 11, 2020 at 5:10 AM Cornelia Huck <cohuck@redhat.com> wrote:
> >
> > On Fri, 08 May 2020 10:16:22 -0700
> > Alexander Duyck <alexander.duyck@gmail.com> wrote:
> >
> > > From: Alexander Duyck <alexander.h.duyck@linux.intel.com>
> > >
> > > Free page hints allow the balloon driver to provide information on what
> > > pages are not currently in use so that we can avoid the cost of copying
> > > them in migration scenarios. Add a feature description for free page hints
> > > describing basic functioning and requirements.
> > >
> > > Signed-off-by: Alexander Duyck <alexander.h.duyck@linux.intel.com>
> > > ---
> > > content.tex | 128 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++---
> > > 1 file changed, 122 insertions(+), 6 deletions(-)
> > >
> >
>
> I've taken care of the spelling/grammar items pointed out. Will be
> fixed for next version.
>
> > > +hinting request.
> > > +
> > > +The driver SHOULD return pages for use once \field{free_page_hint_cmd_id}
> > > +reports a value of VIRTIO_BALLOON_CMD_ID_DONE.
> > > +
> > > +\devicenormative{\paragraph}{Free Page Hinting}{Device Types / Memory Balloon Device / Device Operation / Free Page Hinting}
> > > +
> > > +Normative statements in this section apply if the
> > > +VIRTIO_BALLOON_F_FREE_PAGE_HINT feature has been negotiated.
> > > +
> > > +The device MUST set \field{free_page_hint_cmd_id} to
> > > +VIRTIO_BALLOON_CMD_ID_STOP any time that the dirty pages for the given
> > > +guest are being recorded.
> > > +
> > > +The device MUST NOT reuse a command ID until it has received an output
> >
> > What does 'reuse' mean in this context? I would expect that it is
> > forbidden to do the following:
> > - device sets id in config space
> > - driver queues descriptor with id
> > - device changes id to anything other than the current id or the
> > reserved ids <== bad
> >
> > Maybe "The device MUST NOT change a command ID actively in use by the
> > driver until..." ?
>
> Actually what I was referring to was something more like:
> - device sets the ID <n> in config space
> - device sets the ID value to CMD_ID_STOP.
> - device set the ID value to <n> again.
>
> In order to be able to do that the driver has to reply indicating it
> has stopped reporting hints before we can go back and reuse <n>. The
> expectation is that the device will use <n+1> when it resumes.
>
I see. So what about
"The device MUST NOT set \field{free_page_hint_cmd_id} to a previously
used ID until after it has received an output descriptor containing
VIRTIO_BALLOON_CMD_ID_STOP from the driver." ?
(Also, is the sequence I mentioned above valid? What happens if the
driver continues queuing with the old id -- does the device ignore it?
Or does the device need to present STOP before presenting another id?)
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-11 15:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 17:16 [virtio-comment] [PATCH 0/3] virtio-spec: Add documentation for recently added balloon features Alexander Duyck
2020-05-08 17:16 ` [virtio-comment] [PATCH 1/3] content: Document balloon feature free page hints Alexander Duyck
2020-05-11 12:09 ` [virtio-comment] " Cornelia Huck
2020-05-11 15:22 ` Alexander Duyck
2020-05-11 15:50 ` Cornelia Huck [this message]
2020-05-08 17:16 ` [virtio-comment] [PATCH 2/3] content: Document balloon feature page poison Alexander Duyck
2020-05-11 12:25 ` [virtio-comment] " Cornelia Huck
2020-05-11 15:29 ` Alexander Duyck
2020-05-15 17:17 ` [virtio-comment] " David Hildenbrand
2020-05-15 18:38 ` Alexander Duyck
2020-05-08 17:16 ` [virtio-comment] [PATCH 3/3] content: Document balloon feature free page reporting Alexander Duyck
2020-05-11 12:36 ` [virtio-comment] " Cornelia Huck
2020-05-11 15:36 ` Alexander Duyck
2020-05-11 12:38 ` [virtio-comment] Re: [PATCH 0/3] virtio-spec: Add documentation for recently added balloon features Cornelia Huck
2020-05-11 12:44 ` David Hildenbrand
2020-05-11 15:51 ` Alexander Duyck
2020-05-15 17:06 ` Alexander Duyck
2020-05-15 17:08 ` David Hildenbrand
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=20200511175036.53640bfc.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