From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4F290C54E58 for ; Tue, 12 Mar 2024 06:40:36 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id BF9908D0015; Tue, 12 Mar 2024 02:40:35 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id BB0026B0196; Tue, 12 Mar 2024 02:40:35 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id A45BE8D0015; Tue, 12 Mar 2024 02:40:35 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 8DDC56B0195 for ; Tue, 12 Mar 2024 02:40:35 -0400 (EDT) Received: from smtpin29.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 38AEC1C09E0 for ; Tue, 12 Mar 2024 06:40:35 +0000 (UTC) X-FDA: 81887438430.29.E331C28 Received: from mail-yw1-f173.google.com (mail-yw1-f173.google.com [209.85.128.173]) by imf27.hostedemail.com (Postfix) with ESMTP id 77E2940016 for ; Tue, 12 Mar 2024 06:40:33 +0000 (UTC) Authentication-Results: imf27.hostedemail.com; dkim=pass header.d=sifive.com header.s=google header.b=FILdLpo+; dmarc=pass (policy=reject) header.from=sifive.com; spf=pass (imf27.hostedemail.com: domain of nylon.chen@sifive.com designates 209.85.128.173 as permitted sender) smtp.mailfrom=nylon.chen@sifive.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1710225633; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=Mib1xt+v7eiFKuFk82ox3G2c2WM33T8wDeEP+aPgnEY=; b=ehKrnizDGJM9uKZowIrcKX+4SwcAenNOQbpxHTokOZ33yl/RVtH/bWXdZv795hJKp2qv8x 2UatEsDfmevj3fGDL3jH+8eM6MvxSpldtOdCp1p7ulnAalxdOyCwmpD/CWu1CQhGnGXxuJ EOaMGoQlUg13PoJQe+LOCh/lZvfFq4g= ARC-Authentication-Results: i=1; imf27.hostedemail.com; dkim=pass header.d=sifive.com header.s=google header.b=FILdLpo+; dmarc=pass (policy=reject) header.from=sifive.com; spf=pass (imf27.hostedemail.com: domain of nylon.chen@sifive.com designates 209.85.128.173 as permitted sender) smtp.mailfrom=nylon.chen@sifive.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1710225633; a=rsa-sha256; cv=none; b=NCS/cONMCQh/EiAv1eNELNmXUcyAM+2+KX/PZRgdoWMbC8uKw7TfWI9QkexE5VAuZ5Tw6t cfUx7w4/rJ4+LjM3aGy0psLKiJl2q12DaVLeq8kDZItLAQsXGZhcObKHgrXGj0BDGWb4xP WwVY4iKB26vVjKaHvl4B7YUdbJUYzRo= Received: by mail-yw1-f173.google.com with SMTP id 00721157ae682-609f3ca61e0so50101457b3.3 for ; Mon, 11 Mar 2024 23:40:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; t=1710225632; x=1710830432; darn=kvack.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Mib1xt+v7eiFKuFk82ox3G2c2WM33T8wDeEP+aPgnEY=; b=FILdLpo+wSZkL/9nPRq766LXc7hQEFxT5j16soFYa6IvJ7aqBaopjjQ5HnswR84TJP 8w6FoQh/TxuY78HLcCSB1fa9nELZsAjbvJh0h7BBtZsy1rGz1WeC0TyuhLI5UvEsV4/K mMS3tWxBlGAh07Vb/U3+8Xs5GLoib8sNk0whp4b44KtiJGRaGepcW2K2EMSRcXkyoJHt QT/EkxZZ+FATeC8/zTmbOcTriIi8ujou/u1sc+1oOR63pyK8WQpy8H3hR4cAtbx1+nK/ 9lWjdWRGEfSoTPdnoJCjBET8UV5RQY1svX5Y0AVZpe49/YI4MWhe3vUEXla2dJ6FtPFT BQzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710225632; x=1710830432; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Mib1xt+v7eiFKuFk82ox3G2c2WM33T8wDeEP+aPgnEY=; b=YPrbwf8zr61BGsVK+bgZ2M3A2liKmR2G9rQvsjY+wFBrAsQeTTy/eohs5vCzmO4ww6 yODS4gZGmqNcjOCKenjw80tTBa6FFBOazCUKLtQml10gEk9eaUf7WmrJboIOnepkYA+J nvou6hS0jwhCm57PlEgO3RhiZE3G0jOmEHB67jJ75dg/c92nsTO5zW4fIDjHvLZG+wka GBG06VH6q0pIuljnLlJaDdScjSbWpoWe9t9T/p0AnlooXnTHr6AWqEdPyVP1RG5jbGnK EfVSwr+GAby8AkhuB9Z2wSyxYrnr5H+YuM2RGKJHxqXrE4AKZvBZfvLLn2k6GWKWs6L9 sRqw== X-Forwarded-Encrypted: i=1; AJvYcCVTTkuT8+U75hVjsjd5jkIObyXhXZNkYjYifto2aKhSU36NduQ69CK/S/4JmnpnsJRooZDaeejSzGTOlEuKyASBYoI= X-Gm-Message-State: AOJu0YzTcILrmvpjZ43zBRT2G/uwYNUaPAoy4gTCnsiHcyPfbs+EUMnW N0nQ4T8IKh8Dm8lvd4jK4vskyNWcBTcqU5kHvFSjCTRej1ZFE+XcVeMIUjktabtaHab46uOWE0P lmgayl0pWNcspb7W/8Y4ImwfsnPNBYFvIHppfPg== X-Google-Smtp-Source: AGHT+IHbiQrtWLjwG2bwttWyqC5snHDZdcXZiO3RLkmQ0MdJVMi6zl04cbHiQh12269BKPOmXAcs7OMummzUXBHp/Fc= X-Received: by 2002:a25:ac24:0:b0:dcc:588f:1523 with SMTP id w36-20020a25ac24000000b00dcc588f1523mr6918049ybi.49.1710225632392; Mon, 11 Mar 2024 23:40:32 -0700 (PDT) MIME-Version: 1.0 References: <20230316131711.1284451-1-alexghiti@rivosinc.com> <20240118082346.GB31078@hsinchu15> In-Reply-To: From: Nylon Chen Date: Tue, 12 Mar 2024 14:40:20 +0800 Message-ID: Subject: Re: Fwd: [PATCH v8 0/4] riscv: Use PUD/P4D/PGD pages for the linear mapping To: Alexandre Ghiti Cc: alex@ghiti.fr, apatel@ventanamicro.com, catalin.marinas@arm.com, will@kernel.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, robh+dt@kernel.org, frowand.list@gmail.com, rppt@kernel.org, akpm@linux-foundation.org, anup@brainfault.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, devicetree@vger.kernel.org, linux-mm@kvack.org, zong.li@sifive.com, nylon7717@gmail.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 77E2940016 X-Rspam-User: X-Rspamd-Server: rspam05 X-Stat-Signature: s4mikmhsfi6iufijna1prthqzgumdwpo X-HE-Tag: 1710225633-744784 X-HE-Meta: U2FsdGVkX1+47AngoUcFVC+Y3KYvv9p9vCUS+6xBZeAoOD90bketBNDBCFk9xxxrLyjOdWcdtgwGE8X91d+SPjLZkTq4O62vc1bR3gVZ89s+2D0cpFCSfxG4SWzbI+OROWpJICXPgzmBqLjSIZCaey+h5E3HrEVZ81ZCsqWmeA9+q/dP9ylcSFDoTZi97OKy+7eegvp9miJ1fhkY+mgHeJizSz1NAa6L0kMB1H23BhOs6qHIG+O+ZW1RyYZj3DGiSTYtuOzm7s9OdtQnvyEVRL7iGcjW69wA6ivZ5oc1NoJGNgx2com6aNU5NJOQRPnwVDZvmsJQ3Ubjvq1aQmmGRW42ouTwHsJvWcDT7qOIMOm8cmtTeZpJIZ2jMX6RwfsJjicn7m6Ip4v6Lz2qReQt38IIsRxoiO1BsOihomf+cS+mbGu1DN0RxnTc9bsAoi48QGreTYubtwoVDhovi74j5sbJLGI5/6HOFlTvKYY04hlGj7B1cp0TSWmP2MeHhDAuumTzG9VQYpzijk4Y4wBVczn0EZN00q8QxbE5qh56lhMxEvF5ltWQhW+kGSdRT0HNr9EkuLbVLNOhUs3oHKEjlGDgntlya4X6t7wa7aopGOcSnDjWj3VKlb58iGjDSmd4WBc1hxW0byr3U3W9V2ivb9iQP0+6ImIoJ38cIfKzwrENqHVb/LKmPFXmU+Ss25c3iWNJbvz2gFmOzemmVMyHcCplcUg2sUUMQCexiLSgzO/LTNPbatYBpjToUkk1k2VQZUVKv1ksuEeE2o6sPq8D70CcEeB49nWg3uF3hRjlJpck45CYBYxoSXjZcOSIC6oDOT0tvYeoWHeq9wtXIKT/mILsrh+hId+8dEfrK5y4uQSd7aLCKkOevVdm0/8jM/2+WNh09/at4EQFbpP1JeLqpgZ+0mFiP2hawX5xSOp4itMR+vDt1p9Dde9bTrz1ZqCaskrekMrVku5cbM6x3h5 gsIf+zmm rMtlJRqaucaTeRwN96CjJms4SSe64nRYqQNVdx/TABrcoOKhGzqLUF+3+gFvcTjDpQK81 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: Alexandre Ghiti =E6=96=BC 2024=E5=B9=B42=E6=9C=885= =E6=97=A5 =E9=80=B1=E4=B8=80 =E4=B8=8B=E5=8D=885:32=E5=AF=AB=E9=81=93=EF=BC= =9A > > Hi Nylon, > > On Fri, Jan 19, 2024 at 10:27=E2=80=AFAM Nylon Chen wrote: > > > > Alexandre Ghiti =E6=96=BC 2024=E5=B9=B41=E6=9C= =8818=E6=97=A5 =E9=80=B1=E5=9B=9B =E4=B8=8B=E5=8D=889:01=E5=AF=AB=E9=81=93= =EF=BC=9A > > > > > > Hi Nylon, > > Hi Alexandre, thanks for your feedback, > > > > > > On Thu, Jan 18, 2024 at 9:23=E2=80=AFAM Nylon Chen wrote: > > > > > > > > > On 3/23/23 15:55, Anup Patel wrote: > > > > > > On Thu, Mar 23, 2023 at 6:24=E2=80=AFPM Alexandre Ghiti wrote: > > > > > >> Hi Anup, > > > > > >> > > > > > >> On Thu, Mar 23, 2023 at 1:18=E2=80=AFPM Anup Patel wrote: > > > > > >>> Hi Alex, > > > > > >>> > > > > > >>> On Thu, Mar 16, 2023 at 6:48=E2=80=AFPM Alexandre Ghiti wrote: > > > > > >>>> This patchset intends to improve tlb utilization by using hu= gepages for > > > > > >>>> the linear mapping. > > > > > >>>> > > > > > >>>> As reported by Anup in v6, when STRICT_KERNEL_RWX is enabled= , we must > > > > > >>>> take care of isolating the kernel text and rodata so that th= ey are not > > > > > >>>> mapped with a PUD mapping which would then assign wrong perm= issions to > > > > > >>>> the whole region: it is achieved by introducing a new memblo= ck API. > > > > > >>>> > > > > > >>>> Another patch makes use of this new API in arm64 which used = some sort of > > > > > >>>> hack to solve this issue: it was built/boot tested successfu= lly. > > > > > >>>> > > > > > >>>> base-commit-tag: v6.3-rc1 > > > > > >>>> > > > > > >>>> v8: > > > > > >>>> - Fix rv32, as reported by Anup > > > > > >>>> - Do not modify memblock_isolate_range and fixes comment, as= suggested by Mike > > > > > >>>> - Use the new memblock API for crash kernel too in arm64, as= suggested by Andrew > > > > > >>>> - Fix arm64 double mapping (which to me did not work in v7),= but ends up not > > > > > >>>> being pretty at all, will wait for comments from arm64 re= viewers, but > > > > > >>>> this patch can easily be dropped if they do not want it. > > > > > >>>> > > > > > >>>> v7: > > > > > >>>> - Fix Anup bug report by introducing memblock_isolate_memory= which > > > > > >>>> allows us to split the memblock mappings and then avoid t= o map the > > > > > >>>> the PUD which contains the kernel as read only > > > > > >>>> - Add a patch to arm64 to use this newly introduced API > > > > > >>>> > > > > > >>>> v6: > > > > > >>>> - quiet LLVM warning by casting phys_ram_base into an unsign= ed long > > > > > >>>> > > > > > >>>> v5: > > > > > >>>> - Fix nommu builds by getting rid of riscv_pfn_base in patch= 1, thanks > > > > > >>>> Conor > > > > > >>>> - Add RB from Andrew > > > > > >>>> > > > > > >>>> v4: > > > > > >>>> - Rebase on top of v6.2-rc3, as noted by Conor > > > > > >>>> - Add Acked-by Rob > > > > > >>>> > > > > > >>>> v3: > > > > > >>>> - Change the comment about initrd_start VA conversion so tha= t it fits > > > > > >>>> ARM64 and RISCV64 (and others in the future if needed), a= s suggested > > > > > >>>> by Rob > > > > > >>>> > > > > > >>>> v2: > > > > > >>>> - Add a comment on why RISCV64 does not need to set initrd_s= tart/end that > > > > > >>>> early in the boot process, as asked by Rob > > > > > >>>> > > > > > >>>> Alexandre Ghiti (4): > > > > > >>>> riscv: Get rid of riscv_pfn_base variable > > > > > >>>> mm: Introduce memblock_isolate_memory > > > > > >>>> arm64: Make use of memblock_isolate_memory for the linear= mapping > > > > > >>>> riscv: Use PUD/P4D/PGD pages for the linear mapping > > > > > >>> Kernel boot fine on RV64 but there is a failure which is stil= l not > > > > > >>> addressed. You can see this failure as following message in > > > > > >>> kernel boot log: > > > > > >>> 0.000000] Failed to add a System RAM resource at 8020000= 0 > > > > > >> Hmmm I don't get that in any of my test configs, would you min= d > > > > > >> sharing yours and your qemu command line? > > > > > > Try alexghiti_test branch at > > > > > > https://github.com/avpatel/linux.git > > > > > > > > > > > > I am building the kernel using defconfig and my rootfs is > > > > > > based on busybox. > > > > > > > > > > > > My QEMU command is: > > > > > > qemu-system-riscv64 -M virt -m 512M -nographic -bios > > > > > > opensbi/build/platform/generic/firmware/fw_dynamic.bin -kernel > > > > > > ./build-riscv64/arch/riscv/boot/Image -append "root=3D/dev/ram = rw > > > > > > console=3DttyS0 earlycon" -initrd ./rootfs_riscv64.img -smp 4 > > > > > > > > > > > > > > > So splitting memblock.memory is the culprit, it "confuses" the re= sources > > > > > addition and I can only find hacky ways to fix that... > > > > Hi Alexandre, > > > > > > > > We encountered the same error as Anup. After adding your patch > > > > (3335068f87217ea59d08f462187dc856652eea15), we will not encounter t= he > > > > error again. > > > > > > > > What I have observed so far is > > > > > > > > - before your patch > > > > When merging consecutive memblocks, if the memblock types are diffe= rent, > > > > they will be merged into reserved > > > > - after your patch > > > > When consecutive memblocks are merged, if the memblock types are > > > > different, they will be merged into memory. > > > > > > > > Such a result will cause the memory location of OpenSBI to be chang= ed > > > > from reserved to memory. Will this have any side effects? > > > > > > I guess it will end up in the memory pool and pages from openSBI > > > region will be allocated, so we should see very quickly bad stuff > > > happening (either PMP violation or M-mode ecall never > > > returning/trapping/etc). > > > > > > But I don't observe the same thing, I always see the openSBI region > > > being reserved: > > > > > > reserved[0x0] [0x0000000080000000-0x000000008007ffff], > > > 0x0000000000080000 bytes flags: 0x0 > > > > > > Can you elaborate a bit more about "When consecutive memblocks are > > > merged, if the memblock types are different, they will be merged into > > > memory"? Where/when does this merge happen? Can you give me a config > > > file and a kernel revision so that I can take a look? > > Ok, If you want to reproduce the same results you just need to modify O= penSBI > > > > [ lib/sbi/sbi_domain.c ] > > +#define TEST_SIZE 0x200000 > > > > - (scratch->fw_size - scratch->fw_rw_of= fset), > > + (TEST_SIZE - scratch->fw_rw_offset), > > > > In addition, you can insert checks in the kernel merged function > > [ mm/memblock.c ] > > static void __init_memblock memblock_merge_regions(struct memblock_type= *type) > > while (i < type->cnt - 1) { > > ... > > /* move forward from next + 1, index of which is i + 2 = */ > > memmove(next, next + 1, (type->cnt - (i + 2)) * sizeof(= *next)); > > type->cnt--; > > } > > + pr_info("Merged memblock_type: cnt =3D %lu, max =3D %lu, > > total_size =3D 0x%llx\n",type->cnt, type->max, type->total_size); > > + for (i =3D 0; i < type->cnt; i++) { > > + const char *region_type =3D > > memblock_is_memory(type->regions[i].base) ? "memory" : "reserve"; > > + pr_info("Region %d: base =3D 0x%llx, size =3D 0x%llx, t= ype > > =3D %s\n", i, type->regions[i].base, type->regions[i].size, > > region_type); > > + } > > } > > This is kernel boot log > > - before your patch > > ... > > [ 0.000000] OF: fdt: Reserving memory: base =3D 0x80000000, size =3D= 0x200000 > > [ 0.000000] Merged memblock_type: cnt =3D 4, max =3D 128, total_size= =3D 0x1628501 > > [ 0.000000] Region 0: base =3D 0x80000000, size =3D 0x1600000, type = =3D reserve > > ... > > > > - after your patch > > ... > > [ 0.000000] OF: fdt: Reserving memory: base =3D 0x80000000, size =3D= 0x200000 > > [ 0.000000] Merged memblock_type: cnt =3D 4, max =3D 128, total_size= =3D 0x180c42e > > [ 0.000000] Region 0: base =3D 0x80000000, size =3D 0x1800000, type = =3D memory > Hi Alex, thanks for your feedback. > So the openSBI region is marked as memory, and not reserved because > this region is now described as nomap, and memblock_mark_nomap() does > not move this region into the reserved memblock list, but keep it in > the memory list with the nomap flag > (https://elixir.bootlin.com/linux/latest/source/drivers/of/fdt.c#L479). > But as stated in the description of memblock_mark_nomap() > (https://elixir.bootlin.com/linux/latest/source/mm/memblock.c#L969), > the pages associated with the region will be marked as PageReserved > and the region will not be covered in the linear mapping. I traced it via GDB, and indeed, it enters early_init_dt_reserve_memory() and calls memblock_reserve to reserve this block of memory. [before your patch] [ 0.000000] OF: fdt: check nomap Reserving memory: base =3D 0x80000000, size =3D 0x200000 [ 0.000000] --- Reserved memory: Base address: 80000000, Size: 200000--- [ 0.000000] Merged memblock_type: cnt =3D 4, max =3D 128, total_size =3D 0x1e28501 [ 0.000000] Region 0: base =3D 0x80000000, size =3D 0x1e00000, type =3D reserve [ 0.000000] Region 1: base =3D 0xbfe00000, size =3D 0x6002, type =3D memory .... [ 0.000000] OF: fdt: Reserved memory: reserved region for node 'mmode_resv0@80000000': base 0x0000000080000000, size 2 MiB [ 0.000000] OF: reserved mem: 0x0000000080000000..0x00000000801fffff (2048 KiB) map non-reusable mmode_resv0@80000000 [after your patch] [ 0.000000] OF: fdt: check nomap Reserving memory: base =3D 0x80000000, size =3D 0x200000 [ 0.000000] --- Reserved memory: Base address: 80000000, Size: 200000--- [ 0.000000] Merged memblock_type: cnt =3D 4, max =3D 128, total_size =3D= 0x1e25501 [ 0.000000] Region 0: base =3D 0x80000000, size =3D 0x1e00000, type =3D = memory [ 0.000000] Region 1: base =3D 0xbfe00000, size =3D 0x6002, type =3D mem= ory ... [ 0.000000] OF: fdt: Reserved memory: reserved region for node 'mmode_resv0@80000000': base 0x0000000080000000, size 2 MiB [ 0.000000] OF: reserved mem: 0x0000000080000000..0x00000000801fffff (2048 KiB) map non-reusable mmode_resv0@80000000 At the moment, it can be confirmed that there is no need to worry about this block of memory being used. But I still have a question I'd like to ask, which is why this location is flagged as 'reserve' instead of 'memory' in the memblock Thanks, Nylon > > So to me, this is normal and we are safe. Let me know if I made a mistake= . > > And sorry for the long delay, that slipped my mind! > > Thanks, > > Alex > > > ... > > [ 0.000000] Failed to add a system RAM resource at 80200000 > > ... > > > > > > Thanks, > > > > > > Alex > > > > > > > > > > > > > So given that the arm64 patch with the new API is not pretty and = that > > > > > the simplest solution is to re-merge the memblock regions afterwa= rds > > > > > (which is done by memblock_clear_nomap), I'll drop the new API an= d the > > > > > arm64 patch to use the nomap API like arm64: I'll take advantage = of that > > > > > to clean setup_vm_final which I have wanted to do for a long time= . > > > > > > > > > > @Mike Thanks for you reviews! > > > > > > > > > > @Anup Thanks for all your bug reports on this patchset, I have to > > > > > improve my test flow (it is in the work :)). > > > > > > > > > > > > > > > > Regards, > > > > > > Anup > > > > > > > > > > > >> Thanks > > > > > >> > > > > > >>> Regards, > > > > > >>> Anup > > > > > >>> > > > > > >>>> arch/arm64/mm/mmu.c | 25 +++++++++++------ > > > > > >>>> arch/riscv/include/asm/page.h | 19 +++++++++++-- > > > > > >>>> arch/riscv/mm/init.c | 53 +++++++++++++++++++++++= +++++------- > > > > > >>>> arch/riscv/mm/physaddr.c | 16 +++++++++++ > > > > > >>>> drivers/of/fdt.c | 11 ++++---- > > > > > >>>> include/linux/memblock.h | 1 + > > > > > >>>> mm/memblock.c | 20 +++++++++++++ > > > > > >>>> 7 files changed, 119 insertions(+), 26 deletions(-) > > > > > >>>> > > > > > >>>> -- > > > > > >>>> 2.37.2 > > > > > >>>> > > > > > > _______________________________________________ > > > > > > 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