All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH] x86: also allow disabling LAPIC NMI watchdog on newer CPUs
Date: Wed, 01 Aug 2012 16:22:48 +0100	[thread overview]
Message-ID: <CC3F0858.3A2BC%keir.xen@gmail.com> (raw)
In-Reply-To: <501938070200007800091E24@nat28.tlf.novell.com>

On 01/08/2012 13:07, "Jan Beulich" <JBeulich@suse.com> wrote:

> This complements c/s 9146:941897e98591, and also replaces a literal
> zero with a proper manifest constant.
> 
> Signed-off-by: Jan Beulich <jbeulich@suse.com>

Acked-by: Keir Fraser <keir@xen.org>

> --- a/xen/arch/x86/nmi.c
> +++ b/xen/arch/x86/nmi.c
> @@ -175,15 +175,9 @@ static void disable_lapic_nmi_watchdog(v
>      case X86_VENDOR_INTEL:
>          switch (boot_cpu_data.x86) {
>          case 6:
> -            if (boot_cpu_data.x86_model > 0xd)
> -                break;
> -
>              wrmsr(MSR_P6_EVNTSEL0, 0, 0);
>              break;
>          case 15:
> -            if (boot_cpu_data.x86_model > 0x4)
> -                break;
> -
>              wrmsr(MSR_P4_IQ_CCCR0, 0, 0);
>              wrmsr(MSR_P4_CRU_ESCR0, 0, 0);
>              break;
> @@ -192,7 +186,7 @@ static void disable_lapic_nmi_watchdog(v
>      }
>      nmi_active = -1;
>      /* tell do_nmi() and others that we're not active any more */
> -    nmi_watchdog = 0;
> +    nmi_watchdog = NMI_NONE;
>  }
>  
>  static void enable_lapic_nmi_watchdog(void)
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

      reply	other threads:[~2012-08-01 15:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 12:07 [PATCH] x86: also allow disabling LAPIC NMI watchdog on newer CPUs Jan Beulich
2012-08-01 15:22 ` Keir Fraser [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=CC3F0858.3A2BC%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=JBeulich@suse.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 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.