All of
 help / color / mirror / Atom feed
From: Meng Xu <>
To: Andrew Cooper <>
Cc: Wei Liu <>,
	"" <>
Subject: Re: Question about Xen reboot on panic
Date: Thu, 12 Nov 2015 11:13:26 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Andrew,

I thought I might find where the system got stuck.

As you suggested, I add several printks inside machine_restart();
If the machine restart when Xen kernel crashes, I can see the following output:

        umount: /run/lock: not mounted

        umount: /run/shm: not mounted

         * Will now restart

        [  122.261583] Restarting system.

        (XEN) Domain 0 shutdown: rebooting machine.

        (XEN) machine_restart start running
(This is what I added at the first line of the machine_restart())

        (XEN) machine_restart start running

        (XEN) reboot_type=97

        (XEN) Resetting with ACPI MEMORY or I/O RESET_REG.

So when the machine reboots correctly at Xen kernel crash,  the
machine_restart will be called twice.

After looking into the code, I found the following code in the
machine_restart(), which is quite suspicious.

    if ( system_state >= SYS_STATE_smp_boot )



        /* Ensure we are the boot CPU. */

        if ( get_apic_id() != boot_cpu_physical_apicid )


            /* Send IPI to the boot CPU (logical cpu 0). */

            on_selected_cpus(cpumask_of(0), __machine_restart,

                             &delay_millisecs, 0);

            for ( ; ; )





This function basically try to send an IPI from the current CPU to
notify the boot CPU to run machine_restart() function and then the
current CPU goes to halt().

If the boot CPU missed the IPI, the machine_restart() will never be
called and the system hangs. Am I correct?

If I'm correct, how should I fix this? Should I just let the current
CPU keep sending the IPI to the boot CPU to run machine_restart()?
This seems too hacky to me, but I'm not quite sure why we have to use
the boot CPU to restart. If we can let any CPU to reset the CPU status
and reboot, we can avoid this.

or is it because the system_state is not correctly set? If we can
avoid getting into the if statement, we can also avoid this problem.

Do you have any suggestions?

Thank you very much for your help!



Meng Xu
PhD Student in Computer and Information Science
University of Pennsylvania

  reply	other threads:[~2015-11-12 16:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 22:49 Question about Xen reboot on panic Meng Xu
2015-11-11 22:54 ` Andrew Cooper
2015-11-11 23:21   ` Meng Xu
2015-11-11 23:34     ` Andrew Cooper
2015-11-12  2:10       ` Meng Xu
2015-11-12 12:52         ` Andrew Cooper
2015-11-12 12:57           ` Wei Liu
2015-11-12 13:16             ` Ian Campbell
2015-11-12 15:09               ` Meng Xu
2015-11-12 15:07           ` Meng Xu
2015-11-12 16:13             ` Meng Xu [this message]
2015-11-12 16:57               ` Meng Xu
2015-11-12 17:08                 ` Jan Beulich
2015-11-12 19:54                   ` Meng Xu
2015-11-13  7:39                     ` Jan Beulich
2015-11-19  3:58                       ` Meng Xu
2015-11-19  7:26                         ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.