From: Conor Dooley <conor@kernel.org>
To: Anup Patel <apatel@ventanamicro.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Atish Patra <atishp@atishpatra.org>,
Heiko Stuebner <heiko@sntech.de>, Arnd Bergmann <arnd@arndb.de>,
Anup Patel <anup@brainfault.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Add PMEM support for RISC-V
Date: Sat, 19 Nov 2022 12:59:29 +0000 [thread overview]
Message-ID: <Y3jTMeeikmNJtq3r@spud> (raw)
In-Reply-To: <CAK9=C2VRbUiFS2dCNVoC4KJNe4L+EMXNpfSfTrGoFuLRko1TkA@mail.gmail.com>
On Sat, Nov 19, 2022 at 06:11:08PM +0530, Anup Patel wrote:
> On Mon, Nov 14, 2022 at 10:11 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > Hey Anup,
> >
> > Looks like patches 2 and 3 are failing for the nommu defconfigs:
> > https://patchwork.kernel.org/project/linux-riscv/list/?series=694995
> > Unfortunately, if the build fails NIPA doesn't appear to save a log.
> >
> > In case it's relevant, should be gcc-11 & bintutils 2.37.
>
> I tried nommu defconfigs with gcc-12.1.0 and binutils-2.39 and I did
> not see any failure.
In the interim, I got my new machine set up properly and have gcc-11
locally now (11.1.0) with binutils 2.37. I just gave the series a try
and I cannot see the failure either but I am not using tuxmake.
Apologies for the noise Anup!
FWIW:
Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Regards,
> Anup
>
> >
> > Thanks,
> > Conor.
> >
> > On Mon, Nov 14, 2022 at 02:35:33PM +0530, Anup Patel wrote:
> > > The Linux NVDIMM PEM drivers require arch support to map and access the
> > > persistent memory device. This series adds RISC-V PMEM support using
> > > recently added Svpbmt and Zicbom support.
> > >
> > > First two patches are fixes and remaining two patches add the required
> > > PMEM support for Linux RISC-V.
> > >
> > > These patches can also be found in riscv_pmem_v6 branch at:
> > > https://github.com/avpatel/linux.git
> > >
> > > Changes since v5:
> > > - Rebased on Linux-6.1-rc5
> > > - Directly add pmem.o in obj-y of PATCH3
> > > - Dropped PATCH1 since this is already merged.
> > >
> > > Changes since v4:
> > > - Simplify PATCH2 by implementing RISC-V specific arch_memremap_wb()
> > >
> > > Changes since v3:
> > > - Pickup correct version of Drew's patch as PATCH1
> > >
> > > Changes since v2:
> > > - Rebased on Linux-6.1-rc1
> > > - Replaced PATCH1 with the patch proposed by Drew
> > >
> > > Changes since v1:
> > > - Fix error reported by test bot
> > > https://lore.kernel.org/all/202208272028.IwrNZ0Ur-lkp@intel.com/
> > >
> > > Anup Patel (3):
> > > RISC-V: Fix MEMREMAP_WB for systems with Svpbmt
> > > RISC-V: Implement arch specific PMEM APIs
> > > RISC-V: Enable PMEM drivers
> > >
> > > arch/riscv/Kconfig | 1 +
> > > arch/riscv/configs/defconfig | 1 +
> > > arch/riscv/include/asm/io.h | 5 +++++
> > > arch/riscv/mm/Makefile | 1 +
> > > arch/riscv/mm/pmem.c | 21 +++++++++++++++++++++
> > > 5 files changed, 29 insertions(+)
> > > create mode 100644 arch/riscv/mm/pmem.c
> > >
> > > --
> > > 2.34.1
> > >
_______________________________________________
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 <conor@kernel.org>
To: Anup Patel <apatel@ventanamicro.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Atish Patra <atishp@atishpatra.org>,
Heiko Stuebner <heiko@sntech.de>, Arnd Bergmann <arnd@arndb.de>,
Anup Patel <anup@brainfault.org>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Add PMEM support for RISC-V
Date: Sat, 19 Nov 2022 12:59:29 +0000 [thread overview]
Message-ID: <Y3jTMeeikmNJtq3r@spud> (raw)
In-Reply-To: <CAK9=C2VRbUiFS2dCNVoC4KJNe4L+EMXNpfSfTrGoFuLRko1TkA@mail.gmail.com>
On Sat, Nov 19, 2022 at 06:11:08PM +0530, Anup Patel wrote:
> On Mon, Nov 14, 2022 at 10:11 PM Conor Dooley <conor@kernel.org> wrote:
> >
> > Hey Anup,
> >
> > Looks like patches 2 and 3 are failing for the nommu defconfigs:
> > https://patchwork.kernel.org/project/linux-riscv/list/?series=694995
> > Unfortunately, if the build fails NIPA doesn't appear to save a log.
> >
> > In case it's relevant, should be gcc-11 & bintutils 2.37.
>
> I tried nommu defconfigs with gcc-12.1.0 and binutils-2.39 and I did
> not see any failure.
In the interim, I got my new machine set up properly and have gcc-11
locally now (11.1.0) with binutils 2.37. I just gave the series a try
and I cannot see the failure either but I am not using tuxmake.
Apologies for the noise Anup!
FWIW:
Acked-by: Conor Dooley <conor.dooley@microchip.com>
>
> Regards,
> Anup
>
> >
> > Thanks,
> > Conor.
> >
> > On Mon, Nov 14, 2022 at 02:35:33PM +0530, Anup Patel wrote:
> > > The Linux NVDIMM PEM drivers require arch support to map and access the
> > > persistent memory device. This series adds RISC-V PMEM support using
> > > recently added Svpbmt and Zicbom support.
> > >
> > > First two patches are fixes and remaining two patches add the required
> > > PMEM support for Linux RISC-V.
> > >
> > > These patches can also be found in riscv_pmem_v6 branch at:
> > > https://github.com/avpatel/linux.git
> > >
> > > Changes since v5:
> > > - Rebased on Linux-6.1-rc5
> > > - Directly add pmem.o in obj-y of PATCH3
> > > - Dropped PATCH1 since this is already merged.
> > >
> > > Changes since v4:
> > > - Simplify PATCH2 by implementing RISC-V specific arch_memremap_wb()
> > >
> > > Changes since v3:
> > > - Pickup correct version of Drew's patch as PATCH1
> > >
> > > Changes since v2:
> > > - Rebased on Linux-6.1-rc1
> > > - Replaced PATCH1 with the patch proposed by Drew
> > >
> > > Changes since v1:
> > > - Fix error reported by test bot
> > > https://lore.kernel.org/all/202208272028.IwrNZ0Ur-lkp@intel.com/
> > >
> > > Anup Patel (3):
> > > RISC-V: Fix MEMREMAP_WB for systems with Svpbmt
> > > RISC-V: Implement arch specific PMEM APIs
> > > RISC-V: Enable PMEM drivers
> > >
> > > arch/riscv/Kconfig | 1 +
> > > arch/riscv/configs/defconfig | 1 +
> > > arch/riscv/include/asm/io.h | 5 +++++
> > > arch/riscv/mm/Makefile | 1 +
> > > arch/riscv/mm/pmem.c | 21 +++++++++++++++++++++
> > > 5 files changed, 29 insertions(+)
> > > create mode 100644 arch/riscv/mm/pmem.c
> > >
> > > --
> > > 2.34.1
> > >
next prev parent reply other threads:[~2022-11-19 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 9:05 [PATCH v6 0/3] Add PMEM support for RISC-V Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 9:05 ` [PATCH v6 1/3] RISC-V: Fix MEMREMAP_WB for systems with Svpbmt Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 9:05 ` [PATCH v6 2/3] RISC-V: Implement arch specific PMEM APIs Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 9:05 ` [PATCH v6 3/3] RISC-V: Enable PMEM drivers Anup Patel
2022-11-14 9:05 ` Anup Patel
2022-11-14 16:41 ` [PATCH v6 0/3] Add PMEM support for RISC-V Conor Dooley
2022-11-14 16:41 ` Conor Dooley
2022-11-19 12:41 ` Anup Patel
2022-11-19 12:41 ` Anup Patel
2022-11-19 12:59 ` Conor Dooley [this message]
2022-11-19 12:59 ` Conor Dooley
2022-12-03 6:12 ` Anup Patel
2022-12-03 6:12 ` Anup Patel
2022-12-08 23:47 ` Palmer Dabbelt
2022-12-08 23:47 ` Palmer Dabbelt
2022-12-09 1:30 ` patchwork-bot+linux-riscv
2022-12-09 1:30 ` patchwork-bot+linux-riscv
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=Y3jTMeeikmNJtq3r@spud \
--to=conor@kernel.org \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=arnd@arndb.de \
--cc=atishp@atishpatra.org \
--cc=heiko@sntech.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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.