VirtualBox

Ignore:
Timestamp:
Oct 18, 2023 11:27:55 AM (16 months ago)
Author:
vboxsync
Message:

VMM,Main: Don't hardcode the vTimer interrupt number in the NEM backend but let the configuration constructor decide the value so it matches the FDT, bugref:10390 bugref:10528

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/src/VBox/VMM/VMMR3/NEMR3Native-darwin-armv8.cpp

    r101234 r101496  
    7070*   Defined Constants And Macros                                                                                                 *
    7171*********************************************************************************************************************************/
    72 
    73 
    74 /** @todo The vTimer PPI for the virt platform, make it configurable. */
    75 #define NEM_DARWIN_VTIMER_GIC_PPI_IRQ           11
    7672
    7773
     
    14121408            TMCpuSetVTimerNextActivation(pVCpu, UINT64_MAX);
    14131409            pVCpu->nem.s.fVTimerActivated = true;
    1414             return GICPpiSet(pVCpu, NEM_DARWIN_VTIMER_GIC_PPI_IRQ, true /*fAsserted*/);
     1410            return GICPpiSet(pVCpu, pVM->nem.s.u32GicPpiVTimer, true /*fAsserted*/);
    14151411        }
    14161412        default:
     
    14771473        {
    14781474            /* Clear the interrupt. */
    1479             GICPpiSet(pVCpu, NEM_DARWIN_VTIMER_GIC_PPI_IRQ, false /*fAsserted*/);
     1475            GICPpiSet(pVCpu, pVM->nem.s.u32GicPpiVTimer, false /*fAsserted*/);
    14801476
    14811477            pVCpu->nem.s.fVTimerActivated = false;
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette