From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: kvm: qemu: stop/start cpus before/after devices
Date: Wed, 25 Mar 2009 11:26:19 -0300
Message-ID: <20090325142619.GA28345@amt.cnet>
References: <20090324171652.GA3655@amt.cnet> <49CA1970.1090509@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: kvm-devel <kvm@vger.kernel.org>, Dor Laor <dlaor@redhat.com>,
	Yaniv Kamay <yaniv@redhat.com>
To: Avi Kivity <avi@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx2.redhat.com ([66.187.237.31]:41072 "EHLO mx2.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755853AbZCYO0d (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 25 Mar 2009 10:26:33 -0400
Content-Disposition: inline
In-Reply-To: <49CA1970.1090509@redhat.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

On Wed, Mar 25, 2009 at 01:45:52PM +0200, Avi Kivity wrote:
> Marcelo Tosatti wrote:
>> From: Yaniv Kamay <yaniv@qumranet.com>
>>
>> Stop cpus before devices when stopping the VM, start cpus after devices
>> when starting VM.
>>
>>   
>
> Why is this needed?

A vcpu could access a stopped device otherwise.