public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Dmitry Torokhov <dtor@vmware.com>
Cc: linux-kernel@vger.kernel.org, pv-drivers@vmware.com,
	Alok Kataria <akataria@vmware.com>,
	Saileshkumar Jain <sajain@vmware.com>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 1/4] virtio-balloon: allow hypervisor refuse locking some pages
Date: Sat, 20 Mar 2010 15:01:40 +0200	[thread overview]
Message-ID: <4BA4C734.3060907@redhat.com> (raw)
In-Reply-To: <20100319204647.4418.23072.stgit@localhost.localdomain>

On 03/19/2010 10:46 PM, Dmitry Torokhov wrote:
> Some hypervisors may refuse our request to lock pages in certain
> circumstances. For example, VMware may decide that the target balloon
> size decreased since it was last communicated to the guest and thus
> current page should not be locked.
>
>
>   static struct virtio_driver virtio_balloon_driver = {
> diff --git a/include/linux/virtio_balloon.h b/include/linux/virtio_balloon.h
> index a50ecd1..4baad1c 100644
> --- a/include/linux/virtio_balloon.h
> +++ b/include/linux/virtio_balloon.h
> @@ -6,12 +6,16 @@
>   #include<linux/virtio_config.h>
>
>   /* The feature bitmap for virtio balloon */
> -#define VIRTIO_BALLOON_F_MUST_TELL_HOST	0 /* Tell before reclaiming pages */
> -#define VIRTIO_BALLOON_F_STATS_VQ	1 /* Memory Stats virtqueue */
> +#define VIRTIO_BALLOON_F_MUST_TELL_HOST		0 /* Tell before reclaiming pages */
> +#define VIRTIO_BALLOON_F_STATS_VQ		1 /* Memory Stats virtqueue */
> +#define VIRTIO_BALLOON_F_HOST_MAY_REFUSE	2 /* Host may refuse some pages */
>
>   /* Size of a PFN in the balloon interface. */
>   #define VIRTIO_BALLOON_PFN_SHIFT 12
>
> +#define VIRTIO_BALLOON_PFN_OK		0
> +#define VIRTIO_BALLOON_PFN_FAIL		1
> +
>   struct virtio_balloon_config
>   {
>   	/* Number of pages host wants Guest to give up. */
>    

Please update the virtio pci spec (can't find the URL - Rusty?) to 
reflect the protocol change.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2010-03-20 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 20:46 [RFC/PATCH 0/4] VMware balloon driver over virtio Dmitry Torokhov
2010-03-19 20:46 ` [PATCH 1/4] virtio-balloon: allow hypervisor refuse locking some pages Dmitry Torokhov
2010-03-20 13:01   ` Avi Kivity [this message]
2010-03-19 20:46 ` [PATCH 2/4] virtio-balloon: implement balloon reset Dmitry Torokhov
2010-03-19 20:46 ` [PATCH 3/4] x86: export vmware_platform() symbol Dmitry Torokhov
2010-03-19 20:47 ` [PATCH 4/4] Add VMware memory balloon driver Dmitry Torokhov
2010-03-20 13:10   ` Avi Kivity
2010-03-20 19:54     ` Dmitry Torokhov
2010-03-21  9:19       ` Avi Kivity

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=4BA4C734.3060907@redhat.com \
    --to=avi@redhat.com \
    --cc=akataria@vmware.com \
    --cc=dtor@vmware.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=rusty@rustcorp.com.au \
    --cc=sajain@vmware.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