linux-kernel - Re: [PATCH] iSCSI/iBFT: use proper address translation

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: <4AC5234C.5030409@citrix.com>
Date:	Thu, 01 Oct 2009 14:46:52 -0700
From:	Jeremy Fitzhardinge <Jeremy.Fitzhardinge@...rix.com>
To:	Jan Beulich <JBeulich@...ell.com>
CC:	"ketuzsezr@...nok.org" <ketuzsezr@...nok.org>,
	"pjones@...hat.com" <pjones@...hat.com>,
	Martin Wilck <Martin.Wilck@...itsu-siemens.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] iSCSI/iBFT: use proper address translation

On 10/01/09 01:01, Jan Beulich wrote:
> In virtual environments (namely, Xen Dom0) virt <-> phys and
> virt <-> isa-bus translations cannot be freely interchanged. When
> looking at memory below 1M, the latter translations should always
> be used.
>   

Do you have a different definition for isa_virt_to_bus in your kernel? 
As far as I can see it is defined to be the same as virt_to_phys.  Also,
the ISA memory is identity mapped into the domain's physical mapping
space, so it should be directly accessible without any problems.

    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/