Re: [PATCH 1/2] zboot: enable arm64 kexec_load for zboot image

2023-09-12 Thread Dave Young
Hi, On Wed, 13 Sept 2023 at 08:54, Pingfan Liu wrote: > > On Mon, Sep 11, 2023 at 6:37 PM Dave Young wrote: > > > > kexec_file_load support of zboot kernel image decompressed the vmlinuz, > > so in kexec_load code just load the kernel with reading the decompressed > > kernel fd into a new buffer

Re: [PATCH 1/2] zboot: enable arm64 kexec_load for zboot image

2023-09-12 Thread Pingfan Liu
On Mon, Sep 11, 2023 at 6:37 PM Dave Young wrote: > > kexec_file_load support of zboot kernel image decompressed the vmlinuz, > so in kexec_load code just load the kernel with reading the decompressed > kernel fd into a new buffer and use it directly. > > Signed-off-by: Dave Young > --- > includ

Re: [PATCH V1 0/3] riscv: kexec: cleanup and fixups

2023-09-12 Thread patchwork-bot+linux-riscv
Hello: This series was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Thu, 7 Sep 2023 18:33:01 +0800 you wrote: > Hi, > > I had posted 2 patches [1][2] for riscv/kexec, but there was no "effective" > response to them until now, so I merged them in this series with the 3rd > fixup. >

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jan Hendrik Farr
> These are sort of "tautological" arguments. There must be some > objective reasons why this architecture was chosen instead of > other (i.e. using what already pre-exists). I think I misunderstood you in my earlier reply. I do not understand in what way you think my arguments are tautological

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jan Hendrik Farr
> These are sort of "tautological" arguments. There must be some > objective reasons why this architecture was chosen instead of > other (i.e. using what already pre-exists). You mean like your argument that the same can already be achieved with the normal EFI stub and builin initrd/cmdline? ;)

Re: [PATCH v2 0/2] x86/kexec: UKI Support

2023-09-12 Thread Jan Hendrik Farr
> By the way, could you provide detailed steps about how to test this > patchset so that people interested can give it a shot? Sure. 0. Build and run your kernel with my patches. 1. You're gonna need a UKI to kexec. I personally use sbctl or ukify to create them. sbctl command example (assumes

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jarkko Sakkinen
On Tue Sep 12, 2023 at 9:56 PM EEST, Jan Hendrik Farr wrote: > > What sort of bottleneck does the EFI stub have so that we need yet > > another envelope? > > Well I can come up with a few advantages of UKI compared to normal bzImage > with builtin initrd and cmdline. > > 1. You already identified

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jan Hendrik Farr
> What sort of bottleneck does the EFI stub have so that we need yet > another envelope? Well I can come up with a few advantages of UKI compared to normal bzImage with builtin initrd and cmdline. 1. You already identified this one. Using addons to adjust your cmdline 2. I can use my normal init

Re: [PATCHv6 1/3] powerpc/setup: Loosen the mapping between cpu logical id and its seq in dt

2023-09-12 Thread kernel test robot
Hi Pingfan, kernel test robot noticed the following build errors: [auto build test ERROR on powerpc/fixes] [also build test ERROR on linus/master v6.6-rc1 next-20230912] [cannot apply to powerpc/next] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jarkko Sakkinen
On Tue Sep 12, 2023 at 6:32 PM EEST, Jan Hendrik Farr wrote: > >> The format itself is rather simple. It's just a PE file (as required > >> by the UEFI spec) that contains a small stub application in the .text, > >> .data, etc sections that is responsible for invoking the contained > >> kernel and

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jan Hendrik Farr
On Tue, Sep 12, 2023, at 12:33 PM, Jarkko Sakkinen wrote: > On Tue Sep 12, 2023 at 1:54 AM EEST, Jan Hendrik Farr wrote: >> > What the heck is UKI? >> >> UKI (Unified Kernel Image) is the kernel image + initrd + cmdline (+ >> some other optional stuff) all packaged up together as one EFI >> appl

