From: Avi Kivity <avi@redhat.com>
To: Liu Ping Fan <pingfank@linux.vnet.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Stefan Hajnoczi <stefanha@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>,
Jan Kiszka <jan.kiszka@siemens.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [patch v5 6/8] memory: make mmio dispatch able to be out of biglock
Date: Mon, 29 Oct 2012 11:41:53 +0200 [thread overview]
Message-ID: <508E4F61.7070103@redhat.com> (raw)
In-Reply-To: <1351468127-15025-7-git-send-email-pingfank@linux.vnet.ibm.com>
On 10/29/2012 01:48 AM, Liu Ping Fan wrote:
> Without biglock, we try to protect the mr by increase refcnt.
> If we can inc refcnt, go backward and resort to biglock.
>
> Another point is memory radix-tree can be flushed by another
> thread, so we should get the copy of terminal mr to survive
> from such issue.
>
> +static bool memory_region_section_ref(MemoryRegionSection *mrs)
> +{
> + MemoryRegion *mr;
> + bool ret = false;
> +
> + mr = mrs->mr;
> + if (mr->ops && mr->ops->ref) {
> + ret = mr->ops->ref(mr);
I still don't see why ->ref() needs to return something.
> + }
> + return ret;
> +}
> +
>
> while (len > 0) {
> page = addr & TARGET_PAGE_MASK;
> l = (page + TARGET_PAGE_SIZE) - addr;
> if (l > len)
> l = len;
> - section = phys_page_find(d, page >> TARGET_PAGE_BITS);
> +
> + if (as->lock) {
> + qemu_mutex_lock(as->lock);
> + safe_ref = memory_region_section_lookup_ref(d, page, &obj_mrs);
> + qemu_mutex_unlock(as->lock);
> + if (!safe_ref) {
> + qemu_mutex_lock_iothread();
> + qemu_mutex_lock(as->lock);
> + /* when 2nd try, mem map can change, need to judge it again */
> + safe_ref = memory_region_section_lookup_ref(d, page, &obj_mrs);
> + qemu_mutex_unlock(as->lock);
> + if (safe_ref) {
> + qemu_mutex_unlock_iothread();
> + }
> + }
> + } else {
> + /* Caller hold the big lock */
> + memory_region_section_lookup_ref(d, page, &obj_mrs);
It's not a property of the address space, it's a property of the caller.
> + }
> + section = &obj_mrs;
>
> if (is_write) {
> if (!memory_region_is_ram(section->mr)) {
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-10-29 9:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 23:48 [Qemu-devel] [patch v5 0/8] push mmio dispatch out of big lock Liu Ping Fan
2012-10-28 23:48 ` [Qemu-devel] [patch v5 1/8] atomic: introduce atomic operations Liu Ping Fan
2012-10-28 23:48 ` [Qemu-devel] [patch v5 2/8] qom: apply atomic on object's refcount Liu Ping Fan
2012-10-28 23:48 ` [Qemu-devel] [patch v5 3/8] hotplug: introduce qdev_unplug_complete() to remove device from views Liu Ping Fan
2012-10-28 23:48 ` [Qemu-devel] [patch v5 4/8] pci: remove pci device from mem view when unplug Liu Ping Fan
2012-10-28 23:48 ` [Qemu-devel] [patch v5 5/8] memory: introduce local lock for address space Liu Ping Fan
2012-10-29 7:42 ` Peter Maydell
2012-10-29 8:41 ` liu ping fan
2012-10-29 9:32 ` Avi Kivity
2012-10-29 9:46 ` liu ping fan
2012-11-01 15:45 ` Avi Kivity
2012-11-01 18:44 ` Jan Kiszka
2012-11-02 0:52 ` liu ping fan
2012-11-02 8:00 ` Jan Kiszka
2012-11-05 12:36 ` Avi Kivity
2012-10-28 23:48 ` [Qemu-devel] [patch v5 6/8] memory: make mmio dispatch able to be out of biglock Liu Ping Fan
2012-10-29 9:41 ` Avi Kivity [this message]
2012-10-30 7:06 ` liu ping fan
2012-11-01 2:04 ` liu ping fan
2012-11-01 15:46 ` Avi Kivity
2012-10-28 23:48 ` [Qemu-devel] [patch v5 7/8] memory: introduce tls context to record nested dma Liu Ping Fan
2012-10-29 8:51 ` Paolo Bonzini
2012-11-05 5:35 ` liu ping fan
2012-11-02 10:39 ` Jan Kiszka
2012-11-05 5:35 ` liu ping fan
2012-10-28 23:48 ` [Qemu-devel] [patch v5 8/8] vcpu: push mmio dispatcher out of big lock Liu Ping Fan
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=508E4F61.7070103@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=jan.kiszka@siemens.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pingfank@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.