linux-kernel - Re: swiotlb: remove duplicated #include

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:	Sun, 4 Jan 2009 14:01:13 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
Cc:	jeremy@...p.org, beckyb@...nel.crashing.org, jj@...osbits.net,
	weiyi.huang@...il.com, linux-kernel@...r.kernel.org
Subject: Re: swiotlb: remove duplicated #include


* FUJITA Tomonori <fujita.tomonori@....ntt.co.jp> wrote:

> > In a few days, but wanted to hear back from either Jeremy or Becky 
> > first about how well they actually work in their usecases.
> 
> Well, you don't need to wait, I think.
> 
> All Jeremy and Becky need is adding highmem support to swiotlb. How we 
> support it doesn't matter. We can choose better one.
> 
> We all (including Jeremy) agreed that Becky's physical address scheme is 
> better (simpler) than Jeremy's struct page and offset scheme. Surely, 
> Becky's scheme works for Xen and him (Jeremy said that he tested it 
> lightly).

Jeremy said, when he submitted this series, shortly before Christmas:

 >> Here's a work in progress series [...]
 >>
 >> Quick testing showed no problems, but I haven't had the chance to do 
 >> anything extensive.

Jeremy, did you have a chance to do more testing with the current 
tip/master bits on Xen, so that we can push it to Linus?

> One remaining issue is how to support map_page/unmap_page. As we 
> discussed, we can add some workarounds for it but it's better to unify 
> dma_mapping_ops. I send patches to do it after testing them on an IA64 
> box tomorrow.

ok.

	Ingo
--
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/