在 2018年12月05日 19:30, Borislav Petkov 写道: > On Tue, Dec 04, 2018 at 05:35:09PM +0800, lijiang wrote: >> There are more people to review and improve this document together, that would >> be fine. > > That's basically kernel development :) > >> Generating VMCOREINFO is easy in the first kernel, for example: >> # makedumpfile -g VMCOREINFO -x vmlinux > > I get: > > $ makedumpfile -g VMCOREINFO -x vmlinux > The kernel version is not supported. > The makedumpfile operation may be incomplete. > > The vmcoreinfo is saved to VMCOREINFO. > > makedumpfile Completed. > > But the text file looks ok AFAICT. Please add that command to the > documentation file. > Ok, no problem. >> For these two *why*, it should be easy to understand. Because user-space tools >> need to know basic information, such as the symbol values, field offset, structure >> size, etc. Otherwise, these tools won't know how to analyze the memory of the crash >> kernel. > > That's clear. The question is *why* *exactly* is every piece of export > needed. > >> For the second question 'how they are used', we can get the answer >> from user-space tools, such as makedumpfile, crash tools. Therefore, >> it may not need to explain any more in kernel document. On the other >> hand, if we must put these contents into kernel document, i have to >> say, that would be a hard task. > > You can put one or two sentences for each, stating what they're used > for. This way, people can go and look up makedumpfile source code for > further info and people trying to add new items to VMCOREINFO can look > in this documentation here first to figure out whether maybe the info > they need has been exported already. > This is a considerate suggestion. I will try my best to do that. Thanks. Lianbo. > Thx. >