| 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, 02 May 2014 14:37:57 -0700 From: "H. Peter Anvin" <h.peter.anvin@...el.com> To: Linus Torvalds <torvalds@...ux-foundation.org>, Andy Lutomirski <luto@...capital.net> CC: Thomas Gleixner <tglx@...utronix.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, the arch/x86 maintainers <x86@...nel.org>, Steven Rostedt <rostedt@...dmis.org>, Gleb Natapov <gleb@...nel.org>, Paolo Bonzini <pbonzini@...hat.com> Subject: Re: [RFC/HACK] x86: Fast return to kernel On 05/02/2014 02:07 PM, Linus Torvalds wrote: > On Fri, May 2, 2014 at 2:04 PM, Andy Lutomirski <luto@...capital.net> wrote: >> >> Because otherwise I'd have to keep track of whether it's a zeroentry >> or an errorentry. I can't stuff the offset in a register without even >> more stack hackery, since there are no available registers there. I >> could split the whole thing into two code paths, I guess. > > Ahh. Never mind. I didn't think about the fact that the error entry > case had one more field on the stack. Your approach is all fine, it > was me not seeing the problem. > I have to admit to being rather partial to the idea of simply doing "push $0" on entry for the vectors that don't push an error code, like the early exception handling code does. -hpa -- 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