of 128 by 24 places cannot be represented in type 'int'
(XEN) Xen WARN at common/ubsan/ubsan.c:174
Signed-off-by: Jahan Murudi
---
xen/arch/arm/vgic-v2.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xen/arch/arm/vgic-v2.c b/xen/arch/arm/vgic-v2.c
index a19d610178..
while fixing the UBSAN warning
The issue was detected by UBSAN:
(XEN) UBSAN: Undefined behaviour in arch/arm/vgic-v2.c:73:56
(XEN) left shift of 128 by 24 places cannot be represented in type 'int'
(XEN) Xen WARN at common/ubsan/ubsan.c:174
Signed-off-by: Jahan Murudi
---
Change
Hi Stefano/Julien,
This v2 patch was reviewed-by Michal Orzel on 2nd June. Could it be merged?
Link :
https://patchwork.kernel.org/project/xen-devel/patch/20250601163212.2988162-1-jahan.murudi...@renesas.com/
Thanks,
Jahan Murudi
-Original Message-
From: Orzel, Michal
Sent: 02
peration ordering, code readability, and runtime
traceability
for IPMMU on R-Car Gen3/Gen4 SoCs
Signed-off-by: Jahan Murudi
---
xen/drivers/passthrough/arm/ipmmu-vmsa.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/drivers/passthrough/arm/ipmmu-vmsa.c
b/xen/driver
e 2025 12:56
To: Jahan Murudi ; xen-devel@lists.xenproject.org
Cc: Stefano Stabellini ; Julien Grall ;
Bertrand Marquis ; Volodymyr Babchuk
Subject: Re: [PATCH] xen/arm: Enhance IPMMU-VMSA driver robustness and debug
output
On 20/06/2025 12:31, Jahan Murudi wrote:
> - Fix typo in source c
Changed "RCar3/RCar4" to "R-Car Gen3/Gen4" to match official Renesas branding
Aligns with documentation and industry-standard terminology
Signed-off-by: Jahan Murudi
---
xen/arch/arm/platforms/Kconfig | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff
Change "RCar3/RCar4" to "R-Car Gen3/Gen4" to match official Renesas branding.
Aligns with documentation and industry-standard terminology.
Signed-off-by: Jahan Murudi
---
xen/arch/arm/platforms/Kconfig | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff
g
flushes applies globally. This is true for both stage-1 and stage-2.
Given that the patch has already been Acked by Michal, can we proceed with
applying it?
Regards,
Jahan Murudi
redundant. In v2 of the RFC patch, I've
removed both the explicit pcpu.o rule and the pattern rule.
https://patchwork.kernel.org/project/xen-devel/patch/20250709082810.3052544-1-jahan.murudi...@renesas.com/
Regards,
Jahan Murudi
6.3 8
DomD -r 767.038.1 8
Physical CPU Usage:
┌───┬┐
│ Core │ Usage │
├───┼┤
│ 0 │ 98.1% │
│ ... │ ... │
│ 7 │ 97.3% │
└───┴────┘
Signed-off-by: Jahan Murudi
---
tools/xentop/Makefile | 5 +
% │
│ ... │ ... │
│ 7 │ 97.3% │
└───┴────┘
Signed-off-by: Jahan Murudi
---
tools/xentop/Makefile | 11 +++-
tools/xentop/pcpu.c | 116 ++
tools/xentop/pcpu.h | 18 +++
tools/xentop/xentop.c | 30 +--
4 files changed,
Hi Andriy,
Thank you for your review.
>On 08/07/ 2025 18:26, Andriy Sultanov wrote:
> > diff --git a/tools/xentop/xentop.c b/tools/xentop/xentop.c > index
> > f5d6c19cf9..477299c883 100644 > --- a/tools/xentop/xentop.c > +++
> > b/tools/xentop/xentop.c > @@ -69,6 +70,12 @@ > > #define
ng.
> Anyway, I am not against using "dsb(sy)". It is stronger than necessary but
> also probably not a massive deal in the TLB flush path.
Thank you. I agree the performance impact is negligible in the flush path, and
it's better to be safe when dealing with passthrough devices in xen.
Regards,
Jahan Murudi
Hi Anthony,
Just following up on the patch I sent earlier that adds -p/--pcpus support to
xentop.
Would you mind reviewing (and merging if everything looks good)? Please let me
know if any changes are needed.
Thank you for your time.
Regards,
Jahan Murudi
│
├───┼┤
│ 0 │ 98.1% │
│ ... │ ... │
│ 7 │ 97.3% │
└───┴────┘
Signed-off-by: Jahan Murudi
---
tools/xentop/Makefile | 5 +-
tools/xentop/pcpu.c | 152 ++
tools/xentop/pcpu.h | 15 +
tools/xentop/xentop.c |
15 matches
Mail list logo