When the crashkernel kernel command line option is specified, the
low 1M memory will always be reserved, which makes that the memory
allocated later won't fall into the low 1M area, thereby, it's not
necessary to create a backup region and also no need to copy the
first 640k content to a backup
In purgatory(), the main things are as below:
[1] verify sha256 hashes for various segments.
Lets keep these codes, and do not touch the logic.
[2] copy the first 640k content to a backup region.
Lets safely remove it and clean all code related to backup region.
This patch series will
Kdump kernel will reuse the first 640k region because the real mode
trampoline has to work in this area. When the vmcore is dumped, the
old memory in this area may be accessed, therefore, kernel has to
copy the contents of the first 640k area to a backup region so that
kdump kernel can read the
Hi Kazu,
Sorry for top posting, but I am on leave for Diwali Holidays and will
return to the office in a couple of days.
I have the solution/patchset ready and I just need to finish the
commit messages to make sure they are self-explanatory for upstream
acceptance.
I will try to post them and
On 10/29/19 at 02:06pm, lijiang wrote:
> >> struct crash_memmap_data {
> >> @@ -68,6 +70,19 @@ static inline void cpu_crash_vmclear_loaded_vmcss(void)
> >>rcu_read_unlock();
> >> }
> >>
> >> +/*
> >> + * When the crashkernel option is specified, only use the low
> >> + * 1MiB for the real
在 2019年10月29日 13:28, Baoquan He 写道:
> On 10/29/19 at 10:10am, Lianbo Jiang wrote:
>> Kdump kernel will reuse the first 640k region because the real mode
>> trampoline has to work in this area. When the vmcore is dumped, the
>> old memory in this area may be accessed, therefore, kernel has to
>>
