Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.apple2.programmer > #3910
| From | Benoit0123 <bgilon@free.fr> |
|---|---|
| Newsgroups | comp.sys.apple2.programmer |
| Subject | Re: Query about ProDOS 8 |
| Date | 2017-09-05 09:13 +0000 |
| Organization | Mac GUI |
| Message-ID | <benoit0123-1504602782@macgui.com> (permalink) |
| References | <benoit0123-1504365722@macgui.com> <benoit0123-1504384751@macgui.com> <8abdd2b9-3b52-407a-8617-9ae15e344b76@googlegroups.com> |
John Brooks wrote: (small snip) > Hi Benoit. That sounds like a pretty cool chunk of Apple II tech. Thanks John. > So is it a sampling profiler? IE, recording the PC every IRQ and streaming > it to a big file? If so, what are the set_mark & read in IRQ used for? My current design is to store a sequence of frequency counters (indexed by PC) into this file. So a part of the ISR duty currently would be to: * Gather the foreground PC and memory state (LC bank switching and Main/Aux mem state) from the pz0/stack that the ROM firmware (IRQ handler) put there; * Compute a hash value (hash function being worked on currently) based on those raw data; * Use the result value as the offset within the data file. Every reachable storage cell will be three bytes wide (for a counter/frequency value in the range 0..16777215, initially 0). * Read this counter from file by a SET_MARK, READ sequence * Increment the counter by one (using *saturated* unsigned arithmetic) * Write back this counter value to the file @ at the same offset therefore a second SET_MARK call to rewind the file position by the cell size amount before issuing the WRITE. To sum things up, it is not my intent currently to write the raw details in a pure sequencial form into a potentially infinite size file. > For high-speed interrupts, you might consider running your code on the > IIGS. The GS provides great IRQ control either through scan-line > interrupts, or by using the Ensoniq for up to 32x general-purpose timers, > each with IRQ enable/disable control. > > Your instrumented code can still run at 1MHz 6502 on the GS, and can also > rely on the /RAM5 ram disk for fast block I/O. At the early stage of design, I would rather be using dev environments which I am confortable with. Therefore I am limiting myself to the Apple //e (enhanced) for the time being. As soon as I think the application/utility is be ready to be released (at least for the capture/collect/gather step), I’ll do it and the complete source will be included. > Is this instrumentation intended to run on a real Apple II machine in the > future? If emulation is good enough for your use-case, you could also > instrument GSplus, etc to log data faster than an IRQ-sampler could manage > (every CPU insn if you wanted). Thank you John, I’ll get a look at GSPort and GSPlus. > Yes, my current in-progress driver has both a min-bank and max-bank > parameter which is used at boot to set up the size of the /RAM3 drive. > These values are currently set to 1 and the max bank found by scanning the > Ramworks banks, but my intent is to allow them to be adjusted for > Appleworks and other 'big aux mem' applications. > > However, since bank assignment is a boot-time decision, I do not have a > good idea on the API/approach to use to allow these parameters to be > adjusted. Any ideas on how you'd like to see aux-mem banks reserved? I think that the only medium for communicating to a booting process would be to use the keyboard (including the open/close apple keys) or the game paddles/joystick buttons on the 2 and 2+). However, there might be peripheral cards (e.g. the Transwarp original accelerator in one of my Apple //e) which test for some keys to be pressed upon powering up the Apple 2. So an idea I have would be to have a delayed keyboard scan routine in the ProDOS Loader which, for say for 1 or 2 seconds waits for a user key press and reacts accordingly with an adequate prompt displayed on screen. On the absence of any user keypress within this delay, then a default configuration will be activated, one « non default » configuration could also dictates to postpone the RAM driver install to sometime in the future. The allowable configurations could be stored in some bytes within the first blocks of the boot volume if space allows (which I hope). Those configurations could contain directives for acceleration status, RAM drive driver installation and amount of disk space allocated. There could even could be some extra bits available for third party extensions (e.g. network settings). The system disc could also include a utility to import/export such configurations from/to text files.. but I disgress… > > -JB > @JBrooksBSI > -- Growing old is mandatory.. growing up is optional.. But the other way round is as true.
Back to comp.sys.apple2.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 15:17 +0000
Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-02 09:35 -0700
Re: Query about ProDOS 8 James Davis <JPD.Enterprises@outlook.com> - 2017-09-02 12:20 -0700
Re: Query about ProDOS 8 ol.sc@web.de (Oliver Schmidt) - 2017-09-08 10:53 +0000
Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-11 21:53 -0700
Re: Query about ProDOS 8 Steve Nickolas <usotsuki@buric.co> - 2017-09-12 03:51 -0400
Re: Query about ProDOS 8 David Schmenk <dschmenk@gmail.com> - 2017-09-12 06:59 -0700
Re: Query about ProDOS 8 ol.sc@web.de (Oliver Schmidt) - 2017-09-12 14:41 +0000
Re: Query about ProDOS 8 Michael J. Mahon <mjmahon@aol.com> - 2017-09-12 11:18 -0500
Re: Query about ProDOS 8 roger.shimada@gmail.com - 2017-09-02 10:48 -0700
Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 20:34 +0000
Re: Query about ProDOS 8 roger.shimada@gmail.com - 2017-09-02 20:35 -0700
Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-02 21:47 -0700
Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-03 09:34 +0000
Re: Query about ProDOS 8 David Schmenk <dschmenk@gmail.com> - 2017-09-03 07:15 -0700
Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-03 16:12 +0000
Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-04 22:00 -0700
Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-05 09:13 +0000
Re: Query about ProDOS 8 James Davis <JPD.Enterprises@outlook.com> - 2017-09-06 17:56 -0700
Re: Query about ProDOS 8 John Brooks <jbrooks@blueshiftinc.com> - 2017-09-07 00:00 -0700
Re: Query about ProDOS 8 Steve Nickolas <usotsuki@buric.co> - 2017-09-10 23:30 -0400
Re: Query about ProDOS 8 David Schmenk <dschmenk@gmail.com> - 2017-09-11 06:52 -0700
Re: Query about ProDOS 8 roger.shimada@gmail.com - 2017-09-03 07:05 -0700
Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 20:37 +0000
Re: Query about ProDOS 8 Antoine Vignau <antoine.vignau@laposte.net> - 2017-09-02 14:07 -0700
Re: Query about ProDOS 8 Benoit0123 <bgilon@free.fr> - 2017-09-02 21:36 +0000
Re: Query about ProDOS 8 James Davis <JPD.Enterprises@outlook.com> - 2017-09-03 18:45 -0700
Re: Query about ProDOS 8 Antoine Vignau <antoine.vignau@laposte.net> - 2017-09-03 23:52 -0700
Re: Query about ProDOS 8 Jorge <jorge@jorgechamorro.com> - 2017-09-12 13:42 -0700
Re: Query about ProDOS 8 ol.sc@web.de (Oliver Schmidt) - 2017-09-13 10:30 +0000
Re: Query about ProDOS 8 Steven Hirsch <snhirsch@gmail.com> - 2017-09-13 08:00 -0400
Re: Query about ProDOS 8 Jorge <jorge@jorgechamorro.com> - 2017-09-14 07:30 -0700
csiph-web