DatabaseCampaign: abstract campain for interaction with MySQL Database

The DatabaseCampaign interacts with the MySQL tables that are created
by the import-trace and prune-trace tools. It does offer all
unfinished experiment pilots from the database to the
fail-clients. Those clients send back a (by the experiment) defined
protobuf message as a result. The custom protobuf message does have to
need the form:

   import "DatabaseCampaignMessage.proto";

   message ExperimentMsg {
       required DatabaseCampaignMessage fsppilot = 1;

       repeated group Result = 2 {
          // custom fields
          required int32 bitoffset = 1;
          optional int32 result = 2;
       }
   }

The DatabaseCampaignMessage is the pilot identifier from the
database. For each of the repeated result entries a row in a table is
allocated. The structure of this table is constructed (by protobuf
reflection) from the description of the message. Each field in the
Result group becomes a column in the result table. For the given
example it would be:

    CREATE TABLE result_ExperimentMessage(
           pilot_id INT,
           bitoffset INT NOT NULL,
           result INT,
           PRIMARY_KEY(pilot_id)
    )

Change-Id: I28fb5488e739d4098b823b42426c5760331027f8
This commit is contained in:
Christian Dietrich
2013-03-25 16:04:05 +01:00
parent 59e5fd3169
commit f18cddc63c
25 changed files with 1161 additions and 119 deletions

View File

@ -5,8 +5,10 @@ set(SRCS
)
## Setup desired protobuf descriptions HERE ##
set(MY_PROTOS
set(PROTOS
FailControlMessage.proto
DatabaseCampaignMessage.proto
TracePlugin.proto
)
#### PROTOBUFS ####
@ -14,7 +16,7 @@ find_package(Protobuf REQUIRED)
include_directories(${PROTOBUF_INCLUDE_DIRS})
include_directories(${CMAKE_CURRENT_BINARY_DIR})
PROTOBUF_GENERATE_CPP(PROTO_SRCS PROTO_HDRS ${MY_PROTOS})
PROTOBUF_GENERATE_CPP(PROTO_SRCS PROTO_HDRS ${PROTOS})
add_library(fail-comm ${SRCS} ${PROTO_SRCS} ${PROTO_HDRS})
target_link_libraries(fail-comm ${PROTOBUF_LIBRARY})

View File

@ -0,0 +1,13 @@
import "google/protobuf/descriptor.proto";
extend google.protobuf.FieldOptions {
optional bool sql_primary_key = 32382 [ default = false];
optional bool sql_ignore = 32383 [ default = false];
}
message DatabaseCampaignMessage {
required int32 pilot_id = 1 [(sql_primary_key) = true];
required int32 variant_id = 2 [(sql_ignore) = true];
required int32 fspmethod_id = 3 [(sql_ignore) = true];
required int32 instr2 = 4 [(sql_ignore) = true];
required int32 data_address = 5 [(sql_ignore) = true];
}

View File

@ -24,6 +24,7 @@ public:
ExperimentData(google::protobuf::Message* m) : msg(m) , m_workloadID(0) { }
google::protobuf::Message& getMessage() { return *msg; }
void setMessage(google::protobuf::Message *msg) { this->msg = msg; }
uint32_t getWorkloadID() const { return m_workloadID; };
void setWorkloadID(uint32_t id) { m_workloadID = id; }
/**

View File

@ -0,0 +1,30 @@
message Trace_Event_Extended {
// data value read/written
optional uint64 data = 5;
// register contents
repeated group Registers = 6 {
// register ID
required uint32 id = 1;
// register value
optional uint64 value = 2;
// data register points to
optional uint32 value_deref = 3;
}
// selected stack content
repeated group Stack = 7 {
required uint32 value = 1;
}
}
message Trace_Event {
required uint64 ip = 1;
optional uint64 memaddr = 2;
optional uint32 width = 3;
enum AccessType {
READ = 1;
WRITE = 2;
}
optional AccessType accesstype = 4;
optional Trace_Event_Extended trace_ext = 5;
}