On Thu, Feb 28, 2013 at 12:55 PM, James Bottomley <jbottomley@xxxxxxxxxxxxx> wrote: > If you want a filesystem > in /sys, then you have the same problem as debugfs and cgroupfs, so it > can't be done without distro support: specifically a fstab entry, so > this patch is as far as the kernel should go. Sure, something would have to do the actual mounting for you. In systemd this is done during early boot to /sys/firmware/efi/efivars/ [0], which means that until Matt's rework is in, it will only work when efivars is compiled into the kernel. > Even a split won't solve the problem that the directory won't exist > until the modules are loaded and the modules are autoloaded by the mount > call, so the problem is the same whether the modules are split or > monolithic. Sorry, I was unclear. The efi subsystem itself would not be a module, and hence /sys/firmware/efi/efivars would always exist if the system supports it (similarly to, say, /sys/firmware/acpi). The relevant patch is here [1]. > We definitely need this patch in 3.8 because that's where the efivarfs > filesystem was added, so it should probably have a cc stable which I > forgot. Yeah, that might make sense for now (though, due to the above, this would not really help any of the distros, so they'd need to compile efivars into the kernel anyway). Cheers, Tom [0]: <http://cgit.freedesktop.org/systemd/systemd/tree/src/core/mount-setup.c#n93> [1]: <http://www.mail-archive.com/linux-efi@xxxxxxxxxxxxxxx/msg00785.html> -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
