Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3204527ybl; Mon, 19 Aug 2019 14:08:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqwFPZqdmUQLSFRt0HaS5Zwu3ZRdpdhx8Ltmiel6Lt3N7BHu6S7Hn4ZsnfSQw0uXAPsrBvll X-Received: by 2002:a17:902:7202:: with SMTP id ba2mr25283275plb.266.1566248916273; Mon, 19 Aug 2019 14:08:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566248916; cv=none; d=google.com; s=arc-20160816; b=wWSPBVTjkAJ3Yyc3ub0yPoEalQkH3NyDgz6B7vjE8M7a3uecYCs43TWXXpi5H+IevH 4bQmFkr2Qymyu3qDPDgqvvjoukDbpHCJheV565P/012JWllEuZlfoa52EOrY5dC50qZc N0dWdvdWj5m1DBnvDVW7gMpPwoBHB4kwjTjAbV43e9Rv9vbJlZZ8q38SWdHF+igwLG/G cDJ1KmzCLQzGz2Mo+GZAt6A9Q6ZVHwRnqLLjkY5yCFs9zUN1LfI5mPfEEX5jqSFk0KZR TN9xxnCsetVw80dCnb6z1AklkkxOc7wWM8NCNSRpBdEdtdXl10qRHWlWG0gIeNMdsXJ6 iUrg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=uvWb0DTWB7bj3kSWq3rM6QFTH1NBwMPuUbb6f3frp9c=; b=HTeWtjMyy0aPU+7OXcP/VKJhOO5aH8lKgaGscsswO3eFkQDs+MEvDuYKR7nukT3z8n nAcE/On1+O9S5wYPoFMKzWiiTnJ7kpaBRfFTmE98hJfi0qfxaQ2hicETy+gOhvGjd72x CAwZBZgP1Mk+UHI2R4BDgHuWcMk1de/hsjFeg8AsK19nefENN6FXWBmxwQSzh3G4jXhT TrLpH4aegFx6vKuwD/kVBEJ8VUMWSurG8EulPOHhKaI079bme/AaszGDLBPpt9vUKJ9k DFW2oQbpKTYuZTDk0MtMy0UmFKxyg0QjTAmqSAYNxL0+k+U+Yrp/qxVXbyQTkjrApS0w KaDw== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r200si10355031pgr.518.2019.08.19.14.08.20; Mon, 19 Aug 2019 14:08:36 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728363AbfHSVHJ (ORCPT + 99 others); Mon, 19 Aug 2019 17:07:09 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:49463 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728018AbfHSVHJ (ORCPT ); Mon, 19 Aug 2019 17:07:09 -0400 Received: from pd9ef1cb8.dip0.t-ipconnect.de ([217.239.28.184] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hzoro-0004Nn-57; Mon, 19 Aug 2019 23:07:04 +0200 Date: Mon, 19 Aug 2019 23:07:03 +0200 (CEST) From: Thomas Gleixner To: Bandan Das cc: Ingo Molnar , Borislav Petkov , x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86/apic: reset LDR in clear_local_APIC In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Bandan, On Wed, 14 Aug 2019, Bandan Das wrote: > On a 32 bit RHEL6 guest with greater than 8 cpus, the > kdump kernel hangs when calibrating apic. This happens > because when apic initializes bigsmp, it also initializes LDR > even though it probably wouldn't be used. 'It probably wouldn't be used' is a not really a useful technical statement. Either it is used, then it needs to be handled. Or it is unused then why is it written in the first place? The bigsmp APIC uses physical destination mode because the logical flat model only supports 8 APICs. So clearly bigsmp_init_apic_ldr() is bogus and should be empty. > When booting into kdump, KVM apic incorrectly reads the stale LDR > values from the guest while building the logical destination map > even for inactive vcpus. While KVM apic can be fixed to ignore apics > that haven't been enabled, a simple guest only change can be to > just clear out the LDR. This does not make much sense either. What has KVM to do with logical destination maps while booting the kdump kernel? The kdump kernel is not going through the regular cold/warm boot process, so KVM does not even know that the crashing kernel jumped into the kdump one. What builds the logical destination maps and what has LDR and the KVM APIC to do with that? I'm not opposed to the change per se, but I'm not accepting change logs which have the fairy tale smell. Thanks, tglx