From: Jan Kiszka <jan.kiszka@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai-core <xenomai@xenomai.org>
Subject: Re: [Xenomai-core] [PATCH] detect problematic kernel configs
Date: Sat, 15 Apr 2006 18:02:07 +0200 [thread overview]
Message-ID: <444118FF.7020509@domain.hid> (raw)
In-Reply-To: <17473.3055.737663.656203@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Gilles Chanteperdrix wrote:
> Jan Kiszka wrote:
> > Hi,
> >
> > this patch tries to reduce the traps newbies may tap by leaving (for us)
> > well-known problematic kernel switches on. And are there any futher I
> > forgot, e.g. on other archs?
> >
> > Jan
> > Index: ksrc/arch/i386/Kconfig
> > ===================================================================
> > --- ksrc/arch/i386/Kconfig (revision 924)
> > +++ ksrc/arch/i386/Kconfig (working copy)
> > @@ -194,3 +194,19 @@ depends on XENO_OPT_NUCLEUS
> > source "drivers/xenomai/Kconfig"
> >
> > endmenu
> > +
> > +if XENOMAI = y
> > +
> > +comment "WARNING: Potential latency killers detected!"
> > + depends on PM || ACPI || CPU_FREQ
> > +
> > +comment "Power Management (PM)"
> > + depends on PM
> > +
> > +comment "ACPI"
> > + depends on ACPI
>
> Only ACPI_PROCESSOR is a latency killer.
>
Good point. Are there also some more fine-grained switches under
CONFIG_PM? Never tried this in details, always picked the safe way.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
prev parent reply other threads:[~2006-04-15 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 18:38 [Xenomai-core] [PATCH] detect problematic kernel configs Jan Kiszka
2006-04-15 15:06 ` Gilles Chanteperdrix
2006-04-15 16:02 ` Jan Kiszka [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=444118FF.7020509@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.