qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
Cc: ohmura.kei@lab.ntt.co.jp, kvm@vger.kernel.org,
	mtosatti@redhat.com, Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, yoshikawa.takuya@oss.ntt.co.jp,
	avi@redhat.com
Subject: [Qemu-devel] Re: [RFC PATCH 07/20] Introduce qemu_put_vector() and qemu_put_vector_prepare() to use put_vector() in QEMUFile.
Date: Thu, 22 Apr 2010 14:29:52 -0500	[thread overview]
Message-ID: <4BD0A3B0.8040609@linux.vnet.ibm.com> (raw)
In-Reply-To: <1271829445-5328-8-git-send-email-tamura.yoshiaki@lab.ntt.co.jp>

On 04/21/2010 12:57 AM, Yoshiaki Tamura wrote:
> For fool proof purpose, qemu_put_vector_parepare should be called
> before qemu_put_vector.  Then, if qemu_put_* functions except this is
> called after qemu_put_vector_prepare, program will abort().
>
> Signed-off-by: Yoshiaki Tamura<tamura.yoshiaki@lab.ntt.co.jp>
>    

I don't get it.  What's this protecting against?

Regards,

Anthony Liguori

> ---
>   hw/hw.h  |    2 ++
>   savevm.c |   53 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>   2 files changed, 55 insertions(+), 0 deletions(-)
>
> diff --git a/hw/hw.h b/hw/hw.h
> index 921cf90..10e6dda 100644
> --- a/hw/hw.h
> +++ b/hw/hw.h
> @@ -77,6 +77,8 @@ void qemu_fflush(QEMUFile *f);
>   int qemu_fclose(QEMUFile *f);
>   void qemu_put_buffer(QEMUFile *f, const uint8_t *buf, int size);
>   void qemu_put_byte(QEMUFile *f, int v);
> +void qemu_put_vector(QEMUFile *f, QEMUIOVector *qiov);
> +void qemu_put_vector_prepare(QEMUFile *f);
>   void *qemu_realloc_buffer(QEMUFile *f, int size);
>   void qemu_clear_buffer(QEMUFile *f);
>
> diff --git a/savevm.c b/savevm.c
> index 944e788..22d928c 100644
> --- a/savevm.c
> +++ b/savevm.c
> @@ -180,6 +180,7 @@ struct QEMUFile {
>       uint8_t *buf;
>
>       int has_error;
> +    int prepares_vector;
>   };
>
>   typedef struct QEMUFileStdio
> @@ -557,6 +558,58 @@ void qemu_put_byte(QEMUFile *f, int v)
>           qemu_fflush(f);
>   }
>
> +void qemu_put_vector(QEMUFile *f, QEMUIOVector *v)
> +{
> +    struct iovec *iov;
> +    int cnt;
> +    size_t bufsize;
> +    uint8_t *buf;
> +
> +    if (qemu_file_get_rate_limit(f) != 0) {
> +        fprintf(stderr,
> +                "Attempted to write vector while bandwidth limit is not zero.\n");
> +        abort();
> +    }
> +
> +    /* checks prepares vector.
> +     * For fool proof purpose, qemu_put_vector_parepare should be called
> +     * before qemu_put_vector.  Then, if qemu_put_* functions except this
> +     * is called after qemu_put_vector_prepare, program will abort().
> +     */
> +    if (!f->prepares_vector) {
> +        fprintf(stderr,
> +            "You should prepare with qemu_put_vector_prepare.\n");
> +        abort();
> +    } else if (f->prepares_vector&&  f->buf_index != 0) {
> +        fprintf(stderr, "Wrote data after qemu_put_vector_prepare.\n");
> +        abort();
> +    }
> +    f->prepares_vector = 0;
> +
> +    if (f->put_vector) {
> +        qemu_iovec_to_vector(v,&iov,&cnt);
> +        f->put_vector(f->opaque, iov, 0, cnt);
> +    } else {
> +        qemu_iovec_to_size(v,&bufsize);
> +        buf = qemu_malloc(bufsize + 1 /* for '\0' */);
> +        qemu_iovec_to_buffer(v, buf);
> +        qemu_put_buffer(f, buf, bufsize);
> +        qemu_free(buf);
> +    }
> +
> +}
> +
> +void qemu_put_vector_prepare(QEMUFile *f)
> +{
> +    if (f->prepares_vector) {
> +        /* prepare vector */
> +        fprintf(stderr, "Attempted to prepare vector twice\n");
> +        abort();
> +    }
> +    f->prepares_vector = 1;
> +    qemu_fflush(f);
> +}
> +
>   int qemu_get_buffer(QEMUFile *f, uint8_t *buf, int size1)
>   {
>       int size, l;
>    

  reply	other threads:[~2010-04-22 19:30 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-21  5:57 [Qemu-devel] [RFC PATCH 00/20] Kemari for KVM v0.1 Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 01/20] Modify DIRTY_FLAG value and introduce DIRTY_IDX to use as indexes of bit-based phys_ram_dirty Yoshiaki Tamura
2010-04-22 19:26   ` [Qemu-devel] " Anthony Liguori
2010-04-23  2:09     ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 02/20] Introduce cpu_physical_memory_get_dirty_range() Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 03/20] Use cpu_physical_memory_set_dirty_range() to update phys_ram_dirty Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 04/20] Make QEMUFile buf expandable, and introduce qemu_realloc_buffer() and qemu_clear_buffer() Yoshiaki Tamura
2010-04-21  8:03   ` [Qemu-devel] " Stefan Hajnoczi
2010-04-21  8:27     ` Yoshiaki Tamura
2010-04-23  9:53   ` Avi Kivity
2010-04-23  9:59     ` Yoshiaki Tamura
2010-04-23 13:14       ` Avi Kivity
2010-04-26 10:43         ` Yoshiaki Tamura
2010-04-23 13:26     ` Anthony Liguori
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 05/20] Introduce put_vector() and get_vector to QEMUFile and qemu_fopen_ops() Yoshiaki Tamura
2010-04-22 19:28   ` [Qemu-devel] " Anthony Liguori
2010-04-23  3:37     ` Yoshiaki Tamura
2010-04-23 13:22       ` Anthony Liguori
2010-04-23 13:48         ` Avi Kivity
2010-05-03  9:32           ` Yoshiaki Tamura
2010-05-03 12:05             ` Anthony Liguori
2010-05-03 15:36               ` Yoshiaki Tamura
2010-05-03 16:07                 ` Anthony Liguori
2010-04-26 10:43         ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 06/20] Introduce iovec util functions, qemu_iovec_to_vector() and qemu_iovec_to_size() Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 07/20] Introduce qemu_put_vector() and qemu_put_vector_prepare() to use put_vector() in QEMUFile Yoshiaki Tamura
2010-04-22 19:29   ` Anthony Liguori [this message]
2010-04-23  4:02     ` [Qemu-devel] " Yoshiaki Tamura
2010-04-23 13:23       ` Anthony Liguori
2010-04-26 10:43         ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 08/20] Introduce RAMSaveIO and use cpu_physical_memory_get_dirty_range() to check multiple dirty pages Yoshiaki Tamura
2010-04-22 19:31   ` [Qemu-devel] " Anthony Liguori
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 09/20] Introduce writev and read to FdMigrationState Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 10/20] Introduce skip_header parameter to qemu_loadvm_state() so that it can be called iteratively without reading the header Yoshiaki Tamura
2010-04-22 19:34   ` [Qemu-devel] " Anthony Liguori
2010-04-23  4:25     ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 11/20] Introduce some socket util functions Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 12/20] Introduce fault tolerant VM transaction QEMUFile and ft_mode Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 13/20] Introduce util functions to control ft_transaction from savevm layer Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 14/20] Upgrade QEMU_FILE_VERSION from 3 to 4, and introduce qemu_savevm_state_all() Yoshiaki Tamura
2010-04-22 19:37   ` [Qemu-devel] " Anthony Liguori
2010-04-23  3:29     ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 15/20] Introduce FT mode support to configure Yoshiaki Tamura
2010-04-22 19:38   ` [Qemu-devel] " Anthony Liguori
2010-04-23  3:09     ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 16/20] Introduce event_tap fucntions and ft_tranx_ready() Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 17/20] Modify migrate_fd_put_ready() when ft_mode is on Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 18/20] Modify tcp_accept_incoming_migration() to handle ft_mode, and add a hack not to close fd when ft_mode is enabled Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 19/20] Insert do_event_tap() to virtio-{blk, net}, comment out assert() on cpu_single_env temporally Yoshiaki Tamura
2010-04-22 19:39   ` [Qemu-devel] " Anthony Liguori
2010-04-23  4:51     ` Yoshiaki Tamura
2010-04-21  5:57 ` [Qemu-devel] [RFC PATCH 20/20] Introduce -k option to enable FT migration mode (Kemari) Yoshiaki Tamura
2010-04-22  8:58 ` [Qemu-devel] [RFC PATCH 00/20] Kemari for KVM v0.1 Dor Laor
2010-04-22 10:35   ` Yoshiaki Tamura
2010-04-22 11:36     ` Takuya Yoshikawa
2010-04-22 12:35       ` Yoshiaki Tamura
2010-04-22 12:19     ` Dor Laor
2010-04-22 13:16       ` Yoshiaki Tamura
2010-04-22 20:33         ` Anthony Liguori
2010-04-23  1:53           ` Yoshiaki Tamura
2010-04-23 13:20             ` Anthony Liguori
2010-04-26 10:44               ` Yoshiaki Tamura
2010-04-22 20:38         ` Dor Laor
2010-04-23  5:17           ` Yoshiaki Tamura
2010-04-23  7:36             ` Fernando Luis Vázquez Cao
2010-04-25 21:52               ` Dor Laor
2010-04-22 16:15     ` Jamie Lokier
2010-04-23  0:20       ` Yoshiaki Tamura
2010-04-23 15:07         ` Jamie Lokier
2010-04-22 19:42 ` [Qemu-devel] " Anthony Liguori
2010-04-23  0:45   ` Yoshiaki Tamura
2010-04-23 13:10     ` Anthony Liguori
2010-04-23 13:24 ` Avi Kivity
2010-04-26 10:44   ` Yoshiaki Tamura

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BD0A3B0.8040609@linux.vnet.ibm.com \
    --to=aliguori@linux.vnet.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=ohmura.kei@lab.ntt.co.jp \
    --cc=qemu-devel@nongnu.org \
    --cc=tamura.yoshiaki@lab.ntt.co.jp \
    --cc=yoshikawa.takuya@oss.ntt.co.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).