mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luming Yu <luming.yu@gmail.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Christoph Hellwig <hch@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: [RFC PATCH] Add TRACE_IRQFLAGS_SUPPORT, LOCKDEP_SUPPORT then  enable ftrace for ia64
Date: Wed, 9 Dec 2009 16:52:36 +0800	[thread overview]
Message-ID: <3877989d0912090052v79fdce6aqb507639143b5d71e@mail.gmail.com> (raw)
In-Reply-To: <3877989d0912082245m3ee1ea14y3b3c8aca99e9f378@mail.gmail.com>

On Wed, Dec 9, 2009 at 2:45 PM, Luming Yu <luming.yu@gmail.com> wrote:
>>
>> But let me try more on other ia64 boxes that I can get access.
>>
>> Stay tuned.
>
> I might have reproduced the problem on a HP ia64 system
> with -32 kernel as the following info. But -31 kernel with
> lockdep code enabled just works. ....debugging...

ah, I seem to have found the change in -32 against -31 that causes the trouble.

Commenting out the change make -32 Lockdep kernel boot.

Tony, please let me know whether you can reproduce..

kernel/lockdep.c
static int save_trace(struct stack_trace *trace)
{
        trace->nr_entries = 0;
        trace->max_entries = MAX_STACK_TRACE_ENTRIES - nr_stack_trace_entries;
        trace->entries = stack_trace + nr_stack_trace_entries;

        trace->skip = 3;

        save_stack_trace(trace);
#if 0

        /*
         * Some daft arches put -1 at the end to indicate its a full trace.
         *
         * <rant> this is buggy anyway, since it takes a whole extra entry so a
         * complete trace that maxes out the entries provided will be reported
         * as incomplete, friggin useless </rant>
         */
        if (trace->entries[trace->nr_entries-1] == ULONG_MAX)
                trace->nr_entries--;
#endif

  reply	other threads:[~2009-12-09  8:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  3:18 Luming Yu
2009-08-28  6:22 ` Ingo Molnar
2009-09-02 23:27   ` Luck, Tony
2009-09-03  8:46     ` Peter Zijlstra
2009-09-03 16:02       ` Luck, Tony
2009-12-04  7:29   ` Luming Yu
2009-12-04 19:16     ` Luck, Tony
2009-12-05  3:19       ` Luming Yu
2009-12-07  5:56         ` Luming Yu
2009-12-07 21:35           ` Tony Luck
2009-12-08 12:25             ` Luming Yu
2009-12-09  6:45               ` Luming Yu
2009-12-09  8:52                 ` Luming Yu [this message]
2009-12-09 18:11                   ` Tony Luck
2009-12-09 18:22                     ` Peter Zijlstra

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=3877989d0912090052v79fdce6aqb507639143b5d71e@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=fenghua.yu@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shaohua.li@intel.com \
    --cc=tony.luck@gmail.com \
    /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®