4c04857681
There could be multiple ways in the scenario configuration to specify that no INTx allocation is explicitly allocation to a prelaunched VM: * Do not have a `pt_intx` node at all. * Have a `pt_intx` node with no text. * Have a `pt_intx` node with a text that has nothing but whitespaces, tabs and newlines. The current implementation only supports the first way, and will cause build-time failures when a scenario configuration uses the latter two. The following changes are introduced by this patch to fix such errors. * The INTx static allocator queries the text() of `pt_intx` nodes directly to gracefully handle `pt_intx` nodes with no text. * The XSLT of pt_intx.c clears all kinds of white spaces from the text of `pt_intx` nodes before calculating the set of allocated INTx mappings. Tracked-On: #6287 Signed-off-by: Junjie Mao <junjie.mao@intel.com> |
||
---|---|---|
.. | ||
lib | ||
bdf.py | ||
cpu_affinity.py | ||
gpa.py | ||
hv_ram.py | ||
intx.py | ||
main.py | ||
pio.py |