On 17 September 2014 16:22, Richard Henderson r...@twiddle.net wrote:
On 09/17/2014 04:54 AM, Andreas Färber wrote:
I am fine with adding such hooks, but please let's use a better, active
name. CPUClass is the struct name and cpu-exec is a file name; the hook
should say what it's doing, not
Am 13.09.2014 um 18:45 schrieb Richard Henderson:
In preparation for removing a bunch of ifdefs from cpu_exec.
Cc: Andreas Färber afaer...@suse.de
Signed-off-by: Richard Henderson r...@twiddle.net
---
cpu-exec.c| 9 ++---
include/qom/cpu.h | 5 +
qom/cpu.c | 6
On 09/17/2014 04:54 AM, Andreas Färber wrote:
I am fine with adding such hooks, but please let's use a better, active
name. CPUClass is the struct name and cpu-exec is a file name; the hook
should say what it's doing, not where the code (used to) live(s). Just
exec_enter/exec_exit possibly?
Richard Henderson writes:
In preparation for removing a bunch of ifdefs from cpu_exec.
Cc: Andreas Färber afaer...@suse.de
Signed-off-by: Richard Henderson r...@twiddle.net
---
cpu-exec.c| 9 ++---
include/qom/cpu.h | 5 +
qom/cpu.c | 6 --
3 files changed,
In preparation for removing a bunch of ifdefs from cpu_exec.
Cc: Andreas Färber afaer...@suse.de
Signed-off-by: Richard Henderson r...@twiddle.net
---
cpu-exec.c| 9 ++---
include/qom/cpu.h | 5 +
qom/cpu.c | 6 --
3 files changed, 11 insertions(+), 9 deletions(-)
