From: Alex Ghiti <alex@ghiti.fr> To: Palmer Dabbelt <palmer@dabbelt.com> Cc: Paul Walmsley <paul.walmsley@sifive.com>, aou@eecs.berkeley.edu, jszhang@kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH -fixes] riscv: Fix PTDUMP output now BPF region moved back to module region Date: Thu, 8 Jul 2021 13:42:02 +0200 [thread overview] Message-ID: <b2922513-e542-d8c0-a29d-a8990d838479@ghiti.fr> (raw) In-Reply-To: <mhng-fe8bcaf3-d184-4584-99f5-6ea4b9144934@palmerdabbelt-glaptop> Le 7/07/2021 à 01:16, Palmer Dabbelt a écrit : > On Thu, 24 Jun 2021 05:17:21 PDT (-0700), alex@ghiti.fr wrote: >> BPF region was moved back to the region below the kernel at the end of >> the >> module region in commit 3a02764c372c ("riscv: Ensure BPF_JIT_REGION_START >> aligned with PMD size"), so reflect this change in kernel page table >> output. >> >> Signed-off-by: Alexandre Ghiti <alex@ghiti.fr> >> --- >> arch/riscv/mm/ptdump.c | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/arch/riscv/mm/ptdump.c b/arch/riscv/mm/ptdump.c >> index 0536ac84b730..22d6555d89dc 100644 >> --- a/arch/riscv/mm/ptdump.c >> +++ b/arch/riscv/mm/ptdump.c >> @@ -98,8 +98,8 @@ static struct addr_marker address_markers[] = { >> {0, "vmalloc() end"}, >> {0, "Linear mapping"}, >> #ifdef CONFIG_64BIT >> - {0, "Modules mapping"}, >> - {0, "Kernel mapping (kernel, BPF)"}, >> + {0, "Modules/BPF mapping"}, >> + {0, "Kernel mapping"}, >> #endif >> {-1, NULL}, >> }; > > Thanks, this is on for-next. As this fix was for 5.13, I add stable in cc. Cc: stable@vger.kernel.org # v5.13 > > _______________________________________________ > linux-riscv mailing list > linux-riscv@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-riscv
WARNING: multiple messages have this Message-ID (diff)
From: Alex Ghiti <alex@ghiti.fr> To: Palmer Dabbelt <palmer@dabbelt.com> Cc: Paul Walmsley <paul.walmsley@sifive.com>, aou@eecs.berkeley.edu, jszhang@kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org Subject: Re: [PATCH -fixes] riscv: Fix PTDUMP output now BPF region moved back to module region Date: Thu, 8 Jul 2021 13:42:02 +0200 [thread overview] Message-ID: <b2922513-e542-d8c0-a29d-a8990d838479@ghiti.fr> (raw) In-Reply-To: <mhng-fe8bcaf3-d184-4584-99f5-6ea4b9144934@palmerdabbelt-glaptop> Le 7/07/2021 à 01:16, Palmer Dabbelt a écrit : > On Thu, 24 Jun 2021 05:17:21 PDT (-0700), alex@ghiti.fr wrote: >> BPF region was moved back to the region below the kernel at the end of >> the >> module region in commit 3a02764c372c ("riscv: Ensure BPF_JIT_REGION_START >> aligned with PMD size"), so reflect this change in kernel page table >> output. >> >> Signed-off-by: Alexandre Ghiti <alex@ghiti.fr> >> --- >> arch/riscv/mm/ptdump.c | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/arch/riscv/mm/ptdump.c b/arch/riscv/mm/ptdump.c >> index 0536ac84b730..22d6555d89dc 100644 >> --- a/arch/riscv/mm/ptdump.c >> +++ b/arch/riscv/mm/ptdump.c >> @@ -98,8 +98,8 @@ static struct addr_marker address_markers[] = { >> {0, "vmalloc() end"}, >> {0, "Linear mapping"}, >> #ifdef CONFIG_64BIT >> - {0, "Modules mapping"}, >> - {0, "Kernel mapping (kernel, BPF)"}, >> + {0, "Modules/BPF mapping"}, >> + {0, "Kernel mapping"}, >> #endif >> {-1, NULL}, >> }; > > Thanks, this is on for-next. As this fix was for 5.13, I add stable in cc. Cc: stable@vger.kernel.org # v5.13 > > _______________________________________________ > linux-riscv mailing list > linux-riscv@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-riscv _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-07-08 11:42 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-24 12:17 [PATCH -fixes] riscv: Fix PTDUMP output now BPF region moved back to module region Alexandre Ghiti 2021-06-24 12:17 ` Alexandre Ghiti 2021-06-25 13:31 ` Jisheng Zhang 2021-06-25 13:31 ` Jisheng Zhang 2021-07-06 23:16 ` Palmer Dabbelt 2021-07-06 23:16 ` Palmer Dabbelt 2021-07-08 11:42 ` Alex Ghiti [this message] 2021-07-08 11:42 ` Alex Ghiti
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=b2922513-e542-d8c0-a29d-a8990d838479@ghiti.fr \ --to=alex@ghiti.fr \ --cc=aou@eecs.berkeley.edu \ --cc=jszhang@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=stable@vger.kernel.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: 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.