On Monday, April 9, 2018 at 4:37:28 PM UTC+5:30, J. Kiszka wrote:
> On 2018-04-09 13:04, [email protected] wrote:
> > On Monday, April 9, 2018 at 11:55:26 AM UTC+5:30, J. Kiszka wrote:
> >> On 2018-04-08 11:59, [email protected] wrote:
> >>> On Saturday, April 7, 2018 at 3:24:13 PM UTC+5:30, Jan Kiszka wrote:
> >>>> On 2018-04-07 06:01, [email protected] wrote:
> >>>>> Hi Henning,
> >>>>> Thanks for understanding our issue for ready to help us. I want to
> >>>>> inform one more failure which we observed we after non rootcell bootup(
> >>>>> it shows io remap failed).
> >>>>>
> >>>>>
> >>>>>
> >>>>> 0.403714] cpuidle: using governor ladder
> >>>>> [ 0.412705] cpuidle: using governor menu
> >>>>> [ 0.416813] PCI: Using configuration type 1 for base access
> >>>>> [ 0.422401] PCI: ashok JH PCI MMCONFIG
> >>>>> [ 0.426159] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem
> >>>>> 0x80000000-0x8fffffff] (base 0x80000000)
> >>>>> [ 0.435469] ------------[ cut here ]------------
> >>>>> [ 0.440098] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:121
> >>>>> __ioremap_caller+0x286/0x360
> >>>>> [ 0.448536] ioremap on RAM at 0x0000000080000000 - 0x000000008fffffff
> >>>>> [ 0.454974] Modules linked in:
> >>>>> [ 0.458050] CPU: 0 PID: 1 Comm: swapper/0 Not tainted
> >>>>> 4.9.47-rt37+-RedHawk-7.4-custom #27
> >>>>> [ 0.466216] ffffc9000062bd10 ffffffff8155da23 ffffc9000062bd60
> >>>>> 0000000000000000
> >>>>> [ 0.473666] ffffc9000062bd50 ffffffff81077d1b 00000079ffffffff
> >>>>> 0000000010000000
> >>>>> [ 0.481119] 0000000000000002 ffffffff81d95e3f 0000000080000000
> >>>>> 0000000000000000
> >>>>> [ 0.488573] Call Trace:
> >>>>> [ 0.491021] [<ffffffff8155da23>] dump_stack+0x85/0xc2
> >>>>> [ 0.496159] [<ffffffff81077d1b>] __warn+0xcb/0xf0
> >>>>> [ 0.500945] [<ffffffff81d95e3f>] ? pci_mmcfg_arch_map+0x2f/0x70
> >>>>> [ 0.506947] [<ffffffff81077d8f>] warn_slowpath_fmt+0x4f/0x60
> >>>>> [ 0.512685] [<ffffffff81060c16>] __ioremap_caller+0x286/0x360
> >>>>> [ 0.518510] [<ffffffff810dec19>] ? vprintk_default+0x29/0x40
> >>>>> [ 0.524249] [<ffffffff811afde4>] ? printk+0x48/0x50
> >>>>> [ 0.529213] [<ffffffff82b35f15>] ? pcibios_resource_survey+0x70/0x70
> >>>>> [ 0.535641] [<ffffffff81060d07>] ioremap_nocache+0x17/0x20
> >>>>> [ 0.541205] [<ffffffff81d95e3f>] pci_mmcfg_arch_map+0x2f/0x70
> >>>>> [ 0.547029] [<ffffffff82b35fbd>] pci_mmcfg_arch_init+0x1d/0x42
> >>>>> [ 0.552941] [<ffffffff82ae0a25>] jailhouse_pci_arch_init+0x40/0x44
> >>>>> [ 0.559197] [<ffffffff82b35f50>] pci_arch_init+0x3b/0x66
> >>>>> [ 0.564588] [<ffffffff81000420>] do_one_initcall+0x50/0x190
> >>>>> [ 0.570238] [<ffffffff8109aa7a>] ? parse_args+0x26a/0x3f0
> >>>>> [ 0.575717] [<ffffffff82ac9154>] kernel_init_freeable+0x1cf/0x257
> >>>>> [ 0.581887] [<ffffffff81f3cab0>] ? rest_init+0x90/0x90
> >>>>> [ 0.587102] [<ffffffff81f3cabe>] kernel_init+0xe/0x120
> >>>>> [ 0.592321] [<ffffffff81f464fa>] ret_from_fork+0x2a/0x40
> >>>>> [ 0.597728] ---[ end trace 38a36dc7a73d77e3 ]---
> >>>>> [ 0.602349] PCI: can't map MMCONFIG at [mem 0x80000000-0x8fffffff]
> >>>>> [ 0.609402] kworker/u4:4 (63) used greatest stack depth: 13512 bytes
> >>>>> left
> >>>>>
> >>>>>
> >>>>> I attached complete logs for your reference. we will try with what ever
> >>>>> the inputs you gave to us and will let you know. I am also sharing
> >>>>> rootcell and non root cell configs which we are using.
> >>>>
> >>>> You configured a conflict here: The shared memory region is also a RAM
> >>>> region for the cell.
> >>>>
> >>>> Jan
> >>>
> >>> Jan,
> >>> we added below region for shared memory
> >>>
> >>> .phys_start = 0x404100000,
> >>>
> >>> .virt_start = 0x404100000,
> >>> .size = 0x100000,
> >>> This is not RAM region. I attached iomem file for by Machine. Can you
> >>> please check.
> >>>
> >>
> >> Ah, sorry, it's not the shared memory, it's the MMCONFIG region:
> >>
> >> [ 0.440098] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:121
> >> __ioremap_caller+0x286/0x360
> >> [ 0.448536] ioremap on RAM at 0x0000000080000000 - 0x000000008fffffff
> >>
> >> because of (fixed)
> >>
> >> .platform_info = {
> >> .pci_mmconfig_base = 0x80000000,
> >> .pci_mmconfig_end_bus = 0xff,
> >>
> >>
> >> vs.
> >>
> >> /* high RAM */
> >> {
> >> .phys_start = 0x404300000/*0x401100000*/,
> >> .virt_start = 0x00200000,
> >> .size = 0xC0000000, /*1GB*/
> >> /*.size = 0x32000000, */ /*800MB try*/
> >> /*0x1BF00000, 400MB rajmohan*/ /*0xC800000*/
> >> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
> >> JAILHOUSE_MEM_EXECUTE | JAILHOUSE_MEM_DMA |
> >> JAILHOUSE_MEM_LOADABLE,
> >> },
> >>
> >> BTW, I would recommend to cleanup your configs. They are... hard to read
> >> now.
> >>
> >> Jan
> >> --
> >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> >> Corporate Competence Center Embedded Linux
> >
> > Hi Jan,
> >
> > From the above config, pci_mmconfig_base = 0x80000000(2GB) & phys_start =
> > 0x404300000, size is 0xC0000000 (1GB)Our hypervisor start addresses is
> > 0x400000000(16Gb).
> > How will they conflict?
>
> From the guest POV, RAM starts at 0x00200000, and that actually
> conflicts both the MMCONFIG and the shared memory region.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux
Hi Jan,
>From my non rootcell config,I can see that RAM virtual start address is
>0x00200000. How it will conflict with shared memory and MMconfig
Regards,
Anil
/* high RAM */
{
.phys_start = 0x404300000/*0x401100000*/,
.virt_start = 0x00200000,
.size = 0xC0000000, /*1GB*/
/*0x1BF00000*/ /*0xC800000*/
.flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
JAILHOUSE_MEM_EXECUTE | JAILHOUSE_MEM_DMA |
JAILHOUSE_MEM_LOADABLE,
},
/* MemRegion: 404100000 : IVSHMEM :JH-added */
{
.phys_start = 0x404100000,
.virt_start = 0x404100000,
.size = 0x100000,
.flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
JAILHOUSE_MEM_ROOTSHARED,
},
Regards,
Anil
--
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].
For more options, visit https://groups.google.com/d/optout.
