From: Paolo Bonzini <pbonzini@redhat.com>
To: David Marchand <david.marchand@6wind.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org,
claudio.fontana@huawei.com, armbru@redhat.com,
jani.kokkonen@huawei.com, cam@cs.ualberta.ca
Subject: Re: [Qemu-devel] [PATCH v3 2/2] docs: update ivshmem device spec
Date: Tue, 26 Aug 2014 13:04:30 +0200 [thread overview]
Message-ID: <53FC69BE.7010100@redhat.com> (raw)
In-Reply-To: <53FC2D9C.8020804@6wind.com>
Il 26/08/2014 08:47, David Marchand ha scritto:
>
> Using a version message supposes we want to keep ivshmem-server and QEMU
> separated (for example, in two distribution packages) while we can avoid
> this, so why would we do so ?
>
> If we want the ivshmem-server to come with QEMU, then both are supposed
> to be aligned on your system.
What about upgrading QEMU and ivshmem-server while you have existing
guests? You cannot restart ivshmem-server, and the new QEMU would have
to talk to the old ivshmem-server.
Paolo
> If you want to test local modifications, then it means you know what you
> are doing and you will call the right ivshmem-server binary with the
> right QEMU binary.
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Marchand <david.marchand@6wind.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: kvm@vger.kernel.org, claudio.fontana@huawei.com,
qemu-devel@nongnu.org, armbru@redhat.com,
jani.kokkonen@huawei.com, cam@cs.ualberta.ca
Subject: Re: [Qemu-devel] [PATCH v3 2/2] docs: update ivshmem device spec
Date: Tue, 26 Aug 2014 13:04:30 +0200 [thread overview]
Message-ID: <53FC69BE.7010100@redhat.com> (raw)
In-Reply-To: <53FC2D9C.8020804@6wind.com>
Il 26/08/2014 08:47, David Marchand ha scritto:
>
> Using a version message supposes we want to keep ivshmem-server and QEMU
> separated (for example, in two distribution packages) while we can avoid
> this, so why would we do so ?
>
> If we want the ivshmem-server to come with QEMU, then both are supposed
> to be aligned on your system.
What about upgrading QEMU and ivshmem-server while you have existing
guests? You cannot restart ivshmem-server, and the new QEMU would have
to talk to the old ivshmem-server.
Paolo
> If you want to test local modifications, then it means you know what you
> are doing and you will call the right ivshmem-server binary with the
> right QEMU binary.
next prev parent reply other threads:[~2014-08-26 11:05 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 8:55 [PATCH v3 0/2] ivshmem: update documentation, add client/server tools David Marchand
2014-08-08 8:55 ` [Qemu-devel] " David Marchand
2014-08-08 8:55 ` [PATCH v3 1/2] contrib: add ivshmem client and server David Marchand
2014-08-08 8:55 ` [Qemu-devel] " David Marchand
2014-08-08 14:51 ` Stefan Hajnoczi
2014-08-08 14:51 ` Stefan Hajnoczi
2014-08-18 12:09 ` David Marchand
2014-08-18 12:09 ` David Marchand
2014-08-10 3:57 ` Gonglei
2014-08-10 3:57 ` [Qemu-devel] " Gonglei
2014-08-18 12:19 ` David Marchand
2014-08-18 12:19 ` David Marchand
2014-08-08 8:55 ` [PATCH v3 2/2] docs: update ivshmem device spec David Marchand
2014-08-08 8:55 ` [Qemu-devel] " David Marchand
2014-08-08 9:04 ` Claudio Fontana
2014-08-08 9:04 ` [Qemu-devel] " Claudio Fontana
2014-08-08 9:32 ` David Marchand
2014-08-08 9:32 ` [Qemu-devel] " David Marchand
2014-08-08 15:02 ` Stefan Hajnoczi
2014-08-08 15:02 ` Stefan Hajnoczi
2014-08-26 6:47 ` David Marchand
2014-08-26 6:47 ` David Marchand
2014-08-26 11:04 ` Paolo Bonzini [this message]
2014-08-26 11:04 ` Paolo Bonzini
2014-08-28 9:49 ` Stefan Hajnoczi
2014-08-28 9:49 ` Stefan Hajnoczi
2014-09-01 9:52 ` David Marchand
2014-09-01 9:52 ` David Marchand
2014-09-09 19:04 ` Eric Blake
2014-09-09 19:04 ` [Qemu-devel] " Eric Blake
2014-08-08 9:30 ` [Qemu-devel] [PATCH v3 0/2] ivshmem: update documentation, add client/server tools Gonglei (Arei)
2014-08-08 9:30 ` Gonglei (Arei)
2014-08-08 9:54 ` David Marchand
2014-08-08 9:54 ` David Marchand
2014-08-08 10:26 ` Gonglei (Arei)
2014-08-08 10:26 ` Gonglei (Arei)
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=53FC69BE.7010100@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=claudio.fontana@huawei.com \
--cc=david.marchand@6wind.com \
--cc=jani.kokkonen@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.