Gabe Black has uploaded this change for review. (
https://gem5-review.googlesource.com/9721
Change subject: dev: arm: Minor reworking of the KMI device.
..
dev: arm: Minor reworking of the KMI device.
This reworking was an
Ok, I've studied the ARM KVM implementation in the kernel, and it's pretty
clear to me that it schedules a timer to keep track of physical time, and
makes the virtual timer in the simulation track with that physical time.
When reading the timer register values, even when the guest isn't running,
Hi Ciro,
I think deactivating the github issues makes sense. And, I'll happily sign
off on a patch to the CONTRIBUTING document if you want to create a quick
review request :).
@Ali: Could you add me to the gem5 github group? I can take care of
removing the issue tracker and other github admin
No problem Jason,
Do we think we should delete the GitHub issues completely or just
leave it there?
If not, people will still open issues there, and what should we do about those?
An intermediate approach is to add a CONTRIBUTING.md saying that "the
official issue tracker is the mailing list".
As an aside, opengrok was set up by Ali who now works for ARM. He has
showed up very briefly since I came back to the project, but I don't think
he's actively following the project. I would take care of some of these
things, but for some reason my root access on gem5.org seems to have been
removed
Hi Ciro,
First of all, we appreciate your efforts to further document gem5 and
answer questions on the gem5 users list!
Right now, we're really just using github as a backup mirror of gem5. I'm
not sure why this was started initially, TBH. It doesn't seem necessary now
that we are hosting the
If made collaborator, I commit to keep every spam out. But there is
little to no spam on GitHub by default anyways.
I feel that if users want to use GitHub issues, which seems to be the
case, we should cater for their preferred communication mechanism.
Issue trackers have several advantages,
Hi Everyone,
I think the first thing we need to establish is whether we want to use
GitHub for issue tracking in the first place. The issue tracker there
was left enabled by accident.
As some of you may recall, we used to run a Flyspray-based issue tracker
a long time ago. If memory serves me
*
build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/minor-timing:
FAILED!
* build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/o3-timing:
FAILED!
*
build/RISCV/tests/opt/quick/se/02.insttest/riscv/linux-rv64c/simple-atomic:
FAILED!
*
