use uint32 for addresses in protobuf msgs
This prevents integer overflows when using addresses > 2GiB, which are common for x86 operating systems with paging (Linux, Fiasco.OC) or some test cases on the PandaBoard. Note that this results in slightly different result table definitions when automatically translating an experiment's protobuf message in the DatabaseCampaign. This change affects all existing protobuf messages to prevent copy/paste propagation of this issue. Change-Id: I09ec4b9d45eddd67a7a24c8b101e8b2b258df5e2
This commit is contained in:
committed by
Horst Schirmeier
parent
84edd02b6f
commit
122eb8c9dc
@ -3,11 +3,11 @@ message OOStuBSProtoMsg {
|
||||
// (client executes 8 experiments, one for each bit at mem_addr)
|
||||
|
||||
// FI at #instructions from experiment start
|
||||
required int32 instr_offset = 1;
|
||||
required uint32 instr_offset = 1;
|
||||
// the exact IP value at this point in time (from golden run)
|
||||
optional int32 instr_address = 2; // for sanity checks
|
||||
optional uint32 instr_address = 2; // for sanity checks
|
||||
// address of the byte to inject bit-flips
|
||||
required int32 mem_addr = 3;
|
||||
required uint32 mem_addr = 3;
|
||||
|
||||
// ----------------------------------------------------
|
||||
|
||||
@ -15,11 +15,11 @@ message OOStuBSProtoMsg {
|
||||
|
||||
// IP where we did the injection: for debugging purposes, must be identical
|
||||
// to instr_address
|
||||
optional int32 injection_ip = 4;
|
||||
optional uint32 injection_ip = 4;
|
||||
|
||||
repeated group Result = 5 {
|
||||
// single experiment bit offset
|
||||
required int32 bit_offset = 1;
|
||||
required uint32 bit_offset = 1;
|
||||
|
||||
// result type:
|
||||
// FINISHED = planned number of instructions were executed
|
||||
|
||||
Reference in New Issue
Block a user