On Wed, Jan 24, 2024 at 07:57:27PM +0530, Dhaval Sharma wrote:
> "The CpuDxe interface will be the wrapper." Yes, of course. It needs to be
> added. I was just saying that maybe any CMO checking is not required there
> as cmo library will take care of it.
>
That's correct.
> On Tue, Jan 23, 2024
"The CpuDxe interface will be the wrapper." Yes, of course. It needs to be
added. I was just saying that maybe any CMO checking is not required there
as cmo library will take care of it.
On Tue, Jan 23, 2024 at 10:24 PM Sunil V L wrote:
> On Tue, Jan 23, 2024 at 11:42:57AM +0530, Dhaval Sharma
On Tue, Jan 23, 2024 at 11:42:57AM +0530, Dhaval Sharma wrote:
> Sunil,
> I thought "WriteBackDataCacheRange not supported" is more explicit over
> "CMO not available".
>
Okay.
> @Pedro Falcato For the example you mentioned, is
> your concern more about someone not being able to notice the
On Tue, Jan 23, 2024 at 6:13 AM Dhaval Sharma wrote:
>
> Sunil,
> I thought "WriteBackDataCacheRange not supported" is more explicit over "CMO
> not available".
>
> @Pedro Falcato For the example you mentioned, is your concern more about
> someone not being able to notice the problem (that the
Sunil,
I thought "WriteBackDataCacheRange not supported" is more explicit over
"CMO not available".
@Pedro Falcato For the example you mentioned, is
your concern more about someone not being able to notice the problem (that
the system is non-coherent) at the time of development and later ending
On Thu, Jan 18, 2024 at 03:20:18PM +0530, Dhaval wrote:
> Some platforms do not implement cache management operations. Especially
> for DMA drivers have code to manage data cache. The code seem to depend
> on the underlying CPU/cache drivers to enact functionality and simply
> return if such
On Thu, Jan 18, 2024 at 03:58:04PM +, Pedro Falcato wrote:
> On Thu, Jan 18, 2024 at 9:50 AM Dhaval wrote:
> >
> > Some platforms do not implement cache management operations. Especially
> > for DMA drivers have code to manage data cache. The code seem to depend
> > on the underlying
What's very confusing about the current situation is that we have a Pcd that
can set whether I support CMO instructions. When I correctly set up my platform
to not support CMO instructions and hope that everything goes well, I will
trigger Assert in the debug version. But I also can't set the
Hi Pedro,
Agree Assert is slightly more enforcing over logs, but you could still get
away with even Assert in release mode.
One alternative is to convert VERBOSE into WARNING?
=D
On Thu, Jan 18, 2024 at 9:28 PM Pedro Falcato
wrote:
> On Thu, Jan 18, 2024 at 9:50 AM Dhaval wrote:
> >
> > Some
On Thu, Jan 18, 2024 at 9:50 AM Dhaval wrote:
>
> Some platforms do not implement cache management operations. Especially
> for DMA drivers have code to manage data cache. The code seem to depend
> on the underlying CPU/cache drivers to enact functionality and simply
> return if such
On 1/18/24 10:50, Dhaval wrote:
> Some platforms do not implement cache management operations. Especially
> for DMA drivers have code to manage data cache. The code seem to depend
> on the underlying CPU/cache drivers to enact functionality and simply
> return if such functionality is not
Some platforms do not implement cache management operations. Especially
for DMA drivers have code to manage data cache. The code seem to depend
on the underlying CPU/cache drivers to enact functionality and simply
return if such functionality is not implemented. However this causes
issue with CMO
12 matches
Mail list logo
