The bus bridge code has the "filter_ranges_a" and "filter_ranges_b" parameters. These were intended for this sort of case and can be used to disallow bridges from propagating certain addresses. I'm not sure if this can fix the exact problem since I haven't followed this thread closely, but it's certainly a place to start.
Nate On Wed, May 6, 2009 at 7:23 AM, Geoffrey Blake <[email protected]> wrote: > Yes, that extra bridge is the cause. What is happening is that the bridge is > being probed by l3bus which then probes l3bus2 for address ranges, l3bus2 > probes the L3 cache for ranges as will l3bus a some point, both probes to > the bridge and the L3 cache will return the same address range at some point > causing the error. The way address range propagation is handled currently > disallows more than 1 path to a device that responds to memory address > ranges, which is what that extra bridge is causing (2 possible paths to get > to the L3 cache and underlying physmem). You will either have to just limit > your experimentation to not doing this, or muck with the address range > propagation code in bus.cc to allow multiple paths. > > Geoff > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Shoaib Akram > Sent: Monday, May 04, 2009 3:54 PM > To: M5 users mailing list > Subject: Re: [m5-users] Range Error > > I have attached a diagram(pdf file) of configuration and fs2.py. Please note > that the problem occurs because of l3Bridge (commented in fs2.py). > > Ofcourse, I have a solution to maintain coherence at the back end. > > ---- Original message ---- >>Date: Mon, 4 May 2009 15:04:57 -0400 >>From: "Geoffrey Blake" <[email protected]> >>Subject: Re: [m5-users] Range Error >>To: "'M5 users mailing list'" <[email protected]> >> >>If you haven't modified any code, it is most likely with how your fs.py >>configures the devices. You have to make sure no device can pass its >>address range back through multiple paths (ie. devices cannot be >>connected to multiple bridges that connect to one bus), and no two >>devices have the same address ranges set. The best way is to post your >>fs.py file so some here can help if they are able. >> >>Geoff >> >>-----Original Message----- >>From: [email protected] [mailto:[email protected]] On >>Behalf Of Shoaib Akram >>Sent: Monday, May 04, 2009 2:40 PM >>To: [email protected] >>Subject: [m5-users] Range Error >> >>I am getting a "Two devices with same range" error. I have never been >>involved with the Range business. Can some one give hints as to where >>to look for the problem. I am running fs.py with a few extra bridges. >>Is this problem need to be resolved at the front-end or tweaking bus.cc? >>_______________________________________________ >>m5-users mailing list >>[email protected] >>http://m5sim.org/cgi-bin/mailman/listinfo/m5-users >> >> >> >>No virus found in this incoming message. >>Checked by AVG - www.avg.com >>Version: 8.5.287 / Virus Database: 270.12.16/2094 - Release Date: >>05/03/09 16:51:00 >> >>_______________________________________________ >>m5-users mailing list >>[email protected] >>http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.287 / Virus Database: 270.12.19/2099 - Release Date: 05/05/09 > 13:07:00 > > _______________________________________________ > m5-users mailing list > [email protected] > http://m5sim.org/cgi-bin/mailman/listinfo/m5-users > > _______________________________________________ m5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
