From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 0/2] tcg: Move TCG arch-specific initialization inside TCG code
Date: Fri, 19 Dec 2014 10:47:23 +0100 [thread overview]
Message-ID: <5493F42B.3080208@suse.de> (raw)
In-Reply-To: <1418963165-498-1-git-send-email-ehabkost@redhat.com>
Am 19.12.2014 um 05:26 schrieb Eduardo Habkost:
> Many architectures manually call arch-specific TCG initialization at CPU init
> time[1], instead of having tcg_init() doing all initialization steps. This
> series introduces a tcg_arch_init() function that may be implemented by
> architecture-specific code for TCG initialization.
How do you imagine this to work with multiple CPU types? From the looks
of it, this is for the target CPU, not the TCG architecture, so
tcg_arch_init() limits us to one implementation unlike now.
On the other hand it doesn't seem to be a per-CPU, i.e. CPUClass,
initialization either...
Regards,
Andreas
--
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 21284 AG Nürnberg
next prev parent reply other threads:[~2014-12-19 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 4:26 [Qemu-devel] [PATCH 0/2] tcg: Move TCG arch-specific initialization inside TCG code Eduardo Habkost
2014-12-19 4:26 ` [Qemu-devel] [PATCH 1/2] tcg: Introduce tcg_arch_init() function Eduardo Habkost
2014-12-19 14:05 ` Richard Henderson
2014-12-19 4:26 ` [Qemu-devel] [PATCH 2/2] target-i386: Implement tcg_arch_init() Eduardo Habkost
2014-12-19 9:47 ` Andreas Färber [this message]
2014-12-19 10:29 ` [Qemu-devel] [PATCH 0/2] tcg: Move TCG arch-specific initialization inside TCG code Paolo Bonzini
2014-12-19 13:16 ` 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=5493F42B.3080208@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).