Re: jailhouse config size issue while accessing memory region

[Henning Schild]

Am Wed, 21 Mar 2018 09:45:09 -0700
schrieb :

> On Wednesday, March 21, 2018 at 8:54:00 PM UTC+5:30, Henning Schild
> wrote:
> > Am Wed, 21 Mar 2018 07:31:43 -0700
> > schrieb :
> >   
> > > Hi Jan,
> > > we are working on jailhouse on x86 and facing some issues with
> > > system(root cell) config. This is one of the issue while
> > > accessing /proc/iomem for our system x86 (xeon)
> > > 
> > >   7933d018-7933d018 : APEI ERST
> > >   7933d01c-7933d021 : APEI ERST
> > >   7933d028-7933d039 : APEI ERST
> > >   7933d040-7933d04c : APEI ERST
> > >   7933d050-7933f04f : APEI ERST  
> > 
> > This is just a part of /proc/iomem, so far i do not understand where
> > the issue/problem is.
> >   
> > > we are doing memory size check  while accessing memory regions
> > > from rootcell config.  
> > 
> > What does that mean? Did you modify jailhouse or are you processing
> > the configs somehow? Or are you talking about a check inside an
> > unmodified jailhouse?
> >   
> > > From the above information in /proc/iomem, jailhouse
> > > generating config file with "zero" size.  
> > 
> > The first line will result in size 0, in the others the size should
> > get rounded up to at least one page.
> >   
> > > we want to know is there any
> > > issue with creating size for some of the memory regions.  
> > 
> > The example you sent is incomplete and the generator might not be
> > able to handle those lines correctly. The start should be
> > page-alligned. On the Xeons i have, i see similar lines but they
> > are behind a "reserverd" and should be ignored.
> > 
> > Please send the output of "jailhouse config collect /tmp/target.tar"
> > and explain you problem in more detail.
> > 
> > Henning
> >   
> > > Regards,
> > > Anil
> > >  
> 
> Hi Henning,
> Thanks for your reply. please find my rootcell config generated by
> jailhouse and system /proc/iomem files. Regards,

The iomem-parser matched "reserved" and not "Reserved" when ignoring
regions. So in your case the regions where added. On my 4.14.28 box
the string is also "Reserved", i just sent a patch.
Please apply it to your jailhouse and let me know if it works.

Henning 

> 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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jailhouse config size issue while accessing memory region

[Anil Kumar]

Hi Alex,
Thanks for your reply. Yes since my system has this configuration,
jailhouse is generating this memory size "0". But I don't want to create
memory region with "0" size. Because no one can either read/write into this
region. so I want to give some size or don't want to create such a memory
region while configuring and I don't want to change after creating system
config. I want to take care of this while generating system config.Can you
please suggest some thoughts.
Regards,
Anil

On Thu, Mar 22, 2018 at 1:28 PM,  wrote:

> Hi,
>
> Well, the config script reads, parses and generates the memory regions
> based on your system /proc/iomem layout.
>
> In your attachment, you have:
>
> 79162000-79a5efff : Reserved
>   7933d018-7933d018 : APEI ERST
>   7933d01c-7933d021 : APEI ERST
>
> This will restult in zero-sized memory regions in the generated root cell.
> Please check your host setup.
>
> -Alex
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jailhouse" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jailhouse-dev/H0NxGoDOV9I/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jailhouse-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jailhouse config size issue while accessing memory region

[alex . ciobotaru]

Hi,

Well, the config script reads, parses and generates the memory regions based on 
your system /proc/iomem layout.

In your attachment, you have:

79162000-79a5efff : Reserved
  7933d018-7933d018 : APEI ERST
  7933d01c-7933d021 : APEI ERST

This will restult in zero-sized memory regions in the generated root cell. 
Please check your host setup.

-Alex

-- 
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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jailhouse config size issue while accessing memory region

[anilappana]

On Wednesday, March 21, 2018 at 8:54:00 PM UTC+5:30, Henning Schild wrote:
> Am Wed, 21 Mar 2018 07:31:43 -0700
> schrieb :
> 
> > Hi Jan,
> > we are working on jailhouse on x86 and facing some issues with
> > system(root cell) config. This is one of the issue while
> > accessing /proc/iomem for our system x86 (xeon)
> > 
> >   7933d018-7933d018 : APEI ERST
> >   7933d01c-7933d021 : APEI ERST
> >   7933d028-7933d039 : APEI ERST
> >   7933d040-7933d04c : APEI ERST
> >   7933d050-7933f04f : APEI ERST
> 
> This is just a part of /proc/iomem, so far i do not understand where
> the issue/problem is.
> 
> > we are doing memory size check  while accessing memory regions from
> > rootcell config.
> 
> What does that mean? Did you modify jailhouse or are you processing the
> configs somehow? Or are you talking about a check inside an unmodified
> jailhouse?
> 
> > From the above information in /proc/iomem, jailhouse
> > generating config file with "zero" size.
> 
> The first line will result in size 0, in the others the size should get
> rounded up to at least one page.
> 
> > we want to know is there any
> > issue with creating size for some of the memory regions.
> 
> The example you sent is incomplete and the generator might not be able
> to handle those lines correctly. The start should be page-alligned.
> On the Xeons i have, i see similar lines but they are behind a
> "reserverd" and should be ignored.
> 
> Please send the output of "jailhouse config collect /tmp/target.tar"
> and explain you problem in more detail.
> 
> Henning
> 
> > Regards,
> > Anil
> >

