-
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:
Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by:
Avi Kivity <avi@redhat.com>
Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>Avi Kivity authoredThe 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:
Anthony Liguori <aliguori@us.ibm.com>
Signed-off-by:
Avi Kivity <avi@redhat.com>
Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com>
Loading