Hi Greg, Arnd, and Daniel, > I understand that it is not appropriate to hardcode c. > How about using __setup() to add a new kernel parameter and allow the admin > to specify the sysrq command when booting?
I have received a lot of advice regarding sysrq, but after some consideration, I would like to change to calling panic() directly as in v1 instead of sysrq. If the administrator wants to request a diagnostic, I think they usually expect crash with NMI like x86 and take a dump the kernel. It's not common to handle diagnostic interrupts with sysrq now, so I don't think it's necessary to make this driver extensible at this time. Also, A64FX's BMC is not possible to send sideband data with the request, so it is difficult to take advantage of the flexibility of sysrq. If you have any comments on this, please reply. Thank you Hitomi Hasegawa _______________________________________________ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport
