qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com, filip.navara@gmail.com, avi@redhat.com
Subject: [Qemu-devel] [PATCH RFC 0/3] QEMU Object Model
Date: Thu,  6 Aug 2009 10:52:13 -0300	[thread overview]
Message-ID: <1249566736-5020-1-git-send-email-lcapitulino@redhat.com> (raw)

 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.

             reply	other threads:[~2009-08-06 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 13:52 Luiz Capitulino [this message]
2009-08-06 13:52 ` [Qemu-devel] [PATCH 1/3] Introduce qobject header file Luiz Capitulino
2009-08-06 14:02   ` [Qemu-devel] " Avi Kivity
2009-08-06 14:07     ` Luiz Capitulino
2009-08-06 15:54   ` [Qemu-devel] " malc
2009-08-06 13:52 ` [Qemu-devel] [PATCH 2/3] Introduce QString data type Luiz Capitulino
2009-08-06 13:52 ` [Qemu-devel] [PATCH 3/3] Introduce QNumber " Luiz Capitulino
2009-08-06 14:04   ` [Qemu-devel] " Avi Kivity
2009-08-06 14:05     ` François Revol
2009-08-06 14:48       ` Avi Kivity
2009-08-06 14:10     ` Luiz Capitulino
2009-08-06 21:21     ` Luiz Capitulino
2009-08-06 14:06 ` [Qemu-devel] Re: [PATCH RFC 0/3] QEMU Object Model Avi Kivity

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=1249566736-5020-1-git-send-email-lcapitulino@redhat.com \
    --to=lcapitulino@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=filip.navara@gmail.com \
    --cc=qemu-devel@nongnu.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).