public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Lenny Szubowicz <lszubowi@redhat.com>
Cc: "Uwe Kleine-König" <uwe@kleine-koenig.org>,
	linux-kernel@vger.kernel.org, rafael.j.wysocki@intel.com,
	tglx@linutronix.de, x86@kernel.org,
	"Lu Baolu" <baolu.lu@linux.intel.com>
Subject: Re: Failure to shutdown/reboot with intel_iommu=on
Date: Tue, 12 May 2020 23:13:18 +0200	[thread overview]
Message-ID: <20200512211317.GG8135@suse.de> (raw)
In-Reply-To: <26b328dc-2161-fdaa-f533-bf0027c13efc@redhat.com>

Hi Lenny,

On Tue, May 12, 2020 at 04:00:26PM -0400, Lenny Szubowicz wrote:
> Some Lenovo laptops provide an ACPI DMAR RMRR that identifies the memory
> range that the kernel should open up for permissable DMA access
> for this purpose. Unfortunately, the PCI device that performs these
> DMA operations is hidden from the kernel by the BIOS. Given that the
> associated PCI device is hidden, the Linux kernel does not act upon
> the associated DMAR RMRR.

That sounds aweful. We should add to the VT-d driver that it sets up
RMRR mappings for request-ids which are not present as a PCI device, to
fix the Laptops which have it.

For the others, is the region the TPM talks to via DMA known so that we
can add a quirk?


	Joerg

      reply	other threads:[~2020-05-12 21:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 14:46 Failure to shutdown/reboot with intel_iommu=on Uwe Kleine-König
2020-05-08 15:07 ` Joerg Roedel
2020-05-09  1:58   ` Lu Baolu
2020-05-11 19:59     ` Uwe Kleine-König
2020-05-11 20:16       ` Uwe Kleine-König
2020-05-11 13:43   ` Lenny Szubowicz
2020-05-11 19:58     ` Uwe Kleine-König
2020-05-12 13:34     ` Joerg Roedel
2020-05-12 20:00       ` Lenny Szubowicz
2020-05-12 21:13         ` Joerg Roedel [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200512211317.GG8135@suse.de \
    --to=jroedel@suse.de \
    --cc=baolu.lu@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lszubowi@redhat.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=tglx@linutronix.de \
    --cc=uwe@kleine-koenig.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox