qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v0 2/2] spapr: Abort when HTAB of requested size isn't allocated
Date: Thu, 24 Sep 2015 14:12:22 +1000	[thread overview]
Message-ID: <20150924041222.GQ15944@voom.fritz.box> (raw)
In-Reply-To: <20150924034358.GF16381@in.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1778 bytes --]

On Thu, Sep 24, 2015 at 09:13:58AM +0530, Bharata B Rao wrote:
> On Wed, Sep 23, 2015 at 01:29:51PM +1000, David Gibson wrote:
> > On Tue, Sep 22, 2015 at 09:09:49AM +0530, Bharata B Rao wrote:
> > > Terminate the guest when HTAB of requested size isn't allocated by
> > > the host.
> > > 
> > > When memory hotplug is attempted on a guest that has booted with
> > > less than requested HTAB size, the guest kernel will not be able
> > > to gracefully fail the hotplug request. This patch will ensure that
> > > we never end up in a situation where memory hotplug fails due to
> > > less than requested HTAB size.
> > > 
> > > Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > 
> > Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> > 
> > > ---
> > >  hw/ppc/spapr.c | 4 ++++
> > >  1 file changed, 4 insertions(+)
> > > 
> > > diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> > > index 4692122..66446af 100644
> > > --- a/hw/ppc/spapr.c
> > > +++ b/hw/ppc/spapr.c
> > > @@ -992,6 +992,10 @@ static void spapr_alloc_htab(sPAPRMachineState *spapr)
> > >  
> > >      if (shift > 0) {
> > >          /* Kernel handles htab, we don't need to allocate one */
> > > +        if (shift != spapr->htab_shift) {
> > > +            error_setg(&error_abort, "Failed to allocated requested HTAB size");
> 
> Do you think we should have a bit more verbose message here so that
> use knows what action to take after this abortion ? Like
> 
> "Failed to allocate requested HTAB size, try with lower maxmem"

Uh, yeah, I guess that's better.

-- 
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 --]

      reply	other threads:[~2015-09-24  4:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22  3:39 [Qemu-devel] [RFC PATCH v0 0/2] spapr: Abort when HTAB size requirement can't be met Bharata B Rao
2015-09-22  3:39 ` [Qemu-devel] [RFC PATCH v0 1/2] spapr: Allocate HTAB from machine init Bharata B Rao
2015-09-23  3:28   ` David Gibson
2015-09-24  3:41     ` Bharata B Rao
2015-09-24  4:12       ` David Gibson
2015-09-22  3:39 ` [Qemu-devel] [RFC PATCH v0 2/2] spapr: Abort when HTAB of requested size isn't allocated Bharata B Rao
2015-09-23  3:29   ` David Gibson
2015-09-24  3:43     ` Bharata B Rao
2015-09-24  4:12       ` 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=20150924041222.GQ15944@voom.fritz.box \
    --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).