From: Robert Jennings <rcj@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc: Support lower minimum entitlement for virtual processors
Date: Wed, 9 May 2012 10:56:39 -0500 [thread overview]
Message-ID: <20120509155639.GA12000@linux.vnet.ibm.com> (raw)
In-Reply-To: <1335763810.20866.38.camel@pasglop>
* Benjamin Herrenschmidt (benh@kernel.crashing.org) wrote:
> On Fri, 2012-03-23 at 16:22 -0500, Robert Jennings wrote:
> > This patch changes the architecture vector to advertise support for a
> > lower minimum virtual processor entitled capacity. The default
> > minimum without this patch is 10%, this patch specifies 5%. This will
> > allow 20 LPARs per CPU rather than only 10.
>
> Any reason why we don't just put 1% in there and thus don't have to
> change again when pHyp decides to lower their minimum ? :-)
>
> (Can you test that it works, ie, that pHyp doesn't barf if we put 1% and
> properly uses 5% in that case ?)
Thanks Ben, makes good sense.
I'm in the process of validating this and I'll post reply or a new
version of the patch when I get it completed.
--Rob Jennings
> > Signed-off-by: Robert Jennings <rcj@linux.vnet.ibm.com>
> > ---
> > arch/powerpc/kernel/prom_init.c | 8 ++++++--
> > 1 files changed, 6 insertions(+), 2 deletions(-)
> >
> > diff --git a/arch/powerpc/kernel/prom_init.c b/arch/powerpc/kernel/prom_init.c
> > index eca626e..3d882ea 100644
> > --- a/arch/powerpc/kernel/prom_init.c
> > +++ b/arch/powerpc/kernel/prom_init.c
> > @@ -689,6 +689,9 @@ static void __init early_cmdline_parse(void)
> > #define OV3_VMX 0x40 /* VMX/Altivec */
> > #define OV3_DFP 0x20 /* decimal FP */
> >
> > +/* Option vector 4: IBM PAPR implementation */
> > +#define OV4_MIN_ENT_CAP 0x05 /* minimum VP entitled capacity */
> > +
> > /* Option vector 5: PAPR/OF options supported */
> > #define OV5_LPAR 0x80 /* logical partitioning supported */
> > #define OV5_SPLPAR 0x40 /* shared-processor LPAR supported */
> > @@ -753,8 +756,9 @@ static unsigned char ibm_architecture_vec[] = {
> > OV3_FP | OV3_VMX | OV3_DFP,
> >
> > /* option vector 4: IBM PAPR implementation */
> > - 2 - 2, /* length */
> > + 3 - 2, /* length */
> > 0, /* don't halt */
> > + OV4_MIN_ENT_CAP, /* minimum VP entitled capacity */
> >
> > /* option vector 5: PAPR/OF options */
> > 13 - 2, /* length */
> > @@ -771,7 +775,7 @@ static unsigned char ibm_architecture_vec[] = {
> > * must match by the macro below. Update the definition if
> > * the structure layout changes.
> > */
> > -#define IBM_ARCH_VEC_NRCORES_OFFSET 100
> > +#define IBM_ARCH_VEC_NRCORES_OFFSET 101
> > W(NR_CPUS), /* number of cores supported */
> >
> > /* option vector 6: IBM PAPR hints */
>
>
prev parent reply other threads:[~2012-05-10 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 21:22 [PATCH] powerpc: Support lower minimum entitlement for virtual processors Robert Jennings
2012-04-30 5:30 ` Benjamin Herrenschmidt
2012-05-09 15:56 ` Robert Jennings [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=20120509155639.GA12000@linux.vnet.ibm.com \
--to=rcj@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.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).