From: Avi Kivity <avi@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "K. Y. Srinivasan" <kys@microsoft.com>,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
andi@firstfloor.org
Subject: Re: [PATCH 2/2] Drivers: hv: Add Hyper-V balloon driver
Date: Wed, 10 Oct 2012 11:47:23 +0200 [thread overview]
Message-ID: <5075442B.80100@redhat.com> (raw)
In-Reply-To: <20121009124449.f54bf8cb.akpm@linux-foundation.org>
On 10/09/2012 09:44 PM, Andrew Morton wrote:
> On Sun, 7 Oct 2012 16:59:46 -0700
> "K. Y. Srinivasan" <kys@microsoft.com> wrote:
>
>> Add the basic balloon driver.
>
> hm, how many balloon drivers does one kernel need?
>
> Although I see that the great majority of this code is hypervisor-specific.
Much like each network driver is NIC specific.
You could think up a framework into which hypervisor specific balloon
drivers plug in, but you'll find that in each driver 85% of the code is
devoted to talking to the hypervisor, 15% is outdated comments, and the
rest is a call to alloc_pages() and a call to free_pages().
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-10 9:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 23:59 [PATCH 0/2] Drivers: hv K. Y. Srinivasan
2012-10-07 23:59 ` [PATCH 1/2] mm: Export vm_committed_as K. Y. Srinivasan
2012-10-07 23:59 ` [PATCH 2/2] Drivers: hv: Add Hyper-V balloon driver K. Y. Srinivasan
2012-10-08 0:45 ` Greg KH
2012-10-08 3:37 ` KY Srinivasan
2012-10-08 5:45 ` Rusty Russell
2012-10-08 14:53 ` KY Srinivasan
2012-10-09 19:44 ` Andrew Morton
2012-10-10 0:09 ` KY Srinivasan
2012-10-10 1:14 ` Andrew Morton
2012-10-10 2:26 ` KY Srinivasan
2012-10-10 23:34 ` Jeremy Fitzhardinge
2012-10-10 23:56 ` Andrew Morton
2012-10-11 8:05 ` Rusty Russell
2012-10-10 9:47 ` Avi Kivity [this message]
2012-10-08 0:43 ` [PATCH 1/2] mm: Export vm_committed_as Greg KH
2012-10-08 3:35 ` KY Srinivasan
2012-10-08 13:35 ` Greg KH
2012-10-08 13:45 ` KY Srinivasan
2012-10-09 19:47 ` Andrew Morton
2012-10-10 0:11 ` KY Srinivasan
2012-10-10 1:16 ` Andrew Morton
2012-10-10 3:18 ` KY Srinivasan
2012-11-03 14:09 ` KY Srinivasan
2012-11-05 21:44 ` Andrew Morton
2012-11-05 22:12 ` KY Srinivasan
2012-11-05 22:33 ` David Rientjes
2012-11-06 14:46 ` Michal Hocko
2012-11-08 22:01 ` KY Srinivasan
2012-11-08 22:05 ` Andrew Morton
2012-11-08 22:08 ` KY Srinivasan
2012-11-08 22:14 ` David Rientjes
2012-11-08 22:18 ` Andrew Morton
2012-11-06 9:05 ` Michal Hocko
2012-11-06 12:53 ` KY Srinivasan
2012-11-08 13:28 ` KY Srinivasan
2012-11-08 21:55 ` David Rientjes
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=5075442B.80100@redhat.com \
--to=avi@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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