From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
Subject: Re: [PATCH v2] powerpc/mm: export current mmu mode info
Date: Tue, 27 Sep 2016 00:14:55 +0530 [thread overview]
Message-ID: <4586df3a-626d-0124-8dc2-cb658166f14d@linux.vnet.ibm.com> (raw)
In-Reply-To: <87y42i7ty4.fsf@concordia.ellerman.id.au>
Hi Michael/Aneesh,
Thanks for reviewing the patch..
On Friday 23 September 2016 04:40 PM, Michael Ellerman wrote:
> Hari Bathini <hbathini@linux.vnet.ibm.com> writes:
>
>> diff --git a/arch/powerpc/include/asm/mmu.h b/arch/powerpc/include/asm/mmu.h
>> index e2fb408..558987c 100644
>> --- a/arch/powerpc/include/asm/mmu.h
>> +++ b/arch/powerpc/include/asm/mmu.h
>> @@ -199,6 +199,21 @@ static inline void mmu_clear_feature(unsigned long feature)
>>
>> extern unsigned int __start___mmu_ftr_fixup, __stop___mmu_ftr_fixup;
>>
>> +/*
>> + * Possible MMU modes
>> + */
>> +#define MMU_MODE_NONE 0
>> +#define MMU_MODE_RADIX 1
>> +#define MMU_MODE_HASH 2
>> +#define MMU_MODE_HASH32 3
>> +#define MMU_MODE_NOHASH 4
>> +#define MMU_MODE_NOHASH32 5
> These are already defined in the same file:
>
> /*
> * MMU families
> */
> #define MMU_FTR_HPTE_TABLE ASM_CONST(0x00000001)
> #define MMU_FTR_TYPE_8xx ASM_CONST(0x00000002)
> #define MMU_FTR_TYPE_40x ASM_CONST(0x00000004)
> #define MMU_FTR_TYPE_44x ASM_CONST(0x00000008)
> #define MMU_FTR_TYPE_FSL_E ASM_CONST(0x00000010)
> #define MMU_FTR_TYPE_47x ASM_CONST(0x00000020)
> #define MMU_FTR_TYPE_RADIX ASM_CONST(0x00000040)
>
> And the values for the current CPU are in cur_cpu_spec->mmu_features.
I primarily tried to introduce this patch as crash tool doesn't have
access to
offset info (which is needed to access structure member mmu_features) early
in it's initialization process.
> So if you must export anything, make it that value, and hopefully the
> rest of the patch goes away.
On second thought, as long as we can get the vmemmap start address, for
which
we have a variable already, we can push finding of MMU type for later. I
may need
no kernel patch in that case. Working on patches for crash &
makedumpfile tools
accordingly. Will post a v3 only if that doesn't work out..
Thanks
Hari
prev parent reply other threads:[~2016-09-26 18:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 16:02 [PATCH v2] powerpc/mm: export current mmu mode info Hari Bathini
2016-09-22 16:21 ` Hari Bathini
2016-09-22 16:24 ` Aneesh Kumar K.V
2016-09-22 16:53 ` Hari Bathini
2016-09-23 4:44 ` Aneesh Kumar K.V
2016-09-23 6:18 ` Hari Bathini
2016-09-23 11:10 ` Michael Ellerman
2016-09-26 18:44 ` Hari Bathini [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=4586df3a-626d-0124-8dc2-cb658166f14d@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
/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).