| commit | 09a67f3d0e2cb9e66b2ba438de09789527ccb9fe | |
| author | Cédric Le Goater <clg@kaod.org> | |
| Wed, 2 Mar 2022 05:51:38 +0000 (2 06:51 +0100) | ||
| committer | Cédric Le Goater <clg@kaod.org> | |
| Wed, 2 Mar 2022 05:51:38 +0000 (2 06:51 +0100) | ||
| tree | ae3c699b832c4333b11f5d3228ea4be3db256c47 | treesnapshot (tar.gz zip) |
| parent | f8a233dedf2560d7d592dab347ddf2a58e8a98db | commitdiff |
ppc/xive2: Introduce a presenter matching routine
The VP space is larger in XIVE2 (P10), 24 bits instead of 19bits on
XIVE (P9), and the CAM line can use a 7bits or 8bits thread id.
For now, we only use 7bits thread ids, same as P9, but because of the
change of the size of the VP space, the CAM matching routine is
different between P9 and P10. It is easier to duplicate the whole
routine than to add extra handlers in xive_presenter_tctx_match() used
for P9.
We might come with a better solution later on, after we have added
some more support for the XIVE2 controller.
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
The VP space is larger in XIVE2 (P10), 24 bits instead of 19bits on
XIVE (P9), and the CAM line can use a 7bits or 8bits thread id.
For now, we only use 7bits thread ids, same as P9, but because of the
change of the size of the VP space, the CAM matching routine is
different between P9 and P10. It is easier to duplicate the whole
routine than to add extra handlers in xive_presenter_tctx_match() used
for P9.
We might come with a better solution later on, after we have added
some more support for the XIVE2 controller.
Reviewed-by: Daniel Henrique Barboza <danielhb413@gmail.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
| hw/intc/xive2.c | diffblobblamehistory | |
| include/hw/ppc/xive2.h | diffblobblamehistory |