lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 9 Feb 2007 12:49:57 -0500 From: Len Brown <lenb@...nel.org> To: James Morris <jmorris@...ei.org> Cc: Rusty Russell <rusty@...tcorp.com.au>, lkml - Kernel Mailing List <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>, Andi Kleen <ak@....de>, virtualization <virtualization@...ts.osdl.org> Subject: Re: [PATCH 6c/10] lguest: the guest code On Friday 09 February 2007 12:14, James Morris wrote: > On Fri, 9 Feb 2007, Len Brown wrote: > > > On Friday 09 February 2007 05:57, Rusty Russell wrote: > > > > > +#ifdef CONFIG_ACPI > > > + acpi_disabled = 1; > > > + acpi_ht = 0; > > > +#endif > > > > If this is hard-coded to have ACPI disabled, why isn't it enforced at build-time? > > This is being disabled in the guest kernel only. The host and guest > kernels are expected to be the same build. Okay, but better to use disable_acpi() indeed, since this would be the first code not already inside CONFIG_ACPI to invoke disable_acpi(), we could define the inline as empty and you could then scratch the #ifdef too. cheers, -Len - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists