[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PULL 04/11] target-i386: Rename cpu_x86_init() to cpu_
From: |
Eduardo Habkost |
Subject: |
Re: [Qemu-devel] [PULL 04/11] target-i386: Rename cpu_x86_init() to cpu_x86_init_user() |
Date: |
Thu, 26 Feb 2015 12:59:49 -0300 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Wed, Feb 25, 2015 at 11:06:55PM +0100, Andreas Färber wrote:
> Am 25.02.2015 um 20:58 schrieb Eduardo Habkost:
> > The function is used only for CONFIG_USER, so make its purpose clear.
> >
> > Reviewed-by: Paolo Bonzini <address@hidden>
> > Signed-off-by: Eduardo Habkost <address@hidden>
> > ---
> > target-i386/cpu.c | 2 +-
> > target-i386/cpu.h | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
>
> Please don't. I happily got all architectures aligned that it's at least
> cpu_something_init, and it only happens to be user-only for x86. It is
> rather the legacy function that was used in both system and user.
If that's a legacy function, what are the steps you plan to follow to
eliminate it? I would be glad to help eliminating legacy code.
Initialization of CPUs in *-user and *-softmmu is different in i386, so
we are going to have different code for both. How do you think I should
name the *-user-specific CPU init function in target-i386, then?
--
Eduardo
[Qemu-devel] [PULL 02/11] target-i386: Eliminate unnecessary get_cpuid_vendor() function, Eduardo Habkost, 2015/02/25
[Qemu-devel] [PULL 05/11] target-i386: Eliminate cpu_init() function, Eduardo Habkost, 2015/02/25
[Qemu-devel] [PULL 06/11] target-i386: Simplify error handling on cpu_x86_init_user(), Eduardo Habkost, 2015/02/25
[Qemu-devel] [PULL 08/11] linux-user: Check for cpu_init() errors, Eduardo Habkost, 2015/02/25