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


* Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Ingo Molnar wrote:
>> * 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?
>>   
>
> I'm going to be on vacation until the 12th, so I won't have a chance to 
> do anything until then (perhaps Ian will have a chance to poke at them 
> before then).  I'm expecting Becky's patches to work as-is, or if not, 
> be easily fixed with a couple of small bugfix patches.  So I say go 
> ahead if they work for everyone else.

ok, i have put it into the to-Linus pile.

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