On Fri, Apr 1, 2016 at 7:55 AM, Zheng, Lv <lv.zheng@xxxxxxxxx> wrote: > Hi, Hi Lv, >> Add support for acpi_user_table configfs items that allows the user to >> load new tables. The data attributes contains the table data and once it >> is filled from userspace the table is loaded and ACPI devices are >> enumerated. > [Lv Zheng] > We've been considering to implement this facility before. > The 2 alternative solutions are: > 1. implement LOAD/UNLOAD ioctl for /sys/kernel/debug/acpi/acpidbg - this will be useful for extracting AML byte stream from kernel to be used by a userspace disassembler. AFAIK adding new ioctls is discouraged. > 2. transition /sys/firmware/acpi/tables/xxx into directory and implement /sys/firmware/acpi/tables/load, /sys/firmware/acpi/tables/unload - this should be able to meet your requirement. We can't do that as it would break the ABI. > So my first question is: > Why do you use configfs rather than the existing mechanisms? sysfs is not a good choice for dealing with objects created from userspace, configfs was created to address this specific need. Since we want to be able to create and load new tables from userspace this use-case fits very well with configfs. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
