Skip to content

katetsu/Flexus-Debugging

BranchesTags
 
 

Repository files navigation

Flexus Debugger

Flexus Debugger is a debugging tool which can help analyze Flexus. Flexus Debugger uses Python3 script to get important lines from the Flexus log file and to systemize them. It also uses Neo4j, a high-performance Graph Database, which supports all the features expected of a mature database including query language.

How to start Flexus Debugger

Every work of Flexus Debugger, such as starting Neo4j database server, parsing the log file, and inserting the parsed data into the Neo4j, can be run with a single Docker image.

Before you start, make sure you have 'debug.out' file under 'Flexus-Debugging/' directory.
(Please refer How to make debug.out if you need help)

You can build docker with following command.

$ sudo chown -R root:root data
$ sudo docker build -t test:0.1 .

Run the docker.

$ sudo docker run --publish=7474:7474 --publish=7687:7687 --volume=$HOME/docker_test/data:/data --volume=$HOME/docker_test/logs:/logs test:0.1

First, you can see the Neo4j server running in the background. If it runs successfully, you can find following message.

...
======== Neo4j 3.4.4 ========
Starting...
Bolt enabled on 0.0.0.0:7687.
Started.
Remote interface available at http://localhost:7474/

After a few seconds, log parsing script will run and terminate with following message.

...
IMPORT DONE in 5s 250ms.
Imported:
   166237 nodes
   387298 relationships
   1738752 properties
Peak memory usage: 1.03 GB

Then, Neo4j server will be terminated and restarted. After seeing Neo4j Started message, you can use Neo4j browser to analyze your log file.

