• Avi Kivity's avatar
    Type-safe ioport callbacks · acd1c812
    Avi Kivity authored
    The current ioport callbacks are not type-safe, in that they accept an "opaque"
    pointer as an argument whose type must match the argument to the registration
    function; this is not checked by the compiler.
    This patch adds an alternative that is type-safe.  Instead of an opaque
    argument, both registation and the callback use a new IOPort type.  The
    callback then uses container_of() to access its main structures.
    Currently the old and new methods exist side by side; once the old way is gone,
    we can also save a bunch of memory since the new method requires one pointer
    per ioport instead of 6.
    Acked-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
    Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
    Signed-off-by: default avatarAnthony Liguori <aliguori@us.ibm.com>
ioport.c 8.82 KB