[siemens/jailhouse] 7a3fec: hypervisor: Makefile: hook-in Wextra

2020-11-08 Thread 'Nikhil Devshatwar' via Jailhouse
Branch: refs/heads/next Home: https://github.com/siemens/jailhouse Commit: 7a3fecfc146052dd154597a0b9e12545ea67afef https://github.com/siemens/jailhouse/commit/7a3fecfc146052dd154597a0b9e12545ea67afef Author: Andrea Bastoni Date: 2020-11-08 (Sun, 08 Nov 2020) Changed

[siemens/jailhouse] 7a3fec: hypervisor: Makefile: hook-in Wextra

2020-11-08 Thread 'Nikhil Devshatwar' via Jailhouse
Branch: refs/heads/coverity_scan Home: https://github.com/siemens/jailhouse Commit: 7a3fecfc146052dd154597a0b9e12545ea67afef https://github.com/siemens/jailhouse/commit/7a3fecfc146052dd154597a0b9e12545ea67afef Author: Andrea Bastoni Date: 2020-11-08 (Sun, 08 Nov 2020)

[siemens/jailhouse] 7a3fec: hypervisor: Makefile: hook-in Wextra

2020-11-23 Thread 'Nikhil Devshatwar' via Jailhouse
Branch: refs/heads/master Home: https://github.com/siemens/jailhouse Commit: 7a3fecfc146052dd154597a0b9e12545ea67afef https://github.com/siemens/jailhouse/commit/7a3fecfc146052dd154597a0b9e12545ea67afef Author: Andrea Bastoni Date: 2020-11-08 (Sun, 08 Nov 2020) Changed

[PATCH] arm64: Report exception link register ELR in the regdump

2020-11-02 Thread 'Nikhil Devshatwar' via Jailhouse
For an arm64 CPU, when an exception is taken, the PC of the CPU is copied in the ELR_ELx. This is useful for debugging which code path caused the exception. Modify fill_trap_context to populate ELR_EL2 and dump it as part of the dump_regs Signed-off-by: Nikhil Devshatwar ---

[PATCH] hypervisor: include: Add a BUG() macro

2020-10-30 Thread 'Nikhil Devshatwar' via Jailhouse
Add a new BUG macro in utils which can be used in places where you don't expect control to reach. Whenever this happens, the code will intentionally crash via a null pointer de reference. Signed-off-by: Nikhil Devshatwar --- hypervisor/include/jailhouse/utils.h | 2 ++ 1 file changed, 2

[PATCH v3] arm64: pvu: Avoid failure in config_commit

2020-10-30 Thread 'Nikhil Devshatwar' via Jailhouse
Current PVU iommu implementation ignores possible failures in the config_commit part. This would allow inconsistent configuration to run and may introduce unknown bugs. Solve this by making sure that the pvu_iommu_config_commit never fails. Catch the errors early in the mapping phase. Use

Re: [J7] jailhouse hypervisor in TI J7

2020-11-06 Thread 'Nikhil Devshatwar' via Jailhouse
On 06:30-20201106, Liang Jingyan (M) wrote: > Dear Jailhouse develop Team, > > We are Marelli(Guangzhou) Team, We are now developing TI J7 board, as we > know, TI use the jailhouse hypervisor with their Cockpit Demo. Now Marelli > team want to know more detail about the jailhouse hypervisor, we

Re: [PATCH v3] arm64: pvu: Avoid failure in config_commit

2020-11-06 Thread 'Nikhil Devshatwar' via Jailhouse
On 17:57-20201030, 'Nikhil Devshatwar' via Jailhouse wrote: > Current PVU iommu implementation ignores possible failures in the > config_commit part. This would allow inconsistent configuration > to run and may introduce unknown bugs. > > Solve this by making sure that the pvu_iomm

Re: [PATCH v2] arm64: pvu: Avoid failure in config_commit

2020-10-29 Thread 'Nikhil Devshatwar' via Jailhouse
On 17:09-20201029, Jan Kiszka wrote: > On 29.10.20 16:27, Nikhil Devshatwar wrote: > > On 08:14-20201029, Jan Kiszka wrote: > >> On 28.10.20 15:14, 'Nikhil Devshatwar' via Jailhouse wrote: > >>> Current PVU iommu implementation ignores possible failures in the > &

Re: [PATCH v2] arm64: pvu: Avoid failure in config_commit

2020-10-29 Thread 'Nikhil Devshatwar' via Jailhouse
On 08:14-20201029, Jan Kiszka wrote: > On 28.10.20 15:14, 'Nikhil Devshatwar' via Jailhouse wrote: > > Current PVU iommu implementation ignores possible failures in the > > config_commit part. This would allow inconsistent configuration > > to run and may introduce unknown

<    1   2