summaryrefslogtreecommitdiff
path: root/dev
diff options
context:
space:
mode:
authorRon Dreslinski <rdreslin@umich.edu>2005-01-21 04:55:43 -0500
committerRon Dreslinski <rdreslin@umich.edu>2005-01-21 04:55:43 -0500
commit867d80d55df081b4deae36a15d48dc36560fbde5 (patch)
treec6863b7f1e0426058fb2a20386fb7e52f2dda9eb /dev
parent10371be698b411bc068137bf2add0c5a74ec60eb (diff)
downloadgem5-867d80d55df081b4deae36a15d48dc36560fbde5.tar.xz
Fix annoying bug that lead to dropped packets in the P4 system
dev/pktfifo.cc: Make it so that we don't unserialize the size of the fifo, clobering the fact that we were trying to make it bigger, and leading to a misleading config.out that states the un-overwritten max_size. Perhaps this should instead be a panic if the size (amount that was serialized) is bigger than the maxsize that was assigned by the configuration file. --HG-- extra : convert_revision : d4b0527bfd7a584554ddc87c9b2103f7a3a72332
Diffstat (limited to 'dev')
-rw-r--r--dev/pktfifo.cc2
1 files changed, 1 insertions, 1 deletions
diff --git a/dev/pktfifo.cc b/dev/pktfifo.cc
index 79a96cc1d..dcb1c4c03 100644
--- a/dev/pktfifo.cc
+++ b/dev/pktfifo.cc
@@ -54,7 +54,7 @@ PacketFifo::unserialize(const string &base, Checkpoint *cp,
const string &section)
{
paramIn(cp, section, base + ".size", _size);
- paramIn(cp, section, base + ".maxsize", _maxsize);
+// paramIn(cp, section, base + ".maxsize", _maxsize);
paramIn(cp, section, base + ".reserved", _reserved);
int fifosize;
paramIn(cp, section, base + ".packets", fifosize);