Re: [PATCH v2 00/14] Split crash out from kexec and clean up related config items

Hi Baoquan, On 04/02/24 8:56 am, Baoquan He wrote: Hope Hari and Pingfan can help have a look, see if it's doable. Now, I make it either have both kexec and crash enabled, or disable both of them altogether. Sure. I will take a closer look... Thanks a lot. Please feel free to post patches to

Re: [PATCHv7 07/16] x86/mm: Return correct level from lookup_address() if pte is none

On 02/20/24 at 02:36pm, Kirill A. Shutemov wrote: > On Tue, Feb 20, 2024 at 06:25:43PM +0800, Baoquan He wrote: > > > I am not sure what part of the comment you see doesn't reflect the > > > behaviour. From my PoV, changed code matches the comment closer that > > > original. > > > > Oh, I didn't

Re: [PATCH v5 0/8] ima: kexec: measure events between kexec load and execute

On Wed, 2024-02-14 at 07:38 -0800, Tushar Sugandhi wrote: > The current Kernel behavior is IMA measurements snapshot is taken at > kexec 'load' and not at kexec 'execute'. IMA log is then carried > over to the new Kernel after kexec 'execute'. 'Kernel' should not be capitalized since it isn't a

Re: [PATCH v5 1/8] ima: define and call ima_alloc_kexec_file_buf

On Wed, 2024-02-14 at 07:38 -0800, Tushar Sugandhi wrote: > Carrying the IMA measurement list across kexec requires allocating a > buffer and copying the measurement records. Separate allocating the > buffer and copying the measurement records into separate functions in > order to allocate the

Re: [PATCH 1/2] x86/mm: Do not zap PMD entry mapping unaccepted memory table during kdump.

Hi Kirill, On 2/20/2024 6:42 AM, Kirill A. Shutemov wrote: On Tue, Feb 20, 2024 at 01:18:29AM +, Ashish Kalra wrote: From: Ashish Kalra During crashkernel boot only pre-allocated crash memory is presented as E820_TYPE_RAM. This can cause PMD entry mapping unaccepted memory table to be

Re: [PATCH linux-next 1/3] kexec/kdump: make struct crash_mem available without CONFIG_CRASH_DUMP

On 02/13/24 at 05:01pm, Hari Bathini wrote: > struct crash_mem defined under include/linux/crash_core.h represents > a list of memory ranges. While it is used to represent memory ranges >From its name, it's not only representing memory ranges, it's representing crash memory ranges. Except of

Re: [PATCH 1/2] x86/mm: Do not zap PMD entry mapping unaccepted memory table during kdump.

On Tue, Feb 20, 2024 at 01:18:29AM +, Ashish Kalra wrote: > From: Ashish Kalra > > During crashkernel boot only pre-allocated crash memory is presented as > E820_TYPE_RAM. This can cause PMD entry mapping unaccepted memory table > to be zapped during phys_pmd_init() as SNP/TDX guest use

Re: [PATCHv7 07/16] x86/mm: Return correct level from lookup_address() if pte is none

On Tue, Feb 20, 2024 at 06:25:43PM +0800, Baoquan He wrote: > > I am not sure what part of the comment you see doesn't reflect the > > behaviour. From my PoV, changed code matches the comment closer that > > original. > > Oh, I didn't make it clear. I mean update the code comment for >

Re: [PATCH v3 09/17] x86: Add KHO support

Hi Alex, On Wed, Jan 17, 2024 at 02:46:56PM +, Alexander Graf wrote: > We now have all bits in place to support KHO kexecs. This patch adds > awareness of KHO in the kexec file as well as boot path for x86 and > adds the respective kconfig option to the architecture so that it can > use KHO

Re: [PATCHv7 07/16] x86/mm: Return correct level from lookup_address() if pte is none

On 02/19/24 at 03:52pm, Kirill A. Shutemov wrote: > On Mon, Feb 19, 2024 at 01:12:32PM +0800, Baoquan He wrote: > > On 02/12/24 at 12:44pm, Kirill A. Shutemov wrote: > > > lookup_address() only returns correct page table level for the entry if > > > the entry is not none. > > > > > > Make the