Hi Henning,
Thanks for your reply. please find my rootcell config generated by jailhouse 
and system /proc/iomem files.
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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
sudo  cat /proc/iomem 
[sudo] password for xeon: 
-0fff : Reserved
1000-000997ff : System RAM
00099800-0009 : Reserved
000a-000b : PCI Bus :00
000c-000c7fff : Video ROM
000c8000-000c8fff : Adapter ROM
000c9000-000c9fff : Adapter ROM
000ca000-000cafff : Adapter ROM
000e-000f : Reserved
  000f-000f : System ROM
0010-3aff : System RAM
3b00-6eff : Reserved
6f00-79161fff : System RAM
79162000-79a5efff : Reserved
  7933d018-7933d018 : APEI ERST
  7933d01c-7933d021 : APEI ERST
  7933d028-7933d039 : APEI ERST
  7933d040-7933d04c : APEI ERST
  7933d050-7933f04f : APEI ERST
79a5f000-79f77fff : ACPI Non-volatile Storage
79f78000-8fff : Reserved
  8000-8fff : PCI MMCONFIG  [bus 00-ff]
9000-c7ffbfff : PCI Bus :00
  9000-900f : PCI Bus :03
9000-9001 : :03:00.0
9002-9003 : :03:00.0
9004-9005 : :03:00.1
9006-9007 : :03:00.1
  c600-c70f : PCI Bus :05
c600-c70f : PCI Bus :06
  c600-c6ff : :06:00.0
  c700-c701 : :06:00.0
  c710-c71f : PCI Bus :03
c710-c711 : :03:00.1
  c710-c711 : igb
c712-c713 : :03:00.0
  c712-c713 : igb
c714-c7143fff : :03:00.1
  c714-c7143fff : igb
c7144000-c7147fff : :03:00.0
  c7144000-c7147fff : igb
  c720-c72f : PCI Bus :01
c720-c721 : :01:00.1
c722-c723 : :01:00.1
  c722-c723 : e1000e
c724-c725 : :01:00.1
  c724-c725 : e1000e
c726-c727 : :01:00.0
c728-c729 : :01:00.0
  c728-c729 : e1000e
c72a-c72b : :01:00.0
  c72a-c72b : e1000e
  c730-c730 : :00:14.0
c730-c730 : xhci-hcd
  c731-c7313fff : :00:04.7
c731-c7313fff : ioatdma
  c7314000-c7317fff : :00:04.6
c7314000-c7317fff : ioatdma
  c7318000-c731bfff : :00:04.5
c7318000-c731bfff : ioatdma
  c731c000-c731 : :00:04.4
c731c000-c731 : ioatdma
  c732-c7323fff : :00:04.3
c732-c7323fff : ioatdma
  c7324000-c7327fff : :00:04.2
c7324000-c7327fff : ioatdma
  c7328000-c732bfff : :00:04.1
c7328000-c732bfff : ioatdma
  c732c000-c732 : :00:04.0
c732c000-c732 : ioatdma
  c7331000-c73310ff : :00:1f.3
  c7332000-c73327ff : :00:1f.2
c7332000-c73327ff : ahci
  c7333000-c7ff : :00:1d.0
c7333000-c7ff : ehci_hcd
  c7334000-c73343ff : :00:1a.0
c7334000-c73343ff : ehci_hcd
  c7336000-c733600f : :00:16.1
  c7337000-c733700f : :00:16.0
  c7338000-c73387ff : :00:11.4
c7338000-c73387ff : ahci
  c7339000-c7339fff : :00:05.4
c7ffc000-c7ffcfff : dmar1
c800-fbffbfff : PCI Bus :80
  fbf0-fbf03fff : :80:04.7
fbf0-fbf03fff 

Re: jailhouse config size issue while accessing memory region

[Henning Schild]

Am Wed, 21 Mar 2018 07:31:43 -0700
schrieb :

> Hi Jan,
> we are working on jailhouse on x86 and facing some issues with
> system(root cell) config. This is one of the issue while
> accessing /proc/iomem for our system x86 (xeon)
> 
>   7933d018-7933d018 : APEI ERST
>   7933d01c-7933d021 : APEI ERST
>   7933d028-7933d039 : APEI ERST
>   7933d040-7933d04c : APEI ERST
>   7933d050-7933f04f : APEI ERST

This is just a part of /proc/iomem, so far i do not understand where
the issue/problem is.

> we are doing memory size check  while accessing memory regions from
> rootcell config.

What does that mean? Did you modify jailhouse or are you processing the
configs somehow? Or are you talking about a check inside an unmodified
jailhouse?

> From the above information in /proc/iomem, jailhouse
> generating config file with "zero" size.

The first line will result in size 0, in the others the size should get
rounded up to at least one page.

> we want to know is there any
> issue with creating size for some of the memory regions.

The example you sent is incomplete and the generator might not be able
to handle those lines correctly. The start should be page-alligned.
On the Xeons i have, i see similar lines but they are behind a
"reserverd" and should be ignored.

Please send the output of "jailhouse config collect /tmp/target.tar"
and explain you problem in more detail.

Henning

> 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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jailhouse config size issue while accessing memory region

[anilappana]

Hi Jan,
we are working on jailhouse on x86 and facing some issues with system(root 
cell) config. This is one of the issue while accessing /proc/iomem for our 
system x86 (xeon)

  7933d018-7933d018 : APEI ERST
  7933d01c-7933d021 : APEI ERST
  7933d028-7933d039 : APEI ERST
  7933d040-7933d04c : APEI ERST
  7933d050-7933f04f : APEI ERST

we are doing memory size check  while accessing memory regions from rootcell 
config. From the above information in /proc/iomem, jailhouse generating config 
file with "zero" size. we want to know is there any issue with creating size 
for some of the memory regions.

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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.