From nobody Thu Jan 13 08:12:31 2022 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id A284F19428A1 for ; Thu, 13 Jan 2022 08:12:35 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JZHGq42NCz3JSh for ; Thu, 13 Jan 2022 08:12:35 +0000 (UTC) (envelope-from avg@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1642061555; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NBnH4AGcPt4xGmTLfiTCJqVVSdrwtP8eUWj6HWkkEeI=; b=B4ERl4XF4D+A01n94C5nPwst2+tBSlKMa6htYuder7zkawh6DOkfDGHKl2tHJNa+FfKkYy 3ft4e794Ri3gMbZgCpj22URmYWVhl9v5DK2elUIGSSySuKJkXhDzmi68mByC4YZNDdRFIC eVLKT/pYXnCWaI7DLsCIlG9HcBil/AfVA/DAfj9K/IfwWLz+KYQMrKlq5mUmGjsA1bPRdC q9LlMk3FQhwCPk9S3pYaLVCcujQaJHbPScXhHPe/j5MgSM2h1zrDtbGrUoMSLbwQWC49oR T0dieC79TXV3B22sFbGvzUMuTJSc1sLIUMq2z7W5RvPQajiNyYGHaZAixXRbUQ== Received: from [192.168.0.88] (unknown [195.64.148.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: avg/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 33517299D3 for ; Thu, 13 Jan 2022 08:12:35 +0000 (UTC) (envelope-from avg@FreeBSD.org) Message-ID: <54e5f61c-64fd-0ebf-c3cd-d4a7a4cbb7e7@FreeBSD.org> Date: Thu, 13 Jan 2022 10:12:31 +0200 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.4.1 Subject: Re: IO-APIC interrupt delivery mode on Ryzen Content-Language: en-US From: Andriy Gapon To: FreeBSD Hackers References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1642061555; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=NBnH4AGcPt4xGmTLfiTCJqVVSdrwtP8eUWj6HWkkEeI=; b=Y0ZixbdkhuyyVqVA3INiT3GdcLZj8tGSTSXVgaFM8Y0VR3I7dHehU3eLDf7buqm8HxxXoo CpZi7LXit76Q3Qc6r4cvFO0TsdZPUoCNyn0ssMDCyLX02lpyeazV0jXj7l6aIvW02FpxAU 60opFTLXeW1CY3h0O/4nPauCc+k4fZgDQvxHngNzdiAtgqIuzzgEG6CJFgVQx+SXY45GQQ JbqDy3SMWOOArE1lM85qhEQuMkwxSosXeCy2N8bL/agUVnfdIt/iyx8+V7xVe+63bVFEQW 67C4/4hKDJS4OBPbwFBOhfClgCtsB4fsTpD4RqhhZdCYA/iKWvSVvCO/CAO2xA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1642061555; a=rsa-sha256; cv=none; b=hVdPUk9w8iiGser6b1RDZoiBGpoxD/pZSaJuRYusY8AV5xbaZ2X3JzfpdDIoSjvaJ/B9zB ttk4KGXp8ToiuA8sZ47YjjLfOhlI2IEO56i3c7PxMgCPLzz0HUoQnrnj6TmjJroPGh2rVO yUXukJV3k+1sXywIwwQewgSomCT/23UCD3/ejpTi1rPqKo3OH2ePnW2ZYGtNEGZmcSbrQ+ Sm30CGe6jXpQs/3kUYEM/r7VLVnrBE6EVbKgzhShNmN7OGJJYRL1trFLxl+KIPFIMq1LQa rDZi3hHXouDjLLx/cidvK0QRw4TJky9zAM1snjbcbRA94Pvds/T/snGcJ3ySjQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 14/02/2018 09:16, Andriy Gapon wrote: > > A while ago I discovered that all AMD IO-APICs (in separate southbridges and in > FCHs) had a bug with respect to how the interrupt delivery mode got interpreted. > I am curious if the problem has been fixed in Ryzen or if it is being carried on. > > I would appreciate any help with testing that. > > The discussion of the problem and the tests I used can be found in this thread: > https://mail.coreboot.org/pipermail/coreboot/2016-October/082148.html > https://mail.coreboot.org/pipermail/coreboot/2016-October/082156.html > > If you are interested and it's not really clear how to conduct a test, please > write me. FWIW, Ryzen IO-APICs do not have the problem. They interpret the delivery mode according to the APIC specification, not the HyperTransport one. -- Andriy Gapon