Skip to contentSkip to conversation

Why isn't there individual CONFIG in CONFIG_PREEMPT_RT_FULL?

DISCUSSION Hiraku Toyooka 2 participants 2 messages Oct 24, 2013 – Nov 22, 2013

lore
Share & tools
lore
#0 lore raw

Hello,

I recently started to look at PREEMPT_RT patches(3.10.14-rt9) and I have a question.

CONFIG_PREEMPT_RT_FULL consists of many patches. I think it doesn't represent specific feature but is general term of various features. Why don't those features have each CONFIG_* ?

Best regards,

Signature · 4 lines
Hiraku TOYOOKA
Linux Technology Center
Yokohama Research Laboratory
Hitachi Ltd.
#1 lore raw
Quoted 1 line · * Hiraku Toyooka | 2013-10-24 21:43:14 [+0900]:

Hello,

Hello

Quoted 3 lines

CONFIG_PREEMPT_RT_FULL consists of many patches. I think it doesn't represent specific feature but is general term of various features. Why don't those features have each CONFIG_* ?

Do you have something in particular in mind?
As long as it makes sense, there are CONFIG_* introduced. If a patch breaks locks for instance then we don't a special CONFIG item because this what we need and we don't keep both versions around (and the non-RT variant can work both ways).

Quoted 1 line

Best regards,

Sebastian