linux-kernel - Re: [PATCH 0 of 9] swiotlb: use phys_addr

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]

Message-ID: <4957083B.6090801@goop.org>
Date:	Sun, 28 Dec 2008 16:01:47 +1100
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
CC:	mingo@...e.hu, tony.luck@...el.com, linux-kernel@...r.kernel.org,
	xen-devel@...ts.xensource.com, x86@...nel.org,
	ian.campbell@...rix.com, beckyb@...nel.crashing.org
Subject: Re: [PATCH 0 of 9] swiotlb: use phys_addr_t for pages

FUJITA Tomonori wrote:
> Well, I asked Jeremy to use Becky's approach so I don't have though
> this patchset isn't enough for Becky (possibly for Xen too) since
> Jeremy didn't put Becky's map_single_page changes. These changes are
> necessary to support map_map_page with highmem. I think that we can do
> it simpler than his patch. I'll send patches to that in a different
> way soon.
>
> It's not principal objection, but as I said, the patches to revert
> Jeremy's highmem patches in this patchset like the following are
> pointless.
>   

I don't mind either way.  I was hoping to go with something that I've 
actually tested, but I don't see any reason why Becky's patches won't 
work in principle for Xen.  I'm on vacation at the moment, but I can 
test things out when I get back in a couple of weeks and apply whatever 
fixes are needed at whatever stage we're at then.

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