Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754240AbbLIXvG (ORCPT ); Wed, 9 Dec 2015 18:51:06 -0500 Received: from mail-ob0-f181.google.com ([209.85.214.181]:33597 "EHLO mail-ob0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753433AbbLIXvD (ORCPT ); Wed, 9 Dec 2015 18:51:03 -0500 MIME-Version: 1.0 In-Reply-To: References: <1449666173-15366-1-git-send-email-brgerst@gmail.com> From: Andy Lutomirski Date: Wed, 9 Dec 2015 15:50:43 -0800 Message-ID: Subject: Re: [PATCH] x86/entry/64: Remove duplicate syscall table for fast path To: Brian Gerst Cc: Andy Lutomirski , "the arch/x86 maintainers" , Linux Kernel Mailing List , Borislav Petkov , =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= , Denys Vlasenko , Linus Torvalds Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1209 Lines: 33 On Wed, Dec 9, 2015 at 1:15 PM, Andy Lutomirski wrote: > On Wed, Dec 9, 2015 at 1:08 PM, Brian Gerst wrote: >> Simplified version: >> ENTRY(stub_ptregs_64) >> cmpl $fast_path_return, (%rsp) > > Does that instruction actually work the way you want it to? (Does it > link?) I think you might need to use leaq the way I did in my patch. > >> jne 1f >> SAVE_EXTRA_REGS offset=8 >> call *%rax >> RESTORE_EXTRA_REGS offset=8 >> ret >> 1: >> jmp *%rax >> END(stub_ptregs_64) > > This'll work, I think, but I still think I prefer keeping as much > complexity as possible in the slow path. I could be convinced > otherwise, though -- this variant is reasonably clean. On further reflection, there's at least one functional difference. With my variant, modifying pt_regs from sys_foo/ptregs is safe. In your variant, it's unsafe unless force_iret() is called. I don't know whether we care. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/