[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101201072654.GL10050@sequoia.sous-sol.org>
Date: Tue, 30 Nov 2010 23:26:54 -0800
From: Chris Wright <chrisw@...s-sol.org>
To: Suresh Siddha <suresh.b.siddha@...el.com>
Cc: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
linux-kernel@...r.kernel.org,
Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>,
Chris Wright <chrisw@...s-sol.org>,
Max Asbock <masbock@...ux.vnet.ibm.com>,
indou.takao@...fujitsu.com,
Jesse Barnes <jbarnes@...tuousgeek.org>,
Bjorn Helgaas <bjorn.helgaas@...com>,
David Woodhouse <dwmw2@...radead.org>, stable@...nel.org
Subject: Re: [patch 1/4] vt-d: quirk for masking vtd spec errors to platform
error handling logic
* Suresh Siddha (suresh.b.siddha@...el.com) wrote:
> On platforms with Intel 7500 chipset, there were some reports of system
> hang/NMI's during kexec/kdump in the presence of interrupt-remapping enabled.
>
> During kdump, there is a window where the devices might be still using old
> kernel's interrupt information, while the kdump kernel is coming up. This can
> cause vt-d faults as the interrupt configuration from the old kernel map to
> null IRTE entries in the new kernel etc. (with out interrupt-remapping enabled,
> we still have the same issue but in this case we will see benign spurious
> interrupt hit the new kernel).
>
> Based on platform config settings, these platforms seem to generate NMI/SMI
> when a vt-d fault happens and there were reports that the resulting SMI causes
> the system to hang.
>
> Fix it by masking vt-d spec defined errors to platform error reporting logic.
> VT-d spec related errors are already handled by the VT-d OS code, so need to
> report the same erorr through other channels.
>
> Signed-off-by: Suresh Siddha <suresh.b.siddha@...el.com>
Acked-by: Chris Wright <chrisw@...s-sol.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists