Displaying 5 results from an estimated 5 matches for "virtio_balloon_free_page_vq_hdr".
2017 Dec 11
1
[PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled
...out without reading them, still a win.
> >
> >
>
> Since this poison value comes with the free page reporting feature, how
> about sending the poison value via the free_page_vq, along with the cmd id
> in the outbuf? That is, use the following interface:
>
> struct virtio_balloon_free_page_vq_hdr {
> bool page_poisoning;
> __virtio32 poison_value;
> __virtio32 cmd_id;
> }
Can we put the value in config space instead?
> We need "bool page_poisoning" because "poison_value=0" doesn't tell whether
> page poising is in use by the guest.
Ca...
2017 Dec 11
1
[PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled
...out without reading them, still a win.
> >
> >
>
> Since this poison value comes with the free page reporting feature, how
> about sending the poison value via the free_page_vq, along with the cmd id
> in the outbuf? That is, use the following interface:
>
> struct virtio_balloon_free_page_vq_hdr {
> bool page_poisoning;
> __virtio32 poison_value;
> __virtio32 cmd_id;
> }
Can we put the value in config space instead?
> We need "bool page_poisoning" because "poison_value=0" doesn't tell whether
> page poising is in use by the guest.
Ca...
2017 Dec 01
3
[PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled
On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote:
> The guest free pages should not be discarded by the live migration thread
> when page poisoning is enabled with PAGE_POISONING_NO_SANITY=n, because
> skipping the transfer of such poisoned free pages will trigger false
> positive when new pages are allocated and checked on the destination.
> This patch skips the reporting
2017 Dec 01
3
[PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled
On Wed, Nov 29, 2017 at 09:55:26PM +0800, Wei Wang wrote:
> The guest free pages should not be discarded by the live migration thread
> when page poisoning is enabled with PAGE_POISONING_NO_SANITY=n, because
> skipping the transfer of such poisoned free pages will trigger false
> positive when new pages are allocated and checked on the destination.
> This patch skips the reporting
2017 Dec 11
0
[PATCH v18 10/10] virtio-balloon: don't report free pages when page poisoning is enabled
...t discard them, host can send
> them out without reading them, still a win.
>
>
Since this poison value comes with the free page reporting feature, how
about sending the poison value via the free_page_vq, along with the cmd
id in the outbuf? That is, use the following interface:
struct virtio_balloon_free_page_vq_hdr {
bool page_poisoning;
__virtio32 poison_value;
__virtio32 cmd_id;
}
We need "bool page_poisoning" because "poison_value=0" doesn't tell
whether page poising is in use by the guest. PAGE_POISONING_ZERO sets
"page_poisoning=true, poisoning_value=0"...