(Neo4j Browser: http://localhost:7474/); Remote access is also supported.

How to use Flexus Debugger

Flexus Debugger makes it much easier to analyze the log file of Flexus.

Here is part of the sample debug.out.


108  {1606}- 01-nic   Packet contains: MemoryMessage[Fetch Reply]: Addr:0xp:007c4b000 Size:64 Serial: 345 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
111  {1606}- Network Received msg From 1 to 0, on vc 0, serial: 252 Message =  MemoryMessage[Fetch Reply]: Addr:0xp:007c4b000 Size:64 Serial: 345 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
122  {1606}- sys-L1d  sendFront (D-1, I-0) : instr=>> #1076[00] @PC= v:0010647b8 opc=| e403c01d | Disas=lduw [%o7 + %i5], %l2                 {executed} << MemoryMessage[Load Reply]: Addr:0xp:00fd6ff74 Size:4 Serial: 454 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
125  {1606}- sys-L1d  sendFront (D-1, I-0) : instr=>> #1086[00] @PC= v:0010646cc opc=| d25e20a0 | Disas=ldx [%i0 + 160], %o1                  {executed} << MemoryMessage[Load Reply]: Addr:0xp:00800c0a0 Size:8 Serial: 455 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
127  {1606}- sys-L1d Sent on Port FrontSideOut_D [0]: instr=>> #1076[00] @PC= v:0010647b8 opc=| e403c01d | Disas=lduw [%o7 + %i5], %l2               {executed} << MemoryMessage[Load Reply]: Addr:0xp:00fd6ff74 Size:4 Serial: 454 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
131  {1606}- sys-L1d Sent on Port FrontSideOut_D [0]: instr=>> #1086[00] @PC= v:0010646cc opc=| d25e20a0 | Disas=ldx [%i0 + 160], %o1                {executed} << MemoryMessage[Load Reply]: Addr:0xp:00800c0a0 Size:8 Serial: 455 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
143  {1607}- sys-L1d Received on Port FrontSideIn(Request) [0]: instr=>> #1092[00] @PC= v:0010646e8 opc=| d85260fa | Disas=ldsh [%o1 + 250], %o4             {executed} << MemoryMessage[Load Request]: Addr:0xp:00800c0fa Size:2 Serial: 459 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
146  {1607}- sys-L1d Received on Port FrontSideIn(Request) [0]: instr=>> #1095[00] @PC= v:0010646f4 opc=| f85a60e0 | Disas=ldx [%o1 + 224], %i4              {executed} << MemoryMessage[Load Request]: Addr:0xp:00800c0e0 Size:8 Serial: 460 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
149  {1607}- sys-L1d  scheduling request to bank 0: instr=>> #1092[00] @PC= v:0010646e8 opc=| d85260fa | Disas=ldsh [%o1 + 250], %o4          {executed} << MemoryMessage[Load Request]: Addr:0xp:00800c0fa Size:2 Serial: 459 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack eL1
150  {1607}- sys-L1d  scheduling request to bank 0: instr=>> #1095[00] @PC= v:0010646f4 opc=| f85a60e0 | Disas=ldx [%o1 + 224], %i4           {executed} << MemoryMessage[Load Request]: Addr:0xp:00800c0e0 Size:8 Serial: 460 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack eL1

You can get some information from each line of the file:

LineNumber  {Cycle}- [MemoryMessage]: instr=>> #InstructionNumber[CPUID] @PC= opc=| opcode | Disas= Disassembly {Semantic} Addr: Size: Serial: Core: DStream: Outstanding Msgs:

The debugger parses every line of the log file and categorizes them using Neo4j, so that you can trace and analyze the result more easily.

First of all, each line in the log file becomes the smallest grey node. Then, they are categorized based on the Serial, Address, and Instruction.

After categorize them, each serial node generates Trace that shows visual graph trace for each serial.

Serial_sample

Above figure shows the example for following information.


658  {1631}- sys-L1d Received on Port FrontSideIn(Request) [0]: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7              {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
661  {1631}- sys-L1d  scheduling request to bank 0: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7           {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack eL1
662  {1631}- sys-L1d  schedule Request instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                 {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
663  {1631}- sys-L1d  runRequestProcess 180: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                  {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
665  {1631}- sys-L1d  Handle Request: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                  {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
666  {1631}- sys-L1d  Examine Request instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                  {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
668  {1631}- sys-L1d  Do Request: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                {executed} << MemoryMessage[Load Request]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
670  {1631}- sys-L1d  Hit: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7             {executed} << MemoryMessage[Load Reply]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
671  {1631}- sys-L1d   Action for instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7             {executed} << MemoryMessage[Load Reply]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack is: kReplyAndRemoveMAF
719  {1634}- sys-L1d  sendFront (D-1, I-0) : instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                  {executed} << MemoryMessage[Load Reply]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
721  {1634}- sys-L1d Sent on Port FrontSideOut_D [0]: instr=>> #1162[00] @PC= v:0010630fc opc=| ee5e22c0 | Disas=ldx [%i0 + 704], %l7                {executed} << MemoryMessage[Load Reply]: Addr:0xp:0080352c0 Size:8 Serial: 483 Core: 0 DStream: true Outstanding Msgs: 0 Requires Ack
  • Line: the smallest grey circles
  • Serial: the red circle
  • Address: the green circle
  • Instrunction: the purple circle

Each line nodes are categorized based on serial, address, and instruction.

  • Trace: the yellow graph; You can see the trace of lines visually. Each arrows have sequence # (cycle diff), and each nodes have component name within the circle.

  • Pattern: the blue circle; Some serials with same trace, which means exactly same number of processes with identical component name, can be categorized as same pattern.

Style

You can import Flexus-Debugging/setting/style.grass file into your browser by drag&drop to make your graph have better looking.

Node and Relationships

When you open the Neo4j browser, you can see every Node Labels and Relationships. You can list them clicking the name of nodes/relationships.

Expand Relationships

You can expand a node by double-clicking it. You can see every nodes and relationships of the node, and follow them to debug more easily.

Browser Settings

It shows maximum 25 nodes/relationships by default. You can change this maximum value at Browser Settings in the bottom left corner. Or you can use Cypher query langauges instead.

Cypher query language

Cypher is SQL-inspired language for describing patterns in graphs visually using an ASCII-art syntax. There are some sample scripts in Flexus-Debugging/setting/Scripts.cypher file.

  • MATCH(n:Serial) RETURN count(n)

    : This script returns the number of Serials in the log file.

  • MATCH(a)-[*]->(n:Serial)-[*]->(b)<-[*]-(c) WHERE n.serial="483" RETURN n, a, b, c

    serial_sample

    : This script shows whole information related to 'serial #483'. You can see the address, instruction, pattern and traces of the serial.

  • MATCH(p:Pattern_Serial)-[*]->(n)<-[*0..1]-(m) WHERE p.patternId="P:S:5" RETURN p, n, m

    pattern_sample

    : This script shows every serial matched to the given pattern, and their information.

  • MATCH(n:Addr)-[*]->(m)<-[*]-(k) WHERE n.addr="0xp:0080352c0" RETURN n, m, k

    addr_sample

    : This script shows pattern, serials, and instructions related to 'address 0xp:0080352c0".

Cypher query language is easy and powerful, so you can do much more things with it.

Neo4j Cypher Refcard 3.4: here

Intro to Cypher: here

How to make debug.out

Before run Flexus, you need to apply the patch for more verbosity of the simulator. You can find the patch file named link.patch/ under Flexus-Debugging/ directory.

Compiling

Trace

$ make -j CMP.L2Shared.Trace

Timing

$ make -j CMP.L2SharedNUCA.OoO

Running

Trace

$ run_job -clobber -cfg cortex-a15-1core-1024kl2 -local -run trace -job trace-a15-1core-1024kl2 CMP.L2Shared.Trace nutch/1cpu

Flexpoint

$ run_job -clobber -cfg cortex-a15-1core-1024kl2 -local -run flexpoint -dkpt-gen -postprocess "/home/parsacom/tools/flexus/postprocess_ckptgen.sh flexpoint 20 cortex-a15-1core-1024kl2" -job flexpoint-a15-1core-1024kl2 CMP.L2Shared.Trace nutch/1cpu

Timing

$ run_job -clobber -ma -cfg cortex-a15-1core-1024kl2 -local -run timing -job timing-a15-1core-1024kl2-$1 -state cortex-a15-1core-1024kl2 -postprocess "/home/parsacom/tools/flexus/postprocess.sh" CMP.LwSharedNUCA.OoO nutch/1cpu

After these steps, copy the simulator to the .skel folder, and run go.sh again. Press Ctrl-c to stop simulation, enable more verbosity by flexus.debug-set-severity-level vverb, and hit 'r'.

Then you can find your debug.out with more information. Move the file under the Flexus-Debugging/ directory.

About

No description, website, or topics provided.

Resources

Readme
Activity

Stars

0 stars

Watchers

1 watching

Forks

0 forks
Report repository

Releases

No releases published

Packages

No packages published

Languages

  • Jupyter Notebook 80.1%
  • Python 10.7%
  • Shell 8.1%
  • Dockerfile 1.1%