From: Alexander Graf <agraf@suse.de>
To: qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, pbonzini@redhat.com,
qemu-stable@nongnu.org, kvm@vger.kernel.org,
stuart.yoder@freescale.com
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH] kvm: Fix memory slot page alignment logic
Date: Fri, 07 Nov 2014 22:24:07 +0100 [thread overview]
Message-ID: <545D3877.1070900@suse.de> (raw)
In-Reply-To: <1415395125-18926-1-git-send-email-agraf@suse.de>
On 07.11.14 22:18, Alexander Graf wrote:
> Memory slots have to be page aligned to get entered into KVM. There
> is existing logic that tries to ensure that we pad memory slots that
> are not page aligned to the biggest region that would still fit in the
> alignment requirements.
>
> Unfortunately, that logic is broken. It tries to calculate the start
> offset based on the region size.
>
> Fix up the logic to do the thing it was intended to do and document it
> properly in the comment above it.
>
> With this patch applied, I can successfully run an e500 guest with more
> than 3GB RAM (at which point RAM starts overlapping subpage memory regions).
>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Alexander Graf <agraf@suse.de>
If everyone agrees that this patch does indeed do what the code is
intended to do (I think it's quite correct, to be 100% right it should
use getpagesize() rather than TARGET_PAGE_SIZE), this should go into 2.2
still.
Alex
next prev parent reply other threads:[~2014-11-07 21:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 21:18 [Qemu-devel] [PATCH] kvm: Fix memory slot page alignment logic Alexander Graf
2014-11-07 21:24 ` Alexander Graf [this message]
2014-11-10 12:31 ` Igor Mammedov
2014-11-10 13:16 ` Alexander Graf
2014-11-10 13:54 ` Paolo Bonzini
2014-11-10 13:55 ` Peter Maydell
2014-11-10 14:48 ` Alexander Graf
2014-11-10 13:55 ` Igor Mammedov
2014-11-10 14:47 ` Alexander Graf
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=545D3877.1070900@suse.de \
--to=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=stuart.yoder@freescale.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;
as well as URLs for NNTP newsgroup(s).