On Fri, 24 Jan 2025 17:28:02 +0100
Philippe Mathieu-Daudé wrote:
> On 24/1/25 17:20, Jonathan Cameron wrote:
> > On Thu, 23 Jan 2025 09:51:51 +
> > Jonathan Cameron via wrote:
> >
> >> On Wed, 22 Jan 2025 07:56:24 +0100
> >> Philippe Mathieu-Daudé wrote:
> >>
> >>> Map the component I/
On Thu, 23 Jan 2025 09:51:51 +
Jonathan Cameron via wrote:
> On Wed, 22 Jan 2025 07:56:24 +0100
> Philippe Mathieu-Daudé wrote:
>
> > Map the component I/O region as UnimplementedDevice
> > to be able to trace guest I/O accesses with '-d unimp'.
> >
> > Signed-off-by: Philippe Mathieu-Daud
On 24/1/25 17:20, Jonathan Cameron wrote:
On Thu, 23 Jan 2025 09:51:51 +
Jonathan Cameron via wrote:
On Wed, 22 Jan 2025 07:56:24 +0100
Philippe Mathieu-Daudé wrote:
Map the component I/O region as UnimplementedDevice
to be able to trace guest I/O accesses with '-d unimp'.
Signed-off-b
On Wed, 22 Jan 2025 07:56:24 +0100
Philippe Mathieu-Daudé wrote:
> Map the component I/O region as UnimplementedDevice
> to be able to trace guest I/O accesses with '-d unimp'.
>
> Signed-off-by: Philippe Mathieu-Daudé
I'm not that familiar with this infrastructure but seems
fine to me.
I'd de
Map the component I/O region as UnimplementedDevice
to be able to trace guest I/O accesses with '-d unimp'.
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/cxl/cxl_component.h | 3 ++-
hw/cxl/cxl-component-utils.c | 14 +++---
hw/cxl/Kconfig | 1 +
3 files change