From: David Vrabel <david.vrabel@citrix.com>
To: Julien Grall <julien.grall@linaro.org>
Cc: xen-devel <xen-devel@lists.xen.org>,
Ian Campbell <Ian.Campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Multiple issues with event channel on Xen on ARM
Date: Wed, 5 Feb 2014 10:09:18 +0000 [thread overview]
Message-ID: <52F20DCE.3080501@citrix.com> (raw)
In-Reply-To: <52F1753C.3010508@linaro.org>
On 04/02/14 23:18, Julien Grall wrote:
>
> Now, if I'm using Linux 3.14-rc1 as guest and trying to destroy the domain,
> I get this following Xen trace:
>
> (XEN) Assertion 'slot >= 0 && slot < DOMHEAP_ENTRIES' failed, line 334, file mm.c
[...]
> (XEN) Xen call trace:
> (XEN) [<0023f7d0>] __bug+0x28/0x44 (PC)
> (XEN) [<0023f7d0>] __bug+0x28/0x44 (LR)
> (XEN) [<00247d6c>] domain_page_map_to_mfn+0x50/0xb4
> (XEN) [<0020b17c>] unmap_guest_page+0x20/0x54
> (XEN) [<0020b1d0>] cleanup_control_block+0x20/0x34
> (XEN) [<0020bd3c>] evtchn_fifo_destroy+0x2c/0x6c
> (XEN) [<0020b024>] evtchn_destroy+0x1a8/0x1b0
> (XEN) [<00207f80>] domain_kill+0x60/0x128
> (XEN) [<00206050>] do_domctl+0xa7c/0x1104
> (XEN) [<0024cee0>] do_trap_hypervisor+0xad8/0xd78
> (XEN) [<0024f6d0>] return_from_trap+0/0x4
This is because ARM's domain_page_map_to_mfn() doesn't work with pages
mapped with map_domain_page_global() which uses vmap().
x86's implementation has
if ( va >= VMAP_VIRT_START && va < VMAP_VIRT_END )
{
pl1e = virt_to_xen_l1e(va);
BUG_ON(!pl1e);
}
// ...
return l1e_get_pfn(*pl1e);
So I think ARM's needs something similar.
David
next prev parent reply other threads:[~2014-02-05 10:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 23:18 Multiple issues with event channel on Xen on ARM Julien Grall
2014-02-05 10:09 ` David Vrabel [this message]
2014-02-05 10:33 ` Julien Grall
2014-02-05 10:45 ` David Vrabel
2014-02-05 13:34 ` David Vrabel
2014-02-05 13:44 ` Julien Grall
2014-02-05 13:52 ` David Vrabel
2014-02-05 13:58 ` Julien Grall
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=52F20DCE.3080501@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).