[Fault-injection-developer] RE: About delete the trigger, codesegment
Status: Alpha
Brought to you by:
rustyl
From: Wang, S. <sta...@in...> - 2003-01-06 06:09:30
|
I think that the faultset won't be eliminated :) We must make FITH be compatible with our earier release. Hence we must us the fsml to describe the faultset. And user needn't add and remove all triggers in turn. Though the faultset concept means nothing to FITH's kernel part(I suggest to implement it in FITH's command line tool). Cheers! Stan > -----Original Message----- > From: Gao, Kevin > Sent: 2003-01-06 13:45 > To: 'fau...@li...'; Zhuang, Louis; > Wang, Frank; Wang, Stanley > Subject: About delete the trigger, codesegment > > > If we want to stop our corruption of driver, we always remove > of disable the triggers. > In past time, There are some triggers in one faultset. When > user wants to do a > fault injection for one driver, he will put all the related > trigger into one faultset. So all the > trigger of the fault injection can be inserted, removed together. > > Now there is no "faultset" concept, we only use trigger to > inject fault. For one fault injection > operation. User should inject/remove the related trigger by > turn. If there is any issue/problem? > For example, when we remove one trigger, before remove other > related trigger, if the remained > trigger will cause some kernel, address or other potential issue? > > For complex fault, One FI operation must be have many > triggers. So in order to make user > control there FI operation easily and clearly, I think > "faultset" concept is still useful > > Regards > > Kevin > |