aboutsummaryrefslogtreecommitdiff
path: root/os-posix.c
diff options
context:
space:
mode:
authorDaniel Henrique Barboza <danielhb413@gmail.com>2022-01-18 12:56:31 +0100
committerCédric Le Goater <clg@kaod.org>2022-01-18 12:56:31 +0100
commit6f506c90c3e1814a4a7df5be8d08782c06226820 (patch)
tree77f1b82b39ed945e9b826e890517eab8b4572280 /os-posix.c
parentd2704eb3fd5093224fb14ecbfdc916d42d42416b (diff)
downloadqemu-6f506c90c3e1814a4a7df5be8d08782c06226820.zip
qemu-6f506c90c3e1814a4a7df5be8d08782c06226820.tar.gz
qemu-6f506c90c3e1814a4a7df5be8d08782c06226820.tar.bz2
ppc/pnv: reduce stack->stack_no usage
'stack->stack_no' represents the order that a stack appears in its PEC. Its primary use is in XSCOM address space calculation in pnv_phb4_xscom_realize() when calculating the memory region offset. This attribute is redundant with phb->phb_id, which is calculated via pnv_phb4_pec_get_phb_id() using stack->stack_no information. It'll also be awkward to assign it when dealing with PECs and PHBs only in a future patch. A new pnv_phb4_get_phb_stack_no() helper is introduced to eliminate most of the stack->stack_no uses we have. The only use left after this patch is during pnv_pec_stk_default_phb_realize() when calculating phb_id, which will also handled in the next patches. Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> Reviewed-by: Cédric Le Goater <clg@kaod.org> Message-Id: <20220114180719.52117-3-danielhb413@gmail.com> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Diffstat (limited to 'os-posix.c')
0 files changed, 0 insertions, 0 deletions