From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 68027C433DB for ; Fri, 19 Mar 2021 16:06:12 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3170361972 for ; Fri, 19 Mar 2021 16:06:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230258AbhCSQFl (ORCPT ); Fri, 19 Mar 2021 12:05:41 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:37822 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229987AbhCSQF2 (ORCPT ); Fri, 19 Mar 2021 12:05:28 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1616169927; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=106TxHLyAtVBuDkUwRrxGzFn3N3YZC0Oy6JLDXxkcVM=; b=n6uGhy4oFLlNYqoTAK0NnbF6MwaJDk9Uo9SiCgbud5ITjJvKDa7FN9znEu5CI2G2nNszX2 EPFOhJA6EWqKAs0/3yIuIHDR2T670qEFLXxg8nZHYtgDnfF95a7P5NL96sRYPbDuNsgrXF AXJXplX08ASDvMgDdR9PH+taDshX8vMeXJhRpf6aMmbmFi3vwu0MbiwYENHRENElwK/HeQ Cs8LabpHheH1VybxTD28GLAdRWKe6tf/Fhe0BkafEqABQ3shDiAkcAu1vjFBMlcFv0OiLV AQ6ALunNdaYo49UJlF/5tG9uD1U7v+fyGx7cZIntixvcFx7U1bMEkBZGxZZ1zw== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1616169927; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=106TxHLyAtVBuDkUwRrxGzFn3N3YZC0Oy6JLDXxkcVM=; b=slKqoBUYD3EXzUUzx4Zqmba+Ip1ao4FJsSAQ60pplrT1XwRrgSLRtxr8AsUX11L+Znxxu/ 8HqnthuPOzKNJ0CQ== To: Andy Lutomirski , x86@kernel.org Cc: LKML , Mark Rutland , Brian Gerst , Andy Lutomirski , Josh Poimboeuf Subject: Re: [PATCH v4 3/9] x86/entry: Convert ret_from_fork to C In-Reply-To: References: Date: Fri, 19 Mar 2021 17:05:27 +0100 Message-ID: <87v99n5dtk.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Mar 17 2021 at 11:12, Andy Lutomirski wrote: > ret_from_fork is written in asm, slightly differently, for x86_32 and > x86_64. Convert it to C. > +__visible void noinstr ret_from_fork(struct task_struct *prev, > + int (*kernel_thread_fn)(void *), > + void *kernel_thread_arg, > + struct pt_regs *user_regs) > +{ > + instrumentation_begin(); > + > + schedule_tail(prev); > + > + if (kernel_thread_fn) { > + kernel_thread_fn(kernel_thread_arg); > + user_regs->ax = 0; If you replace this with: syscall_set_return_value(current, user_regs, 0, 0); then it's architecture agnostic and can move to kernel/entry, no? Thanks, tglx