From: Pavel Machek <pavel@suse.cz>
To: Constantin Baranov <const@mimas.ru>
Cc: Ingo Molnar <mingo@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.28-rc3] x86: make CONFIG_SWIOTLB configurable
Date: Wed, 5 Nov 2008 11:21:26 +0100 [thread overview]
Message-ID: <20081105102126.GC1424@ucw.cz> (raw)
In-Reply-To: <49107844.8070509@mimas.ru>
On Tue 2008-11-04 20:28:52, Constantin Baranov wrote:
> Make it possible to enable individually the CONFIG_SWIOTLB option.
> This is useful for Intel x86_64 systems without DMAR support.
>
> Signed-off-by: Constantin Baranov <const@mimas.ru>
> ---
> Tested on my system based on Gigabyte GA-EP45-DS3 mainboard
> (P45 chipset) with 8 GiB of RAM.
> Currently I need to enable either CONFIG_GART_IOMMU or
> CONFIG_AMD_IOMMU for proper work. Both are AMD specific.
> When the patch applied, just CONFIG_SWIOTLB is sufficient.
>
> arch/x86/Kconfig | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> --- linux-2.6.28-rc3/arch/x86/Kconfig 2008-11-04 17:32:29.846408880 +0400
> +++ linux-2.6.28-rc3-swiotlb/arch/x86/Kconfig 2008-11-04 18:11:47.796408084 +0400
> @@ -566,7 +566,9 @@ config AMD_IOMMU
>
> # need this always selected by IOMMU for the VIA workaround
> config SWIOTLB
> - bool
> + bool "Support for software bounce buffers"
> + depends on X86_64 && EXPERIMENTAL
> + default n
> help
> Support for software bounce buffers used on x86-64 systems
> which don't have a hardware IOMMU (e.g. the current generation
Why experimental?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-11-05 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-04 16:28 [PATCH 2.6.28-rc3] x86: make CONFIG_SWIOTLB configurable Constantin Baranov
2008-11-05 10:21 ` Pavel Machek [this message]
2008-11-05 15:59 ` Constantin Baranov
2008-11-06 0:53 ` FUJITA Tomonori
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=20081105102126.GC1424@ucw.cz \
--to=pavel@suse.cz \
--cc=const@mimas.ru \
--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 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.