Hi Prabhakar,
On 29.11.22 15:29, Lad, Prabhakar wrote:
> Hi Jan,
>
> On Sun, Nov 6, 2022 at 11:05 PM Lad Prabhakar
> wrote:
>>
>> Hi All,
>>
>> This patch series adds support for Renesas RZ/G2M SoC [0] (root cell
>> config) and adds demo cell config for HopeRun HiHope RZ/G2M platform [1].
>>
>>
From: Jan Kiszka
This was not complete, rather assumed SVT to be 01b and completely
ignored SQ. The SID test failed when the root cell chose SVT to be 10b
to describe a source behind a PCIe-PCI bridge, thus switching SID to
startbus/endbus encoding (now needed for QEMU).
Let's make it simple
Happy New Year, everyone!
Long time no activity from my side, but now I finally found a few days
to do some long overdue renovation work. One outcome is this patch
series which allows to use ivshmem devices with latest QEMU again, see
patch 3 for the background.
Will now look into refreshing the
From: Jan Kiszka
Not only the subdevices need to be assigned to the given IOMMU, also the
bridge itself. Otherwise, the config generator will bail out with
something like
RuntimeError: PCI device 00:03.0 outside the scope of an IOMMU
Signed-off-by: Jan Kiszka
---
pyjailhouse/sysfs_parser.py
From: Jan Kiszka
Needed now as we had to move ivshmem devices behind this hotplug-capable
bridge.
Signed-off-by: Jan Kiszka
---
README.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index b5937300..dc2c3afa 100644
--- a/README.md
+++
From: Jan Kiszka
Recent QEMU disabled hotplugging support for the root bus. Linux will
still find the ivshmem devices we inject there so far, but it will fail
to allocate IRQs for it because the related irq domain was frozen in
size, given that hotplug is not possible.
Work around this issue by
On 13.12.22 20:33, Tommi Parkkila wrote:
> Hi all - I am trying to configure and deploy Jailhouse on STM32MP1 w/
> dual Cortex-A7. I get Jailhouse built and installed on target, and
> kernel module installed successfully, but when enabling Jailhouse the
> whole system hangs and restarts after
On 11.12.22 17:06, 张家铭 wrote:
> Hi,
>
> Recently, I have used inmate-demo(inmates/demos/ivshmem-demo.c) and
> ivshmem-demo(tools/ivshmem-demo.c) on rpi4 to study how to communicate
> between two cells. I have following problems:
>
> 1. I found this result, However, I'm not sure it is correct.
On 13.12.22 14:40, Ralf Ramsauer wrote:
> Hi Jussi,
>
> On 13/12/2022 14:05, Jussi Pajala wrote:
>> Hi,
>>
>> I'm currently running old jailhouse 0.8 on 4.9 kernel - provided by
>> TI's SDK.
>>
>> Now, I need to upgrade to 5.10 kernel but TI has removed Jailhouse
>> support from the newest SDK
On 21.11.22 07:47, Peng Fan wrote:
> Hi,
>
> I have a question regarding ivshmem-net, not sure whether we need to use
> local_bh_disable/enable to guard napi_schedule.
>
> See below patch:
> https://patches.linaro.org/project/linux-usb/patch/877dk162mo@nanos.tec.linutronix.de/
> "
> The
On 21.11.22 23:35, Marco Barletta wrote:
> Dear all;
> I tried to use the repo Jailhouse of demo images for building a QEMU
> target (x86), as I did a few months ago. But something has broken. First
> of all the SRC_URI in jailhouse.inc is a git:// URI, deprecated by
> github (afaik). I replaced
On 24.11.22 20:19, Yelena Konyukh wrote:
> Hi All,
>
> Answering my own question :) :
>
> I have run the demo from https://github.com/siemens/jailhouse-images for
> Raspberry Pie and simply collected the output of "cat /proc/iomem"
> before running Jailhouse, then after enabling Jailhouse in the
On 19.10.22 23:21, Lukas Saintz wrote:
> Hi Jan,
> I'm studying Jailhouse Hypervisor and its implementation on a BananPi
> M1 Board.
> Following your guide I've successfully compiled and executed both
> Bananapi.cell and FreeRTOS-demo.cell.
> Now I want to study IVSHEMEM and how the two cells can
13 matches
Mail list logo
