From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Andreas Färber" <afaerber@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 3/3] target-i386: replace cpuid_*features fields with a feature word array
Date: Fri, 14 Dec 2012 18:47:20 +0100 [thread overview]
Message-ID: <20121214184720.10439cd4@thinkpad.mammed.net> (raw)
In-Reply-To: <20121214173622.GD17653@otherpad.lan.raisama.net>
On Fri, 14 Dec 2012 15:36:22 -0200
Eduardo Habkost <ehabkost@redhat.com> wrote:
> On Fri, Dec 14, 2012 at 06:20:41PM +0100, Andreas Färber wrote:
> > Am 14.12.2012 17:52, schrieb Eduardo Habkost:
> > > On Fri, Dec 14, 2012 at 04:14:32PM +0100, Andreas Färber wrote:
> > >> Am 12.12.2012 23:22, schrieb Eduardo Habkost:
[...]
> >
> > >> The clock code using first_cpu looks solvable; what about CR4 and MSR
> > >> helpers, how performance-sensitive are they? (if they're not yet using
> > >> X86CPU for something else)
> > >
> > > I guess any CPU-state code inside QEMU is not performance-sensitive, as
> > > it woud already require switching between KVM kernelspace and QEMU
> > > userspace.
> >
> > I mean target-i386/[misc_]helper.c and thus TCG, IIUC. :)
>
> Oh, right. I wonder how much performance impact it would have, if people
> are already using TCG.
>
> Anyway, would this really have any impact at all? I mean:
> ENV_GET_CPU(env) is basically subtracing an constant offset from 'env'.
> So I expect similar code to be generated, just using a different offset
> from 'env' to get the cpuid_features field.
ENV_GET_CPU(env) does dynamic_cast which is expensive.
>
> --
> Eduardo
--
Regards,
Igor
next prev parent reply other threads:[~2012-12-14 17:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 22:22 [Qemu-devel] [PATCH 0/3] replace cpuid_*features fields with a featue word array (v2) Eduardo Habkost
2012-12-12 22:22 ` [Qemu-devel] [PATCH 1/3] target-i386: add EXT2_PPRO_FEATURES #define Eduardo Habkost
2012-12-14 9:44 ` Igor Mammedov
2012-12-14 11:44 ` Andreas Färber
2012-12-14 12:15 ` Eduardo Habkost
2012-12-12 22:22 ` [Qemu-devel] [PATCH 2/3] target-i386/cpu.c: coding style fix Eduardo Habkost
2012-12-12 23:36 ` Igor Mammedov
2012-12-13 13:16 ` Eduardo Habkost
2012-12-12 22:22 ` [Qemu-devel] [PATCH 3/3] target-i386: replace cpuid_*features fields with a feature word array Eduardo Habkost
2012-12-14 9:38 ` Igor Mammedov
2012-12-14 12:27 ` Eduardo Habkost
2012-12-14 13:52 ` Igor Mammedov
2012-12-14 14:02 ` Eduardo Habkost
2012-12-14 14:53 ` Andreas Färber
2012-12-14 17:16 ` Eduardo Habkost
2012-12-14 15:14 ` Andreas Färber
2012-12-14 16:52 ` Eduardo Habkost
2012-12-14 17:20 ` Andreas Färber
2012-12-14 17:36 ` Eduardo Habkost
2012-12-14 17:47 ` Igor Mammedov [this message]
2012-12-14 18:32 ` Eduardo Habkost
-- strict thread matches above, loose matches on Subject: below --
2012-12-18 16:29 [Qemu-devel] [PATCH 0/3] replace cpuid_*features fields with a featue word array (v3) Eduardo Habkost
2012-12-18 16:29 ` [Qemu-devel] [PATCH 3/3] target-i386: replace cpuid_*features fields with a feature word array Eduardo Habkost
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=20121214184720.10439cd4@thinkpad.mammed.net \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.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).