Re: [Gems-users] Printing Out Complete Address (with Data Block Bits)

[Brianna Sue Bethel <Brianna.Bethel@xxxxxxxxxxxx>]

I think I figured out how to print out the full address in Sequencer.C makeRequest before the isReady function is called.

Now I have a few more clarifying questions:

1) Does one sequencer send requests from all processors?  Without Opal, is there more than one sequencer?

2)  When the sequencer calls makeRequest, does this request go into the mandatoryQueue in the .sm file?  In other words, is there a way to confirm that a request seen in the sequencer is the same as the request seen in the .sm file MandatoryQueue?

Thanks again for all your help!
Brianna

---- Original message ----
>Date: Sat, 21 Apr 2007 17:02:29 -0600 (MDT)
>From: Brianna Sue Bethel <Brianna.Bethel@xxxxxxxxxxxx>  
>Subject: [Gems-users] Printing Out Complete Address (with Data Block Bits)  
>To: Gems Users <gems-users@xxxxxxxxxxx>
>
>First of all, thanks for all your help so far.  We are making progress, slowly but surely.
>
>In order for our speculation, we need to be able to compare the full 64 bit address, including the DataBlockBits so we can determine which location in the cache line is being referenced.  Originally in our protocol .sm file we tried to store the 'address' variable which was used in the trigger function.  However, even then, we seem to get the memory address with the data block bits masked off...the last 6 bits are always zero.  
>
>My question is how can we access the ORIGINAL address, without the data block bits being masked to zero?
>
>Thanks, 
>Brianna
>_______________________________________________
>Gems-users mailing list
>Gems-users@xxxxxxxxxxx
>https://lists.cs.wisc.edu/mailman/listinfo/gems-users
>Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/"; to your search.
>