Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 19 May 2021 09:17:30 -0700
User-Agent: K-9 Mail for Android
In-Reply-To: <YKT2mW0xVZltBOSh@gmail.com>
References: <20210518191303.4135296-1-hpa@zytor.com> <YKT2mW0xVZltBOSh@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PATCH v4 0/6] x86/syscall: use int for x86-64 system calls
To:     Ingo Molnar <mingo@kernel.org>
CC:     Thomas Gleixner <tglx@linutronix.de>,
        Ingo Molnar <mingo@redhat.com>,
        Andy Lutomirski <luto@kernel.org>,
        Borislav Petkov <bp@alien8.de>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
From:   "H. Peter Anvin" <hpa@zytor.com>
Message-ID: <62DB118D-3923-42E8-B3D2-3DF98F9A84C7@zytor.com>
Precedence: bulk

:)

On May 19, 2021 4:29:29 AM PDT, Ingo Molnar <mingo@kernel=2Eorg> wrote:
>
>* H=2E Peter Anvin <hpa@zytor=2Ecom> wrote:
>
>> From: "H=2E Peter Anvin (Intel)" <hpa@zytor=2Ecom>
>>=20
>> This patchset addresses several inconsistencies in the handling of
>> system call numbers in x86-64 (and x32)=2E
>
>>  arch/x86/entry/common=2Ec                         |  93 +++--
>>  arch/x86/entry/entry_64=2ES                       |   2 +-
>>  arch/x86/include/asm/syscall=2Eh                  |   2 +-
>>  tools/testing/selftests/x86/syscall_numbering=2Ec | 488
>+++++++++++++++++++++---
>>  4 files changed, 508 insertions(+), 77 deletions(-)
>
>Thanks Peter - this series is really nice now, and I agree that this=20
>inconsistency should be fixed=2E
>
>Thanks,
>
>	Ingo

--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E