From: Anthony Liguori <anthony@codemonkey.ws>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Marcelo Tosatti <marcelo@kvack.org>,
kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [PATCH] virtio-balloon: do not attempt to release more than available pages
Date: Mon, 10 Mar 2008 19:52:46 -0500 [thread overview]
Message-ID: <47D5D7DE.5010906@codemonkey.ws> (raw)
In-Reply-To: <200803111126.55421.rusty@rustcorp.com.au>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
Rusty Russell wrote:
> On Sunday 09 March 2008 06:06:38 Marcelo Tosatti wrote:
>
>> But making the driver robust against it seems sensate. I agree that
>> zeroing num_pages is hackish. What do you suggest?
>>
>
> OK, after more discussion on IRC, this seems like the correct thing to do.
>
> 1) Allow more than 2G of pages. It doesn't cost us much to break the 8TB
> barrier. This is an ABI change, so best to do this now.
>
I don't think there's a compelling need to break the ABI. If we truly
ever needed to break the 8TB barrier, we could simply introduce another
ballooning device. virtio_pci relies on PFNs fitting into a 32-bit
value so breaking the 8TB barrier here doesn't given it to us for free
anyway.
Plus, we've released an external drivers package. Breaking the ABI at
this stage is going to cause user confusion. Sure, the ABI isn't stable
until 2.6.25 ships but I do think we should have a more compelling
reason to do it if we truly have to.
> 2) Handle the case where we get nonsense from the host, which causes us to
> wrap around.
>
Here's my neither compiled nor tested version which should fix this
problem without breaking the ABI.
Regards,
Anthony Liguori
[-- Attachment #2: virtio:balloon_signage.patch --]
[-- Type: application/mbox, Size: 682 bytes --]
[-- Attachment #3: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #4: Type: text/plain, Size: 158 bytes --]
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
next prev parent reply other threads:[~2008-03-11 0:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 16:28 [PATCH] virtio-balloon: do not attempt to release more than available pages Marcelo Tosatti
2008-03-05 16:59 ` Avi Kivity
2008-03-05 18:12 ` Marcelo Tosatti
2008-03-05 18:13 ` Avi Kivity
2008-03-05 18:43 ` Anthony Liguori
2008-03-05 19:39 ` Marcelo Tosatti
2008-03-05 19:42 ` Anthony Liguori
2008-03-06 7:06 ` Avi Kivity
2008-03-05 18:42 ` Anthony Liguori
2008-03-05 22:39 ` Rusty Russell
2008-03-08 19:06 ` Marcelo Tosatti
2008-03-11 0:26 ` Rusty Russell
2008-03-11 0:52 ` Anthony Liguori [this message]
2008-03-11 11:54 ` Rusty Russell
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=47D5D7DE.5010906@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=kvm-devel@lists.sourceforge.net \
--cc=marcelo@kvack.org \
--cc=rusty@rustcorp.com.au \
/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