Re: [PATCH 11/21] ioport: insert event_tap_ioport() to ioport_write().

Michael S. Tsirkin
2010-11-28T09:41:32Z

On Thu, Nov 25, 2010 at 03:06:50PM +0900, Yoshiaki Tamura wrote:
> Record ioport event to replay it upon failover.
>
> Signed-off-by: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>

Interesting. This will have to be extended to support ioeventfd.
Since each eventfd is really just a binary trigger
it should be enough to read out the fd state.

> ---
> ioport.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/ioport.c b/ioport.c
> index aa4188a..74aebf5 100644
> --- a/ioport.c
> +++ b/ioport.c
> @@ -27,6 +27,7 @@
>
> #include "ioport.h"
> #include "trace.h"
> +#include "event-tap.h"
>
> /***********************************************************/
> /* IO Port */
> @@ -76,6 +77,7 @@ static void ioport_write(int index, uint32_t address, uint32_t data)
> default_ioport_writel
> };
> IOPortWriteFunc *func = ioport_write_table[index][address];
> + event_tap_ioport(index, address, data);
> if (!func)
> func = default_func[index];
> func(ioport_opaque[address], address, data);
> --
> 1.7.1.2
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html