From: "Heiko Stübner" <heiko@sntech.de>
To: 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,
linux-riscv@lists.infradead.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
jianghuaming.jhm@alibaba-inc.com, guoren@kernel.org,
Xianting Tian <xianting.tian@linux.alibaba.com>,
Xianting Tian <xianting.tian@linux.alibaba.com>
Subject: Re: [PATCH v2] RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY
Date: Thu, 12 May 2022 14:31:07 +0200 [thread overview]
Message-ID: <2583718.X9hSmTKtgW@diego> (raw)
In-Reply-To: <20220512060910.601832-1-xianting.tian@linux.alibaba.com>
Am Donnerstag, 12. Mai 2022, 08:09:10 CEST schrieb Xianting Tian:
> Commit 00ab027a3b82 ("RISC-V: Add kernel image sections to the resource tree")
> marked IORESOURCE_BUSY for reserved memory, which casued resource map
typo "caused" 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.
Looking at the comment for IORESOURCE_EXCLUSIVE
(/* Userland may not map this resource */)
this also looks like the way better match for "no-map" :-) .
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Also on qemu + d1-nezha board
Tested-by: Heiko Stuebner <heiko@sntech.de>
Heiko
> 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: "Heiko Stübner" <heiko@sntech.de>
To: 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,
linux-riscv@lists.infradead.org
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
jianghuaming.jhm@alibaba-inc.com, guoren@kernel.org,
Xianting Tian <xianting.tian@linux.alibaba.com>,
Xianting Tian <xianting.tian@linux.alibaba.com>
Subject: Re: [PATCH v2] RISC-V: Mark IORESOURCE_EXCLUSIVE for reserved mem instead of IORESOURCE_BUSY
Date: Thu, 12 May 2022 14:31:07 +0200 [thread overview]
Message-ID: <2583718.X9hSmTKtgW@diego> (raw)
In-Reply-To: <20220512060910.601832-1-xianting.tian@linux.alibaba.com>
Am Donnerstag, 12. Mai 2022, 08:09:10 CEST schrieb Xianting Tian:
> Commit 00ab027a3b82 ("RISC-V: Add kernel image sections to the resource tree")
> marked IORESOURCE_BUSY for reserved memory, which casued resource map
typo "caused" 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.
Looking at the comment for IORESOURCE_EXCLUSIVE
(/* Userland may not map this resource */)
this also looks like the way better match for "no-map" :-) .
Reviewed-by: Heiko Stuebner <heiko@sntech.de>
Also on qemu + d1-nezha board
Tested-by: Heiko Stuebner <heiko@sntech.de>
Heiko
> 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;
>
next prev parent reply other threads:[~2022-05-12 12:32 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 [this message]
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
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=2583718.X9hSmTKtgW@diego \
--to=heiko@sntech.de \
--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=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: link
Be 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.