All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, David Vrabel <david.vrabel@citrix.com>
Cc: xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>
Subject: Re: [PATCHv1] x86: only check for one watchdog NMI
Date: Tue, 23 Jun 2015 10:34:44 +0100	[thread overview]
Message-ID: <55892834.9030203@citrix.com> (raw)
In-Reply-To: <55893E750200007800088004@mail.emea.novell.com>

On 23/06/15 10:09, Jan Beulich wrote:
>>>> On 22.06.15 at 18:21, <david.vrabel@citrix.com> wrote:
>> Since the NMI handler can now recognize watchdog NMIs, make
>> check_nmi_watchdog() only check for at least one watchdog NMI.  This
>> prevents false negatives caused by other processors (which may be
>> being power managed by the BIOS) running at reduced clock frequencies.
> Doesn't this go a little too far, in that it allows through the case where
> an NMI works exactly once (a behavior not unheard of)? Lowering the
> count to e.g. 3 would seem acceptable, but not any further. Raising
> the wait time might then need to be the way to go if the (approximate)
> 1:3 ratio still isn't enough to cope with BIOS power managed CPUs.
>
> Btw., can an OS know of the power state CPUs come up in? I.e. can
> the wait time be adjusted dynamically? Or is this (perhaps intentionally)
> completely transparent to the OS?

With the mwait driver, probably, as it is specifically designed to
completely bypass any firmware settings which might be in place.

Anything else is dependent on how much information can be gleaned from
the ACPI tables, but most firmware deliberately has a "BIOS controlled"
mode which is designed to restrict what the OS is capable of doing.

~Andrew

  reply	other threads:[~2015-06-23  9:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 16:21 [PATCHv1] x86: only check for one watchdog NMI David Vrabel
2015-06-23  9:09 ` Jan Beulich
2015-06-23  9:34   ` Andrew Cooper [this message]
2015-06-23  9:51     ` 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=55892834.9030203@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=david.vrabel@citrix.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 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.