All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Don Slutz <dslutz@verizon.com>, xen-devel@lists.xen.org
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 1/1] x86: Set regs->entry_vector for early_page_fault
Date: Mon, 13 Apr 2015 17:09:05 +0100	[thread overview]
Message-ID: <552BEA21.7030301@citrix.com> (raw)
In-Reply-To: <1428941077-18458-1-git-send-email-dslutz@verizon.com>

On 13/04/15 17:04, Don Slutz wrote:
> This changes:
>
> (XEN) Early fatal page fault at e008:ffff82d080164252 (cr2=0000000000000000, ec=0000)
> (XEN) ----[ Xen-4.6-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff82d080164252>] arch_domain_create+0x3e/0x4ef
> ...
> (XEN) Xen call trace:
> (XEN)    [<ffff82d080164252>] arch_domain_create+0x3e/0x4ef
> (XEN)    [<ffff82d080105262>] domain_create+0x384/0x556
> (XEN)    [<ffff82d0802a0de4>] scheduler_init+0x1c4/0x244
> (XEN)    [<ffff82d0802be359>] __start_xen+0x1d0e/0x22a1
> (XEN)    [<ffff82d080100067>] __high_start+0x53/0x58
> (XEN)
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL TRAP: vector = 0 (divide error)
> (XEN) [error_code=0000] , IN INTERRUPT CONTEXT
> (XEN) ****************************************
> ...
>
> to:
>
> (XEN) Early fatal page fault at e008:ffff82d080164252 (cr2=0000000000000000, ec=0000)
> (XEN) ----[ Xen-4.6-unstable  x86_64  debug=y  Not tainted ]----
> (XEN) CPU:    0
> (XEN) RIP:    e008:[<ffff82d080164252>] arch_domain_create+0x3e/0x4ef
> ...
> (XEN) Xen call trace:
> (XEN)    [<ffff82d080164252>] arch_domain_create+0x3e/0x4ef
> (XEN)    [<ffff82d080105262>] domain_create+0x384/0x556
> (XEN)    [<ffff82d0802a0de4>] scheduler_init+0x1c4/0x244
> (XEN)    [<ffff82d0802be359>] __start_xen+0x1d0e/0x22a1
> (XEN)    [<ffff82d080100067>] __high_start+0x53/0x58
> (XEN)
> (XEN) Faulting linear address: 0000000000000000
> (XEN) Pagetable walk from 0000000000000000:
> (XEN)  L4[0x000] = 000000083a1a6063 ffffffffffffffff
> (XEN)  L3[0x000] = 000000083a1a5063 ffffffffffffffff
> (XEN)  L2[0x000] = 000000083a1a4063 ffffffffffffffff
> (XEN)  L1[0x000] = 0000000000000000 ffffffffffffffff
> (XEN)
> (XEN) ****************************************
> (XEN) Panic on CPU 0:
> (XEN) FATAL TRAP: vector = 14 (page fault)
> (XEN) [error_code=0000] , IN INTERRUPT CONTEXT
> (XEN) ****************************************
> ...
>
> Signed-off-by: Don Slutz <dslutz@verizon.com>

Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

> ---
>  xen/arch/x86/x86_64/entry.S | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/xen/arch/x86/x86_64/entry.S b/xen/arch/x86/x86_64/entry.S
> index 2d25d57..7e63e64 100644
> --- a/xen/arch/x86/x86_64/entry.S
> +++ b/xen/arch/x86/x86_64/entry.S
> @@ -626,6 +626,7 @@ ENTRY(double_fault)
>  
>          .pushsection .init.text, "ax", @progbits
>  ENTRY(early_page_fault)
> +        movl  $TRAP_page_fault,4(%rsp)
>          SAVE_ALL
>          movq  %rsp,%rdi
>          call  do_early_page_fault

      reply	other threads:[~2015-04-13 16:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 16:04 [PATCH 1/1] x86: Set regs->entry_vector for early_page_fault Don Slutz
2015-04-13 16:09 ` 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=552BEA21.7030301@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=jbeulich@suse.com \
    --cc=keir@xen.org \
    --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 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.