---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3302/
---
(Updated Feb. 4, 2016, 1:35 a.m.)
Review request for Default.
Changes
---
Ma
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/3271/#review7986
---
I would like to review this more closely, but am having trouble finding t
I posted most of these x86 patches two weeks ago. If I don't hear
something by Friday (2/5), I'll assume that no one wants to review them,
and will commit them sometime after that.
http://reviews.gem5.org/r/3290/
http://reviews.gem5.org/r/3291/
http://reviews.gem5.org/r/3307/
Thanks,
Steve
I'd also like to express my support for moving to GitHub. Our team is already
using the gem5 GitHub mirror as the upstream for our internal development.
Officially moving to GitHub would simplify all aspects of the development
process as it relates to everything other than simply keeping in sync
Hi Joel,
I would suggest o keep the queued ports, but add methods to reserve resources,
query if it has free space, and a way to register callbacks so that the
MemObject is made aware when packets are sent. That way we can use the queue in
the cache, memory controller etc, without having all th
Hi all,
I intend to push these patches early next week. Let me know if you have
comments or need more time:
http://reviews.gem5.org/r/3271/
http://reviews.gem5.org/r/3294/
Thanks,
Andreas
IMPORTANT NOTICE: The contents of this email and any attachments are
confidential and may also be privi
Dear Tony,
Could you please commit these two patches? I will appreciate it as these
patches are essential for dist-gem5 functionality.
http://reviews.gem5.org/r/3231/
http://reviews.gem5.org/r/3230/
Thank you,
Mohammad Alian
On Wed, Jan 27, 2016 at 12:55 PM, Tony Gutierrez
wrote:
> This is a
Yes, it was a news flash to me that someone was trying to use flyspray. I
agree that it would be nice to move to some hosted cloud service since
things have come a long way in that space since we started the project :).
Steve
On Wed, Feb 3, 2016 at 3:12 AM Andreas Sandberg
wrote:
> Maybe we s
Maybe we should consider moving issue tracking to GitHub? It¹s already
there, it works, and it would remove the need for someone to admin
FlySpray. In general, I¹d like to see us moving to more hosted
infrastructure to avoid having to do boring server management stuff.
Just my 2p.
//Andreas
On 0
* build/ALPHA/tests/opt/quick/se/20.eio-short/alpha/eio/simple-atomic
CHANGED!
* build/ALPHA/tests/opt/quick/se/20.eio-short/alpha/eio/simple-timing
CHANGED!
* build/ALPHA/tests/opt/quick/se/30.eio-mp/alpha/eio/simple-atomic-mp
CHANGED!
* build/ALPHA/tests/opt/quick/se/30.eio-mp/
10 matches
Mail list logo