On Mon, Apr 08, 2013 at 04:36:47PM +0200, Andreas Färber wrote:
> Am 08.04.2013 14:19, schrieb Gleb Natapov:
> > On Tue, Apr 02, 2013 at 04:29:32PM +0300, Gleb Natapov wrote:
> >>> static void kvm_sw_tlb_put(PowerPCCPU *cpu)
> >>> {
> >>> CPUPPCState *env = &cpu->env;
> >>> diff --git a/targ
Am 08.04.2013 14:19, schrieb Gleb Natapov:
> On Tue, Apr 02, 2013 at 04:29:32PM +0300, Gleb Natapov wrote:
>>> static void kvm_sw_tlb_put(PowerPCCPU *cpu)
>>> {
>>> CPUPPCState *env = &cpu->env;
>>> diff --git a/target-s390x/cpu.c b/target-s390x/cpu.c
>>> index 23fe51f..6321384 100644
>>> --
Il 08/04/2013 14:19, Gleb Natapov ha scritto:
>> > Does this compile with kvm support disabled?
Oops, sorry, I thought I had replied to this email (with "hmm, let me
check").
> Well, it does not:
> CCs390x-softmmu/target-s390x/cpu.o
> /users/gleb/work/qemu/target-s390x/cpu.c: In function 's
On Tue, Apr 02, 2013 at 04:29:32PM +0300, Gleb Natapov wrote:
> > static void kvm_sw_tlb_put(PowerPCCPU *cpu)
> > {
> > CPUPPCState *env = &cpu->env;
> > diff --git a/target-s390x/cpu.c b/target-s390x/cpu.c
> > index 23fe51f..6321384 100644
> > --- a/target-s390x/cpu.c
> > +++ b/target-s390x
On Fri, Mar 22, 2013 at 09:37:16PM +0100, Paolo Bonzini wrote:
> Now that we have a CPU object with a reset method, it is better to
> keep the KVM reset close to the CPU reset. Using qemu_register_reset
> as we do now keeps them far apart.
>
> As a side effect, a CPU reset (cpu_reset) will reset
Now that we have a CPU object with a reset method, it is better to
keep the KVM reset close to the CPU reset. Using qemu_register_reset
as we do now keeps them far apart.
As a side effect, a CPU reset (cpu_reset) will reset the KVM state too.
Signed-off-by: Paolo Bonzini
---
include/sysemu/kvm
