Hi Elizabeth, On Mon, Feb 19, 2024 at 11:42 PM Elizabeth Figura <zfigura@xxxxxxxxxxxxxxx> wrote: > ntsync uses a misc device as the simplest and least intrusive uAPI interface. > > Each file description on the device represents an isolated NT instance, intended > to correspond to a single NT virtual machine. > > Signed-off-by: Elizabeth Figura <zfigura@xxxxxxxxxxxxxxx> Thanks for your patch! > --- a/drivers/misc/Kconfig > +++ b/drivers/misc/Kconfig > @@ -506,6 +506,17 @@ config OPEN_DICE > > If unsure, say N. > > +config NTSYNC > + tristate "NT synchronization primitive emulation" > + help > + This module provides kernel support for emulation of Windows NT > + synchronization primitives. It is not a hardware driver. > + > + To compile this driver as a module, choose M here: the > + module will be called ntsync. > + > + If unsure, say N. Is it useful to have this feature on systems or architectures that are not supported by Windows NT? If not, this should depend on <something> || COMPILE_TEST. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds