--- trunk/TODO 2007/10/08 16:20:26 28 +++ trunk/TODO 2007/10/08 16:21:17 34 @@ -1,65 +1,88 @@ -$Id: TODO,v 1.324 2006/07/22 10:23:39 debug Exp $ +$Id: TODO,v 1.453 2007/02/19 01:34:42 debug Exp $ -Hm. This file is in random order, and not all parts of it are up-to-date. +------------------------------------------------------------------------------- -Code cleanup: - x) 64-bit ranges in src/cpus/memory_mips_v2p.c - x) Revert the dyntrans page template experiment? Hm. - x) Refactor the cpu type detection/initialization/listing. +Fix after the 0.4.4 release: + Fix the PowerPC DECR interrupt speed! -Documentation: - x) Rewrite the section about experimental devices, after the - framebuffer acceleration has been implemented, and demos - written. (Symbolic names instead of numbers; example - use cases, etc. Mention demo files that use the various - features?) - x) "a very simple linear framebuffer device (for graphics output)" - under "which machines does gxemul emulate" ==> better - description? - x) Better description on how to set up a cross compiler? - Example for MIPS64. +------------------------------------------------------------------------------- + +Possible (relatively large) work packages to concentrate on in the future: + + x) SMP: + Get SMP working again. It is pretty much broken since I started + the conversion from the old bintrans system to the new dyntrans system. + Add better Test machine demos for SMP in the demos directory. + + x) Network: + Redesign of the networking subsystem, at least the NAT translation + part. The current way of allowing raw ethernet frames to be + transfered to/from the emulator via UDP should probably be extended + to allow the frames to be transmitted other ways as well. + Also adding support for connecting ttys (either to xterms, or to + pipes/sockets etc, or even to PPP->NAT or SLIP->NAT :-). + + x) PCI: + Pretty much everything related to runtime configuration, device + slots, interrupts, whatever. The current code is very hardcoded + and ugly. + + x) Debugging: + Think more about SMP debugging, etc. Right now, the + debugger is a mess. Also, a better connection to GDB would be + very nice to have. -Long-term implementation: - x) Testmachine includes: - + dev_fb block fill and copy - + dev_fb draw characters (from the built-in font)? - + dev_fb input device? mouse pointer coordinates and buttons - (allow changes in these to cause interrupts as well?) - + Redefine the halt() function so that it stops "sometimes - soon", i.e. usage in demo code should be: - for (;;) { - halt(); - } - x) Rewrite the networking stack; make OpenBSD work better as a guest - OS, fix the performance problems, make Linux work with DHCP, etc. - x) Make the wdc controller work with modern versions of NetBSD! - x) Continue on SPARC emulation - + Enable it in the configure script as soon as it can - run all the demo programs. - x) Continue on Alpha emulation (virtual memory, etc). Cleanup. - x) Alignment exceptions (MIPS, PPC, ARM?, ...) + x) Userland emulation: + Primary goals would be NetBSD and Linux syscall emulation. -Long-term design: +And of course, there are _LOTS_ of minor TODOs spread out throughout +the source code, which must be fixed sooner or later. + +------------------------------------------------------------------------------- + +Some other things, in random order, that I'd like to fix: (Some items in +this list are probably out-to-date by now.) + +Dyntrans: x) Instruction combination collisions? How to avoid easily... - o) Actually use the settings object, better debugger stuff, etc! - o) Debugger command for enabling/disabling instruction statistics - during runtime. machine.statistics = on|off - x) MAINBUS REDESIGN! - x) Clock framework! Go through all clock devices, make sure they - return correct data, and run at correct speeds! + x) Think about how to do both SHmedia and SHcompact in a reasonable + way! (Or AMD64 long/protected/real, for that matter.) + x) 68K emulation; think about how to do variable instruction + lengths across page boundaries. x) Dyntrans with valgrind-inspired memory checker. (In memory_rw, it would be reasonably simple to add; in each individual fast load/store routine = a lot more work, and it would become kludgy very fast.) x) Dyntrans with SMP... lots of work to be done here. x) Dyntrans with cache emulation... lots of work here as well. - x) Reimplement the config file parser from scratch. - -Test: - x) Test with more than one Sprite instance on an emulated network! - x) NetBSD 4.x, once it is out. - -------------------------------------------------------------------------------- + o) dev_mp doesn't work well with dyntrans yet + o) In general, IPIs, CAS, LL/SC etc must be made to work with dyntrans + x) Redesign/rethink the delay slot mechanism used for e.g. MIPS, + so that it caches a translation (that is, an instruction + word and the instr_call it was translated to the last + time), so that it doesn't need to do slow + to_be_translated for each end of page? + x) Program Counter statistics: + Per machine? What about SMP? All data to the same file? + A debugger command should be possible to use to enable/ + disable statistics gathering. + Configuration file option! + x) Breakpoints: + o) Physical vs virtual addresses! + o) 32-bit vs 64-bit sign extension for MIPS, and others? + x) INVALIDATION should cause translations in _all_ cpus to be + invalidated, e.g. on a write to a write-protected page + (containing code) + x) 16-bit encodings? (MIPS16, ARM Thumb, 32-bit SH on SH64) + x) Lots of other stuff: see src/cpus/README_DYNTRANS + x) true recompilation backend? think carefully about this. + o) abstract syntax for emitting opcopdes + o) convert into native code only after an entire + block has been translated? probably best. + o) x86/amd64 code generator can be very similar... perhaps + o) branches to already translated code blocks can + link the blocks together + o) load/store are the most important. Simple Valgrind-like checks? o) Mark every address with bits which tell whether or not the address @@ -81,80 +104,133 @@ in warnings. (free() must be modified to free the actually allocated address.) -SMP: - o) dev_mp doesn't work well with dyntrans yet - o) In general, IPIs, CAS, LL/SC etc must be made to work with dyntrans - MIPS: - +) Some more work on opcodes. + o) Nicer MIPS status bits in register dumps. + o) Alignment exceptions. + o) Floating point exception correctness. + o) Fix this? Triggered by NetBSD/sgimips? Hm: + to_be_translated(): TODO: unimplemented instruction: + 000000000065102c: 00200800 (d) rot_00 at,zr,0 + o) Some more work on opcodes. x) MIPS64 revision 2. o) Find out which actual CPUs implement the rev2 ISA! + o) DROTR32 and similar MIPS64 rev 2 instructions, + which have a rotation bit which differs from + previous ISAs. + o) EI and DI instructions for MIPS64/32 rev 2. + NOTE: These are _NOT_ the same as for R5900! x) _MAYBE_ TX79 and R5900 actually differ in their opcodes? Check this carefully! o) Dyntrans: Count register updates are probably not 100% correct yet. o) Refactor code for performance and readability/maintainability. - o) Instruction combinations? Possible candidates (but profile first!): - o) R2000/R3000 cache cleaner! - o) strlen, memset loops etc - o) multiple loads/stores in a row, e.g. relative to - the stack pointer - o) lui + or, lui + add, and 64-bit variants - o) jr ra + addiu to the v0 register? - o) compare + branch - o) DROTR32 and similar MIPS64 rev 2 instructions, which have - a rotation bit which differs from previous ISAs. - o) EI and DI instructions for MIPS64/32 rev 2. NOTE: These are - _NOT_ the same as for R5900! o) (Re)implement 128-bit loads/stores for R5900. o) R4000 and others: x) watchhi/watchlo exceptions, and other exception handling details o) R10000 and others: (R12000, R14000 ?) + x) The code before the line + /* reg[COP0_PAGEMASK] = cpu->cd.mips.coproc[0]->tlbs[0].mask & PAGEMASK_MASK; */ + in cpu_mips.c is not correct for R10000 according to + Lemote's Godson patches for GXemul. TODO: Go through all + register definitions according to http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/hdwr/bks/SGI_Developer/books/R10K_UM/sgi_html/t5.Ver.2.0.book_263.html#HEADING334 + and make sure everything works with R10000. + Then test with OpenBSD/sgi? x) memory space, exceptions, ... x) use cop0 framemask for tlb lookups (http://techpubs.sgi.com/library/tpl/cgi-bin/getdoc.cgi/hdwr/bks/SGI_Developer/books/R10K_UM/sgi_html/t5.Ver.2.0.book_284.html) -Dyntrans: - x) Redesign/rethink the delay slot mechanism used for e.g. MIPS, - so that it caches a translation (that is, an instruction - word and the instr_call it was translated to the last - time), so that it doesn't need to do slow - to_be_translated for each end of page? - x) Program Counter statistics: - Per machine? What about SMP? All data to the same file? - A debugger command should be possible to use to enable/ - disable statistics gathering. - Configuration file option! - x) Common fatal_abort() function, which drops into the debugger - without continuing. - x) INVALIDATION should cause translations in _all_ cpus to be - invalidated, e.g. on a write to a write-protected page - (containing code) - x) Call/return hints? - x) 16-bit encodings? (MIPS16, ARM Thumb, SH3, ...) - x) H8? - x) Lots of other stuff: see src/cpus/README_DYNTRANS - x) true recompilation backend? think carefully about this, - experiment in a separate project (not in GXemul) - o) First test would be to just implement a simple - instruction such as MIPS' addiu or lui, on AMD64 - hosts... - x) Idle loop detection? (Depends on target.) Could be turned - into usleep(1) or similar on the host... except when doing - e.g. SMP emulation. Then it becomes trickier. +SuperH: + x) SH4 interrupt controller: + x) Implement correct priorities of interrupts + x) SH4 DMA (0xffa00000) + x) SH4 UBC (0xff200000) + x) Store queues can copy 32 bytes at a time, there's no need to + copy individual 32-bit words. (Performance improvement.) + x) SH4 BSC (Bus State Controller) + x) SH4 RTC: Read the host's clock. + x) SH4 SCIF: Serial _interrupts_ + x) Instruction tracing should include symbols for branch targets, + and so on, to make the output more human readable. + x) NetBSD/evbsh3, dreamcast, mmeye, hpcsh! Linux? + x) Replace pc-relative loads with immediate load, if within the + same page. (Similar to the same optimization for ARM.) + x) Floating point speed! + x) Floating point exception correctness. + x) Think carefully about how to implement SH5/SH64 (for evbsh5). + +Dreamcast: + x) G2 DMA + x) LAN adapter (dev_mb8696x.c). NetBSD root-on-nfs. + x) PVR: Lots of stuff. See dev_pvr.c. + x) GDROM + x) Modem + x) PCI bridge/bus? + x) Maple bus: + x) Correct controller input + x) Mouse input + x) Software emulation of BIOS calls: + x) GD-ROM emulation: Use the GDROM device. + x) Use the VGA font as a fake ROM font. (Better than + nothing.) + x) Linux/dreamcast? (The gentoo kernel currently crashes.) + x) Make as many as possible of the KOS examples run! + x) More homebrew demos/games. + x) SPU: Sound emulation (ARM cpu). + x) VME processor emulation? "(Sanyo LC8670 "Potato")" according to + Wikipedia, LC86K87 according to Comstedt's page. See + http://www.maushammer.com/vmu.html for a good description of + the differences between LC86104C and the one used in the VME. + +Transputer: + x) Implement support for Helios binaries. + x) Stack and register contents at startup? + x) Figure out how to boot an entire Helios distribution. + x) Implement all instructions. :) + +RCA1802/RCA1805, CHIP8: + x) CHIP8 -> RCA180x conversion + x) Think about how to do dual-mode, variable-instr-length + ISAs, and switch between modes. + x) 1805 "extended" opcode -> trigger CHIP8 emulation? + That is, all calls 0NNN could point to 0x68 opcodes, + which, if running on a 1802 in CHIP8-emulation-mode, + would be manually interpreted. + x) Better solution: + CHIP8 calls to 00xx => handle at high level, + calls to 0xxx in general = call 180X machine code + (0000 = reboot?) + x) 1802 info: http://www.nyx.net/~lturner/public_html/Cosmac.html + and: http://www.elf-emulation.com/1802.html + x) 1805 extended opcodes: Implement at least disassembly support! + x) Keyboard input. + x) Sound (beep only). + x) Slow-down to correct speed? Wikipedia: "it was usually operated + at 3.58 MHz/2 to suit the requirements of the 1861 chip which + gave a speed of a little over 100,000 instructions per second" + (Note that _CHIP8_ emulation would then be even slower.) + x) SCHIP48 (Super) emulation: + Some more opcodes, 128x64 framebuffer, larger + sprites and fonts. Alpha: - o) Virtual memory (tlbs etc) - o) Get {NetBSD,OpenBSD,Linux}/alpha booting. :) + x) OSF1 PALcode, Virtual memory support. + x) PALcode replacement! PAL1E etc opcodes...? + x) Interrupt/exception/trap handling. + x) Floating point exception correctness. + x) More work on bootup memory and register contents. + x) More Alpha machine types, so it could work with + OpenBSD, FreeBSD, and Linux too? SPARC: - o) Add all registers (floating point, control regs etc) - o) Save/restore register windows etc! - o) Load/stores! + o) Implement Adress space identifiers; load/stores etc. + o) Save/restore register windows etc! Both v9 and pre-v9! + o) Finish the subcc and addcc flag computation code. + o) Add more registers (floating point, control regs etc) + o) Exception/trap handling. o) Disassemly of some more instructions? o) Are sll etc 32-bit sign-extending or zero-extending? - o) Finish the cmp (subcc) flag computation code. o) Finish the GDB register stuff. + x) Floating point exception correctness. o) SPARC v8, v7 etc? Debugger: @@ -164,61 +240,107 @@ o) Try to make the debugger more modular and, if possible, reentrant! o) Remove the emul command? (But show network info if showing machines?) - o) Generalize the expression evaluator. (debugger_expr.c?) - settable variables ("show nr of instructions on average") - emul[x] defaults to current emul - machine[x] defaults to current machine - cpu[x] defaults to currently focused cpu - registers cpu arch dependent (#-prefix) - symbols @-prefix - numeric constants decimal, hex, and octal ($-prefix) - boolean yes,no, true,false - operators (+ - * / % & | ^ !) - parentheses for grouping subexpressions - NOTE: the change from % to # for register prefix! - examples: - emul[0].machine[2].cpu[0].pc - machine[test2].cpu[1].ra = main - settings.show_trace_tree = yes - - Settings: - o) Remove a setting. - o) Read/write a setting given a name. (Read as - string and/or int64_t simultaneously?) - o) Warnings when exiting the emulator, if the - settings have not been removed exactly in - the same way as they were added? This would - improve code cleanliness in the long term. - (I.e. require a corresponding _destroy() - function for all _new functions... machine_ - cpu_ etc.) - - Help command should have subsections! One for "expressions", - mirrored in the documentation, but the internal help should - be the one that should be considered correct. + o) Evaluate expressions within []? That would allow stuff like + cpu[x] where x is an expression. + o) Settings: + x) Special handlers for Write! + +) MIPS coproc regs + +) Alpha/MIPS/SPARC zero registers + +) x86 64/32/16-bit registers + x) Value formatter for resulting output. o) see src/debugger.c for more POWER/PowerPC: + x) Fix DECR timer speed, so it matches the host. + x) NetBSD/prep 3.x triggers a possible bug in the emulator: + + + <0x26c550(&ata_xfer_pool,2,0,8,..)> + <0x35c71c(0x3f27000,0,52,8,..)> + + + <__wdccommand_start(0xd005e4c8,0x3f27000,0,13,..)> + + [ wdc: write to SDH: 0xb0 (sectorsize 2, lba=1, drive 1, head 0) ] + + <0x198120(0xd005e4c8,72,64,0xbb8,..)> + + + Note: x) PPC optimizations; instr combs x) 64-bit stuff: either Linux on G5, or perhaps some hobbyist version of AIX? (if there exists such a thing) - x) find and fix the bug which causes NetBSD/macppc to fail after - an install! x) macppc: adb controller; keyboard (for framebuffer mode) x) make OpenBSD/macppc work (PCI controller stuff) + x) Floating point exception correctness. + x) Alignment exceptions. + +PReP: + Clock time! ("Bad battery blah blah") Algor: - PCI and ISA and LOCAL interrupts! --> wdc could start working - Add interrupt controller in dev_algor.c. + o) Other models than the P5064? + o) PCI interrupts... needed for stuff like the tlp NIC? + +BeBox: + o) Interrupts. There seems to be a problem with WDC interrupts + "after a short while", although a few interrupts get through? + o) Perhaps find a copy of BeOS and try it? + +HPCmips: + x) Mouse/pad support! :) + x) A NIC? (As a PCMCIA device?) + +AVR: + o) Everything. ARM: - o) try to get netbsd/evbarm 3.x running (iq80321) + o) See netwinder_reset() in NetBSD; the current "an internal error + occured" message after reboot/halt is too ugly. + o) ARM "wait"-like instruction? + o) try to get netbsd/evbarm 3.x or 4.x running (iq80321) o) make the xscale counter registers (ccnt) work o) make the ata controller usable for FreeBSD! - o) zaurus for openbsd... - o) debian/cats crashes because of unimplemented coproc stuff. + o) Zaurus emulation, for e.g. OpenBSD/zaurus + o) Debian/cats crashes because of unimplemented coproc stuff. fix this? +Test machines: + o) dev_fb block fill and copy + o) dev_fb draw characters (from the built-in font)? + o) dev_fb input device? mouse pointer coordinates and buttons + (allow changes in these to cause interrupts as well?) + o) Redefine the halt() function so that it stops "sometimes + soon", i.e. usage in demo code should be: + for (;;) { + halt(); + } + +Better CD Image file support: + x) Support CD formats that contain more than 1 track, e.g. + CDI files (?). These can then contain a mixture of e.g. sound + and data tracks, and booting from an ISO filesystem path + would boot from [by default] the first data track. + (This would make sense for e.g. Dreamcast CD images, or + possibly other live-CD formats.) + +Networking: + x) Fix performance problems caused by only allowing a + single TCP packet to be unacked. + x) Don't hardcode offsets into packets! + x) Test with lower than 100 max tcp/udp connections, + to make sure that reuse works! + x) Make OpenBSD work better as a guest OS! + x) DHCP? Debian doesn't actually send DHCP packets, even + though it claims to? So it is hard to test. + x) Multiple networks per emulation, and let different + NICs in machines connect to different networks. + x) Support VDE (vde.sf.net)? Easiest/cleanest (before a + redesign of the network framework has been done) is + probably to connect it using the current (udp) solution. + x) Allow SLIP connections, possibly PPP, in addition to + ethernet? + Cache simulation: o) Command line flags for: o) CPU endianness? @@ -235,13 +357,38 @@ is another option (easier to implement, but very very slow). Documentation: - o) machines, cpus, devices. - o) Automagic documentation generation: + x) Note about sandboxing/security: + Not all emulated instructions fail in the way they would + do on real hardware (e.g. a userspace program writing to + a system register might work in GXemul, but it would + fail on real hardware). Sandbox = contain from the + host OS. But the emulated programs will run "less + securely". + x) Try NetBSD/arc 4.x! (It seems to work with disk images!) + x) NetBSD/pmax 4 install instructions: xterm instead of vt100! + x) BETTER DEVICE EXAMPLES! + o) Move away from technical.html to somewhere new. + o) DEVICE_TICK + o) Implement example devices using interrupts, dyntrans + memory access, etc.? + x) Document the dyntrans core? + x) Rewrite the section about experimental devices, after the + framebuffer acceleration has been implemented, and demos + written. (Symbolic names instead of numbers; example + use cases, etc. Mention demo files that use the various + features?) + x) "a very simple linear framebuffer device (for graphics output)" + under "which machines does gxemul emulate" ==> better + description? + x) Better description on how to set up a cross compiler? + Example for MIPS64. + o) Automagic documentation generation? + x) machines, cpus, devices. x) REMEMBER that several machines/devices can be in the same source file! o) Try to rewrite the install instructions for those machines - that use 3MAX into using CATS? (To remove the need to a raw - ffs partition using up all of the disk image.) + that use 3MAX into using CATS or hpcmips? (To remove the need + to use a raw ffs partition, using up all of the disk image.) More generic out_of_memory error reporting, and check everywhere! Causes: OpenBSD has low default limits for normal users. @@ -251,61 +398,45 @@ Unix systems usually allow processes to allocate virtual memory beyond the amount of RAM in the machine.) -Breakpoints: 32-bit vs 64-bit sign extension for MIPS, warnings, etc. - Use the debugger's symbolic name stuff. (which will have to be - extended soon to support stuff like "2*x + symbol + y" etc. cool - stuff) - The Device subsystem: x) allow devices to be moved and/or changed in size (down to a - minimum size, etc, or up to a max size) + minimum size, etc, or up to a max size); if there is a collision, + return false. It is up to the caller to handle this situation! + x) NOTE: Translations must be invalidated, both for + registering new devices, and for moving existing ones. + cpu->invalidate translation caches, for all CPUs that + are connected to a specific memory. x) keep track of interrupts and busses? actually, allowing any device to be a bus might be a nice idea. x) turn interrupt controllers into devices? :-) x) refactor various clocks/nvram/cmos into one device? -Clocks: - x) General framework for automagic clock adjustment for _all_ - kinds of clocks and timers. (Which should be possible to turn - off, of course, like the way DECstation emulation works now.) - PCI: x) last write was ffffffff ==> fix this, it should be used together with a mask to get the correct bits. also, not ALL bits are size bits! (lowest 4 vs lowest 2?) x) add support for address fixups - x) generalize the interrupt routing stuff (lines etc). this should - be per machine? or per bus, that's better - x) add a "pcn" NIC (AMD PCnet32 Lance 79c970 (PCI 1022:2000)), - could be useful for several machine modes (Malta, Algor, evbarm, - hp700?, macppc, etc.) - -Network layer: - o) DHCP (for Debian and BSD installers :-) - o) increase performance - o) don't rely on NetBSD-ish usage - o) Multiple networks per emulation, and let different - NICs in machines connect to different networks. - o) many other issues: see src/net.c + x) generalize the interrupt routing stuff (lines etc) -Busses: - o) Redesign the entire "mainbus" concept! - o) Busses should be placed in a hierarchical tree! - o) Easily configurable interrupt routing in SMP systems. - o) Specific clock/bus speeds, cpu speeds etc. - o) Synchronization over network? or at least in dyntrans within - one emulated machine - o) dev->bus: TurboChannel, PCMCIA, ADB? +Clocks and timers: + x) DON'T HARDCODE 100 HZ IN cpu_mips_coproc.c! + x) Test the 8253? Right now it doesn't seem to be used? + x) NetWinder timeofday is incorrect! + x) Cobalt TOD is incorrect! + x) Go through all other machines, one by one, and fix them. Config file parser: o) Rewrite it from scratch! o) Usage of any expression available through the debugger + o) Allow interrupt controllers to be added! and interrupts + to be used in more ways than before o) Support for running debugger commands (like the -c command line option) Floating point layer: o) make it common enough to be used by _all_ emulation modes - o) implement more stuff + o) implement correct error/exception handling and rounding modes + o) implement more helper functions (i.e. add, sub, mul...) o) non-IEEE modes (i.e. x86)? Userland emulation: @@ -314,13 +445,16 @@ Sound: x) generic sound framework - x) add one or more sound cards as devices + x) add one or more sound cards as devices; add a testmachine + sound card first? + x) Dreamcast sound? Generic PCI sound cards? ASC SCSI controller: x) NetBSD/arc 2.0 uses the ASC controller in a way which GXemul cannot yet handle. (NetBSD 1.6.2 works ok.) (Possibly a problem in NetBSD itself, http://mail-index.netbsd.org/source-changes/ 2005/11/06/0024.html suggests that.) + NetBSD 4.x seems to work? :) Caches / memory hierarchies: (this is mostly MIPS-specific) o) src/memory*.c: Implement correct cache emulation for @@ -339,9 +473,11 @@ possible. File/disk/symbol handling: + o) Make sure that disks can be added/removed during runtime! + (Perhaps this needs a reasonably large re-write.) o) Remove some of the complexity in file format guessing, for Ultrix kernels that are actually disk images? - o) Better handling of tape files + o) Better handling of tape files o) Read function argument count and types from binaries? (ELF?) o) Better demangling of C++ names. Note: GNU's C++ differs from e.g. Microsoft's C++, so multiple schemes must be possible. See @@ -350,17 +486,9 @@ Userland ABI emulation: o) see src/useremul.c -Terminal/console: - o) allow emulated serial ports to be connected to the outside - world in a more generic way, or even to other emulated - machines(?) - -Save state of the whole emulated machine, to be able to load it back - in later? (Memory, all device's states, all registers and - so on. Like taking a snapshot. (SimOS seems to do this, - according to its website.)) - Better framebuffer and X-windows functionality: + o) Generalize the update_x1y1x2y2 stuff to an extend-region() + function... o) -Yx sometimes causes crashes. o) Simple device access to framebuffer_blockcopyfill() etc, and text output (using the built-in fonts), for dev_fb. @@ -371,6 +499,7 @@ o) Non-resizable windows? Or choose scaledown depending on size (and center the image, with a black border). o) Different scaledown on different windows? + o) Non-integral scale-up? (E.g. 640x480 -> 1024x768) o) Switch scaledown during runtime? (Ala CTRL-ALT-plus/minus) o) Bug reported by Elijah Rutschman on MacOS with weird keys (F5 = cursor down?). @@ -384,18 +513,3 @@ o) Generalize the framebuffer stuff by moving _ALL_ X11 specific code to src/x11.c! -Statistics: (this could be interesting) - o) Save to file and show graphics. It should be possible to - run gxemul after a simulation to just show the graphics, - or convert to a .ppm or .tga or similar. - o) memory accesses (to measure cache efficiency and - page coloring efficiency) - o) nr of simultaneous ASIDs in use in the TLB, for MIPS - o) percentage of time spent in different "states", such as - running userland code, kernel code, or idling (for CPUs - that have such an instruction, or whenever the PC is - inside a specific idle-function (address range)). - Possible additional state (for example on R3000): caches - disabled. - o) position of read/write on (SCSI) disks -