Commit 99ec28f1 authored May 09, 2010 by FUJITA Tomonori Committed by Benjamin Herrenschmidt May 21, 2010

powerpc: Remove unused 'protect4gb' boot parameter



'protect4gb' boot parameter was introduced to avoid allocating dma
space acrossing 4GB boundary in 2007 (the commit
56997559).

In 2008, the IOMMU was fixed to use the boundary_mask parameter per
device properly. So 'protect4gb' workaround was removed (the
383af952). But somehow I messed the
'protect4gb' boot parameter that was used to enable the
workaround.

Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

parent 40a5a443

arch/powerpc/kernel/iommu.c

+0 −12

Original line number	Diff line number	Diff line
		@@ -43,20 +43,9 @@
		#define DBG(...)

		static int novmerge;
		static int protect4gb = 1;

		static void __iommu_free(struct iommu_table *, dma_addr_t, unsigned int);

		static int __init setup_protect4gb(char *str)
		{
		if (strcmp(str, "on") == 0)
		protect4gb = 1;
		else if (strcmp(str, "off") == 0)
		protect4gb = 0;

		return 1;
		}

		static int __init setup_iommu(char *str)
		{
		if (!strcmp(str, "novmerge"))
		@@ -66,7 +55,6 @@ static int __init setup_iommu(char *str)
		return 1;
		}

		__setup("protect4gb=", setup_protect4gb);
		__setup("iommu=", setup_iommu);

		static unsigned long iommu_range_alloc(struct device *dev,

Admin message