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

[Wang, C. <che...@in...>]

>  -----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
>=20
> 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 !^_^
>=20
> 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...
>=20
> 2. What does the number storaged in directory
> "/proc/fith_dm/globalcounter"  mean?
>=20
> 3. Why a =A1=B0wp=A1=B1 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.
>=20
> 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.
>=20
> 5. When some critical issue happened that termate the =
=A1=B0ABAT=A1=B1, the
> =A1=B0ABAT=A1=B1 cannot use again, it will always print a error =
information:=A1=B1
> There is another test script that is running!\n=A1=B1, how can it be =
used
> again?
> Remove the hidden file =A1=B0/tmp/.fithlock.*, it can be used again.
>=20
> 6.When set the two trigger with same =A1=B0id=A1=B1, 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.
>=20
> 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.
>=20
> 8. How can I use parameter =A1=B0bitmask=A1=B1 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.
>=20
> 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.
>=20
> 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
>=20
> 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.
>=20
> 12. Why must we remove faultset before remove dummy?
>=20
>=20
>=20
>=20
>=20
> Yours Sincerely,
> Gao, Xiaohe (Kevin)
>=20
> Intel China Software Lab.
> Tel: 021-52574545 ext. 1271
> iNet: 8-752-1271
>=20
>=20