From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xenproject.org,
"Marcos E. Matsunaga" <Marcos.Matsunaga@oracle.com>
Subject: Re: EFI Xen unstable crashes on Dell E6410 when calling efi_get_time.
Date: Wed, 22 Oct 2014 15:22:08 +0100 [thread overview]
Message-ID: <5447BD90.4010908@citrix.com> (raw)
In-Reply-To: <5447D81E0200007800041139@mail.emea.novell.com>
On 22/10/14 15:15, Jan Beulich wrote:
>>>> On 22.10.14 at 13:01, <andrew.cooper3@citrix.com> wrote:
>> On 22/10/14 11:22, Jan Beulich wrote:
>>>>>> On 22.10.14 at 11:45, <andrew.cooper3@citrix.com> wrote:
>>>> For EFI calls, we run on the efi pagetables, not the idle pagetables, so
>>>> I am not surprised that the assertion has failed. I suspect that the
>>>> pagefault hander for hypervisor faults needs to become wise to the fact
>>>> that we may receive a fault when calling into the firmware. As all the
>>>> efi pagetables are xenheap pages, there is nothing conceptually wrong
>>>> with using map_domain_page() to do the walk.
>>> I'm not sure it's worth taking care of this special case. But yes, if
>>> we really want to, extending the condition to also consider
>>> efi_l4_pgtable would seem the right thing to do.
>> I think being able to do a pagetable walk from an EFI fault would be
>> useful, even if only to aid debugging. In this case, a non-debug build
>> would successfully perform the walk.
>>
>> I have had a quick go, but it is rather hard to get the efi_l4_pgtable
>> symbol available to use in domain_page.c without some gross extern'ing.
>> It would be a nice fix if anyone has sufficient tuits.
> I'll take a look, but likely only next week.
>
> Jan
>
The root cause is that the efi additions appear to be strictly linked in
on the side, rather than being recompiled.
As a result, you can't reference efi_l4_pgtable in non-efi code without
breaking the non-efi build, and there is no CONFIG_EFI or equivalent as
domain_page.c isn't recompiled.
~Andrew
next prev parent reply other threads:[~2014-10-22 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 21:06 EFI Xen unstable crashes on Dell E6410 when calling efi_get_time Marcos E. Matsunaga
2014-10-22 0:29 ` Marcos E. Matsunaga
2014-10-22 9:45 ` Andrew Cooper
2014-10-22 10:22 ` Jan Beulich
2014-10-22 11:01 ` Andrew Cooper
2014-10-22 14:15 ` Jan Beulich
2014-10-22 14:22 ` Andrew Cooper [this message]
2014-10-23 14:03 ` Jan Beulich
2014-10-24 2:37 ` Marcos E. Matsunaga
2014-10-24 9:15 ` Jan Beulich
2014-10-27 21:07 ` Marcos E. Matsunaga
2014-10-28 7:34 ` Jan Beulich
2014-10-22 13:12 ` Konrad Rzeszutek Wilk
2014-10-22 14:19 ` Jan Beulich
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=5447BD90.4010908@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=Marcos.Matsunaga@oracle.com \
--cc=xen-devel@lists.xenproject.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 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.