Mailing List Archive

Hi,

On 4 Mar 2020, at 10:40, Subhasree P V <subhasree.pv@pathpartnertech.com<mailto:subhasree.pv@pathpartnertech.com>> wrote:

Hi,
I have been working with using XEN on ODROID-XU4 board.I would like to optimize the boot time of XEN to 3s. Currently it is taking about 5s to boot.I have disabled the prints.There is about 4s delay before kernel load.
Below is the log before disabling prints.

[2020-02-13 12:53:18.791] (XEN) Brought up 8 CPUs
[2020-02-13 12:53:18.791] (XEN) P2M: 40-bit IPA
[2020-02-13 12:53:18.791] (XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
[2020-02-13 12:53:18.797] (XEN) I/O virtualisation disabled
[2020-02-13 12:53:18.802] (XEN) *** LOADING DOMAIN 0 ***
[2020-02-13 12:53:18.802] (XEN) Loading kernel from boot module @ 0000000060000000
[2020-02-13 12:53:18.808] (XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
[2020-02-13 12:53:19.578] (XEN) BANK[0] 0x00000070000000-0x000000b0000000 (1024MB)
[2020-02-13 12:53:19.578] (XEN) Grant table range: 0x000000be800000-0x000000be861000
[2020-02-13 12:53:19.624] (XEN) Loading zImage from 0000000060000000 to 0000000077c00000-0000000077f08f60
[2020-02-13 12:53:19.649] (XEN) Allocating PPI 16 for event channel interrupt
[2020-02-13 12:53:19.649] (XEN) Loading dom0 DTB to 0x0000000078000000-0x000000007800c2f0
[2020-02-13 12:53:19.654] (XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs

You probably want to disable scrubbing memory to speed up your boot (add bootscrub=no to your command line).

Regards
Bertrand


[2020-02-13 12:53:19.915] (XEN) ..done.
[2020-02-13 12:53:20.168] (XEN) Initial low memory virq threshold set at 0x4000 pages.
[2020-02-13 12:53:20.174] (XEN) Std. Loglevel: All
[2020-02-13 12:53:20.174] (XEN) Guest Loglevel: All
[2020-02-13 12:53:20.174] (XEN) Freed 264kB init memory.
[2020-02-13 12:53:24.274] [ 0.000000] [c0] Booting Linux on physical CPU 0x0


I'm getting a delay after Freed 264kB init memory.I'm not able to figure out the reason for delay.Is there any way to reduce the delay?Please help me to solve this.


Thank you.


This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org<mailto:Xen-users@lists.xenproject.org>
https://lists.xenproject.org/mailman/listinfo/xen-users

Thank you so much for your reply Bertrand.I have done it and was able to
reduce about 520ms time.
But still the delay before kernel load is the same.I think it is the time
taken for the processing the interrupts.about 4s delay is there before
kernel load.You can see it in the below log.

[2020-03-06 10:23:32.817] (XEN) Freed 264kB init memory.
[2020-03-06 10:23:36.719] [ 0.000000] [c0] Booting Linux on physical CPU
0x0
[2020-03-06 10:23:36.719] [ 0.000000] [c0] Initializing cgroup subsys cpu
[2020-03-06 10:23:36.724] [ 0.000000] [c0] Initializing cgroup subsys
cpuacct

I have tried by setting *GICH_V2_LR_MAINTENANCE_IRQ* only for non-hardware
irqs and avoiding for hardware irqs.1s reduction in the delay has been
there when i have done so.But dom0 kernel was not loading completely while
doing so.It was hanging at some point.I thought the delay might be because
of too much inflight irqs.Could you please help me to solve it.


Thanks & Regards,
Subhasree






On Thu, Mar 5, 2020 at 10:47 PM Bertrand Marquis <Bertrand.Marquis@arm.com>
wrote:

> Hi,
>
> On 4 Mar 2020, at 10:40, Subhasree P V <subhasree.pv@pathpartnertech.com>
> wrote:
>
> Hi,
> I have been working with using XEN on ODROID-XU4 board.I would like to
> optimize the boot time of XEN to 3s. Currently it is taking about 5s to
> boot.I have disabled the prints.There is about 4s delay before kernel load.
> Below is the log before disabling prints.
>
> [2020-02-13 12:53:18.791] (XEN) Brought up 8 CPUs
> [2020-02-13 12:53:18.791] (XEN) P2M: 40-bit IPA
> [2020-02-13 12:53:18.791] (XEN) P2M: 3 levels with order-1 root, VTCR
> 0x80003558
> [2020-02-13 12:53:18.797] (XEN) I/O virtualisation disabled
> [2020-02-13 12:53:18.802] (XEN) *** LOADING DOMAIN 0 ***
> [2020-02-13 12:53:18.802] (XEN) Loading kernel from boot module @
> 0000000060000000
> [2020-02-13 12:53:18.808] (XEN) Allocating 1:1 mappings totalling 1024MB
> for dom0:
> [2020-02-13 12:53:19.578] (XEN) BANK[0] 0x00000070000000-0x000000b0000000
> (1024MB)
> [2020-02-13 12:53:19.578] (XEN) Grant table range:
> 0x000000be800000-0x000000be861000
> [2020-02-13 12:53:19.624] (XEN) Loading zImage from 0000000060000000 to
> 0000000077c00000-0000000077f08f60
> [2020-02-13 12:53:19.649] (XEN) Allocating PPI 16 for event channel
> interrupt
> [2020-02-13 12:53:19.649] (XEN) Loading dom0 DTB to
> 0x0000000078000000-0x000000007800c2f0
> [2020-02-13 12:53:19.654] (XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
>
>
> You probably want to disable scrubbing memory to speed up your boot (add
> bootscrub=no to your command line).
>
> Regards
> Bertrand
>
>
> [2020-02-13 12:53:19.915] (XEN) ..done.
> [2020-02-13 12:53:20.168] (XEN) Initial low memory virq threshold set at
> 0x4000 pages.
> [2020-02-13 12:53:20.174] (XEN) Std. Loglevel: All
> [2020-02-13 12:53:20.174] (XEN) Guest Loglevel: All
> [2020-02-13 12:53:20.174] (XEN) Freed 264kB init memory.
> [2020-02-13 12:53:24.274] [ 0.000000] [c0] Booting Linux on physical
> CPU 0x0
>
>
> I'm getting a delay after Freed 264kB init memory.I'm not able to figure
> out the reason for delay.Is there any way to reduce the delay?Please help
> me to solve this.
>
>
> Thank you.
>
> This message contains confidential information and is intended only for
> the individual(s) named. If you are not the intended recipient, you are
> notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this mail and attached file/s is strictly
> prohibited. Please notify the sender immediately and delete this e-mail
> from your system. E-mail transmission cannot be guaranteed to be secured or
> error-free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore does
> not accept liability for any errors or omissions in the contents of this
> message, which arise as a result of e-mail transmission.
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-users
>
>
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

On 6 Mar 2020, at 05:50, Subhasree P V <subhasree.pv@pathpartnertech.com<mailto:subhasree.pv@pathpartnertech.com>> wrote:

Thank you so much for your reply Bertrand.I have done it and was able to reduce about 520ms time..

Nice.

But still the delay before kernel load is the same.I think it is the time taken for the processing the interrupts.about 4s delay is there before kernel load.You can see it in the below log.

[2020-03-06 10:23:32.817] (XEN) Freed 264kB init memory.
[2020-03-06 10:23:36.719] [ 0.000000] [c0] Booting Linux on physical CPU 0x0
[2020-03-06 10:23:36.719] [ 0.000000] [c0] Initializing cgroup subsys cpu
[2020-03-06 10:23:36.724] [ 0.000000] [c0] Initializing cgroup subsys cpuacct

I have tried by setting GICH_V2_LR_MAINTENANCE_IRQ only for non-hardware irqs and avoiding for hardware irqs.1s reduction in the delay has been there when i have done so.But dom0 kernel was not loading completely while doing so.It was hanging at some point.I thought the delay might be because of too much inflight irqs.Could you please help me to solve it.


You are probably missing IRQs in Linux when you did that as the maintenance IRQ is needed by the vGIC.

Regarding the delay you see between “Freed” and first linux message it might be interesting to check if this time is actually spent in Xen or in Linux because the Freed is the last message printed by Xen here.

I cannot setup a system now to do some investigation on this but boot time with xen is something I will be definitely look at in the next months.

Regards
Bertrand


Thanks & Regards,
Subhasree






On Thu, Mar 5, 2020 at 10:47 PM Bertrand Marquis <Bertrand.Marquis@arm.com<mailto:Bertrand.Marquis@arm.com>> wrote:
Hi,

On 4 Mar 2020, at 10:40, Subhasree P V <subhasree.pv@pathpartnertech.com<mailto:subhasree.pv@pathpartnertech.com>> wrote:

Hi,
I have been working with using XEN on ODROID-XU4 board.I would like to optimize the boot time of XEN to 3s. Currently it is taking about 5s to boot.I have disabled the prints.There is about 4s delay before kernel load.
Below is the log before disabling prints.

[2020-02-13 12:53:18.791] (XEN) Brought up 8 CPUs
[2020-02-13 12:53:18.791] (XEN) P2M: 40-bit IPA
[2020-02-13 12:53:18.791] (XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
[2020-02-13 12:53:18.797] (XEN) I/O virtualisation disabled
[2020-02-13 12:53:18.802] (XEN) *** LOADING DOMAIN 0 ***
[2020-02-13 12:53:18.802] (XEN) Loading kernel from boot module @ 0000000060000000
[2020-02-13 12:53:18.808] (XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
[2020-02-13 12:53:19.578] (XEN) BANK[0] 0x00000070000000-0x000000b0000000 (1024MB)

This step takes 800ms

[2020-02-13 12:53:19.578] (XEN) Grant table range: 0x000000be800000-0x000000be861000
[2020-02-13 12:53:19.624] (XEN) Loading zImage from 0000000060000000 to 0000000077c00000-0000000077f08f60
[2020-02-13 12:53:19.649] (XEN) Allocating PPI 16 for event channel interrupt
[2020-02-13 12:53:19.649] (XEN) Loading dom0 DTB to 0x0000000078000000-0x000000007800c2f0
[2020-02-13 12:53:19.654] (XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs

You probably want to disable scrubbing memory to speed up your boot (add bootscrub=no to your command line).

Regards
Bertrand


[2020-02-13 12:53:19.915] (XEN) ..done.
[2020-02-13 12:53:20.168] (XEN) Initial low memory virq threshold set at 0x4000 pages.
[2020-02-13 12:53:20.174] (XEN) Std. Loglevel: All
[2020-02-13 12:53:20.174] (XEN) Guest Loglevel: All
[2020-02-13 12:53:20.174] (XEN) Freed 264kB init memory.
[2020-02-13 12:53:24.274] [ 0.000000] [c0] Booting Linux on physical CPU 0x0


I'm getting a delay after Freed 264kB init memory.I'm not able to figure out the reason for delay.Is there any way to reduce the delay?Please help me to solve this.


Thank you.


This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org<mailto:Xen-users@lists.xenproject.org>
https://lists.xenproject.org/mailman/listinfo/xen-users



This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Hi,

I can't find the previous e-mail in my inbox. So I am answering to
Bertrand's e-mail.

On 06/03/2020 08:21, Bertrand Marquis wrote:
>
>> On 6 Mar 2020, at 05:50, Subhasree P V
>> <subhasree.pv@pathpartnertech.com
>> <mailto:subhasree.pv@pathpartnertech.com>> wrote:
>>
>> Thank you so much for your reply Bertrand.I have done it and was able
>> to reduce about 520ms time..
>
> Nice.
>
>> But still the delay before kernel load is the same.I think it is the
>> time taken for the processing the interrupts.about 4s delay is there
>> before kernel load.You can see it in the below log.
Do you have an early console setup? If not, the "delay" is mostly
because Linux has not yet initialized the console. This does not mean it
was because of interrupt processing... Linux is probably just
initializing itself.

>>
>> [2020-03-06 10:23:32.817] (XEN) Freed 264kB init memory.
>> [2020-03-06 10:23:36.719] [    0.000000] [c0] Booting Linux on
>> physical CPU 0x0
>> [2020-03-06 10:23:36.719] [    0.000000] [c0] Initializing cgroup
>> subsys cpu
>> [2020-03-06 10:23:36.724] [    0.000000] [c0] Initializing cgroup
>> subsys cpuacct
>>
>> I have tried by setting *GICH_V2_LR_MAINTENANCE_IRQ* only for
>> non-hardware irqs and avoiding for hardware irqs.1s reduction in the
>> delay has been there when i have done so.But dom0 kernel was not
>> loading completely while doing so.It was hanging at some point.I
>> thought the delay might be because of  too much inflight irqs.Could
>> you please help me to solve it.

The only reason we would request a maintenance IRQs is for virtual
interrupts and if the LRs are full.

So what did you try to avoid? Could you provide the exact version of Xen
your are using and the modification you tried?

>>
>
> You are probably missing IRQs in Linux when you did that as the
> maintenance IRQ is needed by the vGIC.
>
> Regarding the delay you see between “Freed” and first linux message it
> might be interesting to check if this time is actually spent in Xen or
> in Linux because the Freed is the last message printed by Xen here.
>
> I cannot setup a system now to do some investigation on this but boot
> time with xen is something I will be definitely look at in the next months.
>
> Regards
> Bertrand
>
>>
>> Thanks & Regards,
>> Subhasree
>>
>>
>>
>>
>>
>>
>> On Thu, Mar 5, 2020 at 10:47 PM Bertrand Marquis
>> <Bertrand.Marquis@arm.com <mailto:Bertrand.Marquis@arm.com>> wrote:
>>
>> Hi,
>>
>>> On 4 Mar 2020, at 10:40, Subhasree P V
>>> <subhasree.pv@pathpartnertech.com
>>> <mailto:subhasree.pv@pathpartnertech.com>> wrote:
>>>
>>> Hi,
>>> I have been working with using XEN on ODROID-XU4 board.I would
>>> like to optimize the boot time of XEN to 3s. Currently it is
>>> taking about 5s to boot.I have disabled the prints.There is about
>>> 4s delay before kernel load.
>>> Below is the log before disabling prints.
>>>
>>> [2020-02-13 12:53:18.791] (XEN) Brought up 8 CPUs
>>> [2020-02-13 12:53:18.791] (XEN) P2M: 40-bit IPA
>>> [2020-02-13 12:53:18.791] (XEN) P2M: 3 levels with order-1 root,
>>> VTCR 0x80003558
>>> [2020-02-13 12:53:18.797] (XEN) I/O virtualisation disabled
>>> [2020-02-13 12:53:18.802] (XEN) *** LOADING DOMAIN 0 ***
>>> [2020-02-13 12:53:18.802] (XEN) Loading kernel from boot module @
>>> 0000000060000000
>>> [2020-02-13 12:53:18.808] (XEN) Allocating 1:1 mappings totalling
>>> 1024MB for dom0:
>>> [2020-02-13 12:53:19.578] (XEN) BANK[0]
>>> 0x00000070000000-0x000000b0000000 (1024MB)
>>
>
> This step takes 800ms

Which is not surprising given a 1GB of memory is allocated. The
allocator will go through each page to mark them as inuse and also
assign to the domain.

A couple of years ago, Samsung gave a good talk about reducing boot time
on Xen (see [1]). This might be give you some clue where are the biggest
time spending.

Most of Xen boot time is spent on memory initialization (i.e setup_mm())
and dom0 memory allocation (i.e allocate_memory()).

>> This message contains confidential information and is intended only
>> for the individual(s) named.If you are not the intended recipient, you
>> are notified that disclosing, copying, distributing or taking any
>> action in reliance on the contents of this mail and attached file/s is
>> strictly prohibited. Please notify the sender immediately and delete
>> this e-mail from your system. E-mail transmission cannot be guaranteed
>> to be secured or error-free as information could be intercepted,
>> corrupted, lost, destroyed, arrive late or incomplete, or contain
>> viruses. The sender therefore does not accept liability for any errors
>> or omissions in the contents of this message, which arise as a result
>> of e-mail transmission.
>>

This is public mailing list, please configure your e-mail client to
remove the disclaimer.

Cheers,

[1]
https://static.sched.com/hosted_files/xensummit18/48/Xen_Summit2018_Samsung%20Automotive%20Virtualization.pdf

--
Julien Grall

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users

Hi,
Thank you for your reply.I have enabled the CONFIG_DEBUG_LL in
arch/arm/configs/odroidxu3_xen_defconfig and
arch/arm/configs/odroidxu3_defconfig.And now i'm getting the print like
[2020-03-06 16:05:53.443] (XEN) Guest Loglevel: All
[2020-03-06 16:05:53.443] (XEN) Freed 264kB init memory.
[2020-03-06 16:05:55.111] (XEN) DOM0: Uncompressing Linux... done, booting
the kernel.

and it is hanging there.But the print is not coming from XEN.it's coming
from arch/arm/boot/compressed/misc.c of dom0 linux.It's quiet confusing and
I couldn't figure out the problem.Please help


Regards,
Subhasree

On Fri, Mar 6, 2020 at 1:51 PM Bertrand Marquis <Bertrand.Marquis@arm.com>
wrote:

>
> On 6 Mar 2020, at 05:50, Subhasree P V <subhasree.pv@pathpartnertech.com>
> wrote:
>
> Thank you so much for your reply Bertrand.I have done it and was able to
> reduce about 520ms time..
>
>
> Nice.
>
> But still the delay before kernel load is the same.I think it is the time
> taken for the processing the interrupts.about 4s delay is there before
> kernel load.You can see it in the below log.
>
> [2020-03-06 10:23:32.817] (XEN) Freed 264kB init memory.
> [2020-03-06 10:23:36.719] [ 0.000000] [c0] Booting Linux on physical
> CPU 0x0
> [2020-03-06 10:23:36.719] [ 0.000000] [c0] Initializing cgroup subsys
> cpu
> [2020-03-06 10:23:36.724] [ 0.000000] [c0] Initializing cgroup subsys
> cpuacct
>
> I have tried by setting *GICH_V2_LR_MAINTENANCE_IRQ* only for
> non-hardware irqs and avoiding for hardware irqs.1s reduction in the delay
> has been there when i have done so.But dom0 kernel was not loading
> completely while doing so.It was hanging at some point.I thought the delay
> might be because of too much inflight irqs.Could you please help me to
> solve it.
>
>
> You are probably missing IRQs in Linux when you did that as the
> maintenance IRQ is needed by the vGIC.
>
> Regarding the delay you see between “Freed” and first linux message it
> might be interesting to check if this time is actually spent in Xen or in
> Linux because the Freed is the last message printed by Xen here.
>
> I cannot setup a system now to do some investigation on this but boot time
> with xen is something I will be definitely look at in the next months.
>
> Regards
> Bertrand
>
>
> Thanks & Regards,
> Subhasree
>
>
>
>
>
>
> On Thu, Mar 5, 2020 at 10:47 PM Bertrand Marquis <Bertrand.Marquis@arm.com>
> wrote:
>
>> Hi,
>>
>> On 4 Mar 2020, at 10:40, Subhasree P V <subhasree.pv@pathpartnertech.com>
>> wrote:
>>
>> Hi,
>> I have been working with using XEN on ODROID-XU4 board.I would like to
>> optimize the boot time of XEN to 3s. Currently it is taking about 5s to
>> boot.I have disabled the prints.There is about 4s delay before kernel load.
>> Below is the log before disabling prints.
>>
>> [2020-02-13 12:53:18.791] (XEN) Brought up 8 CPUs
>> [2020-02-13 12:53:18.791] (XEN) P2M: 40-bit IPA
>> [2020-02-13 12:53:18.791] (XEN) P2M: 3 levels with order-1 root, VTCR
>> 0x80003558
>> [2020-02-13 12:53:18.797] (XEN) I/O virtualisation disabled
>> [2020-02-13 12:53:18.802] (XEN) *** LOADING DOMAIN 0 ***
>> [2020-02-13 12:53:18.802] (XEN) Loading kernel from boot module @
>> 0000000060000000
>> [2020-02-13 12:53:18.808] (XEN) Allocating 1:1 mappings totalling 1024MB
>> for dom0:
>> [2020-02-13 12:53:19.578] (XEN) BANK[0] 0x00000070000000-0x000000b0000000
>> (1024MB)
>>
>>
> This step takes 800ms
>
> [2020-02-13 12:53:19.578] (XEN) Grant table range:
>> 0x000000be800000-0x000000be861000
>> [2020-02-13 12:53:19.624] (XEN) Loading zImage from 0000000060000000 to
>> 0000000077c00000-0000000077f08f60
>> [2020-02-13 12:53:19.649] (XEN) Allocating PPI 16 for event channel
>> interrupt
>> [2020-02-13 12:53:19.649] (XEN) Loading dom0 DTB to
>> 0x0000000078000000-0x000000007800c2f0
>> [2020-02-13 12:53:19.654] (XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
>>
>>
>> You probably want to disable scrubbing memory to speed up your boot (add
>> bootscrub=no to your command line).
>>
>> Regards
>> Bertrand
>>
>>
>> [2020-02-13 12:53:19.915] (XEN) ..done.
>> [2020-02-13 12:53:20.168] (XEN) Initial low memory virq threshold set at
>> 0x4000 pages.
>> [2020-02-13 12:53:20.174] (XEN) Std. Loglevel: All
>> [2020-02-13 12:53:20.174] (XEN) Guest Loglevel: All
>> [2020-02-13 12:53:20.174] (XEN) Freed 264kB init memory.
>> [2020-02-13 12:53:24.274] [ 0.000000] [c0] Booting Linux on physical
>> CPU 0x0
>>
>>
>> I'm getting a delay after Freed 264kB init memory.I'm not able to figure
>> out the reason for delay.Is there any way to reduce the delay?Please help
>> me to solve this.
>>
>>
>> Thank you.
>>
>> This message contains confidential information and is intended only for
>> the individual(s) named. If you are not the intended recipient, you are
>> notified that disclosing, copying, distributing or taking any action in
>> reliance on the contents of this mail and attached file/s is strictly
>> prohibited. Please notify the sender immediately and delete this e-mail
>> from your system. E-mail transmission cannot be guaranteed to be secured or
>> error-free as information could be intercepted, corrupted, lost, destroyed,
>> arrive late or incomplete, or contain viruses. The sender therefore does
>> not accept liability for any errors or omissions in the contents of this
>> message, which arise as a result of e-mail transmission.
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xenproject.org
>> https://lists.xenproject.org/mailman/listinfo/xen-users
>>
>>
>>
> This message contains confidential information and is intended only for
> the individual(s) named. If you are not the intended recipient, you are
> notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this mail and attached file/s is strictly
> prohibited. Please notify the sender immediately and delete this e-mail
> from your system. E-mail transmission cannot be guaranteed to be secured or
> error-free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore does
> not accept liability for any errors or omissions in the contents of this
> message, which arise as a result of e-mail transmission.
>
>
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

Hi,
I just need to make sure the delay is coming from xen or linux kernel.The
below print is coming from* decompress_kernel* function in
arch/arm/boot/compressed/misc.c.
*DOM0: Uncompressing Linux... done, booting the kernel.*

On Fri, Mar 6, 2020 at 5:10 PM Julien Grall <julien@xen.org> wrote:

> Hello,
>
> You seem to have dropped xen-users@ from the CC. Is there any reason for
> that?
>
> On 06/03/2020 11:25, Subhasree P V wrote:
> > Hi Julien,
> > Thanks for your reply.
> > Below is my current log after disabling the prints and enabling
> > CONFIG_DEBUG_LL in arch/arm/configs/odroidxu3_xen_defconfig and
> > arch/arm/configs/odroidxu3_defconfig.
> > [2020-03-06 16:05:51.039]
> > [2020-03-06 16:05:51.039] CPU: Exynos5422 @ 800 MHz
> > [2020-03-06 16:05:51.039] Model: Odroid XU4 based on EXYNOS5422
> > [2020-03-06 16:05:51.044] Board: Odroid XU4 based on EXYNOS5422
> > [2020-03-06 16:05:51.049] Type: xu4
> > [2020-03-06 16:05:51.049] DRAM: 2 GiB
> > [2020-03-06 16:05:51.183] MMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
> > [2020-03-06 16:05:51.275] MMC Device 0 ( SD ): 7.4 GiB
> > [2020-03-06 16:05:51.275] mmc_init: -5, time 3
> > [2020-03-06 16:05:51.288] *** Warning - bad CRC, using default
> environment
> > [2020-03-06 16:05:51.288]
> > [2020-03-06 16:05:51.447] In: serial
> > [2020-03-06 16:05:51.447] Out: serial
> > [2020-03-06 16:05:51.447] Err: serial
> > [2020-03-06 16:05:51.916] Kernel image @ 0x50000000 [ 0x000000 -
> 0x101700 ]
> > [2020-03-06 16:05:51.916] ## Flattened Device Tree blob at 42000000
> > [2020-03-06 16:05:51.922] Booting using the fdt blob at 0x42000000
> > [2020-03-06 16:05:51.932] reserving fdt memory region: addr=42000000
> > size=d000
> > [2020-03-06 16:05:51.932] Loading Device Tree to 4fff0000, end
> > 4fffffff ... OK
> > [2020-03-06 16:05:52.024]
> > [2020-03-06 16:05:52.025] Starting kernel ...
> > [2020-03-06 16:05:52.025]
> > [2020-03-06 16:05:52.050] (XEN) Checking for initrd in /chosen
> > [2020-03-06 16:05:52.573] Xen 4.6.0
> > [2020-03-06 16:05:52.573] (XEN) Generic Timer IRQ: phys=30 hyp=26
> > virt=27 Freq: 24000 KHz
> > [2020-03-06 16:05:52.579] (XEN) GICv2 initialization:
> > [2020-03-06 16:05:52.579] (XEN) gic_dist_addr=0000000010481000
> > [2020-03-06 16:05:52.584] (XEN) gic_cpu_addr=0000000010482000
> > [2020-03-06 16:05:52.590] (XEN) gic_hyp_addr=0000000010484000
> > [2020-03-06 16:05:52.590] (XEN) gic_vcpu_addr=0000000010486000
> > [2020-03-06 16:05:52.595] (XEN) gic_maintenance_irq=25
> > [2020-03-06 16:05:52.603] (XEN) GICv2: 256 lines, 8 cpus, secure (IID
> > 0200043b).
> > [2020-03-06 16:05:52.614] (XEN) Brought up 8 CPUs
> > [2020-03-06 16:05:52.614] (XEN) I/O virtualisation disabled
> > [2020-03-06 16:05:52.614] (XEN) *** LOADING DOMAIN 0 ***
> > [2020-03-06 16:05:52.619] (XEN) Loading kernel from boot module @
> > 0000000060000000
> > [2020-03-06 16:05:53.443] (XEN) Std. Loglevel: All
> > [2020-03-06 16:05:53.443] (XEN) Guest Loglevel: All
> > [2020-03-06 16:05:53.443] (XEN) Freed 264kB init memory.
> > [2020-03-06 16:05:55.111] (XEN) DOM0: Uncompressing Linux... done,
> > booting the kernel.
> >
> > I'm getting an additional print here now like
> > *(XEN) DOM0: Uncompressing Linux... done, booting the kernel.*
> > But it is coming from arch/arm/boot/compressed/misc.c of dom0 Linux and
> > hangs after that print.
>
> Don't you see any progress at all afterwards?
>
> > Upto "Freed 264kB init memory" my boot time is*1.418*s.But delay is
> > coming after that.
> >
> > In my previous logs without enabling CONFIG_DEBUG_LL i got prints like,
> >
> > [2020-03-06 10:23:31.406] Starting kernel ...
> > [2020-03-06 10:23:31.406]
> > [2020-03-06 10:23:31.432] (XEN) Checking for initrd in /chosen
> > [2020-03-06 10:23:31.954] Xen 4.6.0
> > [2020-03-06 10:23:31.954] (XEN) Generic Timer IRQ: phys=30 hyp=26
> > virt=27 Freq: 24000 KHz
> > [2020-03-06 10:23:31.960] (XEN) GICv2 initialization:
> > [2020-03-06 10:23:31.960] (XEN) gic_dist_addr=0000000010481000
> > [2020-03-06 10:23:31.965] (XEN) gic_cpu_addr=0000000010482000
> > [2020-03-06 10:23:31.971] (XEN) gic_hyp_addr=0000000010484000
> > [2020-03-06 10:23:31.971] (XEN) gic_vcpu_addr=0000000010486000
> > [2020-03-06 10:23:31.977] (XEN) gic_maintenance_irq=25
> > [2020-03-06 10:23:31.984] (XEN) GICv2: 256 lines, 8 cpus, secure (IID
> > 0200043b).
> > [2020-03-06 10:23:31.995] (XEN) Brought up 8 CPUs
> > [2020-03-06 10:23:31.995] (XEN) I/O virtualisation disabled
> > [2020-03-06 10:23:31.995] (XEN) *** LOADING DOMAIN 0 ***
> > [2020-03-06 10:23:32.001] (XEN) Loading kernel from boot module @
> > 0000000060000000
> > [2020-03-06 10:23:32.817] (XEN) Std. Loglevel: All
> > [2020-03-06 10:23:32.817] (XEN) Guest Loglevel: All
> > [2020-03-06 10:23:32.817] (XEN) Freed 264kB init memory.
> > [2020-03-06 10:23:36.719] [ 0.000000] [c0] Booting Linux on physical
> > CPU 0x0
> > [2020-03-06 10:23:36.719] [ 0.000000] [c0] Initializing cgroup subsys
> cpu
> > [2020-03-06 10:23:36.724] [ 0.000000] [c0] Initializing cgroup subsys
> > cpuacct
> >
> > Is that delay coming from xen or dom0 kernel.If it's from xen how could
> > i reduce it..
>
> I don't have enough data to now exactly where the bottlneck is. I would
> recommend to get early prink in Linux fully working so you have more log
> and timestamp to narrow it down.
>
> --
> Julien Grall
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

On 08/03/2020 10:59, Subhasree P V wrote:
> Hi,

Hi,

Please don't top post.

> I just need to make sure the delay is coming from xen or linux
> kernel.The below print is coming from*decompress_kernel* function in
> arch/arm/boot/compressed/misc.c.
> *DOM0: Uncompressing Linux... done, booting the kernel.*

Does the same configuration works on baremetal?

Another solution would be to add earlycon=xen on Linux command line (I
think this works on arm32 as well when CONFIG_SERIAL_EARLYCON=y).

Cheers,

--
Julien Grall

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users

Thank you for your reply Julien.I have searched for the "earlycon" option
in my linux-dom0.but i couldn't see that option in my Kconfig file.my dom0
version is 4.18.0-15-generic.


Thanks & Regards,
Subhasree P V


On Mon, Mar 9, 2020 at 3:48 PM Julien Grall <julien@xen.org> wrote:

>
>
> On 08/03/2020 10:59, Subhasree P V wrote:
> > Hi,
>
> Hi,
>
> Please don't top post.
>
> > I just need to make sure the delay is coming from xen or linux
> > kernel.The below print is coming from*decompress_kernel* function in
> > arch/arm/boot/compressed/misc.c.
> > *DOM0: Uncompressing Linux... done, booting the kernel.*
>
> Does the same configuration works on baremetal?
>
> Another solution would be to add earlycon=xen on Linux command line (I
> think this works on arm32 as well when CONFIG_SERIAL_EARLYCON=y).
>
> Cheers,
>
> --
> Julien Grall
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

Hi,
I'm currently working on boot time optimization of xen in ODROID XU4
Board.I have disabled the boot scrubbing and disabled the prints. My
current log for xen is like below.
[2020-03-10 14:42:21.018] Starting kernel ...
[2020-03-10 14:42:21.019]
[2020-03-10 14:42:21.043] (XEN) Checking for initrd in /chosen
[2020-03-10 14:42:21.561] Xen 4.6.0
[2020-03-10 14:42:21.574] (XEN) Brought up 8 CPUs
[2020-03-10 14:42:21.574] (XEN) *** LOADING DOMAIN 0 ***
[2020-03-10 14:42:22.870] (XEN) Freed 264kB init memory.
[2020-03-10 14:42:25.587] [ 0.000000] [c0] Booting Linux on physical CPU
0x0

I can see a delay of about 2.720s after Freed 264kB init memory and before
the dom0 kernel load.please see the below log

*[2020-03-10 14:42:22.870] (XEN) Freed 264kB init memory.[2020-03-10
14:42:25.587] [ 0.000000] [c0] Booting Linux on physical CPU 0x0*

I'm not able to figure out where the delay is actually coming from.Is it
the time taken for the processing of interrupts or for the kernel
initialization?Is there any way to reduce that delay?somebody please help
me to solve this.


Thanks & Regards,
subhasree

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

On 10 Mar 2020, at 08:46, Subhasree P V <subhasree.pv@pathpartnertech.com<mailto:subhasree.pv@pathpartnertech.com>> wrote:

Thank you for your reply Julien.I have searched for the "earlycon" option in my linux-dom0.but i couldn't see that option in my Kconfig file.my dom0 version is 4.18.0-15-generic.


You need to pass earlycon=xen in the linux command line, usually your linux command line should contain at least "console=hvc0 earlycon=xen” and other options depending on where your rootfs is.

Depending on how you boot this might be possible to set in uboot environment or in your grub configuration for example.

Regards
Bertrand


Thanks & Regards,
Subhasree P V


On Mon, Mar 9, 2020 at 3:48 PM Julien Grall <julien@xen.org<mailto:julien@xen.org>> wrote:


On 08/03/2020 10:59, Subhasree P V wrote:
> Hi,

Hi,

Please don't top post.

> I just need to make sure the delay is coming from xen or linux
> kernel.The below print is coming from*decompress_kernel* function in
> arch/arm/boot/compressed/misc.c.
> *DOM0: Uncompressing Linux... done, booting the kernel.*

Does the same configuration works on baremetal?

Another solution would be to add earlycon=xen on Linux command line (I
think this works on arm32 as well when CONFIG_SERIAL_EARLYCON=y).

Cheers,

--
Julien Grall


This message contains confidential information and is intended only for the individual(s) named. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this mail and attached file/s is strictly prohibited. Please notify the sender immediately and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secured or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission.

Hi,

I am not sure why a new thread has been started with a slightly
different title. Can't the discussion continue in the previous thread?

On 10/03/2020 11:06, Subhasree P V wrote:
> Hi,
> I'm currently working on boot time optimization of xen in ODROID XU4
> Board.I have disabled the boot scrubbing and disabled the prints. My
> current log for xen is like below.
> [2020-03-10 14:42:21.018] Starting kernel ...
> [2020-03-10 14:42:21.019]
> [2020-03-10 14:42:21.043] (XEN) Checking for initrd in /chosen
> [2020-03-10 14:42:21.561]  Xen 4.6.0
> [2020-03-10 14:42:21.574] (XEN) Brought up 8 CPUs
> [2020-03-10 14:42:21.574] (XEN) *** LOADING DOMAIN 0 ***
> [2020-03-10 14:42:22.870] (XEN) Freed 264kB init memory.
> [2020-03-10 14:42:25.587] [    0.000000] [c0] Booting Linux on physical
> CPU 0x0
>
> I can see a delay of about 2.720s after Freed 264kB init memory and
> before the dom0 kernel load.please see the below log
> *[2020-03-10 14:42:22.870] (XEN) Freed 264kB init memory.
> [2020-03-10 14:42:25.587] [    0.000000] [c0] Booting Linux on physical
> CPU 0x0*
> *
> *
> I'm not able to figure out where the delay is actually coming from.Is it
> the time taken for the processing of interrupts or for the kernel
> initialization?Is there any way to reduce that delay?somebody please
> help me to solve this.
>
>
> Thanks & Regards,
> subhasree
>
> **
> *
> *
> *
> *
>
> This message contains confidential information and is intended only for
> the individual(s) named.If you are not the intended recipient, you are
> notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this mail and attached file/s is strictly
> prohibited. Please notify the sender immediately and delete this e-mail
> from your system. E-mail transmission cannot be guaranteed to be secured
> or error-free as information could be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete, or contain viruses. The sender
> therefore does not accept liability for any errors or omissions in the
> contents of this message, which arise as a result of e-mail transmission.
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xenproject.org
> https://lists.xenproject.org/mailman/listinfo/xen-users
>

--
Julien Grall

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users

I'll try that. Thanks for your reply.

Regards
Subhasree

On Tue, Mar 10, 2020, 8:09 PM Bertrand Marquis <Bertrand.Marquis@arm.com>
wrote:

>
>
> On 10 Mar 2020, at 08:46, Subhasree P V <subhasree.pv@pathpartnertech.com>
> wrote:
>
> Thank you for your reply Julien.I have searched for the "earlycon" option
> in my linux-dom0.but i couldn't see that option in my Kconfig file.my dom0
> version is 4.18.0-15-generic.
>
>
> You need to pass earlycon=xen in the linux command line, usually your
> linux command line should contain at least "console=hvc0 earlycon=xen” and
> other options depending on where your rootfs is.
>
> Depending on how you boot this might be possible to set in uboot
> environment or in your grub configuration for example.
>
> Regards
> Bertrand
>
>
> Thanks & Regards,
> Subhasree P V
>
>
> On Mon, Mar 9, 2020 at 3:48 PM Julien Grall <julien@xen.org> wrote:
>
>>
>>
>> On 08/03/2020 10:59, Subhasree P V wrote:
>> > Hi,
>>
>> Hi,
>>
>> Please don't top post.
>>
>> > I just need to make sure the delay is coming from xen or linux
>> > kernel.The below print is coming from*decompress_kernel* function in
>> > arch/arm/boot/compressed/misc.c.
>> > *DOM0: Uncompressing Linux... done, booting the kernel.*
>>
>> Does the same configuration works on baremetal?
>>
>> Another solution would be to add earlycon=xen on Linux command line (I
>> think this works on arm32 as well when CONFIG_SERIAL_EARLYCON=y).
>>
>> Cheers,
>>
>> --
>> Julien Grall
>>
>
> This message contains confidential information and is intended only for
> the individual(s) named. If you are not the intended recipient, you are
> notified that disclosing, copying, distributing or taking any action in
> reliance on the contents of this mail and attached file/s is strictly
> prohibited. Please notify the sender immediately and delete this e-mail
> from your system. E-mail transmission cannot be guaranteed to be secured or
> error-free as information could be intercepted, corrupted, lost, destroyed,
> arrive late or incomplete, or contain viruses. The sender therefore does
> not accept liability for any errors or omissions in the contents of this
> message, which arise as a result of e-mail transmission.
>
>
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

Hi,

Please stop top-posting... I will not spend time helping if you continue
to ignore my request.

On 10/03/2020 08:46, Subhasree P V wrote:
> Thank you for your reply Julien.I have searched for the "earlycon"
> option in my linux-dom0.but i couldn't see that option in my Kconfig
> file.my dom0 version is 4.18.0-15-generic.

I have looked at v4.18 and earlycon exists. How did you pass the option
to Linux?

On a side note, why aren't you using the last stable for v4.18.x? More
importantly, why are you using an non-LTS kernel?

It feels slightly counterproductive to try to optimize on an
out-of-support kernel.

Cheers,

--
Julien Grall

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users

Sorry for the inconvenience Julien. I have top posted by mistake.Will
continue in the same thread.Thanks for your patience and help.

I have used the Linux-dom0 and xen which was provided in the odroid wiki.It
has support for the board.I don't think it is out of support kernel because
I was able to boot Dom0 and domu in odroid-xu4.I have added bootargs in
boot.ini by modifying it.but when I try to set earlycon, I couldn't see it
defined anywhere in linux dom0 that I'm using currently.I have downloaded
another Dom0 kernel and I was able to found earlycon in it.but not sure if
it has support for odroid-xu4.



Thanks & Regards
Subhasree

On Tue, Mar 10, 2020, 8:20 PM Julien Grall <julien@xen.org> wrote:

> Hi,
>
> Please stop top-posting... I will not spend time helping if you continue
> to ignore my request.
>
> On 10/03/2020 08:46, Subhasree P V wrote:
> > Thank you for your reply Julien.I have searched for the "earlycon"
> > option in my linux-dom0.but i couldn't see that option in my Kconfig
> > file.my dom0 version is 4.18.0-15-generic.
>
> I have looked at v4.18 and earlycon exists. How did you pass the option
> to Linux?
>
> On a side note, why aren't you using the last stable for v4.18.x? More
> importantly, why are you using an non-LTS kernel?
>
> It feels slightly counterproductive to try to optimize on an
> out-of-support kernel.
>
> Cheers,
>
> --
> Julien Grall
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

Hi

On 10/03/2020 15:05, Subhasree P V wrote:
> Sorry for the inconvenience Julien. I have top posted by mistake.Will
> continue in the same thread.Thanks for your patience and help.

Please read this [1].

>
> I have used the Linux-dom0 and xen which was provided in the odroid
> wiki.It has support for the board.I don't think it is out of support
> kernel because I was able to boot Dom0 and domu in odroid-xu4.I have
> added bootargs in boot.ini by modifying it.but when I try to set
> earlycon, I couldn't see it defined anywhere in linux dom0 that I'm
> using currently.I have downloaded another Dom0 kernel and I was able to
> found earlycon in it.but not sure if it has support for odroid-xu4.

Booting a kernel does not mean a community will support it.

By wiki, I guess you are referring to [2]. If so, this is a kernel
provided by the Odroid community (or a member of).

I am afraid, I am not going to support this. For new development, my
recommendation is to use newer (or LTS) kernel as they get bug/security
fixes.

If you want support on this specific kernel then please contact the
Odroid community.

Cheers,

> Thanks & Regards
> Subhasree

[1] https://en.wikipedia.org/wiki/Posting_style#Top-posting
[2]
https://wiki.odroid.com/odroid-xu4/application_note/software/xen_virtualization

--
Julien Grall

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users

Thank you for the clarification. I'll look into it.


Regards
Subhasree

On Tue, Mar 10, 2020, 8:49 PM Julien Grall <julien@xen.org> wrote:

> Hi
>
> On 10/03/2020 15:05, Subhasree P V wrote:
> > Sorry for the inconvenience Julien. I have top posted by mistake.Will
> > continue in the same thread.Thanks for your patience and help.
>
> Please read this [1].
>
> >
> > I have used the Linux-dom0 and xen which was provided in the odroid
> > wiki.It has support for the board.I don't think it is out of support
> > kernel because I was able to boot Dom0 and domu in odroid-xu4.I have
> > added bootargs in boot.ini by modifying it.but when I try to set
> > earlycon, I couldn't see it defined anywhere in linux dom0 that I'm
> > using currently.I have downloaded another Dom0 kernel and I was able to
> > found earlycon in it.but not sure if it has support for odroid-xu4.
>
> Booting a kernel does not mean a community will support it.
>
> By wiki, I guess you are referring to [2]. If so, this is a kernel
> provided by the Odroid community (or a member of).
>
> I am afraid, I am not going to support this. For new development, my
> recommendation is to use newer (or LTS) kernel as they get bug/security
> fixes.
>
> If you want support on this specific kernel then please contact the
> Odroid community.
>
> Cheers,
>
> > Thanks & Regards
> > Subhasree
>
> [1] https://en.wikipedia.org/wiki/Posting_style#Top-posting
> [2]
>
> https://wiki.odroid.com/odroid-xu4/application_note/software/xen_virtualization
>
> --
> Julien Grall
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.

oh the irony ...

On 3/10/20 7:42 AM, Julien Grall wrote:
> Hi,
>
> I am not sure why a new thread has been started with a slightly different title. Can't the discussion continue in the previous thread?
>
> On 10/03/2020 11:06, Subhasree P V wrote:
>> Hi,
>> I'm currently working on boot time optimization of xen in ODROID XU4 Board.I have disabled the boot scrubbing and disabled the prints. My current log for xen is like below.
>> [2020-03-10 14:42:21.018] Starting kernel ...
>> [2020-03-10 14:42:21.019]
>> [2020-03-10 14:42:21.043] (XEN) Checking for initrd in /chosen

On 3/10/20 7:50 AM, Julien Grall wrote:
> Hi,
>
> Please stop top-posting... I will not spend time helping if you continue to ignore my request.
>
> On 10/03/2020 08:46, Subhasree P V wrote:
>> Thank you for your reply Julien.I have searched for the "earlycon" option in my linux-dom0.but i couldn't see that option in my Kconfig file.my dom0 version is 4.18.0-15-generic.
>
> I have looked at v4.18 and earlycon exists. How did you pass the option to Linux?
>
> On a side note, why aren't you using the last stable for v4.18.x? More importantly, why are you using an non-LTS kernel?
>
> It feels slightly counterproductive to try to optimize on an out-of-support kernel.
>
> Cheers,
>

> On 10/03/2020 16:03, potsaid2kettle wrote:
>
> > oh the irony ...
>
> You are most welcomed to reveal your name and we can discuss when to
> top-post or not ;).

nah, it's enough fun watching u waste bits acting like a lame list mom in public

_______________________________________________
Xen-users mailing list
Xen-users@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-users

Hi,
I have checked if the delay is coming from kernel initialization.But I can
see that there is a 1.9s delay between Freed 264kB init memory and
*gic_update_one_lr
*.When i traced the function call I can see that entry point is from
*DEFINE_TRAP_ENTRY_NOIRQ
*in entry.S,and it's linked to do_trap_irq.S.So i'm afraid that it's coming
from xen itself.Any help on this is appreciated.

Thanks & Regards
subhasree

On Tue, Mar 10, 2020 at 8:58 PM Subhasree P V <
subhasree.pv@pathpartnertech.com> wrote:

> Thank you for the clarification. I'll look into it.
>
>
> Regards
> Subhasree
>
> On Tue, Mar 10, 2020, 8:49 PM Julien Grall <julien@xen.org> wrote:
>
>> Hi
>>
>> On 10/03/2020 15:05, Subhasree P V wrote:
>> > Sorry for the inconvenience Julien. I have top posted by mistake.Will
>> > continue in the same thread.Thanks for your patience and help.
>>
>> Please read this [1].
>>
>> >
>> > I have used the Linux-dom0 and xen which was provided in the odroid
>> > wiki.It has support for the board.I don't think it is out of support
>> > kernel because I was able to boot Dom0 and domu in odroid-xu4.I have
>> > added bootargs in boot.ini by modifying it.but when I try to set
>> > earlycon, I couldn't see it defined anywhere in linux dom0 that I'm
>> > using currently.I have downloaded another Dom0 kernel and I was able to
>> > found earlycon in it.but not sure if it has support for odroid-xu4.
>>
>> Booting a kernel does not mean a community will support it.
>>
>> By wiki, I guess you are referring to [2]. If so, this is a kernel
>> provided by the Odroid community (or a member of).
>>
>> I am afraid, I am not going to support this. For new development, my
>> recommendation is to use newer (or LTS) kernel as they get bug/security
>> fixes.
>>
>> If you want support on this specific kernel then please contact the
>> Odroid community.
>>
>> Cheers,
>>
>> > Thanks & Regards
>> > Subhasree
>>
>> [1] https://en.wikipedia.org/wiki/Posting_style#Top-posting
>> [2]
>>
>> https://wiki.odroid.com/odroid-xu4/application_note/software/xen_virtualization
>>
>> --
>> Julien Grall
>>
>

--






This
message contains confidential information and is intended only
for the
individual(s) named. If you are not the intended
recipient, you are
notified that disclosing, copying, distributing or taking any
action in
reliance on the contents of this mail and attached file/s is strictly

prohibited. Please notify the
sender immediately and delete this e-mail
from your system. E-mail transmission
cannot be guaranteed to be secured or
error-free as information could be
intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain
viruses. The sender therefore does
not accept liability for any errors or
omissions in the contents of this
message, which arise as a result of e-mail
transmission.