| Message ID | 20180927085039.8391-1-ard.biesheuvel@linaro.org |
|---|---|
| Headers | show |
| Series | EFI updates for v4.20 | expand |
* Marc Zyngier <marc.zyngier@arm.com> wrote: > Hi all, > > On 27/09/18 09:50, Ard Biesheuvel wrote: > > Thomas, Ingo, > > > > Please pull/cherry-pick the below. Note that the first three patches will > > be depended upon by an irqchip series that Marc Zyngier has sent out last > > week, and that targets the next release as well. So please advise how to > > proceed with that: we could simply apply those patches first and use the > > resulting commit in tip.git as a stable branch, I suppose, but I'll let > > Marc chime in in case he has any other ideas. > > A stable branch with these three patches would be great. The irqchip code > will also end-up in tip, so it should all be quite easy to manage anyway. Yeah - nevertheless, to keep it all separated nicely, I've created a new topic tree for this: tip:efi/irqchip (2e3ac98133a3), with just these three patches on top of latest -git. That way it can then all be iterated separately. Does this approach work for you? Thanks, Ingo
* Ingo Molnar <mingo@kernel.org> wrote: > > * Marc Zyngier <marc.zyngier@arm.com> wrote: > > > Hi all, > > > > On 27/09/18 09:50, Ard Biesheuvel wrote: > > > Thomas, Ingo, > > > > > > Please pull/cherry-pick the below. Note that the first three patches will > > > be depended upon by an irqchip series that Marc Zyngier has sent out last > > > week, and that targets the next release as well. So please advise how to > > > proceed with that: we could simply apply those patches first and use the > > > resulting commit in tip.git as a stable branch, I suppose, but I'll let > > > Marc chime in in case he has any other ideas. > > > > A stable branch with these three patches would be great. The irqchip code > > will also end-up in tip, so it should all be quite easy to manage anyway. > > Yeah - nevertheless, to keep it all separated nicely, I've created a new > topic tree for this: tip:efi/irqchip (2e3ac98133a3), with just these three > patches on top of latest -git. > > That way it can then all be iterated separately. > > Does this approach work for you? It's a23d3bb05ccb - i.e. the commit ID of Ard's tree, so if you already based your work on top of that then you won't even need to rebase anything. Thanks, Ingo
On 2 October 2018 at 10:38, Ingo Molnar <mingo@kernel.org> wrote: > > * Ingo Molnar <mingo@kernel.org> wrote: > >> >> * Marc Zyngier <marc.zyngier@arm.com> wrote: >> >> > Hi all, >> > >> > On 27/09/18 09:50, Ard Biesheuvel wrote: >> > > Thomas, Ingo, >> > > >> > > Please pull/cherry-pick the below. Note that the first three patches will >> > > be depended upon by an irqchip series that Marc Zyngier has sent out last >> > > week, and that targets the next release as well. So please advise how to >> > > proceed with that: we could simply apply those patches first and use the >> > > resulting commit in tip.git as a stable branch, I suppose, but I'll let >> > > Marc chime in in case he has any other ideas. >> > >> > A stable branch with these three patches would be great. The irqchip code >> > will also end-up in tip, so it should all be quite easy to manage anyway. >> >> Yeah - nevertheless, to keep it all separated nicely, I've created a new >> topic tree for this: tip:efi/irqchip (2e3ac98133a3), with just these three >> patches on top of latest -git. >> >> That way it can then all be iterated separately. >> >> Does this approach work for you? > > It's a23d3bb05ccb - i.e. the commit ID of Ard's tree, so if you already based your work on top > of that then you won't even need to rebase anything. > Thanks Ingo
On Tue, 02 Oct 2018 09:38:17 +0100, Ingo Molnar <mingo@kernel.org> wrote: > > > * Ingo Molnar <mingo@kernel.org> wrote: > > > > > * Marc Zyngier <marc.zyngier@arm.com> wrote: > > > > > Hi all, > > > > > > On 27/09/18 09:50, Ard Biesheuvel wrote: > > > > Thomas, Ingo, > > > > > > > > Please pull/cherry-pick the below. Note that the first three patches will > > > > be depended upon by an irqchip series that Marc Zyngier has sent out last > > > > week, and that targets the next release as well. So please advise how to > > > > proceed with that: we could simply apply those patches first and use the > > > > resulting commit in tip.git as a stable branch, I suppose, but I'll let > > > > Marc chime in in case he has any other ideas. > > > > > > A stable branch with these three patches would be great. The irqchip code > > > will also end-up in tip, so it should all be quite easy to manage anyway. > > > > Yeah - nevertheless, to keep it all separated nicely, I've created a new > > topic tree for this: tip:efi/irqchip (2e3ac98133a3), with just these three > > patches on top of latest -git. > > > > That way it can then all be iterated separately. > > > > Does this approach work for you? > > It's a23d3bb05ccb - i.e. the commit ID of Ard's tree, so if you > already based your work on top of that then you won't even need to > rebase anything. No, it was already based on the tip/efi/core. Never mind, I'll rebase it. Thanks, M. -- Jazz is not dead, it just smell funny.
Thomas, Ingo, Please pull/cherry-pick the below. Note that the first three patches will be depended upon by an irqchip series that Marc Zyngier has sent out last week, and that targets the next release as well. So please advise how to proceed with that: we could simply apply those patches first and use the resulting commit in tip.git as a stable branch, I suppose, but I'll let Marc chime in in case he has any other ideas. Thanks, Ard. [0] https://lore.kernel.org/lkml/20180921195954.21574-1-marc.zyngier@arm.com/ The following changes since commit 11da3a7f84f19c26da6f86af878298694ede0804: Linux 4.19-rc3 (2018-09-09 17:26:43 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git tags/efi-next for you to fetch changes up to 9c1442a9d039a1a3302fa93e9a11001c5f23b624: x86: boot: Fix EFI stub alignment (2018-09-26 12:15:01 +0200) ---------------------------------------------------------------- EFI updates for v4.20: - Add support for enlisting the help of the EFI firmware to create memory reservations that persist across kexec. - Add page fault handling to the runtime services support code on x86 so we can gracefully recover from buggy EFI firmware. - Fix command line handling on x86 for the boot path that omits the stub's PE/COFF entry point. - Other assorted fixes. ---------------------------------------------------------------- Aaron Ma (1): efi/x86: earlyprintk - Add 64bit efi fb address support Alistair Strachan (1): efi/libstub: arm: support building with clang Ard Biesheuvel (3): efi: honour memory reservations passed via a linux specific config table efi/arm: libstub: add a root memreserve config table efi: add API to reserve memory persistently across kexec reboot Ben Hutchings (1): x86: boot: Fix EFI stub alignment Hans de Goede (1): efi/x86: Call efi_parse_options() from efi_main() Ivan Hu (1): efi/efi_test: add exporting ResetSystem runtime service Sai Praneeth (2): efi: Make efi_rts_work accessible to efi page fault handler efi/x86: Handle page faults occurring while running EFI runtime services Sebastian Andrzej Siewior (1): efi/x86: drop task_lock() from efi_switch_mm() arch/x86/boot/compressed/eboot.c | 10 +++++ arch/x86/boot/tools/build.c | 7 +++ arch/x86/include/asm/efi.h | 1 + arch/x86/mm/fault.c | 9 ++++ arch/x86/platform/efi/early_printk.c | 8 +++- arch/x86/platform/efi/efi_64.c | 10 ++--- arch/x86/platform/efi/quirks.c | 78 +++++++++++++++++++++++++++++++++ drivers/firmware/efi/efi.c | 59 ++++++++++++++++++++++++- drivers/firmware/efi/libstub/Makefile | 3 +- drivers/firmware/efi/libstub/arm-stub.c | 27 ++++++++++++ drivers/firmware/efi/runtime-wrappers.c | 61 +++++++------------------- drivers/firmware/efi/test/efi_test.c | 27 ++++++++++++ drivers/firmware/efi/test/efi_test.h | 10 +++++ include/linux/efi.h | 51 +++++++++++++++++++++ 14 files changed, 307 insertions(+), 54 deletions(-)