qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Gerd Hoffmann <kraxel@redhat.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [Qemu-devel] [PATCH 0/1] Add virtio-input driver.
Date: Thu, 19 Mar 2015 18:05:16 +0100	[thread overview]
Message-ID: <550B01CC.9030602@redhat.com> (raw)
In-Reply-To: <20150319164311-mutt-send-email-mst@redhat.com>



On 19/03/2015 17:33, Michael S. Tsirkin wrote:
> On Thu, Mar 19, 2015 at 03:46:44PM +0100, Gerd Hoffmann wrote:
>> Latest.  As far I know there never ever have been incompatible changes
>> to the interface, and given this is userspace/kernel abi I don't expect
>> that to happen in the future.
> 
> More events are added though, are they not? And distros backport rundom
> subsets.
> So I worry: what happens e.g. if you migrate between hosts which expose
> slightly different subsets of events?
> Might e.g. a button get stuck because button-press event was
> sent but button-release wasn't?

I think this is the same as SCSI.  You can migrate between hosts which
expose slightly different command sets.

Paolo

  reply	other threads:[~2015-03-19 17:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1426756391-26585-1-git-send-email-kraxel@redhat.com>
2015-03-19 13:35 ` [Qemu-devel] [PATCH 0/1] Add virtio-input driver Michael S. Tsirkin
2015-03-19 14:46   ` Gerd Hoffmann
2015-03-19 16:33     ` Michael S. Tsirkin
2015-03-19 17:05       ` Paolo Bonzini [this message]
2015-03-19 16:46     ` Michael S. Tsirkin

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=550B01CC.9030602@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtualization@lists.linux-foundation.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).