Jumping into middle of instruction

Can anyone explain the concept of 'Jumping into the middle of
instructions'. Why it is used? Can we hide arbitrary code (I/O
instructions, system calls) by this technique ?

.

Relevant Pages

  • Re: [RFC, PATCH 16/24] i386 Vmi io header
    ... for port I/O in Linux be writing raw instruction strings. ... wrapper layer here is fairly easy, and makes the full range of I/O ... instructions available to the VMI interface. ... This usage of predefined macros in the driver causing port I/O semantics to change seems a little strange to try to wrap onto an alternate instruction interfaces, since it is dependent definitions local to each .C file, rather than global processor or derived feature bits. ...
    (Linux-Kernel)
  • Re: [RFC] remove bus_memio.h and bus_pio.h
    ... > benefit was swamped by the actual I/O. ... Pentium can do up to 532 instructions in a microsecond even if it is ... CPU cycles @ 4nsec each, plus a huge number of CPU cycles for the i/o ... i/o instructions are slightly faster than memory accesses ...
    (freebsd-arch)
  • Re: counter 0 of atmega48
    ... free running counter, up to 0xff and then to zero and up again. ... ?in areg, TCNT0 ... Or better yet, use the I/O ... Registers as data space using LD and ST instructions, ...
    (comp.arch.embedded)
  • RE: A very basic question
    ... getting a 60% hit ratio, then it you are doing an average of 1.6 I/Os ... a savings of 10K instructions (I/O cost minus look-aside cost) is ...
    (bit.listserv.ibm-main)
  • Re: counter 0 of atmega48
    ... The tcnt0 section says roughly "...tim/cnt0 bit in PRR must be written to zero ...  in areg, TCNT0 ... Or better yet, use the I/O ... Registers as data space using LD and ST instructions, ...
    (comp.arch.embedded)