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:	Fri, 9 Jan 2009 11:36:02 -0600
From:	Becky Bruce <beckyb@...nel.crashing.org>
To:	Ian Campbell <Ian.Campbell@...rix.com>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>, Ingo Molnar <mingo@...e.hu>,
	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
	jj@...osbits.net, weiyi.huang@...il.com,
	linux-kernel@...r.kernel.org
Subject: Re: swiotlb: remove duplicated #include


On Jan 9, 2009, at 10:37 AM, Ian Campbell wrote:

> On Mon, 2009-01-05 at 09:48 +1100, Jeremy Fitzhardinge 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.
>
> Only just got out from under my pile of vacation backlog...
>
> They don't quite work with Xen (at least the version in Jeremy's patch
> queue doesn't) but I agree that it should be possible to make it work
> and that there's no point in holding back just for Xen.

I'm also back (temporarily), and they're not quite going to work for  
powerpc, either, but it shouldn't be anything major to fix, and since  
it didn't work on powerpc before, that shouldn't hold anything up.   
I'm working on getting things working for me again now.   
Unfortunately, it now looks like I'm going to have to be out of the  
office next week, but I expect to get something out as soon as I'm  
back, if I don't get a chance to fix it today.

Jeremy, many thanks for your work merging my patches in with your  
series!

Cheers,
Becky

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