From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v5 12/19] Introduce virtio-testdev Date: Thu, 12 Jun 2014 13:56:50 +0200 Message-ID: <53999582.4000806@redhat.com> References: <1402495294-30737-1-git-send-email-drjones@redhat.com> <1402495294-30737-13-git-send-email-drjones@redhat.com> <53997DF2.9020602@redhat.com> <20140612113000.GF6646@dhcp-27-201.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org, christoffer.dall@linaro.org To: Andrew Jones Return-path: Received: from mail-qa0-f54.google.com ([209.85.216.54]:47760 "EHLO mail-qa0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933142AbaFLL4y (ORCPT ); Thu, 12 Jun 2014 07:56:54 -0400 Received: by mail-qa0-f54.google.com with SMTP id v10so1428890qac.41 for ; Thu, 12 Jun 2014 04:56:53 -0700 (PDT) In-Reply-To: <20140612113000.GF6646@dhcp-27-201.brq.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Il 12/06/2014 13:30, Andrew Jones ha scritto: >> > >> > Hi Drew, >> > >> > quite a few months ago I had promised to help with an alternative >> > implementation that does not require a new virtio device (which would >> > in turn need registration of the device ID and so on. > Does it? I assumed we'd be fine just using 0xffff (which I understood > from the spec to be reserved for development purposes). That actually means "use 65535 until you've requested a unique id". I'd rather use 0xf2d6 (a random high number) than 65535, even though that's out-of-spec. Paolo > I guess a > potential problem would be if this device is also used at the same > time as an experimental device that is also making that assumption, > but that'd be easily fixed by the developer who's doing the > experimenting. >