From: Igor Mammedov <imammedo@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: ehabkost@redhat.com, "Gleb Natapov" <gleb@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
qemu-devel@nongnu.org, blauwirbel@gmail.com,
anthony@codemonkey.ws, X86 <kvm@vger.kernel.org>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [PATCH qom-cpu-next v3 3/4] target-i386: Slim conversion to X86CPU subclasses
Date: Mon, 4 Feb 2013 21:21:16 +0100 [thread overview]
Message-ID: <20130204212116.7c13c978@thinkpad.mammed.net> (raw)
In-Reply-To: <20130204170501.20ddb78f@nial.usersys.redhat.com>
On Mon, 4 Feb 2013 17:05:01 +0100
Igor Mammedov <imammedo@redhat.com> wrote:
> On Mon, 04 Feb 2013 13:52:32 +0100
> Andreas Färber <afaerber@suse.de> wrote:
>
> > Am 04.02.2013 12:08, schrieb Igor Mammedov:
> > > On Sat, 2 Feb 2013 01:37:07 +0100
> > > Andreas Färber <afaerber@suse.de> wrote:
> > >
[...]
>
> > >> @@ -2198,6 +2018,8 @@ static void x86_cpu_initfn(Object *obj)
> > >> CPUState *cs = CPU(obj);
> > >> X86CPU *cpu = X86_CPU(obj);
> > >> CPUX86State *env = &cpu->env;
> > >> + X86CPUClass *xcc = X86_CPU_GET_CLASS(obj);
> > >> + const x86_def_t *def = &xcc->info;
> > >> static int inited;
> > >>
> > >> cpu_exec_init(env);
> > >> @@ -2227,6 +2049,41 @@ static void x86_cpu_initfn(Object *obj)
> > >> x86_cpuid_get_tsc_freq,
> > >> x86_cpuid_set_tsc_freq, NULL, NULL, NULL);
> > >>
> > >> + /* sysenter isn't supported in compatibility mode on AMD,
> > >> + * syscall isn't supported in compatibility mode on Intel.
> > >> + * Normally we advertise the actual CPU vendor, but you can
> > >> + * override this using the 'vendor' property if you want to use
> > >> + * KVM's sysenter/syscall emulation in compatibility mode and
> > >> + * when doing cross vendor migration
> > >> + */
> > >> + if (kvm_enabled()) {
> > >> + host_cpuid(0, 0, NULL, &env->cpuid_vendor1, &env->cpuid_vendor2,
> > >> + &env->cpuid_vendor3);
> > > This is not per instance specific, this override would be better done to
> > > sub-classes in kvm_arch_init().
> >
> > Hmm... I think the issue I addresses this way was that kvm.c didn't have
> > access to your static vendor_words2str() helper. Writing the words into
> > the word fields is more direct than converting them to a string and
> > writing them back into the words.
> you have these correct vendor words ready after you called
> kvm_host_cpu_class_init() in kvm_arch_init(), so just direct copy from host
> class would do.
I was talking nonsense here.
Why not to make vendor_words2str() helper not static and use it in kvm.c
instead of doing partial init of host class and then reuse the value you got
to override vendor in other classes?
[...]
--
Regards,
Igor
prev parent reply other threads:[~2013-02-04 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1359765428-27805-1-git-send-email-afaerber@suse.de>
2013-02-02 0:37 ` [PATCH qom-cpu-next v3 3/4] target-i386: Slim conversion to X86CPU subclasses Andreas Färber
2013-02-04 11:08 ` [Qemu-devel] " Igor Mammedov
2013-02-04 12:52 ` Andreas Färber
2013-02-04 16:05 ` Igor Mammedov
2013-02-04 20:21 ` Igor Mammedov [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=20130204212116.7c13c978@thinkpad.mammed.net \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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