[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111213113628.GB31138@amt.cnet>
Date: Tue, 13 Dec 2011 09:36:28 -0200
From: Marcelo Tosatti <mtosatti@...hat.com>
To: Liu Ping Fan <kernelfans@...il.com>
Cc: kvm@...r.kernel.org, linux-kernel@...r.kernel.org, avi@...hat.com,
aliguori@...ibm.com, gleb@...hat.com, jan.kiszka@....de
Subject: Re: [PATCH v3] kvm: make vcpu life cycle separated from kvm instance
On Mon, Dec 12, 2011 at 10:41:23AM +0800, Liu Ping Fan wrote:
> From: Liu Ping Fan <pingfank@...ux.vnet.ibm.com>
>
> Currently, vcpu can be destructed only when kvm instance destroyed.
> Change this to vcpu's destruction taken when its refcnt is zero,
> and then vcpu MUST and CAN be destroyed before kvm's destroy.
>
> Signed-off-by: Liu Ping Fan <pingfank@...ux.vnet.ibm.com>
> ---
> arch/x86/kvm/i8254.c | 10 ++++--
> arch/x86/kvm/i8259.c | 12 +++++--
> arch/x86/kvm/mmu.c | 7 ++--
> arch/x86/kvm/x86.c | 54 +++++++++++++++++++----------------
> include/linux/kvm_host.h | 71 ++++++++++++++++++++++++++++++++++++++++++----
> virt/kvm/irq_comm.c | 7 +++-
> virt/kvm/kvm_main.c | 62 +++++++++++++++++++++++++++++++++------
> 7 files changed, 170 insertions(+), 53 deletions(-)
This needs a full audit of paths that access vcpus. See for one example
bsp_vcpu pointer.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists