From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MZ3OV-00089A-9l for qemu-devel@nongnu.org; Thu, 06 Aug 2009 09:52:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MZ3OQ-00085N-NA for qemu-devel@nongnu.org; Thu, 06 Aug 2009 09:52:35 -0400 Received: from [199.232.76.173] (port=42896 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MZ3OQ-00085K-IX for qemu-devel@nongnu.org; Thu, 06 Aug 2009 09:52:30 -0400 Received: from mx2.redhat.com ([66.187.237.31]:50400) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MZ3OP-0003rG-TL for qemu-devel@nongnu.org; Thu, 06 Aug 2009 09:52:30 -0400 From: Luiz Capitulino Date: Thu, 6 Aug 2009 10:52:13 -0300 Message-Id: <1249566736-5020-1-git-send-email-lcapitulino@redhat.com> Subject: [Qemu-devel] [PATCH RFC 0/3] QEMU Object Model List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: aliguori@us.ibm.com, filip.navara@gmail.com, avi@redhat.com Hi guys, Before I ago all over the command handlers again, I thought it would be a good idea to submit _early_ implemention of the two most basic types for review: QNumber and QString. I'm a bit concerned about QNumber, because it has to allow us to drop the current long type handling in the monitor and work right on any arch. The way I'm thinking in doing this is to change GET_TLONG() and GET_TPHYSADDR() to receive a QNumber as parameter and work with it to return the appropriate value. For Example: #if TARGET_LONG_BITS == 64 #define GET_TLONG(qnum) qnumber_get_int64(qnum); #else #define GET_TLONG(qnum) qnumber_get_int32(qnum); #endif Remeber that the monitor will always work with int64_t for the 'l' argument type. Thanks.