On Tuesday, July 26, 2016 07:01:33 PM Lv Zheng wrote: > This patch adds debugger output flushing support in kernel via .ioctl() > callback. The in-kernel flushing is more efficient, because it reduces > useless log IOs by bypassing log user_read/kern_write during the flush > period. > > This mechanism is useful for the batch mode. Is it only useful or is it required? Also the batch mode is introduced by the remaining patches in the series, isn't it? > Scripts can integrate a batch mode acpidbg instance to perform AML debugger > functionalities. This sentence is not parsable for me. What does it mean, really? > As the batch mode always starts from a new command write, it thus requires > the kernel debugger driver to drop the old input/output first. What does "the old" mean here? > The old input is automatically dropped by acpi_os_get_line() via an error > returning value, I can't parse this too, sorry. > but the output are remained in acpi_dbg output buffers and should be > dropped prior than reading the new command, otherwise, the old output can > be read out by the batch mode instance and the result of the batch mode > command will be messed up. Can you give an example here for clarity, please? Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
