Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	David Hildenbrand <david@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] Re: [virtio-dev] [PATCH v8 1/3] content: Document balloon feature free page hints
Date: Thu, 12 Nov 2020 08:45:01 +0100	[thread overview]
Message-ID: <20201112084501.491f3d6b.cohuck@redhat.com> (raw)
In-Reply-To: <CAKgT0UfT1Ubw1V6vTDmBsoVthH-oKhSe7+VxFmFifD3KM_mgAg@mail.gmail.com>

On Wed, 11 Nov 2020 14:09:23 -0800
Alexander Duyck <alexander.duyck@gmail.com> wrote:

> On Wed, Nov 11, 2020 at 10:03 AM Cornelia Huck <cohuck@redhat.com> wrote:
> >
> > On Wed, 16 Sep 2020 09:28:34 -0400
> > "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >  
> > > On Mon, Sep 14, 2020 at 08:13:55AM +0200, Cornelia Huck wrote:  
> > > > On Fri, 11 Sep 2020 08:11:15 -0700
> > > > Alexander Duyck <alexander.duyck@gmail.com> wrote:
> > > >  
> > > > > On Thu, Sep 10, 2020 at 10:28 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:  
> > > > > >
> > > > > > On 04.09.20 18:56, Alexander Duyck wrote:  
> > > > > > > On Fri, Sep 4, 2020 at 8:20 AM Jan Kiszka <jan.kiszka@siemens.com> wrote:  
> > > > > > >>
> > > > > > >> On 25.08.20 16:45, Alexander Duyck wrote:  
> > > >  
> > > > > > >>> @@ -5042,13 +5049,17 @@ \subsection{Feature bits}\label{sec:Device Types / Memory Balloon Device / Featu
> > > > > > >>>  VIRTIO_BALLOON_F_MUST_TELL_HOST is not negotiated.
> > > > > > >>>
> > > > > > >>>  \subsection{Device configuration layout}\label{sec:Device Types / Memory Balloon Device / Device configuration layout}
> > > > > > >>> -  Both fields of this configuration
> > > > > > >>> -  are always available.
> > > > > > >>> +  \field{num_pages} and \field{actual} are always available.
> > > > > > >>> +
> > > > > > >>> +  \field{free_page_hint_cmd_id} is available if
> > > > > > >>> +    VIRTIO_BALLOON_F_FREE_PAGE_HINT has been negotiated and is read-only by
> > > > > > >>> +    the driver.  
> > > > > > >>
> > > > > > >> This reads at least to me like "...if VIRTIO_BALLOON_F_FREE_PAGE_HINT
> > > > > > >> ... is read-only by the driver". I suspect you rather meant
> > > > > > >> "free_page_hint_cmd_id is read-only...". Maybe split up into two sentences?  
> > > > > > >
> > > > > > > Yes, the intention is:
> > > > > > > 1. free_page_hint_cmd_id is only available if
> > > > > > > VIRTIO_BALLOON_F_FREE_PAGE_HINT has been negotiated
> > > > > > > 2. free_page_hint_cmd_id is read only by the driver
> > > > > > >
> > > > > > > If needed I suppose we could break it up by splitting it into two
> > > > > > > sentences, or adding "the field" after the "and".
> > > > > > >  
> > > > > >
> > > > > > I'm fine with both options but please adjust this - on top (Michael just
> > > > > > opened the voting for this version again due to the formal typo in round 1).
> > > > > >
> > > > > > Jan  
> > > > >
> > > > > Since the patch set is being voted on is there a preferred method for
> > > > > making this sort of update? I'm just wondering if I should do an
> > > > > additional incremental patch, just submit a replacement for this
> > > > > patch, or make the change and resubmit the entire patch set?  
> > > >
> > > > I think doing an additional patch on top and then doing another vote on
> > > > that is the best way to handle this. (Or maybe it is minor enough to
> > > > simply merge the incremental patch?)  
> > >
> > > yes, this sounds good to me  
> >
> > Which one of the options, actually? I'd be happy to merge a proper
> > patch on top (which I'd consider a trivial fix.)  
> 
> I had submitted a 4/3 for this set that was meant to fix it, but
> looking it over I don't think it would apply cleanly as I think I had
> only applied the patch it fixed and didn't have the poison patch
> applied when I generated it. If you need I can resubmit that patch as
> a trivial fix since it is only a 2 line change.

Thanks, that would be great.

> 
> Thanks.
> 
> - Alex
> 


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/


  reply	other threads:[~2020-11-12  7:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-25 14:44 [virtio-comment] [PATCH v8 0/3] virtio-spec: Add documentation for recently added balloon features Alexander Duyck
2020-08-25 14:45 ` [virtio-comment] [PATCH v8 1/3] content: Document balloon feature free page hints Alexander Duyck
2020-09-04 15:19   ` [virtio-comment] Re: [virtio-dev] " Jan Kiszka
2020-09-04 16:56     ` Alexander Duyck
2020-09-11  5:28       ` Jan Kiszka
2020-09-11 15:11         ` Alexander Duyck
2020-09-14  6:13           ` Cornelia Huck
2020-09-14 19:44             ` [virtio-comment] [PATCH v8 4/3] content: Minor change to clarify free_page_hint_cmd_id Alexander Duyck
2020-09-15  6:56               ` [virtio-comment] " Cornelia Huck
2020-09-16 13:28             ` [virtio-comment] Re: [virtio-dev] [PATCH v8 1/3] content: Document balloon feature free page hints Michael S. Tsirkin
2020-11-11 18:03               ` Cornelia Huck
2020-11-11 22:09                 ` Alexander Duyck
2020-11-12  7:45                   ` Cornelia Huck [this message]
2020-11-12 22:58                     ` Alexander Duyck
2020-08-25 14:45 ` [virtio-comment] [PATCH v8 2/3] content: Document balloon feature page poison Alexander Duyck
2020-08-25 14:45 ` [virtio-comment] [PATCH v8 3/3] content: Document balloon feature free page reporting Alexander Duyck
2020-08-25 15:01 ` [virtio-comment] Re: [PATCH v8 0/3] virtio-spec: Add documentation for recently added balloon features Cornelia Huck
2020-08-25 20:40   ` Alexander Duyck
2020-09-01 14:34     ` Michael S. Tsirkin
2020-09-10 14:50       ` Alexander Duyck
2020-09-10 15:05         ` Cornelia Huck

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=20201112084501.491f3d6b.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=david@redhat.com \
    --cc=jan.kiszka@siemens.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