On Wed, Jun 16, 2010 at 6:34 AM, Anthony Liguori wrote:
> On 06/16/2010 12:05 AM, Cam Macdonell wrote:
>>
>> On Tue, Jun 15, 2010 at 4:33 PM, Anthony Liguori
>> wrote:
>>
>>>
>>> On 06/15/2010 05:26 PM, Cam Macdonell wrote:
>>>
On Tue, Jun 15, 2010 at 10:32 AM, Anthony Liguori
wro
On 06/16/2010 12:05 AM, Cam Macdonell wrote:
On Tue, Jun 15, 2010 at 4:33 PM, Anthony Liguori wrote:
On 06/15/2010 05:26 PM, Cam Macdonell wrote:
On Tue, Jun 15, 2010 at 10:32 AM, Anthony Liguori
wrote:
On 06/15/2010 11:16 AM, Cam Macdonell wrote:
How does thi
On Tue, Jun 15, 2010 at 4:33 PM, Anthony Liguori wrote:
> On 06/15/2010 05:26 PM, Cam Macdonell wrote:
>>
>> On Tue, Jun 15, 2010 at 10:32 AM, Anthony Liguori
>> wrote:
>>
>>>
>>> On 06/15/2010 11:16 AM, Cam Macdonell wrote:
>>>
How does this look for marking the device as non-migratabl
On 06/15/2010 05:26 PM, Cam Macdonell wrote:
On Tue, Jun 15, 2010 at 10:32 AM, Anthony Liguori wrote:
On 06/15/2010 11:16 AM, Cam Macdonell wrote:
How does this look for marking the device as non-migratable? It adds a
field
'no_migrate' to the SaveStateEntry and tests for it in vmst
On Tue, Jun 15, 2010 at 10:32 AM, Anthony Liguori wrote:
> On 06/15/2010 11:16 AM, Cam Macdonell wrote:
>>
>> How does this look for marking the device as non-migratable? It adds a
>> field
>> 'no_migrate' to the SaveStateEntry and tests for it in vmstate_save. This
>> would
>> replace anything
Anthony Liguori writes:
> On 06/15/2010 11:16 AM, Cam Macdonell wrote:
>> How does this look for marking the device as non-migratable? It adds a field
>> 'no_migrate' to the SaveStateEntry and tests for it in vmstate_save. This
>> would
>> replace anything that touches memory.
>>
>> Cam
>>
>>
On 06/15/2010 11:16 AM, Cam Macdonell wrote:
How does this look for marking the device as non-migratable? It adds a field
'no_migrate' to the SaveStateEntry and tests for it in vmstate_save. This would
replace anything that touches memory.
Cam
---
hw/hw.h |1 +
savevm.c | 32 +++