Le 05/05/2016 02:14, Ian Munsie a écrit :
Excerpts from Frederic Barrat's message of 2016-05-05 00:26:09 +1000:
I believe there's a potential problem there for powerVM guest.
In afu_allocate_irqs(), the allocation of the bitmap for the AFU
interrupts should return NULL (since count = 0). There
Excerpts from Frederic Barrat's message of 2016-05-05 00:26:09 +1000:
> I believe there's a potential problem there for powerVM guest.
> In afu_allocate_irqs(), the allocation of the bitmap for the AFU
> interrupts should return NULL (since count = 0). Therefore we'll skip
> the allocation for th
Hi Ian,
diff --git a/drivers/misc/cxl/guest.c b/drivers/misc/cxl/guest.c
index c0cdf3c..04f6dff 100644
--- a/drivers/misc/cxl/guest.c
+++ b/drivers/misc/cxl/guest.c
@@ -552,6 +552,17 @@ static int attach_afu_directed(struct cxl_context *ctx,
u64 wed, u64 amr)
elem->common.sstp0 = cpu
From: Ian Munsie
In the cxl kernel API, it is possible to create a context and start it
without allocating any interrupts. Since we assign or allocate the PSL
interrupt when allocating AFU interrupts this will lead to a situation
where we start the context with no means to take any faults.
The u