From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: lcapitulino@redhat.com, amit.shah@redhat.com
Cc: lvivier@redhat.com, aarcange@redhat.com, drjones@redhat.com,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Ballooning on TPS!=HPS hosts
Date: Thu, 31 Mar 2016 19:00:24 +0100 [thread overview]
Message-ID: <20160331180024.GN2265@work-vm> (raw)
Hi,
I was reading the balloon code and am confused as to how/if ballooning
works on hosts where the host page size is larger than the
target page size.
static void balloon_page(void *addr, int deflate)
{
#if defined(__linux__)
if (!qemu_balloon_is_inhibited() && (!kvm_enabled() ||
kvm_has_sync_mmu())) {
qemu_madvise(addr, TARGET_PAGE_SIZE,
deflate ? QEMU_MADV_WILLNEED : QEMU_MADV_DONTNEED);
}
#endif
}
The virtio-balloon code only does stuff through ballon_page,
and an madvise DONTNEED should fail if you try and do it on
a size smaller than the host page size. So does ballooning work on
Power/ARM?
Am I misunderstanding this?
Of course looking at the above we won't actually generate an error since
we don't check the return of qemu_madvise.
We have three sizes:
a) host page size
b) target page size
c) VIRTIO_BALLOON_PFN_SHIFT
c == 12 (4k) for everyone
1) I think the virtio-balloon code needs to coallesce adjecent requests
and call balloon_page on whole chunks at once passing a length.
2) why does balloon_page use TARGET_PAGE_SIZE, ignoring anything else
shouldn't it be 1 << VIRTIO_BALLOON_PFN_SHIFT ?
3) I'm guessing the guest kernel doesn't know the host page size, so
how can it know what size chunks of balloon to work in?
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next reply other threads:[~2016-03-31 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 18:00 Dr. David Alan Gilbert [this message]
2016-04-01 10:52 ` [Qemu-devel] Ballooning on TPS!=HPS hosts Amit Shah
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=20160331180024.GN2265@work-vm \
--to=dgilbert@redhat.com \
--cc=aarcange@redhat.com \
--cc=amit.shah@redhat.com \
--cc=drjones@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).