From: Scott Wood <scottwood@freescale.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: <kvm-ppc@vger.kernel.org>, <kvm@vger.kernel.org>, <agraf@suse.de>
Subject: Re: [PATCH] KVM: PPC: Implement extension to report number of memslots
Date: Mon, 26 Oct 2015 18:47:54 -0500 [thread overview]
Message-ID: <1445903274.701.286.camel@freescale.com> (raw)
In-Reply-To: <20151026051512.GB7687@iris.ozlabs.ibm.com>
On Mon, 2015-10-26 at 16:15 +1100, Paul Mackerras wrote:
> On Fri, Oct 16, 2015 at 08:41:31AM +0200, Thomas Huth wrote:
> > Yes, we'll likely need this soon! 32 slots are not enough...
>
> Would anyone object if I raised the limit for PPC to 512 slots?
> Would that cause problems on embedded PPC, for instance?
I can't think of any reason why it would cause problems.
-Scott
next prev parent reply other threads:[~2015-10-27 0:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-16 4:57 [PATCH] KVM: PPC: Implement extension to report number of memslots Nikunj A Dadhania
2015-10-16 6:41 ` Thomas Huth
2015-10-26 5:15 ` Paul Mackerras
2015-10-26 23:47 ` Scott Wood [this message]
2015-10-27 13:22 ` Thomas Huth
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=1445903274.701.286.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=paulus@ozlabs.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).