From: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
To: David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: [GIT PULL] VT-d fixes and ACPI device mapping support for 3.15
Date: Mon, 24 Mar 2014 16:44:53 +0100 [thread overview]
Message-ID: <20140324154449.GA2775@8bytes.org> (raw)
In-Reply-To: <1395674279.4880.236.camel-W2I5cNIroUsVm/YvaOjsyQ@public.gmane.org>
On Mon, Mar 24, 2014 at 03:17:59PM +0000, David Woodhouse wrote:
> Jörg, please pull into your x86/vt-d branch from
>
> git://git.infradead.org/iommu-2.6
>
> This contains the two patch sets I've posted in the last week; first the
> set which fixes the use-after-free issues with IOTLB flushes, adds some
> missing IOTLB flushes and generally improves unmap performance. And then
> the support for DMA mapping of ACPI devices.
>
> This contains a couple of fixes triggered by Fengguang's build-test
> robots; one of which was posted as [PATCH 34/33] a few hours ago, and
> the other of which just moves the 'segment' member of struct intel_iommu
> outside the #ifdef CONFIG_INTEL_IOMMU since it's accessed from dmar.c
> without that config option set. I've merged both of those fixes back
> into the original offending patch, rather than putting them on top.
>
> drivers/iommu/dmar.c | 166 ++++++++---
> drivers/iommu/intel-iommu.c | 979 ++++++++++++++++++++++++++++++++++++++++-------------------------
> include/acpi/actbl2.h | 15 +-
> include/linux/dmar.h | 18 +-
> include/linux/intel-iommu.h | 1 +
> 5 files changed, 759 insertions(+), 420 deletions(-)
Pulled, thanks David.
next prev parent reply other threads:[~2014-03-24 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 15:17 [GIT PULL] VT-d fixes and ACPI device mapping support for 3.15 David Woodhouse
[not found] ` <1395674279.4880.236.camel-W2I5cNIroUsVm/YvaOjsyQ@public.gmane.org>
2014-03-24 15:44 ` Joerg Roedel [this message]
2014-04-01 14:35 ` David Woodhouse
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=20140324154449.GA2775@8bytes.org \
--to=joro-zlv9swrftaidnm+yrofe0a@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.