Packages

p

vexiiriscv

schedule

package schedule

Ordering
  1. Alphabetic
Visibility
  1. Public
  2. All

Type Members

  1. class DispatchPlugin extends FiberPlugin

    The role of the dispatch plugin is to : - Collect the instruction exiting the decode pipeline, - Figuring out on which execution lane they could be scheduled (checking for dependencies).

    The role of the dispatch plugin is to : - Collect the instruction exiting the decode pipeline, - Figuring out on which execution lane they could be scheduled (checking for dependencies). If none, then wait for some. - Issue instructions on execution lanes

    It is likely one of the hardest plugin to read, as it does a lot of elaboration time analysis to generate the "right" hadware

    How to check if a instruction can schedule : - If one of the pipeline which implement its micro op is free - There is no inflight non-bypassed RF write to one of the source operand - There is no scheduling fence - ...

    Schedule heuristic : - In priority order, go through the slots - Check which pipeline could schedule it (free && compatible) - Select the pipeline which the highest priority (to avoid using the one which can do load and store, for instance) - If the slot can't be schedule, disable all following ones with same HART_ID

  2. case class FlushCmd(age: Int, laneAgeWidth: Int, withUopId: Boolean) extends Bundle with Product with Serializable
  3. class ReschedulePlugin extends FiberPlugin with ScheduleService

    The ReschedulePlugin act as a arbiter for all the different plugins which want to reschedule what the CPU should execute, aswell as a registry for all the plugins which need to know if the CPU is being flushed until a given point in the pipeline.

  4. trait ScheduleService extends AnyRef

    Provide an API to create new interfaces to flush the CPU pipelines.

    Provide an API to create new interfaces to flush the CPU pipelines. The "age" can be generated from the Ages object.

Value Members

  1. object Ages

    This contains the integer constant which allows to compute identifier for a given point in the pipeline.

    This contains the integer constant which allows to compute identifier for a given point in the pipeline. This id can then be used with the ReschedulePlugin to querry/register flushes

    So for instance, if you want to get the age id for the execute stage 3, then you do EXECUTE + 3*STAGE + NOT_PREDICTION