On 31.05.21 07:00, along li wrote:
> When I run qemu demo. try to partition pci device into inmate.
> I failed.
>
> After some lone time trying , I sucess.
> The PCI device e1000e is partitioned into inmate and ping sucess in
> inmate.
> what the defference is:
> 1. I add this into root.c(qemu-x86.c) and qemu-linux-demo.c
> {
> .phys_start = 0xb0000000,//mmconfig
> .virt_start = 0xb0000000,
> .size = 0x10000000,
> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE,
> },
This is wrong, "jailhouse config check" should also complain. You will
eventually loose interrupts or get even worse behaviour.
> or It will show "Invalid PCI MMCONFIG write, device 02:00:0, reg:110,
> size:4"
>
You need to address the root cause: The guest tries to access a PCI
config registers, likely related to PCI capability that has no write
permission in your config yet. See also the good-old Jailhouse tutorial.
>
> 2. use qemu-6.0 to run the qemu demo.
> When use qemu -2..11.1 to run the demo the network card cann't run sucess.
> It turns off after I turn on it use ifconfig up command.
>
> well, may it help someone. whe to try the qemu demo for pci partition.
>
I'm on 4.2.1 to 6.0 here, those seem to have no issue with changing
resource layout. Possibly, we have to lift the lower version boundary by
now, though.
Can you be more specific in regards to what didn't work? Did you try to
compare if /proc/iomem in the root cell is comparable across those qemu
versions?
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jailhouse-dev/a829b501-b59d-d9f6-531b-6ad07667d2a7%40siemens.com.
