From: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
jroedel-l3A5Bk7waGM@public.gmane.org,
David Woodhouse <dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
Jiang Liu <jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 0/2] iommu/vt-d: Keep RMRR mappings around on driver unbind
Date: Wed, 1 Oct 2014 15:35:10 -0700 [thread overview]
Message-ID: <20141001223510.GB12989@kroah.com> (raw)
In-Reply-To: <1412074923-6342-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
On Tue, Sep 30, 2014 at 01:02:01PM +0200, Joerg Roedel wrote:
> Hi,
>
> here is a patch-set to fix an issue recently discovered when
> the Intel IOMMU is in use with devices that need RMRR
> mappings.
>
> The problem is that the RMRR mappings are destroyed when the
> device driver is unbound from the device, causing DMAR
> faults.
>
> To solve this problem a device driver core change is
> necessary to catch the right point in time for the IOMMU
> code to destroy any mappings for a device.
>
> With this patch-set the RMRR mappings are only destroyed
> when the device is actually removed from the system.
>
> Please review.
I have no objection to these, do you want me to take them through my
tree? Or if they are going through some other one feel free to add:
Acked-by: Greg Kroah-Hartman <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
To the first patch.
thanks,
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joerg Roedel <joro@8bytes.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Jiang Liu <jiang.liu@linux.intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
jroedel@suse.de
Subject: Re: [PATCH 0/2] iommu/vt-d: Keep RMRR mappings around on driver unbind
Date: Wed, 1 Oct 2014 15:35:10 -0700 [thread overview]
Message-ID: <20141001223510.GB12989@kroah.com> (raw)
In-Reply-To: <1412074923-6342-1-git-send-email-joro@8bytes.org>
On Tue, Sep 30, 2014 at 01:02:01PM +0200, Joerg Roedel wrote:
> Hi,
>
> here is a patch-set to fix an issue recently discovered when
> the Intel IOMMU is in use with devices that need RMRR
> mappings.
>
> The problem is that the RMRR mappings are destroyed when the
> device driver is unbound from the device, causing DMAR
> faults.
>
> To solve this problem a device driver core change is
> necessary to catch the right point in time for the IOMMU
> code to destroy any mappings for a device.
>
> With this patch-set the RMRR mappings are only destroyed
> when the device is actually removed from the system.
>
> Please review.
I have no objection to these, do you want me to take them through my
tree? Or if they are going through some other one feel free to add:
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To the first patch.
thanks,
greg k-h
next prev parent reply other threads:[~2014-10-01 22:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 11:02 [PATCH 0/2] iommu/vt-d: Keep RMRR mappings around on driver unbind Joerg Roedel
2014-09-30 11:02 ` Joerg Roedel
[not found] ` <1412074923-6342-1-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-09-30 11:02 ` [PATCH 1/2] driver core: Add BUS_NOTIFY_REMOVED_DEVICE event Joerg Roedel
2014-09-30 11:02 ` Joerg Roedel
2014-09-30 11:02 ` [PATCH 2/2] iommu/vt-d: Only remove domain when device is removed Joerg Roedel
2014-09-30 11:02 ` Joerg Roedel
[not found] ` <1412074923-6342-3-git-send-email-joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-11-04 16:12 ` Alex Williamson
2014-11-04 16:12 ` Alex Williamson
[not found] ` <1415117537.27420.428.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2014-11-06 12:54 ` Joerg Roedel
2014-11-06 12:54 ` Joerg Roedel
[not found] ` <20141106125405.GI8354-l3A5Bk7waGM@public.gmane.org>
2014-11-06 16:16 ` Alex Williamson
2014-11-06 16:16 ` Alex Williamson
[not found] ` <1415290565.16601.92.camel-85EaTFmN5p//9pzu0YdTqQ@public.gmane.org>
2014-11-06 16:43 ` Alex Williamson
2014-11-06 16:43 ` Alex Williamson
2014-12-09 12:15 ` Joerg Roedel
2014-12-09 12:15 ` Joerg Roedel
[not found] ` <20141209121525.GM3762-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-12-11 16:35 ` Jerry Hoemann
2014-12-11 16:35 ` Jerry Hoemann
[not found] ` <20141211163534.GA4765-dMAi7lA+vBPDUbYHzcRnttBPR1lH4CV8@public.gmane.org>
2014-12-12 15:56 ` Joerg Roedel
2014-12-12 15:56 ` Joerg Roedel
2014-10-01 22:35 ` Greg Kroah-Hartman [this message]
2014-10-01 22:35 ` [PATCH 0/2] iommu/vt-d: Keep RMRR mappings around on driver unbind Greg Kroah-Hartman
[not found] ` <20141001223510.GB12989-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2014-10-02 9:20 ` Joerg Roedel
2014-10-02 9:20 ` Joerg Roedel
2014-10-02 0:30 ` Jerry Hoemann
2014-10-02 0:30 ` Jerry Hoemann
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=20141001223510.GB12989@kroah.com \
--to=gregkh-hqyy1w1ycw8ekmwlsbkhg0b+6bgklq7r@public.gmane.org \
--cc=dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jiang.liu-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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.