430 likes | 602 Views
Predicate Abstraction for Software and Hardware Verification. Himanshu Jain Model checking seminar April 22, 2005. Introduction. Scalable software verification Properties Array bounds check, division by zero Pointer safety Assertion checking Lock and unlocking
E N D
Predicate Abstraction for Software and Hardware Verification Himanshu Jain Model checking seminar April 22, 2005
Introduction • Scalable software verification • Properties • Array bounds check, division by zero • Pointer safety • Assertion checking • Lock and unlocking • Focus on partial specifications
Predicate Abstraction • Extract a finite state model from an infinite state system • Used to prove assertions or safety properties • Successfully applied for verification of C programs • SLAM (used in windows device driver verification) • MAGIC, BLAST, F-Soft
Example for Predicate Abstraction void main(){ bool p1, p2; p1=TRUE; p2=TRUE; while(p2) { p1=p1?FALSE:nondet(); p2=!p2; } } intmain() { int i; i=0; while(even(i)) i++; } + = p1 i=0 p2 even(i) C program Predicates Boolean program [Graf, Saidi ’97] [Ball, Rajamani ’01]
Computing Predicate Abstraction • How to get predicates for checking a given property? • How do we compute the abstraction? • Predicate Abstraction is an over-approximation • How to refine coarse abstractions
Initial Abstraction Verification No erroror bug found CProgram ModelChecker Abstract model Property holds Refinement Simulator Simulation sucessful Abstraction refinement Bug found Spurious counterexample Counterexample Guided Abstraction Refinement loop
Abstraction 1: x = ctr; 2: y = ctr + 1; 3: if (x = i-1){ 4: if (y != i){ ERROR: } } 1: skip; 2: skip; 3: if (*){ 4: if (*){ ERROR: } } Abstract C program No predicates available currently
Checking the abstract model Is ERROR reachable? 1: skip; 2: skip; 3: if (*){ 4: if (*){ ERROR: } } yes Abstract model has a path leading to error state
Simulation Does this correspond to a real bug? 1: x = ctr; 2: y = ctr + 1; 3: assume(x == i-1) 4: assume (y != i) 1: skip; 2: skip; 3: if (*){ 4: if (*){ ERROR: } } Check using a SAT solver Concrete trace Not possible
Refinement 1: x = ctr; 2: y = ctr + 1; 3: assume(x == i-1) 4: assume (y != i) 1: skip; 2: skip; 3: if (*){ 4: if (*){ ERROR: } } Initial abstraction Spurious Counterexample
Refinement 1: x = ctr; 2: y = ctr + 1; 3: assume(x == i-1) 4: assume (y != i) 1: skip; 2: skip; 3: if (*){ 4: if (b0){ ERROR: } } boolean b0 : y != i
Refinement 1: x = ctr; 2: y = ctr + 1; 3: assume(x == i-1) 4: assume (y != i) 1: skip; 2: skip; 3: if (b1){ 4: if (b0){ ERROR: } } boolean b0 : y != i boolean b1 : x== i-1
Refinement Weakest precondition of y != i boolean b2 : ctr + 1 ! = i 1: x = ctr; 2: y = ctr + 1; 3: assume(x == i-1) 4: assume (y != i) 1: skip; 2: b0 = b2; 3: if (b1){ 4: if (b0){ ERROR: } } boolean b0 : y != i boolean b1 : x== i-1
Refinement boolean b2 : ctr + 1 ! = i boolean b3: ctr == i -1 1: x = ctr; 2: y = ctr + 1; 3: assume(x == i-1) 4: assume (y != i) 1: b1 = b3; 2: b0 = b2; 3: if (b1){ 4: if (b0){ ERROR: } } boolean b0 : y != i boolean b1 : x== i-1
Refinement boolean b2 : ctr + 1 ! = i boolean b3: ctr == i -1 What about initial values of b2 and b3? 1: b1 = b3; 2: b0 = b2; 3: if (b1){ 4: if (b0){ ERROR: } } b2 and b3 are mutually exclusive. b2 =1, b3 = 0 b2 =0 , b3 = 1 So system is safe! boolean b0 : y != i boolean b1 : x== i-1
Tools for Predicate Abstraction of C • SLAM at Microsoft • Used for verifying correct sequencing of function calls in windows device drivers • MAGIC at CMU • Allows verification of concurrent C programs • Found bugs in MicroC OS • BLAST at Berkeley • Lazy abstraction, interpolation • SATABS at CMU • Computes predicate abstraction using SAT • Can handle pointer arithmetic, bit-vectors • F-Soft at NEC Labs • Localization, register sharing
Applications of Predicate Abstraction in Hardware Verification
System on chip design • Increase in complexity Number of components Level System Level 10E0 Behavioral/RTL Structural 10E3 Abstraction 10E5 Gate level (netlists) 10E7 …………
Introduction • Emergence of system design languages • HardwareC, SpecC, Handel-C, and SystemC • Based on C / C++ • Allows joint modeling of both hardware and software components of a system • Support for bit vectors, concurrency, synchronization, exception handling, timing
Verification support • Most model-checkers used in hardware industry work at netlist level • Higher abstraction levels offered by languages like SpecC or RTL Verilog are not yet supported • Languages like SpecC are more closer to concurrent software • Verification tools must reason about: • Programming languages constructs • Concurrency • Pointers, Objects • Bit vector operations like concatenation, extraction
Why predicate abstraction • Many properties depend on relationship between registers, and not the values stored in them • Predicate Abstraction • Keeps tracks of certain predicates on data • Successfully used in software verification • Can handle larger designs
Initial Abstraction Verification No erroror bug found VerilogProgram ModelChecker Abstract model Property holds Refinement Simulator Simulation sucessful Abstraction refinement Bug found Spurious counterexample Abstraction-Refinement loop
An example module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Property: AG (x = 100 or x = 200) Verilog program
Abstraction-Refinement loop Initial Abstraction Verification No erroror bug found VerilogProgram ModelChecker Abstract model Property holds Refinement Simulator Simulation sucessful Abstraction refinement Bug found Spurious counterexample
Predicate Abstraction module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Property: AG (x = 100 or x = 200) Initial set of predicates: {x = 100, x = 200} Word level predicates Verilog program
Computing abstract transitions Computing Most Precise Abstraction Next state Current state Transition Relation + + <x = 100, x = 200> <x’ = 100, x’ = 200> x’ = y y’ = x Equation passed to the SAT solver
Obtain transitions Computing abstract transitions 10 00 01 … and so on … 11
10 00 01 11 Abstract Model module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Property: AG (x = 100 or x = 200) Initial set of predicates: {x = 100, x = 200} Failure state Initial state Verilog program
Abstraction-Refinement loop Initial Abstraction Verification No erroror bug found VerilogProgram ModelChecker Abstract model Property holds Refinement Simulator Simulation sucessful Abstraction refinement Bug found Spurious counterexample
Model checking module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Abstract Model Initial state Failure state 10 00 01 11 Verilog program
Model checking module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Abstract Model Counterexample Initial state Failure state 10 00 01 11 Verilog program
Abstraction-Refinement loop Initial Abstraction Verification No erroror bug found VerilogProgram ModelChecker Abstract model Property holds Refinement Simulator Simulation sucessful Abstraction refinement Bug found Spurious counterexample
Simulation equation Simulation of the counterexample • Counterexample in the abstract model • <1 , 0> <0 , 0> (length = 1) • Each state is a valuation of h x = 100, x=200 i Initial values of the registers predicate values in the first state of the counterexample Transition relation predicate values in the second state of the counterexample equation is unsatisfiable So counterexample is spurious
Abstraction-Refinement loop Initial Abstraction Verification No erroror bug found VerilogProgram ModelChecker Abstract model Property holds Refinement Simulator Simulation sucessful Abstraction refinement Bug found Spurious counterexample
Refinement • Let length of spurious counterexample be k • Take weakest pre-condition of propertyfor k steps with respect to transition functions • Pick atomic predicates from weakest precondition
spurious counterexample Transition functions Property length =1 x’ = y y’ = x + AG (x = 100 Ç x = 200) + (y = 100 Ç y = 200) weakest precondition x’ = y y’ = x Holds after one step (x’ = 100 Ç x’ = 200) Refinement New predicates y = 100, y = 200
New abstraction Initial state 1001 0110 Abstract again module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Property: AG (x = 100 or x = 200) Updated set of predicates: {x = 100, x = 200, y=100, y=200} Model check Verilog program
New abstraction Initial state 1001 0110 Property holds! Model checking module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Property: AG (x = 100 or x = 200) Updated set of predicates: {x = 100, x = 200, y=100, y=200} Verilog program
Result module main (clk) input clk; reg [10:0] x, y; initial x= 100, y= 200; always @ (posedge clk) begin x <= y; y <= x; end endmodule Property: AG (x = 100 or x = 200) Property holds! Verilog program
Experimental results (VIS benchmarks) * Using lazy abstraction All use predicate partitioning
Tools • VCEGAR (Verilog Counterexample Guided Abstraction Refinement) at CMU • www.cs.cmu.edu/~modelcheck/vcegar