linux-kernel - Re: swiotlb detection should be memory hotplug aware ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Jul 2010 08:44:42 +0900
From:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To:	akataria@...are.com
Cc:	fujita.tomonori@....ntt.co.jp, konrad.wilk@...cle.com,
	ak@...ux.intel.com, lenb@...nel.org, x86@...nel.org,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
	petr@...are.com
Subject: Re: swiotlb detection should be memory hotplug aware ?

On Wed, 21 Jul 2010 10:13:34 -0700
Alok Kataria <akataria@...are.com> wrote:

> > Basically, you want to add hot-plug memory and enable swiotlb, right?
> 
> Not really, I am planning to do something like this, 
> 
> @@ -52,7 +52,7 @@ int __init pci_swiotlb_detect(void)
>  
>  	/* don't initialize swiotlb if iommu=off (no_iommu=1) */
>  #ifdef CONFIG_X86_64
> -	if (!no_iommu && max_pfn > MAX_DMA32_PFN)
> +	if (!no_iommu && (max_pfn > MAX_DMA32_PFN || hotplug_possible()))
>  		swiotlb = 1;

Always enable swiotlb with memory hotplug enabled? Wasting 64MB on a
x86_64 system with 128MB doesn't look to be a good idea. I don't think
that there is an easy solution for this issue though.
--
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/