>On Monday 19 December 2016 01:04 PM, Atsushi Kumagai wrote: >> Hello Kamalesh, >> >> Thanks for taking care of the scripts. >> >> The current scripts are created based on the same kernel version: >> >> =================================== >> Eppic scripts README >> ================================== >> >> The eppic scripts are based on the fedora 19 kernel. >> >> So if you update a part of the scripts, the target kernel version of >> them will be complex and confusing. >> I don't think we need to update these scripts since they are just sample, >> the purpose is to tell users how to write a script. >> > >Thank you for the review. Agree, these scripts are guide on how to write >eppic >scripts. On the other hand, if the user tries to run these scripts on >the latest kernel + >supported makedumpfile for that release, they would fail. These scripts >are outdated, >when run on latest kernel due to data structure changes. I can take up the >responsibility of maintaining eppic scripts against kernel changes for >every makedumpfile >release. If you will maintain them after this, I have no reason to reject it. I don't think all of the kernel version should be covered by the samples, but it's better to keep existing scripts because users don't always use the latest kernel. For that reason, I want to clarify the correspondence between script file and kernel version at least for existing files like: vhost_net_buffers_2_6_18_to_2_6_32.c vhost_net_buffers_2_6_33_to_3_10.c vhost_net_buffers_3_11_to_4_8.c ... // just sample, not fact Of course writing the correspondence table into README is OK, any ideas are welcome. After this clean up, let's follow up newer kernel versions. Thanks, Atsushi Kumagai
