From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH/RFC] provide --accel option
Date: Fri, 12 Sep 2008 22:07:07 +0300 [thread overview]
Message-ID: <f43fc5580809121207u6a0b1008k178c7e42ff9f972@mail.gmail.com> (raw)
In-Reply-To: <1221245233-26152-1-git-send-email-glommer@redhat.com>
On 9/12/08, Glauber Costa <glommer@redhat.com> wrote:
> The --accel option will provide us the ability of defining which
> accelerator to pick at run time. It has the advantage of not using
> the not-well-accepted constructor directives, and also, of stabilishing
> a way to define priorities among accelerators.
>
> The ones registered first, are tried first.
> + case QEMU_OPTION_accel:
> + {
> + int i;
> + for (i = 0; i < sizeof(available_accels)/sizeof(void *); i++) {
ARRAY_SIZE(available_accels)?
> + if (!strcasecmp(optarg, available_accels[i]->name))
> + register_qemu_accel(available_accels[i]);
> + }
> + }
> + break;
next prev parent reply other threads:[~2008-09-12 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-12 18:47 [Qemu-devel] [PATCH/RFC] provide --accel option Glauber Costa
2008-09-12 19:07 ` Blue Swirl [this message]
2008-09-12 19:14 ` Glauber Costa
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=f43fc5580809121207u6a0b1008k178c7e42ff9f972@mail.gmail.com \
--to=blauwirbel@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).