From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:36435) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZNgSb-0002Jv-9i for qemu-devel@nongnu.org; Fri, 07 Aug 2015 08:09:18 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZNgSY-00084W-3P for qemu-devel@nongnu.org; Fri, 07 Aug 2015 08:09:17 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58142) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZNgSX-00084O-UX for qemu-devel@nongnu.org; Fri, 07 Aug 2015 08:09:14 -0400 References: <55BB319A.2010906@suse.com> <55C43A0D.9070000@suse.com> From: Eric Blake Message-ID: <55C49FE2.4030608@redhat.com> Date: Fri, 7 Aug 2015 06:09:06 -0600 MIME-Version: 1.0 In-Reply-To: <55C43A0D.9070000@suse.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="JFtEU1qrtes5CM5S1nIlhltVubaMlaaPm" Subject: Re: [Qemu-devel] The issue about parameters(uint64) of a device are treated as signed long int. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: lma@suse.com, "pbonzini@redhat.com >> Paolo Bonzini" Cc: "qemu-devel@nongnu.org Developers" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --JFtEU1qrtes5CM5S1nIlhltVubaMlaaPm Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 08/06/2015 10:54 PM, Lin Ma wrote: > Hi Paolo, >=20 > As mentioned in below email, The type of wwn is reported as uint64, But= > in qemu command line, The max valid value for wwn is > 0x7fffffffffffffff. Obviously, it's treated as int64 there. I'd like to= > know that does the highest bit of _world wide name_ have special > meaning and must be zero? May I have your thoughts? You can always pass a negative number to set the highest bit (that's what libvirt does: when it is sending a uint64 value to qemu via command line or QMP, it intentionally writes values larger than INT64_MAX by first casting them to signed and writing the int64_t counterpart instead). It's a shortcoming in our data parser, and not an actual prohibition in values you can set. And if you don't like the behavior, patches are welcome. --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --JFtEU1qrtes5CM5S1nIlhltVubaMlaaPm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJVxJ/iAAoJEKeha0olJ0Nq+R4IAJb2YQLodYb+lXmVilFUhrpZ w1O1u0S0mef/CEWIlQWP4tG7xG8p1A/9aLcDfbsGyRr/i1AWLH5EJOPZGi/JYYQJ jn7br6x5HPl6CMH/L7sra16iwa33kJjNuJiF0JqqXenQURXkQ79H+pvQ8n3vXCQN t6BgBK1BaLcbgAPhqARSj2B5iM58iasCEY1a7k8vqZoyKe2tUxLuHbsJdw6YAmeJ GCXs8rzT1mbJvULioNOp52KCoX5TgTfLegShclxsvC64USLx4zWwKS/99QOslO27 UnK82t0YQ1wFj8cCOmaSdm+29qQ4zaC/SZ2M2Bb2qMWGFD7OCLdWeGY0e+48/RQ= =dv9m -----END PGP SIGNATURE----- --JFtEU1qrtes5CM5S1nIlhltVubaMlaaPm--