[Fault-injection-developer] RE: [Fault_injection] FW: About FAQ of FITH

[Zhuang, L. <lou...@in...>]

1. Why using command "ficl -v", the only info be printed is "verbose"?
we do not give the verbose information now, the verbose information =
will
come just after...
[lyzhuang] verbose is just a trending. It means FITH trends to output =
more
verbose information only if it has. But still now, it hasn't. ?
2. What does the number storage in directory =
"/proc/fith_dm/globalcounter"
mean?
[lyzhuang] it is a message counter.
3. Why a "wp" with a byte IO access may catch a word or double word =
access?
We will intercept all access in the address region. So it is =
uninterested in
access length.
[lyzhuang] FITH will intercept all access aligned with the address. But =
FITH
only corrupts 'len' bytes of data at most.
4. When insert a faultset, does it useful or I need enable it?
As long as the faultset is validated, when insert the faultset, the =
state of
faultset is enabled.
[lyzhuang] FITH will enable the faultset just after the faultset is =
inserted
successfully.
5. When some critical issue happened that terminate the "ABAT", the =
"ABAT"
cannot use again, it will always print an error information:" There is
another test script that is running!\n", how can it be used again?
Remove the hidden file "/tmp/.fithlock.*, it can be used again.
[lyzhuang] ABAT doesn't design for running parallel.  So if you run a =
script
when another script is running, error happens.=20
6.When set the two trigger with same "id", there is no warning =
information.
Is there any issue?
id is not used and not checked at this stage. So this unification check =
will
be done in future.
[lyzhuang] id is not be used. It may never be used. So... don't care =
about
it.
7. When do a mmio_readb operation, why the length information in =
ringbuffer
is still 4?
It is a bug of "gcc 2.96". Redhat released an unofficial GCC named =
"2.96".
It is a root of bugs. The last official GCC in 2.xx series is 2.95.3. =
You
should use this version or else ignore this bug.

8. How can I use parameter "bitmask" in fsml file to define a faulset?
We can use it as: final data=3D(data & ~bitmask), and check if final =
data is
between min and max.

9. Why the IO write operation is corrupted while only insert a io read
operation?
Just because dummy driver will alway do read and write operation no =
matter
we call read or write command.

10. What is the max number of faultset, trigger per faultset, op per =
trigger
is validate?
max number of faultset: 16
max number of trigger:  16
max number of op	9

11. How can we set a linear address in faultset?
We use physical address instead of linear address, FITH prefer user to =
set
physical address.[lyzhuang]  Linear address support may be cancelled in
future release.

12. Why must we remove faultset before remove dummy?
[lyzhuang] FITH place some hooks in driver and system for watching =
accesses.
If you remove watched driver before removing faultset, these hooks =
cannot be
clear elegantly. Some unpredicted error may happen.=20


  --Louis

-----Original Message-----
From: Wang, Chenguang [mailto:che...@in...]
Sent: Wednesday, August 14, 2002 8:45 AM
To: SourceforgeFI mail list (E-mail); CarrierlinuxFI mail list (E-mail)
Subject: [Fault_injection] FW: About FAQ of FITH


>  -----Original Message-----
> From:         Gao, Kevin=20
> Sent: 2002=C4=EA8=D4=C213=C8=D5 14:17
> To:   Wang, Frank; Wang, Chenguang; Zhuang, Louis
> Cc:   Duan, Jian Gang; Li, Jack; Pan, Deng; Wang, Chenguang; Wang, =
Frank;
> Yu, Jerry; Zhuang, Louis
> Subject:      About FAQ of FITH
>
> There are the samples I collected. I think some answer I give is not
> clearly, and some I cannot give a good answer. Louis can you help me?
> thanks!!
> Any FAQ samples or comment?
> thank you !^_^
>
> 1. Why using command "ficl =3Dv", the only info be printed is =
"verbose"?
> we do not give the verbose information now, the verbose information =
will
> come just after...
>
> 2. What does the number storaged in directory
> "/proc/fith_dm/globalcounter"  mean?
>
> 3. Why a "wp" with a byte IO access may catch a word or double word
> access?
> We will intercept all access in the address region. So it is =
uninterested
> in access length.
>
> 4. When insert a faultset, does it useful or I need enable it?
> As long as the faultset is validated, when insert the faultset, the =
state
> of faultset is enabled.
>
> 5. When some critical issue happened that termate the "ABAT", the
> "ABAT" cannot use again, it will always print a error information:"
> There is another test script that is running!\n", how can it be used
> again?
> Remove the hidden file "/tmp/.fithlock.*, it can be used again.
>
> 6.When set the two trigger with same "id", there is no warning
> information. Is there any issue?
> id is not used and not checked at this stage. So this unification =
check
> will be done in future.
>
> 7. When do a mmio_readb operation, why the length infomation in =
ringbuffer
> is still 4?
> It is a bug of "gcc 2.96". Redhat released an unoffical GCC named =
"2.96".
> It is a root of bugs. The last offical GCC in 2.xx series is 2.95.3. =
You
> should use this version or else ignore this bug.
>
> 8. How can I use parameter "bitmask" in fsml file to define a =
faulset?
> We can use it as: finaldata=3D(data & ~bitmask), and check if =
finaldata is
> between min and max.
>
> 9. Why the io write operation is corrupted while only insert a io =
read
> operation?
> Just because dummy driver will alway do read and write operation no =
matter
> we call read or write command.
>
> 10. What is the max number of faultset, trigger per faultset, op per
> trigger is validate?
> max faultset: 16
> max trigger:  16
> max op        9
>
> 11. How can we set a liner address in faultset?
> We use physical address instead of liner address, FITH prefer user to =
set
> physical address.
>
> 12. Why must we remove faultset before remove dummy?
>
>
>
>
>
> Yours Sincerely,
> Gao, Xiaohe (Kevin)
>
> Intel China Software Lab.
> Tel: 021-52574545 ext. 1271
> iNet: 8-752-1271
>
>
_______________________________________________
Fault_injection mailing list
Fau...@ca...
http://www.carrierlinux.org/mailman/listinfo/fault_injection