From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: akataria@vmware.com, Thomas Gleixner <tglx@linutronix.de>,
the arch/x86 maintainers <x86@kernel.org>,
Daniel Hecht <dhecht@vmware.com>,
LKML <linux-kernel@vger.kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 05/05] x86: Rename paravirtualized TSC functions
Date: Thu, 10 Jul 2008 10:12:06 +0200 [thread overview]
Message-ID: <20080710081206.GA4819@elte.hu> (raw)
In-Reply-To: <86802c440807100104s1e1f1cdeg421be2dbeffdcb75@mail.gmail.com>
* Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> first round bisect all works..
>
> it seems make oldconfig change setting between different setting...
yeah. The thing i do is this: i create a .config.bisect and at every
bisection step i copy it into .config and do a 'make oldconfig'.
this means that options are picked up again, even if a 'dive back into
the past' causes a bisection point to lose a config setting.
>
> diff .config config.full.good
> 4c4
> < # Thu Jul 10 00:52:52 2008
> ---
> > # Thu Jul 10 00:40:03 2008
> 295,296c295
> < CONFIG_CC_STACKPROTECTOR_ALL=y
> < CONFIG_CC_STACKPROTECTOR=y
> ---
> > # CONFIG_CC_STACKPROTECTOR is not set
>
> it seems some recent change doesn't like stackprotector.
then my guess would be on:
89d7bb5: x86_64: add workaround for no %gs-based percpu
you might want to try your luck and revert that one alone from latest
tip/master.
Ingo
next prev parent reply other threads:[~2008-07-10 8:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 18:43 [PATCH 05/05] x86: Rename paravirtualized TSC functions Alok Kataria
2008-07-09 6:13 ` Ingo Molnar
2008-07-09 7:20 ` Yinghai Lu
2008-07-09 17:30 ` Alok Kataria
2008-07-09 17:38 ` Yinghai Lu
2008-07-10 7:22 ` Ingo Molnar
2008-07-10 7:34 ` Yinghai Lu
2008-07-10 7:50 ` Ingo Molnar
2008-07-10 8:04 ` Yinghai Lu
2008-07-10 8:11 ` Yinghai Lu
2008-07-10 10:22 ` Yinghai Lu
2008-07-10 8:12 ` Ingo Molnar [this message]
2008-07-10 18:59 ` Jeremy Fitzhardinge
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=20080710081206.GA4819@elte.hu \
--to=mingo@elte.hu \
--cc=akataria@vmware.com \
--cc=dhecht@vmware.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yhlu.kernel@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