Skip to content

Latest commit

 

History

History
122 lines (103 loc) · 5.22 KB

BAT.md

File metadata and controls

122 lines (103 loc) · 5.22 KB

BOLT Address Translation (BAT)

Purpose

A regular profile collection for BOLT involves collecting samples from unoptimized binary. BOLT Address Translation allows collecting profile from BOLT-optimized binary and using it for optimizing the input (pre-BOLT) binary.

Overview

BOLT Address Translation is an extra section (.note.bolt_bat) inserted by BOLT into the output binary containing translation tables and split functions linkage information. This information enables mapping the profile back from optimized binary onto the original binary.

Usage

--enable-bat flag controls the generation of BAT section. Sampled profile needs to be passed along with the optimized binary containing BAT section to perf2bolt which reads BAT section and produces profile for the original binary.

Internals

Section contents

The section is organized as follows:

  • Hot functions table
    • Address translation tables
  • Cold functions table

Construction and parsing

BAT section is created from BoltAddressTranslation class which captures address translation information provided by BOLT linker. It is then encoded as a note section in the output binary.

During profile conversion when BAT-enabled binary is passed to perf2bolt, BoltAddressTranslation class is populated from BAT section. The class is then queried by DataAggregator during sample processing to reconstruct addresses/ offsets in the input binary.

Encoding format

The encoding is specified in BoltAddressTranslation.h and BoltAddressTranslation.cpp.

Layout

The general layout is as follows:

Hot functions table
Cold functions table

Functions table:
|------------------|
|  Function entry  |
|                  |
|     Address      |
|   translation    |
|      table       |
|                  |
| Secondary entry  |
|      points      |
|------------------|

Functions table

Hot and cold functions tables share the encoding except differences marked below. Header:

Entry Encoding Description
NumFuncs ULEB128 Number of functions in the functions table

The header is followed by Functions table with NumFuncs entries. Output binary addresses are delta encoded, meaning that only the difference with the last previous output address is stored. Addresses implicitly start at zero. Output addresses are continuous through function start addresses and function internal offsets, and between hot and cold fragments, to better spread deltas and save space.

Hot indices are delta encoded, implicitly starting at zero.

Entry Encoding Description Hot/Cold
Address Continuous, Delta, ULEB128 Function address in the output binary Both
HotIndex Delta, ULEB128 Index of corresponding hot function in hot functions table Cold
FuncHash 8b Function hash for input function Hot
NumBlocks ULEB128 Number of basic blocks in the original function Hot
NumSecEntryPoints ULEB128 Number of secondary entry points in the original function Hot
ColdInputSkew ULEB128 Skew to apply to all input offsets Cold
NumEntries ULEB128 Number of address translation entries for a function Both
EqualElems ULEB128 Number of equal offsets in the beginning of a function Both
BranchEntries Bitmask, alignTo(EqualElems, 8) bits If EqualElems is non-zero, bitmask denoting entries with BRANCHENTRY bit Both

Function header is followed by Address Translation Table with NumEntries total entries, and Secondary Entry Points table with NumSecEntryPoints entries (hot functions only).

Address translation table

Delta encoding means that only the difference with the previous corresponding entry is encoded. Input offsets implicitly start at zero.

Entry Encoding Description Branch/BB
OutputOffset Continuous, Delta, ULEB128 Function offset in output binary Both
InputOffset Optional, Delta, SLEB128 Function offset in input binary with BRANCHENTRY LSB bit Both
BBHash Optional, 8b Basic block hash in input binary BB
BBIdx Optional, Delta, ULEB128 Basic block index in input binary BB

The table omits the first EqualElems input offsets where the input offset equals output offset.

BRANCHENTRY bit denotes whether a given offset pair is a control flow source (branch or call instruction). If not set, it signifies a control flow target (basic block offset).

InputAddr is omitted for equal offsets in input and output function. In this case, BRANCHENTRY bits are encoded separately in a BranchEntries bitvector.

Deleted basic blocks are emitted as having OutputOffset equal to the size of the function. They don't affect address translation and only participate in input basic block mapping.

Secondary Entry Points table

The table is emitted for hot fragments only. It contains NumSecEntryPoints offsets denoting secondary entry points, delta encoded, implicitly starting at zero.

Entry Encoding Description
SecEntryPoint Delta, ULEB128 Secondary entry point offset