parse_test_vector(9)

💅 parse_test_vector(9) 💅

okay so this is parse_test_vector(9) from the Kernel API Manual — manual name folded in near the top like a lil name tag, because we're cute like that. This page is about parsing a single test vector string, and the energy is very "I know her." I'm obsessed, honestly. ✨

🌸 NAME 🌸

parse_test_vector — parse a single test vector string. It's giving short, sweet, iconic.

✨ SYNOPSIS ✨

The exact signature, no edits, no cap:

int parse_test_vector (const char *entry , u64 *dpa , int *pos , u8
*r_eiw , u16 *r_eig , u8 *hb_ways , int *math , u64 *expect_hpa );

🎀 ARGUMENTS 🎀

The ARGUMENTS section is serving us -- undescribed -- eight times in a row, which is a choice 💀. But I'm keeping every single one, exactly:

• entry — -- undescribed --
• dpa — -- undescribed --
• pos — -- undescribed --
• r_eiw — -- undescribed --
• r_eig — -- undescribed --
• hb_ways — -- undescribed --
• math — -- undescribed --
• expect_hpa — -- undescribed --

not me reading that and being like "bestie where is the info" 😭 — but don't worry, DESCRIPTION has the actual tea below, iykyk.

💖 DESCRIPTION 💖

Here's what DESCRIPTION spills, with the labels exactly as written:

• entry: test vector string to parse
• dpa: device physical address
• pos: expected position in region interleave
• r_eiw: region encoded interleave ways
• r_eig: region encoded interleave granularity
• hb_ways: host bridge interleave ways
• math: interleave arithmetic (MODULO_MATH or XOR_MATH)
• expect_spa: expected system physical address

not me noticing that DESCRIPTION says expect_spa while ARGUMENTS says expect_hpa — I'm just the messenger, bestie 💀.

🌈 RETURN 🌈

0 on success, negative error code on failure. That's the whole return vibe, periodt.

🦋 SEE ALSO 🦋

Kernel file ./tools/testing/cxl/test/cxl_translate.c is right there, plus to_hpa(9), to_dpa(9), to_pos(9), and run_translation_test(9). Go off, icons. 👑

---

mwah 💋 — source/version: ./tools/testing/cxl/test · date: October 2026.