]> Git Repo - qemu.git/commit
ppc/xive: Introduce a XivePresenter interface
authorCédric Le Goater <[email protected]>
Mon, 25 Nov 2019 06:58:01 +0000 (07:58 +0100)
committerDavid Gibson <[email protected]>
Mon, 16 Dec 2019 23:39:47 +0000 (10:39 +1100)
commit13bee8521c2e1d4908b1e003ff50fdec3702ad13
tree6fbcc9bbd3c458753979e1c012dc59895c80bf4f
parente2392d4395ddc18a1e991f30f7dbea8cf02ec8e6
ppc/xive: Introduce a XivePresenter interface

When the XIVE IVRE sub-engine (XiveRouter) looks for a Notification
Virtual Target (NVT) to notify, it broadcasts a message on the
PowerBUS to find an XIVE IVPE sub-engine (Presenter) with the NVT
dispatched on one of its HW threads, and then forwards the
notification if any response was received.

The current XIVE presenter model is sufficient for the pseries machine
because it has a single interrupt controller device, but the PowerNV
machine can have multiple chips each having its own interrupt
controller. In this case, the XIVE presenter model is too simple and
the CAM line matching should scan all chips of the system.

To start fixing this issue, we first extend the XIVE Router model with
a new XivePresenter QOM interface representing the XIVE IVPE
sub-engine. This interface exposes a 'match_nvt' handler which the
sPAPR and PowerNV XIVE Router models will need to implement to perform
the CAM line matching.

Signed-off-by: Cédric Le Goater <[email protected]>
Reviewed-by: Greg Kurz <[email protected]>
Signed-off-by: Cédric Le Goater <[email protected]>
Message-Id: <20191125065820[email protected]>
Signed-off-by: David Gibson <[email protected]>
hw/intc/xive.c
include/hw/ppc/xive.h
This page took 0.02692 seconds and 4 git commands to generate.