|
| From: | Paolo Bonzini |
| Subject: | Re: [Qemu-devel] [PATCH 2/5] hostmem: make hostmem global and RAM hotunplg safe |
| Date: | Mon, 15 Apr 2013 08:38:55 +0200 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 |
Il 15/04/2013 03:42, liu ping fan ha scritto: > > It will work because readers will grab either the hostmem_lock or the > > BQL, while writers will grab both. A kind of local/global lock, but I'm > > No only hostmem_lock is used to protect readers from writers. While > the writers are protected agaist each other by biglock. So leaving > the "cur_hostmem = next_hostmem" outside to reflect the lock's rules. Doesn't help much if you do not document them... Paolo
| [Prev in Thread] | Current Thread | [Next in Thread] |