mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Don Zickus <dzickus@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	fweisbec@gmail.com, LKML <linux-kernel@vger.kernel.org>,
	akpm@linux-foundation.org, dannf@hp.com
Subject: Re: [PATCH] x86, nmi_watchdog:  Remove ARCH_HAS_NMI_WATCHDOG and rely on CONFIG_HARDLOCKUP_DETECTOR
Date: Wed, 22 Dec 2010 12:26:36 +0100	[thread overview]
Message-ID: <20101222112636.GH3127@elte.hu> (raw)
In-Reply-To: <20101220153716.GB19138@redhat.com>


* Don Zickus <dzickus@redhat.com> wrote:

> On Sat, Dec 18, 2010 at 04:33:26PM +0100, Ingo Molnar wrote:
> > 
> > * Don Zickus <dzickus@redhat.com> wrote:
> > 
> > > The x86 arch has shifted its use of the nmi_watchdog from a local implementation 
> > > to the global one provide by kernel/watchdog.c.  This shift has caused a whole 
> > > bunch of compile problems under different config options.  I attempt to simplify 
> > > things with the patch below.
> > 
> > ok, this patch is looking better - but even after applying it to -tip (and resolving 
> > the conflict) i get this link failure on 64-bit allyesconfig:
> 
> Sorry about the conflict.  I guess I stupidly based the patch ontop of the
> small hack patch I sent to you a couple of hours before I sent this patch.
> 
> > 
> > watchdog.c:(.text+0x7eacc): undefined reference to `hw_nmi_get_sample_period'
> 
> That said, I'm not sure how you resolved the conflict, but the define
> ARCH_HAS_NMI_WATCHDOG should not be in the arch/x86/kernel/apic/hw_nmi.c
> file.
> 
> Other than that, I am unable to reproduce the error you are seeing.
> Looking at the code, 'hw_nmi_get_sample_period' is defined in one file and
> called in one spot in another file.  Both cases that code is wrapped only
> with CONFIG_HARDLOCKUP_DETECTOR, so I at a loss on where it would fail.
> 
> Do you have a branch I can look at it, just to double check?

Not anymore - could you please send a patch that applies cleanly to -tip - that way 
we eliminate all misinterpretation.

Thanks,

	Ingo

      reply	other threads:[~2010-12-22 11:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-17 16:20 Don Zickus
2010-12-18 15:33 ` Ingo Molnar
2010-12-20 15:37   ` Don Zickus
2010-12-22 11:26     ` Ingo Molnar [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=20101222112636.GH3127@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=dannf@hp.com \
    --cc=dzickus@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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

all inboxes | Powered by JetHome®