Re: [systemd-devel] [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jarkko Sakkinen
On Tue Sep 12, 2023 at 2:20 AM EEST, Neal Gompa wrote: > On Mon, Sep 11, 2023 at 7:15 PM Jarkko Sakkinen wrote: > > On Sat Sep 9, 2023 at 7:18 PM EEST, Jan Hendrik Farr wrote: > > > Hello, > > > > > > this patch implements UKI support for kexec_file_load. It will require > > > support > > > in t

Re: [PATCH 0/1] x86/kexec: UKI support

2023-09-12 Thread Jarkko Sakkinen
On Tue Sep 12, 2023 at 1:54 AM EEST, Jan Hendrik Farr wrote: > > What the heck is UKI? > > UKI (Unified Kernel Image) is the kernel image + initrd + cmdline (+ > some other optional stuff) all packaged up together as one EFI > application. > > This EFI application can then be launched directly by t

Re: [PATCH v2 2/3] vmcore: allow fadump to export vmcore even if is_kdump_kernel() is false

2023-09-12 Thread Hari Bathini
On 11/09/23 4:01 pm, Baoquan He wrote: On 09/11/23 at 05:13pm, Michael Ellerman wrote: Hari Bathini writes: Currently, is_kdump_kernel() returns true when elfcorehdr_addr is set. While elfcorehdr_addr is set for kexec based kernel dump mechanism, alternate dump capturing methods like fadump

[PATCH v3 2/2] powerpc/fadump: make is_kdump_kernel() return false when fadump is active

2023-09-12 Thread Hari Bathini
Currently, is_kdump_kernel() returns true in crash dump capture kernel for both kdump and fadump crash dump capturing methods, as both these methods set elfcorehdr_addr. Some restrictions enforced for crash dump capture kernel, based on is_kdump_kernel(), are specifically meant for kdump case and n

[PATCH v3 1/2] vmcore: remove dependency with is_kdump_kernel() for exporting vmcore

2023-09-12 Thread Hari Bathini
Currently, is_kdump_kernel() returns true when elfcorehdr_addr is set. While elfcorehdr_addr is set for kexec based kernel dump mechanism, alternate dump capturing methods like fadump [1] also set it to export the vmcore. Since, is_kdump_kernel() is used to restrict resources in crash dump capture

Re: [PATCH V2 1/2] efi/unaccepted: Do not let /proc/vmcore try to access unaccepted memory

2023-09-12 Thread David Hildenbrand
On 12.09.23 09:47, Adrian Hunter wrote: On 12/09/23 10:19, David Hildenbrand wrote: On 11.09.23 13:21, Adrian Hunter wrote: Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory

Re: [PATCH V2 1/2] efi/unaccepted: Do not let /proc/vmcore try to access unaccepted memory

2023-09-12 Thread Adrian Hunter
On 12/09/23 10:19, David Hildenbrand wrote: > On 11.09.23 13:21, Adrian Hunter wrote: >> Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 >> ("mm: Add support for unaccepted memory"), whereby a virtual machine may >> need to accept memory before it can be used. >> >> Do n

Re: [PATCH V2 1/2] efi/unaccepted: Do not let /proc/vmcore try to access unaccepted memory

2023-09-12 Thread David Hildenbrand
On 11.09.23 13:21, Adrian Hunter wrote: Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Do not let /proc/vmcore try to access unaccepted memory becaus

Re: [PATCH V2 1/2] efi/unaccepted: Do not let /proc/vmcore try to access unaccepted memory

2023-09-12 Thread David Hildenbrand
On 11.09.23 13:21, Adrian Hunter wrote: Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Do not let /proc/vmcore try to access unaccepted memory becaus

Re: [PATCH V2 2/2] proc/kcore: Do not try to access unaccepted memory

2023-09-12 Thread David Hildenbrand
On 11.09.23 13:21, Adrian Hunter wrote: Support for unaccepted memory was added recently, refer commit dcdfdd40fa82 ("mm: Add support for unaccepted memory"), whereby a virtual machine may need to accept memory before it can be used. Do not try to access unaccepted memory because it can cause th