From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35435) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZL5h8-0007TI-9x for qemu-devel@nongnu.org; Fri, 31 Jul 2015 04:29:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZL5h3-0000Jv-Av for qemu-devel@nongnu.org; Fri, 31 Jul 2015 04:29:34 -0400 Received: from smtp2.provo.novell.com ([137.65.250.81]:48075) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZL5h3-0000J1-5x for qemu-devel@nongnu.org; Fri, 31 Jul 2015 04:29:29 -0400 Message-ID: <55BB319A.2010906@suse.com> Date: Fri, 31 Jul 2015 16:28:10 +0800 From: Lin Ma MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] The issue about parameters(uint64) of a device are treated as signed long int. Reply-To: lma@suse.com List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "qemu-devel@nongnu.org Developers" Hi all, Because qemu uses strtoll to parse string in parse_str function of qapi/string-input-visitor.c, I'd like to know why the parameters of scsi-hd device which are specified as uint64(says wwn) are getting interpreted as signed long int's instead e.g: # qemu-system-x86_64 -device scsi-hd,? ...... scsi-hd.wwn=uint64 ...... Does the highest bit of wwn value have special meaning and it must be a zero? Thanks in advance, Lin