From: Ingo Molnar <mingo@elte.hu>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: Ingo Molnar <mingo@redhat.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] AMD IOMMU updates for 2.6.28-rc5
Date: Tue, 18 Nov 2008 16:49:04 +0100 [thread overview]
Message-ID: <20081118154904.GI30358@elte.hu> (raw)
In-Reply-To: <20081118154322.GX13394@amd.com>
* Joerg Roedel <joerg.roedel@amd.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
next prev parent reply other threads:[~2008-11-18 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 15:43 [GIT PULL] AMD IOMMU updates for 2.6.28-rc5 Joerg Roedel
2008-11-18 15:49 ` Ingo Molnar [this message]
2008-11-19 6:05 ` FUJITA Tomonori
2008-11-19 9:25 ` Joerg Roedel
2008-11-19 9:36 ` Ingo Molnar
2008-11-20 4:25 ` FUJITA Tomonori
2008-11-20 11:31 ` Joerg Roedel
2008-11-19 12:57 ` Muli Ben-Yehuda
2008-11-20 4:25 ` FUJITA Tomonori
2008-11-20 7:51 ` Ingo Molnar
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=20081118154904.GI30358@elte.hu \
--to=mingo@elte.hu \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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