From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Omkar Bolla <omkar.bolla@pathpartnertech.com>,
xen-devel@lists.xensource.com
Subject: Re: Armv8-A: Not able to enable secondary CPUs in Hikey960 board
Date: Mon, 13 Aug 2018 09:01:14 -0400 [thread overview]
Message-ID: <20180813130114.GA14031@char.us.oracle.com> (raw)
In-Reply-To: <CAC4nxbtEJEnZ9o4hRqSwk_9hzJa1aCvNfGPTccvHRMAp7BvS4g@mail.gmail.com>
On Mon, Aug 13, 2018 at 11:16:14AM +0530, Omkar Bolla wrote:
> Hi,
>
> Thankyou very much Konrad,
> As you suggested, I just have started testing previous versions of Xen, and
> it is working with xen-4.7 stable branch.
Does Xen 4.8 or Xen 4.9 or Xen 4.10 work? Trying to get a bisection point working.
(My box is right now packed in a box - moving so can't help rightn ow).
> All secondary CPUs got enabled and started.
>
> If you any idea, please tell me Why latest xen is not working?
Adding xen-devel back.
>
> Thank you,
> Omkar B
>
> On Sat, Aug 11, 2018 at 10:36 PM, Konrad Rzeszutek Wilk <
> konrad.wilk@oracle.com> wrote:
>
> > On Sat, Aug 11, 2018 at 08:44:42PM +0530, Omkar Bolla wrote:
> > > Hi,
> > >
> > > I am using Hikey960 board and i started trying to port xen on hykey960.
> > >
> > > I followed all procedure has given in
> > > https://wiki.xenproject.org/wiki/HiKey960 link.
> > > And using *Xen version 4.11.1-pre *and linux as mentioned in above link.
> > >
> > > But, After flashing, I ended up with secondary CPUs errors and linux Dom0
> > > errors.
> > > Please give some suggestions to start xen with all CPUs.
> >
> > Oh that is weird. What happens if you use an older Xen release?
> >
> > >
> > > Please check below log:
> > > --------------------------------
> > > Using modules provided by bootloader in FDT
> > > Xen 4.11.1-pre (c/s Mon Jul 30 11:30:09 2018 +0200 git:33ced72) EFI
> > loader
> > > Xen 4.11.1-pre
> > > (XEN) Xen version 4.11.1-pre (omkar.bolla@) (aarch64-linux-gnu-gcc
> > (Linaro
> > > GCC 7.1-2017.05) 7.1.1 20170510) debug=n Sat Aug 11 20:35:10 IST 201
> > > 8
> > > (XEN) Latest ChangeSet: Mon Jul 30 11:30:09 2018 +0200 git:33ced72
> > > (XEN) Processor: 410fd034: "ARM Limited", variant: 0x0, part 0xd03, rev
> > 0x4
> > > (XEN) 64-bit Execution:
> > > (XEN) Processor Features: 0000000000002222 0000000000000000
> > > (XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
> > > (XEN) Extensions: FloatingPoint AdvancedSIMD
> > > (XEN) Debug Features: 0000000010305106 0000000000000000
> > > (XEN) Auxiliary Features: 0000000000000000 0000000000000000
> > > (XEN) Memory Model Features: 0000000000001122 0000000000000000
> > > (XEN) ISA Features: 0000000000011120 0000000000000000
> > > (XEN) 32-bit Execution:
> > > (XEN) Processor Features: 00000131:00011011
> > > (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> > > (XEN) Extensions: GenericTimer Security
> > > (XEN) Debug Features: 03010066
> > > (XEN) Auxiliary Features: 00000000
> > > (XEN) Memory Model Features: 10201105 40000000 01260000 02102211
> > > (XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142
> > 00011121
> > > (XEN) Using SMC Calling Convention v1.1
> > > (XEN) Using PSCI v1.1
> > > (XEN) SMP: Allowing 8 CPUs
> > > (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 1920 KHz
> > > (XEN) GICv2 initialization:
> > > (XEN) gic_dist_addr=00000000e82b1000
> > > (XEN) gic_cpu_addr=00000000e82b2000
> > > (XEN) gic_hyp_addr=00000000e82b4000
> > > (XEN) gic_vcpu_addr=00000000e82b6000
> > > (XEN) gic_maintenance_irq=25
> > > (XEN) GICv2: 384 lines, 8 cpus, secure (IID 0200143b).
> > > (XEN) Using scheduler: SMP Credit Scheduler (credit)
> > > (XEN) Allocated console ring of 64 KiB.
> > > (XEN) Bringing up CPU1
> > > (XEN) Failed to bring up CPU1
> > > (XEN) Failed to bring up CPU 1 (error -9)
> > ..
> >
>
> --
>
>
>
>
>
>
> 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-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-13 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-11 15:14 Armv8-A: Not able to enable secondary CPUs in Hikey960 board Omkar Bolla
2018-08-11 17:06 ` Konrad Rzeszutek Wilk
[not found] ` <CAC4nxbtEJEnZ9o4hRqSwk_9hzJa1aCvNfGPTccvHRMAp7BvS4g@mail.gmail.com>
2018-08-13 13:01 ` Konrad Rzeszutek Wilk [this message]
2018-08-13 15:10 ` Julien Grall
2018-08-15 9:15 ` Omkar Bolla
2018-08-15 18:22 ` Julien Grall
2018-08-20 9:46 ` Omkar Bolla
2018-08-21 18:37 ` Julien Grall
2018-08-15 8:07 ` Omkar Bolla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180813130114.GA14031@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=omkar.bolla@pathpartnertech.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).