When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86), which describes the CPUs
and memory in the system, must also be updated, else the resulting
vmcore is inaccurate (eg. missing either CPU context or memory
regions).
The current solution utilizes
Nudge...
Thanks!
eric
On 6/13/22 17:42, Eric DeVolder wrote:
When the kdump service is loaded, if a CPU or memory is hot
un/plugged, the crash elfcorehdr (for x86), which describes the CPUs
and memory in the system, must also be updated, else the resulting
vmcore is inaccurate (eg. missing eith
On 07/05/22 at 10:17am, Eric DeVolder wrote:
> Nudge...
> Thanks!
Seems DavidH has concern and rasied it after you posted v9. Is that
solved?
>
> On 6/13/22 17:42, Eric DeVolder wrote:
> > When the kdump service is loaded, if a CPU or memory is hot
> > un/plugged, the crash elfcorehdr (for x86),
On 7/5/22 20:16, Baoquan He wrote:
On 07/05/22 at 10:17am, Eric DeVolder wrote:
Nudge...
Thanks!
Seems DavidH has concern and rasied it after you posted v9. Is that
solved?
In looking at David's comments on v8:
- [PATCH v8 2/7] crash: prototype change for crash_prepare_elf64_headers
I a
Baoquan,
I believe I've addressed all feedback, just checking to see if you agree.
I have the next patch set ready in the event you think it a good idea to post
it.
Thanks!
eric
On 7/7/22 08:05, Eric DeVolder wrote:
On 7/5/22 20:16, Baoquan He wrote:
On 07/05/22 at 10:17am, Eric DeVolder wr
On 07/20/22 at 02:08pm, Eric DeVolder wrote:
> Baoquan,
> I believe I've addressed all feedback, just checking to see if you agree.
> I have the next patch set ready in the event you think it a good idea to post
> it.
> Thanks!
Thanks for the effort. Please post them for reviewing. The newly made
