From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Feng Jin <joe.jin@oracle.com>,
Zhenzhong Duan <zhenzhong.duan@oracle.com>,
Yuval Shaia <yuval.shaia@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chien Yen <chien.yen@oracle.com>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCH] xen: reuse the same pirq allocated when driver load first time
Date: Tue, 21 May 2013 09:40:59 -0400 [thread overview]
Message-ID: <20130521134059.GE492@phenom.dumpdata.com> (raw)
In-Reply-To: <519B474E.4000202@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 2976 bytes --]
> Looking at the hypervisor code I couldn't see anything obviously wrong.
I think the culprit is "physdev_unmap_pirq":
if ( is_hvm_domain(d) )
{
spin_lock(&d->event_lock);
gdprintk(XENLOG_WARNING,"d%d, pirq: %d is %x %s, irq: %d\n",
d->domain_id, pirq, domain_pirq_to_emuirq(d, pirq),
domain_pirq_to_emuirq(d, pirq) == IRQ_UNBOUND ? "unbound" : "",
domain_pirq_to_irq(d, pirq));
if ( domain_pirq_to_emuirq(d, pirq) != IRQ_UNBOUND )
ret = unmap_domain_pirq_emuirq(d, pirq);
spin_unlock(&d->event_lock);
if ( domid == DOMID_SELF || ret )
goto free_domain;
It always tells me unbound:
(XEN) physdev.c:237:d14 14, pirq: 54 is ffffffff
(XEN) irq.c:1873:d14 14, nr_pirqs: 56
(XEN) physdev.c:237:d14 14, pirq: 53 is ffffffff
(XEN) irq.c:1873:d14 14, nr_pirqs: 56
(XEN) physdev.c:237:d14 14, pirq: 52 is ffffffff
(XEN) irq.c:1873:d14 14, nr_pirqs: 56
(XEN) physdev.c:237:d14 14, pirq: 51 is ffffffff
(XEN) irq.c:1873:d14 14, nr_pirqs: 56
(XEN) physdev.c:237:d14 14, pirq: 50 is ffffffff
(XEN) irq.c:1873:d14 14, nr_pirqs: 56
(a bit older debug code, so the 'unbound' does not show up here).
Which means that the call to unmap_domain_pirq_emuirq does not happen.
The checks in unmap_domain_pirq_emuirq also look to be depend
on the code being IRQ_UNBOUND.
In other words, all of that code looks to only clear things when
they are !IRQ_UNBOUND.
But the other logic (IRQ_UNBOUND) looks to be missing a removal
in the radix tree:
if ( emuirq != IRQ_PT )
radix_tree_delete(&d->arch.hvm_domain.emuirq_pirq, emuirq);
And I think that is what is causing the leak - the radix tree
needs to be pruned? Or perhaps the allocate_pirq should check
the radix tree for IRQ_UNBOUND ones and re-use them?
> I do note that Xen doesn't free the pirq until it has been unbound by
> the guest. Xen will warn if the guest unmaps a pirq that is still bound
> ("domD: forcing unbind of pirq P"). Is this what is happening? If so,
No. It does not b/c of this check in physdev_unmap_pirq:
if ( domid == DOMID_SELF || ret )
goto free_domain
which jumps over the call to unmap_domain_pirq.
> that would suggest a bug in the guest rather than the hypervisor.
No. But then I am not even using it. See attached module.
>
> David
[-- Attachment #2: alloc_and_unmap.c --]
[-- Type: text/plain, Size: 1232 bytes --]
#include <linux/module.h>
#include <linux/kthread.h>
#include <linux/pagemap.h>
#include <linux/init.h>
#include <xen/xen.h>
#include <xen/page.h>
#include <asm/xen/hypervisor.h>
#include <xen/features.h>
#include <xen/events.h>
MODULE_AUTHOR("Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>");
MODULE_DESCRIPTION("alloc_and_unmap");
MODULE_LICENSE("GPL");
MODULE_VERSION("0.1");
static int do_it(void)
{
int rc;
struct physdev_get_free_pirq op_get_free_pirq;
struct physdev_unmap_pirq unmap_irq;
int pirq;
op_get_free_pirq.type = MAP_PIRQ_TYPE_MSI;
rc = HYPERVISOR_physdev_op(PHYSDEVOP_get_free_pirq, &op_get_free_pirq);
if (rc) {
printk(KERN_WARNING "%s:%d rc:%d\n", __func__, __LINE__, rc);
return rc;
}
pirq = op_get_free_pirq.pirq;
unmap_irq.pirq = pirq;
unmap_irq.domid = DOMID_SELF;
rc = HYPERVISOR_physdev_op(PHYSDEVOP_unmap_pirq, &unmap_irq);
if (rc) {
printk(KERN_WARNING "unmap irq failed %d\n", rc);
return rc;
}
printk("PIRQ: %d\n", pirq);
return 0;
}
static int __init alloc_and_unmap_init(void)
{
int i;
for (i = 0; i < 10; i++)
if (do_it())
break;
return 0;
}
static void __exit alloc_and_unmap_exit(void)
{
}
module_init(alloc_and_unmap_init);
module_exit(alloc_and_unmap_exit);
next prev parent reply other threads:[~2013-05-21 13:41 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 8:18 [PATCH] xen: reuse the same pirq allocated when driver load first time Zhenzhong Duan
2013-05-10 18:53 ` Konrad Rzeszutek Wilk
2013-05-13 7:44 ` Zhenzhong Duan
2013-05-13 11:06 ` Stefano Stabellini
2013-05-13 14:07 ` Konrad Rzeszutek Wilk
2013-05-13 14:50 ` Stefano Stabellini
2013-05-13 16:17 ` Konrad Rzeszutek Wilk
2013-05-13 17:24 ` Stefano Stabellini
2013-05-13 18:20 ` Konrad Rzeszutek Wilk
2013-05-14 13:49 ` Stefano Stabellini
2013-05-14 14:20 ` Konrad Rzeszutek Wilk
2013-05-15 9:41 ` Stefano Stabellini
2013-05-15 14:18 ` Zhenzhong Duan
2013-05-17 2:22 ` Zhenzhong Duan
2013-05-20 10:24 ` Stefano Stabellini
2013-05-20 15:24 ` Konrad Rzeszutek Wilk
2013-05-20 17:57 ` Konrad Rzeszutek Wilk
2013-05-20 20:38 ` Konrad Rzeszutek Wilk
2013-05-21 10:07 ` [Xen-devel] " David Vrabel
2013-05-21 13:40 ` Konrad Rzeszutek Wilk [this message]
2013-05-21 16:51 ` Stefano Stabellini
2013-05-21 20:42 ` Konrad Rzeszutek Wilk
2013-05-21 21:50 ` Stefano Stabellini
2013-05-21 22:41 ` Konrad Rzeszutek Wilk
2013-05-22 9:37 ` Jan Beulich
2013-05-22 15:14 ` Konrad Rzeszutek Wilk
2013-05-22 15:25 ` Jan Beulich
2013-05-22 16:41 ` Konrad Rzeszutek Wilk
2013-05-23 6:31 ` Jan Beulich
2013-05-29 17:50 ` Stefano Stabellini
2013-05-30 17:48 ` Konrad Rzeszutek Wilk
2013-06-05 5:27 ` Zhenzhong Duan
2013-06-05 12:50 ` [Xen-devel] " Stefano Stabellini
2013-06-20 2:57 ` Zhenzhong Duan
2013-06-20 14:21 ` Stefano Stabellini
2013-06-24 7:19 ` Zhenzhong Duan
2013-06-24 7:19 ` Zhenzhong Duan
2013-06-24 17:18 ` Stefano Stabellini
2013-06-25 5:33 ` DuanZhenzhong
2013-06-25 5:33 ` DuanZhenzhong
2013-06-25 7:21 ` [PATCH 4.1] x86: fix emuirq regression from XSA-21 fix (was: Re: [PATCH] xen: reuse the same pirq allocated when driver load first time) Jan Beulich
2013-06-25 7:44 ` [PATCH 4.1] x86: fix emuirq regression from XSA-21 fix DuanZhenzhong
2013-06-25 8:36 ` Jan Beulich
2013-06-25 8:43 ` DuanZhenzhong
2013-06-25 10:56 ` [PATCH 4.1] x86: fix emuirq regression from XSA-21 fix (was: Re: [PATCH] xen: reuse the same pirq allocated when driver load first time) Stefano Stabellini
2013-06-25 11:03 ` Stefano Stabellini
2013-06-27 8:34 ` Jan Beulich
2013-06-27 10:46 ` Stefano Stabellini
2013-06-25 17:51 ` [Xen-devel] [PATCH] xen: reuse the same pirq allocated when driver load first time Stefano Stabellini
2013-06-26 4:00 ` Zhenzhong Duan
2013-06-26 4:00 ` Zhenzhong Duan
2013-06-26 18:08 ` Stefano Stabellini
2013-06-27 4:01 ` Zhenzhong Duan
2013-06-27 4:01 ` Zhenzhong Duan
2013-06-27 11:52 ` Stefano Stabellini
2013-06-28 2:33 ` Zhenzhong Duan
2013-06-28 2:33 ` Zhenzhong Duan
2013-06-28 11:12 ` Stefano Stabellini
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=20130521134059.GE492@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=chien.yen@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xensource.com \
--cc=yuval.shaia@oracle.com \
--cc=zhenzhong.duan@oracle.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.