From: Paul Mackerras <paulus@ozlabs•org>
To: Suraj Jitindar Singh <sjitindarsingh@gmail•com>
Cc: linuxppc-dev@ozlabs•org, benh@kernel•crashing.org,
mpe@ellerman•id.au, ruscur@russell•cc, sam.bobroff@au1•ibm.com
Subject: Re: [RFC NO-MERGE 1/2] arch/powerpc/prom_init: Parse the command line before calling CAS
Date: Thu, 23 Feb 2017 15:19:52 +1100 [thread overview]
Message-ID: <20170223041952.GA6330@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <1487657171-17260-1-git-send-email-sjitindarsingh@gmail.com>
On Tue, Feb 21, 2017 at 05:06:10PM +1100, Suraj Jitindar Singh wrote:
> CAS now requires the guest to tell the host whether it would like to use
Readers might not know what CAS is. It would be kind to reword this
as "On POWER9, the hypervisor requires the guest ... hash or radix MMU
at the time of calling ibm,client-architecture-support (CAS)".
> a hash or radix mmu. It is possible to disable radix by passing
> "disable_radix" on the command line. The next patch will add support for
> the new CAS format, thus we need to parse the command line before calling
> CAS so we can correctly represent which mmu we would like to use.
>
> Signed-off-by: Suraj Jitindar Singh <sjitindarsingh@gmail•com>
Reviewed-by: Paul Mackerras <paulus@ozlabs•org>
prev parent reply other threads:[~2017-02-23 4:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 6:06 [RFC NO-MERGE 1/2] arch/powerpc/prom_init: Parse the command line before calling CAS Suraj Jitindar Singh
2017-02-21 6:06 ` [RFC NO-MERGE 2/2] arch/powerpc/CAS: Update to new option-vector-5 format for CAS Suraj Jitindar Singh
2017-02-23 4:44 ` Paul Mackerras
2017-02-24 3:46 ` Suraj Jitindar Singh
2017-02-23 4:19 ` Paul Mackerras [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=20170223041952.GA6330@fergus.ozlabs.ibm.com \
--to=paulus@ozlabs$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mpe@ellerman$(echo .)id.au \
--cc=ruscur@russell$(echo .)cc \
--cc=sam.bobroff@au1$(echo .)ibm.com \
--cc=sjitindarsingh@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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