From: Christophe LEROY <christophe.leroy@c-s.fr> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linuxppc-dev@lists.ozlabs.org Cc: linux-kernel@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>, linux-mm@kvack.org, Joel Stanley <joel@jms.id.au> Subject: Re: [PATCH 0/5] PPC32/ioremap: Use memblock API to check for RAM Date: Fri, 23 Feb 2018 09:01:17 +0100 [thread overview] Message-ID: <ca471c17-d2a7-e8e6-2d5a-a5a534e7e6d9@c-s.fr> (raw) In-Reply-To: <20180222121516.23415-1-j.neuschaefer@gmx.net> Le 22/02/2018 à 13:15, Jonathan Neuschäfer a écrit : > This patchset solves the same problem as my previous one[1] but follows > a rather different approach. Instead of implementing DISCONTIGMEM for > PowerPC32, I simply switched the "is this RAM" check in __ioremap_caller > to the existing page_is_ram function, and unified page_is_ram to search > memblock.memory on PPC64 and PPC32. > > The intended result is, as before, that my Wii can allocate the MMIO > range of its GPIO controller, which was previously not possible, because > the reserved memory hack (__allow_ioremap_reserved) didn't affect the > API in kernel/resource.c. > > Thanks to Christophe Leroy for reviewing the previous patchset. I tested your new serie, it doesn't break my 8xx so it is OK for me. Christophe > > [1]: https://www.spinics.net/lists/kernel/msg2726786.html > > Jonathan Neuschäfer (5): > powerpc: mm: Simplify page_is_ram by using memblock_is_memory > powerpc: mm: Use memblock API for PPC32 page_is_ram > powerpc/mm/32: Use page_is_ram to check for RAM > powerpc: wii: Don't rely on the reserved memory hack > powerpc/mm/32: Remove the reserved memory hack > > arch/powerpc/mm/init_32.c | 5 ----- > arch/powerpc/mm/mem.c | 12 +----------- > arch/powerpc/mm/mmu_decl.h | 1 - > arch/powerpc/mm/pgtable_32.c | 4 +--- > arch/powerpc/platforms/embedded6xx/wii.c | 14 +------------- > 5 files changed, 3 insertions(+), 33 deletions(-) >
WARNING: multiple messages have this Message-ID (diff)
From: Christophe LEROY <christophe.leroy@c-s.fr> To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>, linuxppc-dev@lists.ozlabs.org Cc: linux-kernel@vger.kernel.org, Michael Ellerman <mpe@ellerman.id.au>, linux-mm@kvack.org, Joel Stanley <joel@jms.id.au> Subject: Re: [PATCH 0/5] PPC32/ioremap: Use memblock API to check for RAM Date: Fri, 23 Feb 2018 09:01:17 +0100 [thread overview] Message-ID: <ca471c17-d2a7-e8e6-2d5a-a5a534e7e6d9@c-s.fr> (raw) In-Reply-To: <20180222121516.23415-1-j.neuschaefer@gmx.net> Le 22/02/2018 A 13:15, Jonathan NeuschA?fer a A(C)critA : > This patchset solves the same problem as my previous one[1] but follows > a rather different approach. Instead of implementing DISCONTIGMEM for > PowerPC32, I simply switched the "is this RAM" check in __ioremap_caller > to the existing page_is_ram function, and unified page_is_ram to search > memblock.memory on PPC64 and PPC32. > > The intended result is, as before, that my Wii can allocate the MMIO > range of its GPIO controller, which was previously not possible, because > the reserved memory hack (__allow_ioremap_reserved) didn't affect the > API in kernel/resource.c. > > Thanks to Christophe Leroy for reviewing the previous patchset. I tested your new serie, it doesn't break my 8xx so it is OK for me. Christophe > > [1]: https://www.spinics.net/lists/kernel/msg2726786.html > > Jonathan NeuschA?fer (5): > powerpc: mm: Simplify page_is_ram by using memblock_is_memory > powerpc: mm: Use memblock API for PPC32 page_is_ram > powerpc/mm/32: Use page_is_ram to check for RAM > powerpc: wii: Don't rely on the reserved memory hack > powerpc/mm/32: Remove the reserved memory hack > > arch/powerpc/mm/init_32.c | 5 ----- > arch/powerpc/mm/mem.c | 12 +----------- > arch/powerpc/mm/mmu_decl.h | 1 - > arch/powerpc/mm/pgtable_32.c | 4 +--- > arch/powerpc/platforms/embedded6xx/wii.c | 14 +------------- > 5 files changed, 3 insertions(+), 33 deletions(-) > -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2018-02-23 8:01 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-22 12:15 [PATCH 0/5] PPC32/ioremap: Use memblock API to check for RAM Jonathan Neuschäfer 2018-02-22 12:15 ` Jonathan Neuschäfer 2018-02-22 12:15 ` [PATCH 1/5] powerpc: mm: Simplify page_is_ram by using memblock_is_memory Jonathan Neuschäfer 2018-02-22 12:15 ` Jonathan Neuschäfer 2018-02-22 12:15 ` [PATCH 2/5] powerpc: mm: Use memblock API for PPC32 page_is_ram Jonathan Neuschäfer 2018-02-22 12:15 ` Jonathan Neuschäfer 2018-02-22 12:15 ` [PATCH 3/5] powerpc/mm/32: Use page_is_ram to check for RAM Jonathan Neuschäfer 2018-02-22 12:15 ` Jonathan Neuschäfer 2018-03-19 6:05 ` Michael Ellerman 2018-03-19 6:05 ` Michael Ellerman 2018-03-19 6:05 ` Michael Ellerman 2018-03-19 11:19 ` Michael Ellerman 2018-03-19 11:19 ` Michael Ellerman 2018-03-19 11:19 ` Michael Ellerman 2018-03-27 19:24 ` Jonathan Neuschäfer 2018-02-22 12:15 ` [PATCH 4/5] powerpc: wii: Don't rely on the reserved memory hack Jonathan Neuschäfer 2018-02-22 12:15 ` Jonathan Neuschäfer 2018-02-22 12:15 ` [PATCH 5/5] powerpc/mm/32: Remove " Jonathan Neuschäfer 2018-02-22 12:15 ` Jonathan Neuschäfer 2018-02-23 8:01 ` Christophe LEROY [this message] 2018-02-23 8:01 ` [PATCH 0/5] PPC32/ioremap: Use memblock API to check for RAM Christophe LEROY 2018-02-24 13:48 ` Jonathan Neuschäfer
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=ca471c17-d2a7-e8e6-2d5a-a5a534e7e6d9@c-s.fr \ --to=christophe.leroy@c-s.fr \ --cc=j.neuschaefer@gmx.net \ --cc=joel@jms.id.au \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.