public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: iommu@lists.linux-foundation.org
Cc: David Woodhouse <dwmw2@infradead.org>,
	zhen-hual@hp.com, bhe@redhat.com, linux-kernel@vger.kernel.org,
	Joerg Roedel <joro@8bytes.org>
Subject: [PATCH 0/4] More cleanups and fixes for Intel VT-d
Date: Thu, 11 Jun 2015 15:47:39 +0200	[thread overview]
Message-ID: <1434030463-942-1-git-send-email-joro@8bytes.org> (raw)

Hi,

here are a number of additional fixes for the Intel VT-d
driver and its behavior in a kdump kernel. The most
important fix is the iommu=pt case, which is broken without
these patches.

Regards,

	Joerg

Joerg Roedel (4):
  iommu/vt-d: Remove iommu_attach_domain_with_id()
  iommu/vt-d: Don't consider copied context entries as present
  iommu/vt-d: Remove unmap_device_dma()
  iommu/vt-d: Make sure si_domain is allocated for kdump kernel

 drivers/iommu/intel-iommu.c | 104 ++++++++++++++++----------------------------
 1 file changed, 38 insertions(+), 66 deletions(-)

-- 
1.9.1


             reply	other threads:[~2015-06-11 13:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 13:47 Joerg Roedel [this message]
2015-06-11 13:47 ` [PATCH 1/4] iommu/vt-d: Remove iommu_attach_domain_with_id() Joerg Roedel
2015-06-11 13:47 ` [PATCH 2/4] iommu/vt-d: Don't consider copied context entries as present Joerg Roedel
2015-06-11 14:07   ` David Woodhouse
2015-06-11 14:12     ` Joerg Roedel
2015-06-11 14:19       ` David Woodhouse
2015-06-11 14:25     ` Joerg Roedel
2015-06-11 14:44       ` David Woodhouse
2015-06-11 15:12         ` David Woodhouse
2015-06-11 14:51       ` Joerg Roedel
2015-06-11 13:47 ` [PATCH 3/4] iommu/vt-d: Remove unmap_device_dma() Joerg Roedel
2015-06-11 13:47 ` [PATCH 4/4] iommu/vt-d: Make sure si_domain is allocated for kdump kernel Joerg Roedel
2015-06-11 15:54 ` [PATCH 0/4] More cleanups and fixes for Intel VT-d David Woodhouse
2015-06-12  7:31   ` Joerg Roedel
2015-06-12 20:29   ` Joerg Roedel

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=1434030463-942-1-git-send-email-joro@8bytes.org \
    --to=joro@8bytes.org \
    --cc=bhe@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhen-hual@hp.com \
    /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