From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Joe Millenbach <jmillenbach@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
team-fjord@googlegroups.com
Subject: Re: [PATCH] x86: Changing date reference in CONFIG_SWIOTLB help from a relative to fixed point
Date: Mon, 6 Aug 2012 10:52:16 -0400 [thread overview]
Message-ID: <20120806145216.GE2487@phenom.dumpdata.com> (raw)
In-Reply-To: <1344143521-30151-1-git-send-email-jmillenbach@gmail.com>
On Sat, Aug 04, 2012 at 10:12:01PM -0700, Joe Millenbach wrote:
> CONFIG_SWIOTLB's existing help information refers to "the current
> generation of Intel's x86-64 CPUs", but the statement is no longer
> true. After researching on Intel's ark site, I changed the statement
> to the also true "all Intel CPUs released before 2008".
>
> Signed-off-by: Joe Millenbach <jmillenbach@gmail.com>
> Reviewed-by: Josh Triplett <josh@joshtriplett.org>
> ---
> arch/x86/Kconfig | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 5bed94e..dadbfd6 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -755,10 +755,10 @@ config SWIOTLB
> def_bool y if X86_64
> ---help---
> Support for software bounce buffers used on x86-64 systems
> - which don't have a hardware IOMMU (e.g. the current generation
> - of Intel's x86-64 CPUs). Using this PCI devices which can only
> - access 32-bits of memory can be used on systems with more than
> - 3 GB of memory. If unsure, say Y.
> + which don't have a hardware IOMMU (e.g. all Intel CPUs released
> + before 2008). Using this PCI devices which can only access 32-bits
> + of memory can be used on systems with more than 3 GB of memory. If
> + unsure, say Y.
It actually should have that part about Intel CPUs removed - as the hardware
IOMMUs have nothing to do with the CPU. For example the SWIOTLB is used
on the AMD IOMMUs if the IOMMU does not cover certain devices.
So is the case with the IBM Calgary.
>
> config IOMMU_HELPER
> def_bool (CALGARY_IOMMU || GART_IOMMU || SWIOTLB || AMD_IOMMU)
> --
> 1.7.9.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2012-08-06 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 5:12 [PATCH] x86: Changing date reference in CONFIG_SWIOTLB help from a relative to fixed point Joe Millenbach
2012-08-06 14:52 ` Konrad Rzeszutek Wilk [this message]
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=20120806145216.GE2487@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=hpa@zytor.com \
--cc=jmillenbach@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=team-fjord@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox