All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Alexander Duyck <alexander.duyck@gmail.com>,
	Jason Wang <jasowang@redhat.com>,
	virtio-dev@lists.oasis-open.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [virtio-dev] Re: [PATCH] virtio-balloon: Disable free page hinting/reporting if page poison is disabled
Date: Fri, 17 Apr 2020 06:19:37 -0400	[thread overview]
Message-ID: <20200417061815-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1823d9be-d175-6cb5-0c7d-8a68d959a0d5@redhat.com>

On Fri, Apr 17, 2020 at 12:09:38PM +0200, David Hildenbrand wrote:
>  > What do you call "hinting ends" though? The fact we put
> > a page in the VQ is not a guarantee that it's been consumed
> > by the hypervisor.
> > 
> 
> I'd say hinting ends once the hypervisor sets FREE_PAGE_REPORT_S_DONE.

Can't find that one anywhere. what did I miss?



> > 
> > I think a strict definition is this:
> > - hint includes a command ID
> > - hint implies "page was unused at some point after guest reading command ID"
> > 
> > 
> > Hypervisor can use dirty tracking tricks to get from that to
> > "page is unused at the moment".
> > 
> >> Whereby X is
> >> currently assumed to be 0, correct?
> > 
> > 
> > 
> > Now we are talking about what's safe to do with the page.
> > 
> > If POISON flag is set by hypervisor but clear by guest,
> > or poison_val is 0, then it's clear it's safe to blow
> > away the page if we can figure out it's unused.
> > 
> > Otherwise, it's much less clear :)
> 
> Hah! Agreed :D
> 
> > 
> > 
> > 
> > I'll have to come back and re-read the rest next week, this
> > is complex stuff and I'm too rushed with other things today.
> 
> Yeah, I'm also loaded with other stuff. Maybe Alex has time to
> understand the details as well.
> 
> -- 
> Thanks,
> 
> David / dhildenb


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
	Alexander Duyck <alexander.duyck@gmail.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [virtio-dev] Re: [PATCH] virtio-balloon: Disable free page hinting/reporting if page poison is disabled
Date: Fri, 17 Apr 2020 06:19:37 -0400	[thread overview]
Message-ID: <20200417061815-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1823d9be-d175-6cb5-0c7d-8a68d959a0d5@redhat.com>

On Fri, Apr 17, 2020 at 12:09:38PM +0200, David Hildenbrand wrote:
>  > What do you call "hinting ends" though? The fact we put
> > a page in the VQ is not a guarantee that it's been consumed
> > by the hypervisor.
> > 
> 
> I'd say hinting ends once the hypervisor sets FREE_PAGE_REPORT_S_DONE.

Can't find that one anywhere. what did I miss?



> > 
> > I think a strict definition is this:
> > - hint includes a command ID
> > - hint implies "page was unused at some point after guest reading command ID"
> > 
> > 
> > Hypervisor can use dirty tracking tricks to get from that to
> > "page is unused at the moment".
> > 
> >> Whereby X is
> >> currently assumed to be 0, correct?
> > 
> > 
> > 
> > Now we are talking about what's safe to do with the page.
> > 
> > If POISON flag is set by hypervisor but clear by guest,
> > or poison_val is 0, then it's clear it's safe to blow
> > away the page if we can figure out it's unused.
> > 
> > Otherwise, it's much less clear :)
> 
> Hah! Agreed :D
> 
> > 
> > 
> > 
> > I'll have to come back and re-read the rest next week, this
> > is complex stuff and I'm too rushed with other things today.
> 
> Yeah, I'm also loaded with other stuff. Maybe Alex has time to
> understand the details as well.
> 
> -- 
> Thanks,
> 
> David / dhildenb

  reply	other threads:[~2020-04-17 10:19 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-16 19:30 [virtio-dev] [PATCH] virtio-balloon: Disable free page hinting/reporting if page poison is disabled Alexander Duyck
2020-04-16 19:30 ` Alexander Duyck
2020-04-16 22:13 ` [virtio-dev] " Michael S. Tsirkin
2020-04-16 22:13   ` Michael S. Tsirkin
2020-04-16 23:52   ` [virtio-dev] " Alexander Duyck
2020-04-16 23:52     ` Alexander Duyck
2020-04-17  6:28     ` [virtio-dev] " Michael S. Tsirkin
2020-04-17  6:28       ` Michael S. Tsirkin
2020-04-17  7:49       ` [virtio-dev] " David Hildenbrand
2020-04-17  7:49         ` David Hildenbrand
2020-04-17  8:50         ` Michael S. Tsirkin
2020-04-17  8:50           ` Michael S. Tsirkin
2020-04-17  9:07           ` [virtio-dev] " David Hildenbrand
2020-04-17  9:07             ` David Hildenbrand
2020-04-17  9:21             ` [virtio-dev] " Michael S. Tsirkin
2020-04-17  9:21               ` Michael S. Tsirkin
2020-04-17  9:51               ` [virtio-dev] " David Hildenbrand
2020-04-17  9:51                 ` David Hildenbrand
2020-04-17  9:59                 ` [virtio-dev] " Michael S. Tsirkin
2020-04-17  9:59                   ` Michael S. Tsirkin
2020-04-17 10:09                   ` [virtio-dev] " David Hildenbrand
2020-04-17 10:09                     ` David Hildenbrand
2020-04-17 10:19                     ` Michael S. Tsirkin [this message]
2020-04-17 10:19                       ` [virtio-dev] " Michael S. Tsirkin
2020-04-17 10:26                       ` David Hildenbrand
2020-04-17 10:26                         ` David Hildenbrand
2020-04-17 10:29                         ` [virtio-dev] " Michael S. Tsirkin
2020-04-17 10:29                           ` Michael S. Tsirkin
2020-04-17 10:31                           ` [virtio-dev] " David Hildenbrand
2020-04-17 10:31                             ` David Hildenbrand
2020-04-17 11:02                             ` [virtio-dev] " Michael S. Tsirkin
2020-04-17 11:02                               ` Michael S. Tsirkin
2020-04-17 11:18                               ` [virtio-dev] " David Hildenbrand
2020-04-17 11:18                                 ` David Hildenbrand
2020-04-17 16:22                     ` [virtio-dev] " Alexander Duyck
2020-04-17 16:22                       ` Alexander Duyck
2020-04-20 13:28                       ` [virtio-dev] " David Hildenbrand
2020-04-20 13:28                         ` David Hildenbrand
2020-04-20 18:32                         ` [virtio-dev] " Alexander Duyck
2020-04-20 18:32                           ` Alexander Duyck
2020-04-21  7:29                           ` [virtio-dev] " David Hildenbrand
2020-04-21  7:29                             ` David Hildenbrand
2020-04-21 15:05                             ` [virtio-dev] " Alexander Duyck
2020-04-21 15:05                               ` Alexander Duyck
2020-04-21 15:18                               ` [virtio-dev] " David Hildenbrand
2020-04-21 15:18                                 ` David Hildenbrand
2020-04-21 15:50                                 ` Alexander Duyck
2020-04-21 15:50                                   ` Alexander Duyck
2020-04-22 10:24                                   ` [virtio-dev] " David Hildenbrand
2020-04-22 10:24                                     ` David Hildenbrand
2020-04-22 15:49                                     ` [virtio-dev] " Alexander Duyck
2020-04-22 15:49                                       ` Alexander Duyck
2020-04-17  7:46 ` [virtio-dev] " David Hildenbrand
2020-04-17  7:46   ` 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=20200417061815-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=david@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.