From: <Conor.Dooley@microchip.com> To: <xianting.tian@linux.alibaba.com>, <mick@ics.forth.gr>, <paul.walmsley@sifive.com>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <anup@brainfault.org>, <akpm@linux-foundation.org>, <wangkefeng.wang@huawei.com>, <rppt@kernel.org>, <david@redhat.com>, <wangborong@cdjrlc.com>, <twd2.me@gmail.com>, <seanjc@google.com>, <alex@ghiti.fr>, <petr.pavlu@suse.com>, <atishp@rivosinc.com> Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <jianghuaming.jhm@alibaba-inc.com>, <guoren@kernel.org>, <stable@kernel.org> Subject: Re: [PATCH v2] RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY Date: Mon, 16 May 2022 09:03:26 +0000 [thread overview] Message-ID: <2e62621a-1fb8-5de7-8d0e-e6c4019931a1@microchip.com> (raw) In-Reply-To: <e32a2228-2e2f-0da2-87e8-e364c0450dcd@linux.alibaba.com> On 16/05/2022 09:50, Xianting Tian wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Hi > > Could I get any comments for the v2 patch, thanks Looks like you have 3 Reviewed-bys already & there's only been one full working day since you sent the patch, probably just worth waiting a little for Palmer to get around to picking it up :) Thanks, Conor. > > 在 2022/5/12 下午2:09, Xianting Tian 写道: >> Commit 00ab027a3b82 ("RISC-V: Add kernel image sections to the resource tree") >> marked IORESOURCE_BUSY for reserved memory, which casued resource map >> failed in subsequent operations of related driver, so remove the >> IORESOURCE_BUSY flag. In order to prohibit userland mapping reserved >> memory, mark IORESOURCE_EXCLUSIVE for it. >> >> The code to reproduce the issue, >> dts: >> mem0: memory@a0000000 { >> reg = <0x0 0xa0000000 0 0x1000000>; >> no-map; >> }; >> >> &test { >> status = "okay"; >> memory-region = <&mem0>; >> }; >> >> code: >> np = of_parse_phandle(pdev->dev.of_node, "memory-region", 0); >> ret = of_address_to_resource(np, 0, &r); >> base = devm_ioremap_resource(&pdev->dev, &r); >> // base = -EBUSY >> >> Fixes: 00ab027a3b82 ("RISC-V: Add kernel image sections to the resource tree") >> Reported-by: Huaming Jiang <jianghuaming.jhm@alibaba-inc.com> >> Reviewed-by: Guo Ren <guoren@kernel.org> >> Reviewed-by: Nick Kossifidis <mick@ics.forth.gr> >> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com> >> --- >> arch/riscv/kernel/setup.c | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c >> index 834eb652a7b9..e0a00739bd13 100644 >> --- a/arch/riscv/kernel/setup.c >> +++ b/arch/riscv/kernel/setup.c >> @@ -189,7 +189,7 @@ static void __init init_resources(void) >> res = &mem_res[res_idx--]; >> >> res->name = "Reserved"; >> - res->flags = IORESOURCE_MEM | IORESOURCE_BUSY; >> + res->flags = IORESOURCE_MEM | IORESOURCE_EXCLUSIVE; >> res->start = __pfn_to_phys(memblock_region_reserved_base_pfn(region)); >> res->end = __pfn_to_phys(memblock_region_reserved_end_pfn(region)) - 1; >> >> @@ -214,7 +214,7 @@ static void __init init_resources(void) >> >> if (unlikely(memblock_is_nomap(region))) { >> res->name = "Reserved"; >> - res->flags = IORESOURCE_MEM | IORESOURCE_BUSY; >> + res->flags = IORESOURCE_MEM | IORESOURCE_EXCLUSIVE; >> } else { >> res->name = "System RAM"; >> res->flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; > > _______________________________________________ > 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: <Conor.Dooley@microchip.com> To: <xianting.tian@linux.alibaba.com>, <mick@ics.forth.gr>, <paul.walmsley@sifive.com>, <palmer@dabbelt.com>, <aou@eecs.berkeley.edu>, <anup@brainfault.org>, <akpm@linux-foundation.org>, <wangkefeng.wang@huawei.com>, <rppt@kernel.org>, <david@redhat.com>, <wangborong@cdjrlc.com>, <twd2.me@gmail.com>, <seanjc@google.com>, <alex@ghiti.fr>, <petr.pavlu@suse.com>, <atishp@rivosinc.com> Cc: <linux-riscv@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <jianghuaming.jhm@alibaba-inc.com>, <guoren@kernel.org>, <stable@kernel.org> Subject: Re: [PATCH v2] RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY Date: Mon, 16 May 2022 09:03:26 +0000 [thread overview] Message-ID: <2e62621a-1fb8-5de7-8d0e-e6c4019931a1@microchip.com> (raw) In-Reply-To: <e32a2228-2e2f-0da2-87e8-e364c0450dcd@linux.alibaba.com> On 16/05/2022 09:50, Xianting Tian wrote: > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe > > Hi > > Could I get any comments for the v2 patch, thanks Looks like you have 3 Reviewed-bys already & there's only been one full working day since you sent the patch, probably just worth waiting a little for Palmer to get around to picking it up :) Thanks, Conor. > > 在 2022/5/12 下午2:09, Xianting Tian 写道: >> Commit 00ab027a3b82 ("RISC-V: Add kernel image sections to the resource tree") >> marked IORESOURCE_BUSY for reserved memory, which casued resource map >> failed in subsequent operations of related driver, so remove the >> IORESOURCE_BUSY flag. In order to prohibit userland mapping reserved >> memory, mark IORESOURCE_EXCLUSIVE for it. >> >> The code to reproduce the issue, >> dts: >> mem0: memory@a0000000 { >> reg = <0x0 0xa0000000 0 0x1000000>; >> no-map; >> }; >> >> &test { >> status = "okay"; >> memory-region = <&mem0>; >> }; >> >> code: >> np = of_parse_phandle(pdev->dev.of_node, "memory-region", 0); >> ret = of_address_to_resource(np, 0, &r); >> base = devm_ioremap_resource(&pdev->dev, &r); >> // base = -EBUSY >> >> Fixes: 00ab027a3b82 ("RISC-V: Add kernel image sections to the resource tree") >> Reported-by: Huaming Jiang <jianghuaming.jhm@alibaba-inc.com> >> Reviewed-by: Guo Ren <guoren@kernel.org> >> Reviewed-by: Nick Kossifidis <mick@ics.forth.gr> >> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com> >> --- >> arch/riscv/kernel/setup.c | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/arch/riscv/kernel/setup.c b/arch/riscv/kernel/setup.c >> index 834eb652a7b9..e0a00739bd13 100644 >> --- a/arch/riscv/kernel/setup.c >> +++ b/arch/riscv/kernel/setup.c >> @@ -189,7 +189,7 @@ static void __init init_resources(void) >> res = &mem_res[res_idx--]; >> >> res->name = "Reserved"; >> - res->flags = IORESOURCE_MEM | IORESOURCE_BUSY; >> + res->flags = IORESOURCE_MEM | IORESOURCE_EXCLUSIVE; >> res->start = __pfn_to_phys(memblock_region_reserved_base_pfn(region)); >> res->end = __pfn_to_phys(memblock_region_reserved_end_pfn(region)) - 1; >> >> @@ -214,7 +214,7 @@ static void __init init_resources(void) >> >> if (unlikely(memblock_is_nomap(region))) { >> res->name = "Reserved"; >> - res->flags = IORESOURCE_MEM | IORESOURCE_BUSY; >> + res->flags = IORESOURCE_MEM | IORESOURCE_EXCLUSIVE; >> } else { >> res->name = "System RAM"; >> res->flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY; > > _______________________________________________ > 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:[~2022-05-16 9:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-12 6:09 [PATCH v2] RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY Xianting Tian 2022-05-12 6:09 ` Xianting Tian 2022-05-12 12:31 ` Heiko Stübner 2022-05-12 12:31 ` Heiko Stübner 2022-05-16 8:50 ` Xianting Tian 2022-05-16 8:50 ` Xianting Tian 2022-05-16 9:03 ` Conor.Dooley [this message] 2022-05-16 9:03 ` Conor.Dooley 2022-05-16 9:10 ` Xianting Tian 2022-05-16 9:10 ` Xianting Tian
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=2e62621a-1fb8-5de7-8d0e-e6c4019931a1@microchip.com \ --to=conor.dooley@microchip.com \ --cc=akpm@linux-foundation.org \ --cc=alex@ghiti.fr \ --cc=anup@brainfault.org \ --cc=aou@eecs.berkeley.edu \ --cc=atishp@rivosinc.com \ --cc=david@redhat.com \ --cc=guoren@kernel.org \ --cc=jianghuaming.jhm@alibaba-inc.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=mick@ics.forth.gr \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=petr.pavlu@suse.com \ --cc=rppt@kernel.org \ --cc=seanjc@google.com \ --cc=stable@kernel.org \ --cc=twd2.me@gmail.com \ --cc=wangborong@cdjrlc.com \ --cc=wangkefeng.wang@huawei.com \ --cc=xianting.tian@linux.alibaba.com \ /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.