From: Palmer Dabbelt <palmer@rivosinc.com> To: lizhengyu3@huawei.com Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, aou@eecs.berkeley.edu, robh+dt@kernel.org, frowand.list@gmail.com, zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com, liaochang1@huawei.com, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux@rivosinc.com Subject: [PATCH v1 0/5] Support kexec_file on 32-bit RISC-V Date: Fri, 20 May 2022 08:44:26 -0700 [thread overview] Message-ID: <20220520154430.18593-1-palmer@rivosinc.com> (raw) kexec_file() support was recently added for RISC-V [1], which triggered a handful of build issues on rv32. These all seemed pretty minor, but it looks like this is the only 32-bit platform that has attempted to build the kexec IMA support before so I'm not sure if there's something more complicated going on that I'm missing (I haven't tested any of this). The rv64 support was just merged into kernel.org/riscv/linux/for-next as 83a7a614ce58 ("riscv: kexec: add kexec_file_load() support"). I've put these on top of the pre-merged version at kernel.org/palmer/linux/riscv-kexec_file-rv32 if that helps anyone. 1: https://lore.kernel.org/all/20220408100914.150110-1-lizhengyu3@huawei.com/
WARNING: multiple messages have this Message-ID (diff)
From: Palmer Dabbelt <palmer@rivosinc.com> To: lizhengyu3@huawei.com Cc: Paul Walmsley <paul.walmsley@sifive.com>, Palmer Dabbelt <palmer@dabbelt.com>, aou@eecs.berkeley.edu, robh+dt@kernel.org, frowand.list@gmail.com, zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, jmorris@namei.org, serge@hallyn.com, liaochang1@huawei.com, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux@rivosinc.com Subject: [PATCH v1 0/5] Support kexec_file on 32-bit RISC-V Date: Fri, 20 May 2022 08:44:26 -0700 [thread overview] Message-ID: <20220520154430.18593-1-palmer@rivosinc.com> (raw) kexec_file() support was recently added for RISC-V [1], which triggered a handful of build issues on rv32. These all seemed pretty minor, but it looks like this is the only 32-bit platform that has attempted to build the kexec IMA support before so I'm not sure if there's something more complicated going on that I'm missing (I haven't tested any of this). The rv64 support was just merged into kernel.org/riscv/linux/for-next as 83a7a614ce58 ("riscv: kexec: add kexec_file_load() support"). I've put these on top of the pre-merged version at kernel.org/palmer/linux/riscv-kexec_file-rv32 if that helps anyone. 1: https://lore.kernel.org/all/20220408100914.150110-1-lizhengyu3@huawei.com/ _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-05-20 15:45 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-20 15:44 Palmer Dabbelt [this message] 2022-05-20 15:44 ` [PATCH v1 0/5] Support kexec_file on 32-bit RISC-V Palmer Dabbelt 2022-05-20 15:44 ` [PATCH v1 1/5] drivers: of: kexec ima: Support 32-bit platforms Palmer Dabbelt 2022-05-20 15:44 ` Palmer Dabbelt 2022-05-20 22:42 ` Rob Herring 2022-05-20 22:42 ` Rob Herring 2022-05-20 15:44 ` [PATCH v1 2/5] ima: Fix a build issue on " Palmer Dabbelt 2022-05-20 15:44 ` Palmer Dabbelt 2022-05-20 15:44 ` [PATCH v1 3/5] RISC-V: kexec: Use Elf64 on 64-bit targets Palmer Dabbelt 2022-05-20 15:44 ` Palmer Dabbelt 2022-05-20 15:44 ` [PATCH v1 4/5] RISC-V: purgatory: Use XLEN-length loads to support rv32 Palmer Dabbelt 2022-05-20 15:44 ` Palmer Dabbelt 2022-05-20 15:44 ` [PATCH v1 5/5] RISC-V: Allow kexec_file() on 32-bit platforms Palmer Dabbelt 2022-05-20 15:44 ` Palmer Dabbelt
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=20220520154430.18593-1-palmer@rivosinc.com \ --to=palmer@rivosinc.com \ --cc=aou@eecs.berkeley.edu \ --cc=devicetree@vger.kernel.org \ --cc=dmitry.kasatkin@gmail.com \ --cc=frowand.list@gmail.com \ --cc=jmorris@namei.org \ --cc=liaochang1@huawei.com \ --cc=linux-integrity@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=linux-security-module@vger.kernel.org \ --cc=linux@rivosinc.com \ --cc=lizhengyu3@huawei.com \ --cc=palmer@dabbelt.com \ --cc=paul.walmsley@sifive.com \ --cc=robh+dt@kernel.org \ --cc=serge@hallyn.com \ --cc=zohar@linux.ibm.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.