|[hatari-devel] Feature request/idea: cycle counting|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Feature request/idea: cycle counting
- From: Miro Kropáček <miro.kropacek@xxxxxxxxx>
- Date: Tue, 30 Jan 2018 13:03:02 +1100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=U5rfDshU3Em40RdcqUuXqrj69Ge1N/U6cY7rqKIw5tI=; b=FINlpSj1MdoqnJ4/N9DIOkABPVlmHzTUfBaphk1Pmk62IRp1siaMlx36DL0db6KHtp r4eAZ6D5agCFKBdQOdCzUHKF0wOOx50f6zurkUjEXhX8gQeeAQfYQmrchhRhxyMRmq+p Uv6yEAiNG+9xAV/YwAcbMIEiawzxecxrE1MXuqMbL5bMdz9CsjzrlxlAphISnFQcMzBs hewampxZotHFR8PdpL6UzJM4h25alcHfbW+pHJjysDFJg3283nnGsAqtnFoDH/Nws65j 015ivcKuHNWH6AgIlMdXvmWxwfJKLXh0kNxCJQ5lfSrfaTiCmSxV/tqIvBbigP2Mgu2e XJ1g==
I've been having this idea to create my own cycle counter and just yesterday I've realised that Hatari can do that for me with nearly zero effort. :)
The idea is that you have a m68k code in memory, disassemble it and you see not only each instruction's size but also cycles it eats. And since it would be in Hatari, you could immediately calculate whether it's a cache hit/miss, influence of the instruction head/tail, literally anything needed.
Since Hatari already tries to calculate Falcon's bus activity and CPU cycles, how hard this would be? Virtually just one more column with the cycles number and some indication about instr/data cache state.