From: Paolo Bonzini <pbonzini@redhat.com>
To: "Damjan Marion (damarion)" <damarion@cisco.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"n.nikolaev@virtualopensystems.com"
<n.nikolaev@virtualopensystems.com>
Subject: Re: [Qemu-devel] [PATCH] vhost-user: fix VHOST_USER_SET_MEM_TABLE
Date: Thu, 26 Jun 2014 11:20:14 +0200 [thread overview]
Message-ID: <53ABE5CE.20608@redhat.com> (raw)
In-Reply-To: <BF34D436-B706-4F04-A3F1-D3E5C2D0A709@cisco.com>
Il 26/06/2014 11:10, Damjan Marion (damarion) ha scritto:
> Does it really make a sense to keep old broken code, which doesn’t work if VM have more than 3 GB of RAM?
> As Nikolay said yesterday:
>> > On the other hand there's no wide adoption of
>> > the protocol so it's still not critical to change it.
> I think we should just fix it and keep it as version 1.
>
I agree. Anything that happens before 2.1 is final can stay as version 1.
Paolo
prev parent reply other threads:[~2014-06-26 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 7:55 [Qemu-devel] [PATCH] vhost-user: fix VHOST_USER_SET_MEM_TABLE Damjan Marion
2014-06-26 8:01 ` Michael S. Tsirkin
2014-06-26 9:10 ` Damjan Marion (damarion)
2014-06-26 9:20 ` Paolo Bonzini [this message]
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=53ABE5CE.20608@redhat.com \
--to=pbonzini@redhat.com \
--cc=damarion@cisco.com \
--cc=mst@redhat.com \
--cc=n.nikolaev@virtualopensystems.com \
--cc=qemu-devel@nongnu.org \
/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).