Re: [gem5-users] Understanding cda microop
Hi Gabe.
Thank you for the clarification, greatly appreciated . I will make a record
of this, and attempt to implement it as soon as possible.
Best,
On Thu, Sep 12, 2019 at 3:52 PM Gabe Black wrote:
> It's been a while, but I think your interpretation is correct. It looks
> like O3 doesn't check for NO_ACCESS and so will likely go ahead and do the
> access regardless. That will possibly lead to bad things happening, and
> would probably be worth fixing if you're trying to use x86 with O3.
>
> Gabe
>
> On Wed, Sep 11, 2019 at 2:45 PM Pouya Fotouhi
> wrote:
>
>> Hi All,
>>
>> I'm trying to understand how cda microop works. I can see it's defined as
>> "defineMicroStoreOp('Cda', 'Mem = 0;', mem_flags="Request::NO_ACCESS")".
>> And I see in simple and atomic CPUs that we check the data before we
>> execute the instruction in case of requests with NO_ACCESS flag set.
>> My questions are:
>>
>>1. Is my interpretation correct?
>>2. How about O3 CPU?
>>
>>
>> Best,
>> --
>> Pouya Fotouhi
>> PhD Candidate
>> Department of Electrical and Computer Engineering
>> University of California, Davis
>> ___
>> gem5-users mailing list
>> gem5-users@gem5.org
>> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
>
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
--
Pouya Fotouhi
PhD Candidate
Department of Electrical and Computer Engineering
University of California, Davis
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Re: [gem5-users] Understanding cda microop
It's been a while, but I think your interpretation is correct. It looks
like O3 doesn't check for NO_ACCESS and so will likely go ahead and do the
access regardless. That will possibly lead to bad things happening, and
would probably be worth fixing if you're trying to use x86 with O3.
Gabe
On Wed, Sep 11, 2019 at 2:45 PM Pouya Fotouhi wrote:
> Hi All,
>
> I'm trying to understand how cda microop works. I can see it's defined as
> "defineMicroStoreOp('Cda', 'Mem = 0;', mem_flags="Request::NO_ACCESS")".
> And I see in simple and atomic CPUs that we check the data before we
> execute the instruction in case of requests with NO_ACCESS flag set.
> My questions are:
>
>1. Is my interpretation correct?
>2. How about O3 CPU?
>
>
> Best,
> --
> Pouya Fotouhi
> PhD Candidate
> Department of Electrical and Computer Engineering
> University of California, Davis
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
[gem5-users] Understanding cda microop
Hi All,
I'm trying to understand how cda microop works. I can see it's defined as
"defineMicroStoreOp('Cda', 'Mem = 0;', mem_flags="Request::NO_ACCESS")".
And I see in simple and atomic CPUs that we check the data before we
execute the instruction in case of requests with NO_ACCESS flag set.
My questions are:
1. Is my interpretation correct?
2. How about O3 CPU?
Best,
--
Pouya Fotouhi
PhD Candidate
Department of Electrical and Computer Engineering
University of California, Davis
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
