All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhai, Edwin" <edwin.zhai@intel.com>
To: Gianluca.Guida@eu.citrix.com
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"Zhai, Edwin" <edwin.zhai@intel.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] [IOEMU]: fix the crash of HVM live	migration with intensive disk access
Date: Tue, 01 Sep 2009 08:40:23 +0800	[thread overview]
Message-ID: <4A9C6D77.2070107@intel.com> (raw)
In-Reply-To: <4A823278.6050207@intel.com>

Gianluca,

Do you have comments for this? Maybe Stefano and I are on the same page. 
My assumption is that we need keep the cpu_physical_memory_set_dirty and 
phys_ram_dirty for qemu itself, and make  cpu_physical_memory_set_dirty 
call xc_hvm_modified_memory if in live migration.

Thanks,


Zhai, Edwin wrote:
>
>
> Stefano Stabellini wrote:
>> On Tue, 11 Aug 2009, Zhai, Edwin wrote:
>>  
>>>  [IOEMU]: fix the crash of HVM live migration with intensive disk 
>>> access
>>>
>>> Intensive disk access, e.g. sum of big file, during HVM live 
>>> migration would cause guest error even file system crash. Guest 
>>> dmesg said
>>> "attempt to access beyond end of device
>>> hda1: rw=0, want=10232032112, limit=10474317"
>>>
>>> Current map cache used by qemu dma doesn't mark the page dirty, so 
>>> that these pages(probably holding DMA data struct) are not 
>>> transferred in the last iteration during live migration.
>>>
>>> This patch fixes it, and also merges the qemu's original dirty 
>>> bitmap used by other devices such as vga.
>>>
>>> Signed-Off-By: Zhai Edwin <edwin.zhai@intel.com>
>>>
>>>     
>>
>> I think the fix is correct but we should thinking about dropping
>> logdirty and start using xc_hvm_modified_memory instead for all cases.
>>   
>
> One interface should be better. But I'm not sure about the perf 
> implications. You know, qemu use logdirty for its device emulation 
> even without live migration, e.g. vga screen refresh. Changing to 
> xc_hvm_modified_memory would cause many hypercall to set/get the 
> bitmap in xen...
>
>> I think Gianluca also may have something to say about this but this week
>> he is on vacation.
>>
>>   
>

-- 
best rgds,
edwin

      parent reply	other threads:[~2009-09-01  0:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 12:12 [PATCH] [IOEMU]: fix the crash of HVM live migration with intensive disk access Zhai, Edwin
2009-08-11 12:56 ` Stefano Stabellini
2009-08-12  3:09   ` Zhai, Edwin
2009-08-12 11:28     ` Stefano Stabellini
2009-09-01  0:40     ` Zhai, Edwin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A9C6D77.2070107@intel.com \
    --to=edwin.zhai@intel.com \
    --cc=Gianluca.Guida@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.