Software Tuning, Performance Optimization & Platform Monitoring
Discussion regarding monitoring and software tuning methodologies, Performance Monitoring Unit (PMU) of Intel microprocessors, and platform updating.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
1790 Discussions

Cannot read the structure of Hardware Feedback Interface and ThreadDirector in the memory

y4nx1ang
Beginner
‎08-29-2023 12:10 AM
936 Views

According to the Intel Manual Vol. 3A/B chatpter 15.6: the Hardware Feedback Interface and Intel® Thread Director both have a structure in memory to record some information changes of the CPU. However, I couldn’t find any information about the content of that memory region being '0'.

  1. The manual says that the memory region's address is in :

y4nx1ang_0-1693292817049.png

and the MAXPHYADDR can be found from 

y4nx1ang_1-1693292817033.png

 

     2. I have an i7-12700 CPU and the maxphyaddr is '46'. I obtained the physical address of the Hardware Feedback Interface and Thread Director structure and attempted to read it from a kernel module. However, the content of that memory region appears to be all '0'. I have ensured that both the HFI and Thread Director have been enabled.

 

Is there any method to deal with this? Thanks!

0 Kudos

Link Copied

0 Replies
Reply

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.