Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp3768701ybi; Fri, 5 Jul 2019 13:38:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqwA0vRXp/hmDA2bMrzs1o6sdpTSYiOY+9IsGu2VCuzmMZ3zwV3+dwBPpurBH0ftSjn4Qpkt X-Received: by 2002:a63:dd4d:: with SMTP id g13mr7261730pgj.399.1562359108470; Fri, 05 Jul 2019 13:38:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562359108; cv=none; d=google.com; s=arc-20160816; b=RDgd8d4RFwYJ3dnPG3+htNGp+/5v3Qwqo3QpVjPlGpTiTKtVBQXFIWcSz9PtKLWCuK 9LRsyOXLjxFAz2ZLNOWCcryK1QRJ7kxeNTCcLR3UxtOXbSai1j/LPxOGez7JhYwK+Rba CMNnO65iUe+bs1NXoS3K+CdBtfeFyXHa+CkicPGbTGtCD72PkymDz0GAFNoXEfPMhYpH It/dplpolT5ihgnvHDOWqX+XytowkrE4C4u9+/wclFrcm8rmYnNSDetkJfgCcm64+IS3 wzgZoGEKSC9YX92oSAzbDkj3XpTQYHXRYN8dHig8/FbYBMIOLcYbfywr04AVCeAUqX+l tRKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=hwhM69pmTFqEa0SelOVjjaypvVZxj65DbIJ71+kxY1Q=; b=0xrKu+FviK6P6/X5exbDLWkyuklue8bpmiGT3wqbVoWRuZm7VHaN/PYKqFZqg6yWuS kOEJWZ1YJG6Qpnvl2YkvfP4vHSCPu4WUX+Bhjo+lPc7PA16+/dNG8cHXkaAf111TF+PJ sCGst9DE6g+a4vBPOt95cVskhNiiVRchPi5VBsA6kurE5icDZTGYeXOOAlNjziSrLtyc pdikHou420EjO17m1WoA+0nVsrHmGjhetLq/e6JKkhwTTz0+Hii9oFyLxEE0H5126BqA m8rpKQ3bW7i2oudwmc08xG9ePApRuBDqhk2ZafCg+HYMN9oRhnVVdgfnuObvkAvRmp8T zuNg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vgxt420O; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p3si9131070pjr.18.2019.07.05.13.38.13; Fri, 05 Jul 2019 13:38:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=vgxt420O; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728014AbfGEUhp (ORCPT + 99 others); Fri, 5 Jul 2019 16:37:45 -0400 Received: from mail.kernel.org ([198.145.29.99]:36812 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725813AbfGEUhp (ORCPT ); Fri, 5 Jul 2019 16:37:45 -0400 Received: from mail-wm1-f46.google.com (mail-wm1-f46.google.com [209.85.128.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1E6F821852 for ; Fri, 5 Jul 2019 20:37:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1562359064; bh=R/NZzyRB8n045WyDB+KpdTaWasPlNT5Oy3/V7eWIzqc=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=vgxt420OxsPZ7jUL6hr4u5hltEsus7q8RHArHiTsTO87dnjmEiTXBKka0QiwCS69P jH8Qff/o0KfZJ8eVeJhMhB5MXNHE4XGJ+i8YXJE8pIIHBPaTDfJL0LSTar4FdpNIQF 1WteLkIA/74U/B23jVgkxCGjuJh7w+e6Xid2Z/M8= Received: by mail-wm1-f46.google.com with SMTP id z23so10829928wma.4 for ; Fri, 05 Jul 2019 13:37:44 -0700 (PDT) X-Gm-Message-State: APjAAAV9r79atmvSYYsXGNbqacJO62ecF4c3GHSI02uRMk7h/gRK5IL2 JLXh2GUzFJRy0g1CViZ3Z4wClh6e4GWMILaqYJP/xA== X-Received: by 2002:a1c:a942:: with SMTP id s63mr4590144wme.76.1562359062690; Fri, 05 Jul 2019 13:37:42 -0700 (PDT) MIME-Version: 1.0 References: <20190704155145.617706117@linutronix.de> <20190704155608.636478018@linutronix.de> <958a67c2-4dc0-52e6-43b2-1ebd25a59232@citrix.com> In-Reply-To: From: Andy Lutomirski Date: Fri, 5 Jul 2019 13:37:31 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [patch V2 04/25] x86/apic: Make apic_pending_intr_clear() more robust To: Thomas Gleixner Cc: Andrew Cooper , LKML , X86 ML , Nadav Amit , Ricardo Neri , Stephane Eranian , Feng Tang , Andy Lutomirski , Paolo Bonzini Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 5, 2019 at 1:25 PM Thomas Gleixner wrote: > > Andrew, > > > > > These can be addressed by setting TPR to 0x10, which will inhibit > > Right, that's easy and obvious. > This boots: diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c index 177aa8ef2afa..5257c40bde6c 100644 --- a/arch/x86/kernel/apic/apic.c +++ b/arch/x86/kernel/apic/apic.c @@ -1531,11 +1531,14 @@ static void setup_local_APIC(void) #endif /* - * Set Task Priority to 'accept all'. We never change this - * later on. + * Set Task Priority to 'accept all except vectors 0-31'. An APIC + * vector in the 16-31 range can be delivered otherwise, but we'll + * think it's an exception and terrible things will happen. + * We never change this later on. */ value = apic_read(APIC_TASKPRI); value &= ~APIC_TPRI_MASK; + value |= 0x10; apic_write(APIC_TASKPRI, value); apic_pending_intr_clear();