linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 205303] Compilation for PPC64 fails on warning in watchdog.o
Date: Fri, 25 Oct 2019 08:04:01 +0000	[thread overview]
Message-ID: <bug-205303-206035-HbaFFSGX1n@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205303-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205303

A. Wilcox (awilfox@adelielinux.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |awilfox@adelielinux.org

--- Comment #2 from A. Wilcox (awilfox@adelielinux.org) ---
This is because CONFIG_HARDLOCK_DETECTOR is on and CONFIG_NMI_IPI is off.

CONFIG_HARDLOCK_DETECTOR pulls in CONFIG_PPC_WATCHDOG, which unconditionally
uses smp_send_nmi_ipi (and I believe requires such to work properly). 
CONFIG_PPC_WATCHDOG doesn't depend on CONFIG_NMI_IPI which it probably should. 
And then CONFIG_HARDLOCK_DETECTOR_ARCH should probably depend on CONFIG_NMI_IPI
or CONFIG_PPC_WATCHDOG.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2019-10-25  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24  8:23 [Bug 205303] New: Compilation for PPC64 fails on warning in watchdog.o bugzilla-daemon
2019-10-24  8:33 ` [Bug 205303] " bugzilla-daemon
2019-10-25  8:04 ` bugzilla-daemon [this message]
2021-07-23 10:21 ` bugzilla-daemon

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=bug-205303-206035-HbaFFSGX1n@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.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).