Received: by 2002:ab2:6a05:0:b0:1f8:1780:a4ed with SMTP id w5csp3112897lqo; Tue, 14 May 2024 23:03:41 -0700 (PDT) X-Forwarded-Encrypted: i=3; AJvYcCUZeh7EvIf1w9VkCcnr90p5L+qd8uOLV8OwTGZV2u+5gDPTaHH5Z/SWapRwAmmJRbw/nwGx13tP3p3zahCtjd5ROT+GZBNAP5hXCqW5cw== X-Google-Smtp-Source: AGHT+IGTqsFYrBjuIjC8TxLK1n4RYTjMn+6vZh5bwj6gLuXT3KMOWyw0fWcKbV93KeoaJvOohst4 X-Received: by 2002:a17:906:ae99:b0:a59:be21:3587 with SMTP id a640c23a62f3a-a5a2d18aa67mr1264798666b.8.1715753021151; Tue, 14 May 2024 23:03:41 -0700 (PDT) ARC-Seal: i=2; a=rsa-sha256; t=1715753021; cv=pass; d=google.com; s=arc-20160816; b=IbDwszkfQll4Et7mM8cSs0OOmmGRmHgiuxQ4AhF/DC/PWjj4mwBfefYwWkLR1LJHiV AP5QpuWCUacQH7ar1xlt9oyEjVhMYpaH1KpJ/sYxq4jdfmiWUC3f95vId+9pdlx+E/oX MeSLRMScaFxunHSrzvlMI79RQd0NL47wHHg8vH9npXS1rM2txiiSP0rR9jAW0Vf4HyuV lw62sBxTTWs0hx8j0jLZas8CoL/dNpDVSjpNJ3yR3AUszi37Q9ymzO/thUhvK539g41Z P9X62QvbH72QWpmwL/5Dzvqc+IIGOtbwV8cARF20cZ0W6Je1sMVg5W6x2baksVwDT9lP Lj2g== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:in-reply-to:from:content-language :references:cc:to:subject:user-agent:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:date:message-id; bh=BQ18AX0p1ygeWjfQiTMaF0FMtWssGWybr9aFWVown6A=; fh=c6MRpx46Nd/9/k86wLBHhpHY2nq6zEfPNrxVViE+jWI=; b=tBd6C3sqXyyLEjpHh2YMIW7ktRTvc71RefuWp3wVQAF0D5hlLzibDAmtR/xZJnsvVe dxY4HsSkL8vbGLniPc76YiO7Entid/3alnCtUrKyimFa2RRhO2OtPGyGupQxNofajY3K px+OxDD5QLW3+1ZYnkE22xJsIO0prlgDnJAMeD6DoMnkTgRFLGT2ZHGJRhrN6/a9snxi c+eD1CDbWt3uNh23Vd33neskgh90bOGyYimzFTJ+qVUJas+cZi6bVe9wHt8UNZsT4wMt 6vcmGgZEoUirxotzEZanYOgi7pmXMLkcUouskfVsZuPjcsH1/tRRXbKwhlCPp6+OEmVi ytUg==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; arc=pass (i=1 spf=pass spfdomain=molgen.mpg.de); spf=pass (google.com: domain of linux-kernel+bounces-179502-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-179502-linux.lists.archive=gmail.com@vger.kernel.org" Return-Path: Received: from am.mirrors.kernel.org (am.mirrors.kernel.org. [2604:1380:4601:e00::3]) by mx.google.com with ESMTPS id a640c23a62f3a-a5a1797d9easi683779366b.268.2024.05.14.23.03.41 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 14 May 2024 23:03:41 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel+bounces-179502-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3; Authentication-Results: mx.google.com; arc=pass (i=1 spf=pass spfdomain=molgen.mpg.de); spf=pass (google.com: domain of linux-kernel+bounces-179502-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) smtp.mailfrom="linux-kernel+bounces-179502-linux.lists.archive=gmail.com@vger.kernel.org" Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by am.mirrors.kernel.org (Postfix) with ESMTPS id B32121F20F7F for ; Wed, 15 May 2024 06:03:40 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 2EC803B78D; Wed, 15 May 2024 06:03:35 +0000 (UTC) Received: from mx3.molgen.mpg.de (mx3.molgen.mpg.de [141.14.17.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 426E33A29F for ; Wed, 15 May 2024 06:03:31 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=141.14.17.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715753014; cv=none; b=mLXVLTdgeHe8uGlG66R7CX/7IkgpmoQgh0dQymvahZNHtCr68KOZ2V+yiFEXmLiM+rJjmkL1j5CjK0tJ4+Tbfgo5T8bJRDLO67ADkQIMyZhO5IXhpeHMlxr3H6X3n6c/dubRcs5FgxA+IS8Izr5Awu240ZLctLo/RuHyiJP74x8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1715753014; c=relaxed/simple; bh=A0JCQ/+cjp3ne63Df0ewOWwu5MRtXQ66AotJ2DruUR0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=iRjBdtXxMocMFyzlgRgyLMiju6f8QxGYtPPtg5VPiUtdiaia7a5KZSfispW6ry4Q6g6qobcbkrI2p0tArh07wxBAZ8v2ZVYM3xxkegw7ZtIkVKKyb6gfTQatnqvKTba18ETE73sgacXQPpQN9uqgG7Ya151ymrkxyznR24GHj6g= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de; spf=pass smtp.mailfrom=molgen.mpg.de; arc=none smtp.client-ip=141.14.17.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=molgen.mpg.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=molgen.mpg.de Received: from [192.168.0.2] (ip5f5af258.dynamic.kabel-deutschland.de [95.90.242.88]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: pmenzel) by mx.molgen.mpg.de (Postfix) with ESMTPSA id 32BCD61E5FE07; Wed, 15 May 2024 08:02:56 +0200 (CEST) Message-ID: Date: Wed, 15 May 2024 08:02:55 +0200 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: DMAR-IR: IRQ remapping was enabled on dmar6 but we are not in kdump mode To: Baolu Lu Cc: =?UTF-8?B?SsO2cmcgUsO2ZGVs?= , Will Deacon , iommu@lists.linux.dev, linux-kernel@vger.kernel.org References: <5517f76a-94ad-452c-bae6-34ecc0ec4831@molgen.mpg.de> <433452d0-589a-49c8-8044-dcc93d5be90a@linux.intel.com> <24bf9a11-6abd-4ccf-9ca1-3cf75c45d374@molgen.mpg.de> <42b53bff-4027-4cb6-a457-e26fd62895e5@linux.intel.com> <61ce93c7-e89c-4217-8095-dde9fb01763c@molgen.mpg.de> <7eb01b85-9233-4f21-865e-6d128f39fb46@linux.intel.com> Content-Language: en-US From: Paul Menzel In-Reply-To: <7eb01b85-9233-4f21-865e-6d128f39fb46@linux.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dear Baolu, Am 15.05.24 um 04:13 schrieb Baolu Lu: > On 5/15/24 3:46 AM, Paul Menzel wrote: >> Am 23.01.24 um 01:55 schrieb Baolu Lu: >>> On 2024/1/22 22:53, Paul Menzel wrote: >>>> Am 22.01.24 um 13:38 schrieb Baolu Lu: >>>>> On 2024/1/19 22:45, Paul Menzel wrote: >>>>>> >>>>>> On a Dell PowerEdge T640, Linux 5.9 and 6.6.12 warn about kdump: >>>>>> >>>>>>      [    2.728445] DMAR-IR: IRQ remapping was enabled on dmar6 but we are not in kdump mode >>>>>>      [    2.736544] DMAR-IR: IRQ remapping was enabled on dmar5 but we are not in kdump mode >>>>>>      [    2.744620] DMAR-IR: IRQ remapping was enabled on dmar4 but we are not in kdump mode >>>>>>      [    2.752695] DMAR-IR: IRQ remapping was enabled on dmar3 but we are not in kdump mode >>>>>>      [    2.760774] DMAR-IR: IRQ remapping was enabled on dmar2 but we are not in kdump mode >>>>>>      [    2.768847] DMAR-IR: IRQ remapping was enabled on dmar1 but we are not in kdump mode >>>>>>      [    2.776922] DMAR-IR: IRQ remapping was enabled on dmar0 but we are not in kdump mode >>>>>>      [    2.784999] DMAR-IR: IRQ remapping was enabled on dmar7 but we are not in kdump mode >>>>>> >>>>>> Looking through the logs, this only happens when using kexec to >>>>>> restart the system. >>>>> >>>>> The code that warned this is, >>>>> >>>>>   599         if (ir_pre_enabled(iommu)) { >>>>>   600                 if (!is_kdump_kernel()) { >>>>>   601                         pr_warn("IRQ remapping was enabled on %s but we are not in kdump mode\n", >>>>>   602                                 iommu->name); >>>>>   603                         clear_ir_pre_enabled(iommu); >>>>>   604                         iommu_disable_irq_remapping(iommu); >>>>>   605                 } >>>>> >>>>> The VT-d interrupt remapping is enabled during boot, but this is not a >>>>> kdump kernel. >>>>> >>>>> Do you mind checking whether the disable interrupt remapping callback >>>>> was called during kexec reboot? >>>>> >>>>> 1121 struct irq_remap_ops intel_irq_remap_ops = { >>>>> 1122         .prepare                = intel_prepare_irq_remapping, >>>>> 1123         .enable                 = intel_enable_irq_remapping, >>>>> 1124         .disable                = disable_irq_remapping, >>>>> 1125         .reenable               = reenable_irq_remapping, >>>>> 1126         .enable_faulting        = enable_drhd_fault_handling, >>>>> 1127 }; >>>> >>>> Is there a way to check this without rebuilding the Linux kernel? >>> >>> I am not sure, but you can check whether any messages are dumped in the >>> path of .disable callback? or try to use ftrace? >> >> With >> >> ``` >> diff --git a/drivers/iommu/intel/irq_remapping.c >> b/drivers/iommu/intel/irq_remapping.c >> index 712ebfc9870c6..146f19ae5b5f1 100644 >> --- a/drivers/iommu/intel/irq_remapping.c >> +++ b/drivers/iommu/intel/irq_remapping.c >> @@ -1030,6 +1030,7 @@ static void disable_irq_remapping(void) >>       struct dmar_drhd_unit *drhd; >>       struct intel_iommu *iommu = NULL; >> >> +     pr_warn("XXX: Called %s\n", __func__); >>       /* >>        * Disable Interrupt-remapping for all the DRHD's now. >>        */ >> ``` >> >> I can’t see anything in the logs, so it does not seem to be called. >> >> Can you reproduce the issue? > > How did you reproduce this? On a “server” (with Intel Xeon?), in my case Dell PowerEdge T640 and Dell PowerEdge R930 (Intel E7-8891 v3), run kexec /boot/bzImage --initrd=/boot/grub/initramfs.igz --reuse-cmdline Kind regards, Paul