From: Avi Kivity <avi@redhat.com>
To: Dmitry Torokhov <dtor@dtor-ws.eng.vmware.com>
Cc: Dmitry Torokhov <dtor@vmware.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pv-drivers@vmware.com" <pv-drivers@vmware.com>,
Alok Kataria <akataria@vmware.com>,
Shaileshkumar Jain <sajain@vmware.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [PATCH 4/4] Add VMware memory balloon driver
Date: Sun, 21 Mar 2010 11:19:15 +0200 [thread overview]
Message-ID: <4BA5E493.9050108@redhat.com> (raw)
In-Reply-To: <20100320195359.GA11536@dtor-ws.eng.vmware.com>
On 03/20/2010 09:54 PM, Dmitry Torokhov wrote:
>> So while I'd love to see other hypervisors adopt virtio, I think in this
>> case it makes more sense to have your own balloon driver.
>>
>>
> Fair enough. If this is a common sentiment we'll gladly prepare our
> standalone driver for submission.
>
It's also possible to split out a "balloon core" that can be shared. In
this case it isn't worth it however as there any user visible interfaces
and the shared code would amount to couple dozen lines or so.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-03-21 9:19 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
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 [this message]
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=4BA5E493.9050108@redhat.com \
--to=avi@redhat.com \
--cc=akataria@vmware.com \
--cc=dtor@dtor-ws.eng.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