• State Suggested Answer
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 22 subscribers
  • Views 1056 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[Cortex-R52]About the virtual interrupt ID and the physical interrupt ID relationship

Gavin Li

Dear Arm experts,

Just one question that should the virtual interrupt ID must be same with the physical interrupt ID when the hypervisor wirtes to list register?

Best Regards,

Gavin

Parents
  • 0

    It doesn't have to be.

    The vINTID is what will be seen by the software in the VM.  The pINTID is the linked physical interrupt you want to be de-activated when the virtual interrupt is de-activated.

    Depending on how and why you're doing virtualisation it might make sense for vINTID=pINTID, equally it might make sense for vINTID != pINTID.  The architecture allows you to do either. 

Reply
  • 0

    It doesn't have to be.

    The vINTID is what will be seen by the software in the VM.  The pINTID is the linked physical interrupt you want to be de-activated when the virtual interrupt is de-activated.

    Depending on how and why you're doing virtualisation it might make sense for vINTID=pINTID, equally it might make sense for vINTID != pINTID.  The architecture allows you to do either. 

Children
No data