From owner-freebsd-hackers@freebsd.org Wed Feb 14 07:16:37 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 023C6F06805 for ; Wed, 14 Feb 2018 07:16:37 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6357287E8E for ; Wed, 14 Feb 2018 07:16:36 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f44.google.com with SMTP id w10so15299845lfc.9 for ; Tue, 13 Feb 2018 23:16:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=wDk7PKxVIq7dhILFQKnzmO0/4e1rc1VkyEVib5Hiz/E=; b=S+RvjLrAK5f5xyCP1XVdzvlc0qE+nSDMOtoisshDV8Myjcwuwl7cz149PNlYz3ddl8 ot4RkpslXREf1tSDI/l/amCvRFCOMuBTb/Pckwnmabapf+o1IXX2CvT71KdbscFSfZLo /ha+VOZ+KQcg8r/6LNx3yb3aAKST02bcgomm2Lq0LoyaUeBTqMVSGdOYZ0X66n9OiFDF QIiconGUejFzkneS5b7SbP7EePwZVE1gSuSQ1Hwj/BN0d775GZtt+ANugEjG7RqBuwnB B3GFYF1WzCrvjq2POy6eiE8e6GLnYTB4F+bkUnH6AP/QhHXVk/q8byBUoXPMfDx6hWXx EFSw== X-Gm-Message-State: APf1xPCxHH4uELn19qh/JhgO09AVf7gsMqczFjVnP4qLhsfA0bHKNvHn 0OgyBK4xWoMagLz0WMAH6i5ObnZQ X-Google-Smtp-Source: AH8x226PXPyzoN323jbRHPLG22aAiEc/a1JId4oEavUfLPlaN73TUVJTnt4C2RletaJJIt/AJPvq2g== X-Received: by 10.46.36.21 with SMTP id k21mr442525ljk.14.1518592588952; Tue, 13 Feb 2018 23:16:28 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id q24sm2537966lff.8.2018.02.13.23.16.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Feb 2018 23:16:28 -0800 (PST) To: FreeBSD Hackers From: Andriy Gapon Subject: IO-APIC interrupt delivery mode on Ryzen Message-ID: Date: Wed, 14 Feb 2018 09:16:26 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Feb 2018 07:16:37 -0000 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. Thank you! -- Andriy Gapon