Re: [PATCH] arm/arm64: Simplify bit field extractions using GET_FIELD macro

On 2018-03-06 18:43, Adeel Ahmad wrote: > The bit field extractions are made more readable by the use > of GET_FIELD macro, this also allows them to be mapped > directly to processor manuals. This commit also > includes a typo fix. > > Signed-off-by: Adeel Ahmad > --- >

[PATCH] arm/arm64: Simplify bit field extractions using GET_FIELD macro

The bit field extractions are made more readable by the use of GET_FIELD macro, this also allows them to be mapped directly to processor manuals. This commit also includes a typo fix. Signed-off-by: Adeel Ahmad --- hypervisor/arch/arm/include/asm/sysregs.h | 10

[PATCH] Documentation: update required QEMU version to be >= 2.8

The "x86 Demonstration in QEMU/KVM" section currently lists QEMU version to be 2.7 or newer, as the x-buggy-eim property was introduced in version 2.8, this version won't work. Signed-off-by: Adeel Ahmad --- README.md | 2 +- 1 file changed, 1 insertion(+), 1

shared memory application to run on non rootcell

Jan, we are tying to access( read & write) from shared memory region between root cell and non rootcell. I cant use ivshm-shared.bin file because I want to load another linux kernel on non rootcell. After booting into non rootcell, how can I write into shared memory region and trigger

[siemens/jailhouse] 28cc7c: Documentation: update required QEMU version to be ...

Branch: refs/heads/next Home: https://github.com/siemens/jailhouse Commit: 28cc7ce508123fd21e3a1da0da561f7bd35a6244 https://github.com/siemens/jailhouse/commit/28cc7ce508123fd21e3a1da0da561f7bd35a6244 Author: Adeel Ahmad Date: 2018-03-06 (Tue, 06 Mar

Re: Submitting a patch to the mailing list

> > Your messages got stuck in the spam filter of googlegroups - Google > seems to hate hotmail :). I've whitelisted you and confirmed the last > version of the patch. If anything is missing, please repost now. > > Jan > Hi Jan, I just submitted two patches to the mailing list, but they

need application executa

Jan, we are tying to access( read & write) from shared memory region between root cell and non rootcell. I cant use ivshm-shared.bin file because I want to load another linux kernel on non rootcell. After booting into non rootcell, how can I write into shared memory region and trigger

Re: shared memory application to run on non rootcell

On 2018-03-06 19:19, anilapp...@gmail.com wrote: > Jan, > we are tying to access( read & write) from shared memory region between root > cell and non rootcell. I cant use ivshm-shared.bin file because I want to > load another linux kernel on non rootcell. After booting into non rootcell, > how

Re: [PATCH] Update required QEMU version to be >= 2.8

On 2018-03-05 17:37, Adeel Ahmad wrote: > The current version mentioned in README.md (2.7) does not support the > x-buggy-eim property. > > Signed-off-by: Adeel Ahmad > --- > README.md | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

[PATCH v5 4/7] x86: Align x86_64 PCI_MMCONFIG with 32-bit variant

From: Jan Kiszka Allow to enable PCI_MMCONFIG when only SFI is present and make this option default on. This will help consolidating both into one Kconfig statement. Signed-off-by: Jan Kiszka --- arch/x86/Kconfig | 3 ++- 1 file changed, 2

[PATCH v5 6/7] x86/jailhouse: Allow to use PCI_MMCONFIG without ACPI

From: Jan Kiszka Jailhouse does not use ACPI, but it does support MMCONFIG. Make sure the latter can be built without having to enable ACPI as well. Primarily, we need to make the AMD mmconf-fam10h_64 depend upon MMCONFIG and ACPI, instead of just the former. Saves some

[PATCH v5 0/7] jailhouse: Enhance secondary Jailhouse guest support /wrt PCI

Basic x86 support [1] for running Linux as secondary Jailhouse [2] guest is currently pending in the tip tree. This builds on top and enhances the PCI support for x86 and also ARM guests (ARM[64] does not require platform patches and works already). Key elements of this series are: - detection

[PATCH v5 1/7] jailhouse: Provide detection for non-x86 systems

From: Jan Kiszka Implement jailhouse_paravirt() via device tree probing on architectures != x86. Will be used by the PCI core. CC: Rob Herring CC: Mark Rutland CC: Juergen Gross Signed-off-by: Jan Kiszka

[PATCH v5 5/7] x86: Consolidate PCI_MMCONFIG configs

From: Jan Kiszka Since e279b6c1d329 ("x86: start unification of arch/x86/Kconfig.*"), we have two PCI_MMCONFIG entries, one from the original i386 and another from x86_64. This consolidates both entries into a single one. Signed-off-by: Jan Kiszka

[PATCH v5 3/7] x86/jailhouse: Enable PCI mmconfig access in inmates

From: Otavio Pontes Use the PCI mmconfig base address exported by jailhouse in boot parameters in order to access the memory mapped PCI configuration space. Signed-off-by: Otavio Pontes [Jan: rebased, fixed !CONFIG_PCI_MMCONFIG, used

[PATCH v5 7/7] MAINTAINERS: Add entry for Jailhouse

From: Jan Kiszka Signed-off-by: Jan Kiszka --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 4623caf8d72d..6dc0b8f3ae0e 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7523,6 +7523,13 @@ Q:

[PATCH v5 2/7] PCI: Scan all functions when running over Jailhouse

From: Jan Kiszka Per PCIe r4.0, sec 7.5.1.1.9, multi-function devices are required to have a function 0. Therefore, Linux scans for devices at function 0 (devfn 0/8/16/...) and only scans for other functions if function 0 has its Multi-Function Device bit set or ARI or