qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: Jun Koi <junkoi2004@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] cpu_x86() ?
Date: Tue, 1 Nov 2011 18:47:59 +0400	[thread overview]
Message-ID: <201111011848.00009.jcmvbkbc@gmail.com> (raw)
In-Reply-To: <CA+g7VZ0amKxq-0NuFym5CKMpgUggiYzvBqebammtoVr=bHRmvQ@mail.gmail.com>

> > cpu_exec definition in cpu-exec.c takes place after #include "cpu.h"
> > which contains #define cpu_exec whatever.
> > In case of x86 cpu_x86_exec is actually defined by the cpu-exec.c.
> >
> 
> ok, so which means cpu_exec is redefined accordingly to each architecture.
> 
> why do we need to do this weird thing? as there is no namespace
> collision it seems between architectures, why dont we just let
> cpu_exec() be cpu_exec()?
> 
> is this a trick? i cannot figure out why.

One theory about it is the following (quoted from http://lists.nongnu.org/archive/html/qemu-devel/2011-05/msg02921.html):

One of the long standing goals for QEMU has been to be able to use a
single executable to emulate multiple architectures. I think for
example the lines like
#define cpu_init cpu_sparc_init
#define cpu_exec cpu_sparc_exec
etc. stand for this purpose, so there has been some consideration for this.

Thanks.
-- Max

      parent reply	other threads:[~2011-11-01 14:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 10:45 [Qemu-devel] cpu_x86() ? Jun Koi
2011-11-01 10:58 ` Max Filippov
2011-11-01 14:34   ` Jun Koi
2011-11-01 14:46     ` Andreas Färber
2011-11-01 14:47     ` Max Filippov [this message]

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=201111011848.00009.jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.com \
    --cc=junkoi2004@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).