o for example when
>>>> the CPU writes to PCI space it will trigger an event for the GPU. The only
>>>> Ruby involvement here is that Ruby will send all requests outside of its
>>>> memory range to the IO bus (KVM or not).
>>>>
>>>>
t;>> applications. It basically contains some reasonable register values for
>>> anything that is not modeled in gem5 so that we do not need to model them
>>> (e.g., graphics, power management, video encode/decode, etc.). This is not
>>> required for compute-only GPU va
ot need to model them
>> (e.g., graphics, power management, video encode/decode, etc.). This is not
>> required for compute-only GPU variants but that is a different topic.
>>
>> 4. I’m not familiar enough with this particular application to answer
>&g
ou are trying to do.
> Full system mode is using the real GPU driver, ROCm stack, etc. which
> currently does not support any APU-like devices. SE mode is able to do this
> by making use of an emulated driver.
>
>
>
>
>
> -Matt
>
>
>
> *From:* Anoop Mysore via gem5-u
emulated driver.
-Matt
From: Anoop Mysore via gem5-users
Sent: Friday, June 30, 2023 8:43 AM
To: The gem5 Users mailing list
Cc: Anoop Mysore
Subject: [gem5-users] Re: Replacing CPU model in GPU-FS
Caution: This message originated from an External Source. Use proper caution
when opening
It appears the host part of GPU applications are indeed executed on KVM,
from:
https://www.gem5.org/assets/files/workshop-isca-2023/slides/improving-gem5s-gpufs-support.pdf
.
A few more questions:
1. I missed that it isn't mentioned that O3 CPU models aren't supported --
would that be as easy as c
