Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 11:26:19AM -0300, Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 01:45:52PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
From: Yaniv Kamay ya...@qumranet.com
Stop cpus before devices when stopping the VM, start cpus after
On Thu, Mar 26, 2009 at 12:03:30PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 11:26:19AM -0300, Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 01:45:52PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
From: Yaniv Kamay ya...@qumranet.com
Stop
On Wed, Mar 25, 2009 at 01:45:52PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
From: Yaniv Kamay ya...@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.
--
To
On Wed, Mar 25, 2009 at 11:26:19AM -0300, Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 01:45:52PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
From: Yaniv Kamay ya...@qumranet.com
Stop cpus before devices when stopping the VM, start cpus after devices
when starting VM.
Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 11:26:19AM -0300, Marcelo Tosatti wrote:
On Wed, Mar 25, 2009 at 01:45:52PM +0200, Avi Kivity wrote:
Marcelo Tosatti wrote:
From: Yaniv Kamay ya...@qumranet.com
Stop cpus before devices when stopping the VM, start cpus after
