the stability != preempt seems no longer true as the preempt
path gets more testing out there.
I'm running my notebook with full preemption since years now, without
any problems. I had to use the -ck patches, though, as the normal
preemption did not work well enough for me. I didn't check how
On Thu, 13 Dec 2007 02:24:15 +0100 maximilian attems wrote:
hello francesco,
nice to read you! :)
Hi Maximilian!
Thanks for your quick reply.
On Thu, Dec 13, 2007 at 12:10:04AM +0100, Francesco Poli wrote:
[...]
By reading the bug log, I seem to understand that this is due to
Package: linux-2.6
Followup-For: Bug #311185
If I understand the following output correctly, the current (testing) Linux
kernel does *not* have any preemption activated:
$ grep -i EMPT /boot/config-2.6.22-3-amd64
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
#
hello francesco,
nice to read you! :)
On Thu, Dec 13, 2007 at 12:10:04AM +0100, Francesco Poli wrote:
If I understand the following output correctly, the current (testing) Linux
kernel does *not* have any preemption activated:
$ grep -i EMPT /boot/config-2.6.22-3-amd64
4 matches
Mail list logo
