From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86: show page walk when create_bounce_frame() encounters a fault
Date: Mon, 15 Sep 2014 16:46:56 +0100 [thread overview]
Message-ID: <541709F0.1050000@citrix.com> (raw)
In-Reply-To: <54130A220200007800034830@mail.emea.novell.com>
[-- Attachment #1.1: Type: text/plain, Size: 2429 bytes --]
On 12/09/2014 13:58, Jan Beulich wrote:
> ... getting the native code in sync with the compat mode one.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> --- a/xen/arch/x86/x86_64/entry.S
> +++ b/xen/arch/x86/x86_64/entry.S
> @@ -442,19 +442,30 @@ UNLIKELY_START(z, create_bounce_frame_ba
> __UNLIKELY_END(create_bounce_frame_bad_bounce_ip)
> movq %rax,UREGS_rip+8(%rsp)
> ret
> - _ASM_EXTABLE(.Lft2, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft3, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft4, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft5, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft6, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft7, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft8, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft9, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft10, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft11, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft12, dom_crash_sync_extable)
> - _ASM_EXTABLE(.Lft13, dom_crash_sync_extable)
> -
> + _ASM_EXTABLE(.Lft2, domain_crash_page_fault_32)
> + _ASM_EXTABLE(.Lft3, domain_crash_page_fault_24)
> + _ASM_EXTABLE(.Lft4, domain_crash_page_fault_8)
> + _ASM_EXTABLE(.Lft5, domain_crash_page_fault_16)
> + _ASM_EXTABLE(.Lft6, domain_crash_page_fault)
> + _ASM_EXTABLE(.Lft7, domain_crash_page_fault)
> + _ASM_EXTABLE(.Lft8, domain_crash_page_fault_24)
> + _ASM_EXTABLE(.Lft9, domain_crash_page_fault_16)
> + _ASM_EXTABLE(.Lft10, domain_crash_page_fault_8)
> + _ASM_EXTABLE(.Lft11, domain_crash_page_fault)
> + _ASM_EXTABLE(.Lft12, domain_crash_page_fault_8)
> + _ASM_EXTABLE(.Lft13, domain_crash_page_fault)
> +
> +domain_crash_page_fault_32:
> + addq $8,%rsi
> +domain_crash_page_fault_24:
> + addq $8,%rsi
> +domain_crash_page_fault_16:
> + addq $8,%rsi
> +domain_crash_page_fault_8:
> + addq $8,%rsi
> +domain_crash_page_fault:
> + movq %rsi,%rdi
> + call show_page_walk
> ENTRY(dom_crash_sync_extable)
> # Get out of the guest-save area of the stack.
> GET_STACK_BASE(%rax)
>
>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 3255 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-09-15 15:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 12:58 [PATCH] x86: show page walk when create_bounce_frame() encounters a fault Jan Beulich
2014-09-15 15:46 ` Andrew Cooper [this message]
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=541709F0.1050000@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--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 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).