[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081118154904.GI30358@elte.hu>
Date: Tue, 18 Nov 2008 16:49:04 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Joerg Roedel <joerg.roedel@....com>
Cc: Ingo Molnar <mingo@...hat.com>, iommu@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] AMD IOMMU updates for 2.6.28-rc5
* Joerg Roedel <joerg.roedel@....com> wrote:
> (sorry for resend, forgot to add the mailing lists)
>
> Hi Ingo,
>
>
> The following changes since commit 4e14e833ac3b97a4aa8803eea49f899adc5bb5f4:
> Linus Torvalds (1):
> Merge git://git.kernel.org/.../sfrench/cifs-2.6
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/joro/linux-2.6-iommu.git iommu-fixes-2.6.28
>
> Joerg Roedel (4):
> AMD IOMMU: add parameter to disable device isolation
> AMD IOMMU: enable device isolation per default
> AMD IOMMU: fix fullflush comparison length
> AMD IOMMU: check for next_bit also in unmapped area
>
> Documentation/kernel-parameters.txt | 4 +++-
> arch/x86/kernel/amd_iommu.c | 2 +-
> arch/x86/kernel/amd_iommu_init.c | 6 ++++--
> 3 files changed, 8 insertions(+), 4 deletions(-)
>
> As the most important change these patches enable device isolation
> per default. Tests have shown that there are drivers which have bugs
> and do double-freeing of DMA memory. This can lead to data
> corruption with a hardware IOMMU when multiple devices share the
> same protection domain. Therefore device isolation should be enabled
> by default. The full diff of these changes is appended. Please pull.
pulled into tip/x86/urgent, thanks Joerg!
Ingo
--
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