From: David Gibson <david@gibson.dropbear.id.au>
To: Bharata B Rao <bharata@linux.vnet.ibm.com>
Cc: nfont@linux.vnet.ibm.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH v1 0/2] spapr: Abort when HTAB size requirement can't be met
Date: Tue, 29 Sep 2015 15:22:55 +1000 [thread overview]
Message-ID: <20150929052255.GN19428@voom.redhat.com> (raw)
In-Reply-To: <1443082968-20440-1-git-send-email-bharata@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1531 bytes --]
On Thu, Sep 24, 2015 at 01:52:46PM +0530, Bharata B Rao wrote:
> HTAB size is a factor of maximum memory size that is specified by maxmem=
> command line option. In cases where there is shortage of host memory, host
> will not be able to allocate contiguous memory for guest HTAB and will
> instead allocate a smaller HTAB. This usually is not a problem but when
> user starts hotplugging memory to the guest, we can run out of HTAB entries
> and hence memory hotplug fails. This failure should have been handled
> gracefully by the guest kernel, but currently it leads to guest kernel OOPS.
> This will eventually get fixed when the handling of memory hotplug is
> completely moved to kernel for PowerKVM.
>
> Prevent such kernel failure by refusing to boot the guest when requested
> HTAB size can't be allocated. However HTAB allocation happens in the
> reset path from where it is too late to abort. Hence this patchset
> moves the HTAB allocation to machine init and aborts if HTAB size
> requirement isn't met.
>
> This patchset applies against David Gibson's spapr-next. With this
> patchset, simple boot, reboot and migration tests pass with HV KVM guest.
> For PR KVM guest, boot and reboot tests were done since migration already
> appears broken for PR KVM.
This looks good. Applied to spapr-next
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2015-09-29 6:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 8:22 [Qemu-devel] [RFC PATCH v1 0/2] spapr: Abort when HTAB size requirement can't be met Bharata B Rao
2015-09-24 8:22 ` [Qemu-devel] [RFC PATCH v1 1/2] spapr: Allocate HTAB from machine init Bharata B Rao
2015-09-24 8:22 ` [Qemu-devel] [RFC PATCH v1 2/2] spapr: Abort when HTAB of requested size isn't allocated Bharata B Rao
2015-09-29 5:22 ` David Gibson [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=20150929052255.GN19428@voom.redhat.com \
--to=david@gibson.dropbear.id.au \
--cc=bharata@linux.vnet.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).