64k aliasing conflict: virtual or physical addresses?

Analyzers

Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)

64k aliasing conflict: virtual or physical addresses?

560 Views

Hi there,

I'm facing some 64k aliasing conflicts using MS Windows on Pentium 4.

According to the Intel P-IV Optimization ref.manual, distance should not be modulus 64k of _virtual_ addresses.

What exactly does it mean in the contexto of Windows DDK: should I consider the 32-bits pointers, or the 64-bits physical addresses obtained with MmGetPhysicalAddress function?

I will really appreciate some help with this.

Thanks!

Daniel.

Link Copied

0 Replies

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.