linux-kernel - Re: [ANNOUNCE] 3.0-rt7 - Error with low latency desktop config

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110811102138.GC11398@pengutronix.de>
Date:	Thu, 11 Aug 2011 12:21:39 +0200
From:	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
To:	Tim Sander <tim.sander@....com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [ANNOUNCE] 3.0-rt7 - Error with low latency desktop config

On Wed, Aug 10, 2011 at 06:33:54PM +0200, Tim Sander wrote:
> Hi Uwe
> 
> I triple checked.
> > I think targetinstall should ask about the changed config items.
> It only asks one way, when going from an upatched kernel to an patched one.
> Since i was coming from an preempt rt kernel to an unpatched one no questions
> where asked (probably since all settings where still in place as i wasn't 
> using the preempt rt feature with the preempt rt patched kernel source
> aka "Low latency desktop")
I guess that when the kernel build updates .config your
${PROJECT_DIR}/config/${PLATFORMNAME}/kernelconfig isn't adapted
accordingly. So yes, it might be out of sync. So better provide
${PROJECT_DIR}/${PLATFORMNAME}/build/linux-3.0/.config please.
 
> But i think the regression when going from 3.0-rt7 to 3.0.1-rt8 with 
> CONFIG_PREEMPT_RTB is more worthwhile to discuss. Which i detailed in the 
> other mail.
You didn't talk about CONFIG_PREEMPT_RTB before, did you? I just used it
as indicator that the .config you sent isn't for an -rt kernel.

Your machine is based on Phytec's pcm043? I could try to test on one of
those an unpatched -rt kernel, but I don't promise to come around to do it.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/