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
| ||
|
Message-ID: <alpine.LFD.0.9999.0710261210290.3186@localhost.localdomain> Date: Fri, 26 Oct 2007 12:20:35 +0200 (CEST) From: Thomas Gleixner <tglx@...utronix.de> To: "Huang, Ying" <ying.huang@...el.com> cc: Andrew Morton <akpm@...ux-foundation.org>, "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>, Andi Kleen <ak@...e.de>, "Eric W. Biederman" <ebiederm@...ssion.com>, Chandramouli Narayanan <mouli@...ux.intel.com>, LKML <linux-kernel@...r.kernel.org>, Arjan van de Ven <arjan@...radead.org> Subject: Re: [PATCH 1/3 -v4] x86_64 EFI runtime service support: EFI basic runtime service support On Fri, 26 Oct 2007, Huang, Ying wrote: > On Fri, 2007-10-26 at 10:48 +0200, Thomas Gleixner wrote: > > > EFI uses the Windows x86_64 calling convention. The lin2win may be a > > > more general naming convention that can be used for some other code (the > > > NDISwrapper?) in the future. Do you agree? > > > > I agree not at all. I do not care whether the EFI creators smoked the > > Windows-crackpipe or some other hallucinogen when they decided to use > > this calling convention. We definitely do not want to think about > > NDISwrapper or any other Windows related hackery in the kernel. > > OK, I will change the name to something like lin2efi. Can we simply use call_efi_XXX(). lin2efi() sounds like a conversion routine, but it is not. tglx - 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