aboutsummaryrefslogtreecommitdiff
path: root/include/qemu/buffer.h
diff options
context:
space:
mode:
authorDaniel Henrique Barboza <danielhb413@gmail.com>2022-01-12 11:28:27 +0100
committerCédric Le Goater <clg@kaod.org>2022-01-12 11:28:27 +0100
commitd22b0c94e4c9c5bba1224b9fd6dcc23373af0261 (patch)
tree8c3ef838d4947f4530f09314cbbd74c207a55641 /include/qemu/buffer.h
parent5032f5d70524af38259a27fb132a57cd3ca40619 (diff)
downloadqemu-d22b0c94e4c9c5bba1224b9fd6dcc23373af0261.zip
qemu-d22b0c94e4c9c5bba1224b9fd6dcc23373af0261.tar.gz
qemu-d22b0c94e4c9c5bba1224b9fd6dcc23373af0261.tar.bz2
pnv_phb4_pec: use pnv_phb4_pec_get_phb_id() in pnv_pec_dt_xscom()
Relying on stack->phb to write the xscom DT of the PEC is something that we won't be able to do with user creatable pnv-phb4 devices. Hopefully, this can be done by using pnv_phb4_pec_get_phb_id(), which is already used by pnv_pec_realize() to set the phb-id of the stack. Use the same idea in pnv_pec_dt_xscom() to write ibm,phb-index without the need to accessing stack->phb, since stack->phb is not granted to be != NULL when user creatable phbs are introduced. Reviewed-by: Cédric Le Goater <clg@kaod.org> Signed-off-by: Daniel Henrique Barboza <danielhb413@gmail.com> Message-Id: <20220110143346.455901-4-danielhb413@gmail.com> Signed-off-by: Cédric Le Goater <clg@kaod.org>
Diffstat (limited to 'include/qemu/buffer.h')
0 files changed, 0 insertions, 0 deletions