Re: I got an issue, when testing command like this :qemu–system–aarch64 -kernel uimage -smp 2...

2018-03-13 Thread Adam Lackorzynski

On Tue Mar 13, 2018 at 11:40:37 +, Jiang qihong wrote:
> The whole command , qemu–system–aarch64 -kernel uimage -M vexpress -a15 -cpu 
> cortex-a57 -smp 2 -m256 --nographic 
> The issue is that when running into shell, i didn't find  two cpus.
> The parameter "-smp 2",didn't work. 
> Does qemu support arch arm -v8 when using the parameter(-smp)? 

Currently, the code to boot up secondary cores on the QEMU rv/vexpress
platform is missing in Fiasco for arm64, i.e. your observation is right,
that only a single core comes up. This is being worked on.


Adam

___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: How to show call path in backtrace with jdb?

2018-03-13 Thread Adam Lackorzynski
Hi,

On Tue Mar 13, 2018 at 11:58:57 +0800, Zihan Yang wrote:
> I'm trying to debug L4Linux using jdb in Fiasco. I have added a
> breakpoint in a function(e.g, syscall_exit), and it did hit into jdb
> when I run. However, when I type 'bt' in jdb, it only prints the
> values in the stack, or worse, it sometimes couldn't print the stack.

> I have tried enabling L4_DEBUG_REGISTER_NAMES and CONFIG_FRAME_POINTER
> in L4Linux, and uncheck 'config without frame pointer' and 'generate
> inline code' options in Fiasco, but still it doesn't work.
> 
> QEMU could be an option, but qemu debugs the whole system while I just
> want to focus on the L4Linux itself because I just want to figure out
> the call path of ret_from_fork and how does L4Linux stop the user
> dispatch loop, etc.
> 
> Is there any way to show the the call path in jdb to assist the debugging 
> work?

There's not really such a feature in jdb to assist with that.
I think reading code is the better approach here.
 
> By way, is there any doc describing the call path from fiasco to
> L4Linux, I know it is implemented with sysretq or iretq, but where is
> the entrypoint in L4Linux? For example, when I type 'ls /bin' in
> shell, it would finally go into L4Linux's function 'syscall_exit()',
> but how can I find the call path between them? If I can figure it out,
> maybe I just don't need to debug anymore.

All this entry to Linux and exit from it (to the user process) is
happening in arch/l4/kernel/dispatch.c. There's the entry point
(l4x_vcpu_entry) and that's the path to follow. In there it will branch
to syscall handling, page fault handling, irq handling, or exception
handling, depending on the type of entry.


Adam

___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


Re: I got an issue, when testing command like this :qemu–system–aarch64 -kernel uimage -smp 2...

2018-03-13 Thread Matthias Lange
Hi,

On [13-03-2018 11:40], Jiang qihong wrote:
> The whole command , qemu–system–aarch64 -kernel uimage -M vexpress -a15 -cpu 
> cortex-a57 -smp 2 -m256 --nographic 
> The issue is that when running into shell, i didn't find  two cpus.

In order to debug your problem further it would be nice if you could provide a
little more information about your setup.

Which version of Fiasco are you using (snapshot or public development
version)?

Is CONFIG_MP in your Fiasco configuration enabled?

Please also attach the report generated by "make report" from your L4Re build
directory.

Regards,
Matthias.

> The parameter "-smp 2",didn't work. 
> Does qemu support arch arm -v8 when using the parameter(-smp)? 
> 
> From  jqh mobile phone. 
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers

-- 
Matthias Lange, matthias.la...@kernkonzept.com, +49-351-41 888 614

Kernkonzept GmbH.  Sitz: Dresden.  Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth


___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers


I got an issue, when testing command like this :qemu–system–aarch64 -kernel uimage -smp 2...

2018-03-13 Thread Jiang qihong
The whole command , qemu–system–aarch64 -kernel uimage -M vexpress -a15 -cpu 
cortex-a57 -smp 2 -m256 --nographic 
The issue is that when running into shell, i didn't find  two cpus.
The parameter "-smp 2",didn't work. 
Does qemu support arch arm -v8 when using the parameter(-smp)? 

From  jqh mobile phone. 
___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers