Giter Club home page Giter Club logo

pistachio's People

Contributors

jkehne avatar jstoess avatar ksandstr avatar ssumpf avatar xyzwvut avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

pistachio's Issues

Missing glue/v4-powerpc64/ipc.h?

Hi,

I've recently been trying to build Pistachio, using the POWER4 configuration, on a little-endian POWER9 machine (I'm trying to do a baseline build, so I can start porting the kernel to Cell, and POWER9), using GCC 9.2.1 (which isn't obviously a supported configuration), and despite making reasonable progress (was necessary to change

 cmp 
, to
 cmpd
, in kernel/src/platform/ofpower4/head.S, and patch up some other source files), I'm getting stuck with a missing tcb_layout.h, and asmsyms.h, to build more of the kernel, but I can't generate these, since ipc.h seems to be missing, for some reason.

Is this intentional? If not, is it safe to copy the 32-bit version, if I want to continue on with my project? (Documenting my adventures, in vmlemon/Orion#1, at the moment).

Thanks in advance...

Contrib Scripts don't work with Python 3

While trying to build this software I've come across a problem on more modern systems.
The python scripts in the contrib folder are just meant to be used with Python 2.

It points to /usr/bin/env python which (on todays systems) is almost always Pyton 3.
Sadly the scripts are NOT Python 3 compatible and tells the user to use Python 2.0 or later which Python 3 technically is.

Manually changing the required interpreter fixes the issue.

Missing tcb_layout.h

After following each step:

    make BUILDDIR=$dir
    cd $dir
    make menuconfig
    make

Compiler returns error 2:
    ===> Generating include/tcb_layout.h
    x86_64-unknown-linux-gnu-cpp: erreur fatale: pas de fichier à l'entrée
    compilation terminée.
    x86_64-unknown-linux-gnu-cpp: erreur fatale: pas de fichier à l'entrée
    compilation terminée.
    x86_64-unknown-linux-gnu-cpp: erreur fatale: pas de fichier à l'entrée
    compilation terminée.
    x86_64-unknown-linux-gnu-cpp: erreur fatale: pas de fichier à l'entrée
    compilation terminée.
    ===>
    ===> Generating tcb_layout.h FAILED!!!

("erreur fatale: pas de fichier à l'entrée" = "fatal error: no input file")

Sending string between address spaces on AMD64

Kernel goes to an infinity loop when sending string between address spaces on AMD64

Problem detected around line 406 of pistachio/kernel/src/glue/v4-x86/space.cc

enter_kdebug("ENTER: dst_pgent  ->set_entry");
dst_pgent  ->set_entry (this, pgsize, *src_pgent  );
enter_kdebug("LEAVE: dst_pgent  ->set_entry");

Debugging steps between "ENTER" and "LEAVE" avoids the problem until next call.
Continue running on "ENTER" will cause kernel to go to an infinity loop.

Problem has been reproduced under VMWare.

config.h:

/* Linux version 2.6.37.6 (root@midas64) (gcc version 4.5.2 (GCC) ) #3 SMP Sat Apr 9 22:49:32 CDT 2011 */

define CONFIG_ARCH_X86 1

define CONFIG_SUBARCH_X64 1

define CONFIG_CPU_X86_K8 1

define CONFIG_PLAT_PC99 1

define CONFIG_EXPERIMENTAL 1

define CONFIG_X_PAGER_EXREGS 1

define CONFIG_SCHED_RR 1

define CONFIG_DEBUG 1

define CONFIG_K8_FLUSHFILTER 1

define CONFIG_NEW_MDB 1

define CONFIG_STATIC_TCBS 1

define CONFIG_KDB_DISAS 1

define CONFIG_KDB_ON_STARTUP 1

define CONFIG_KDB_INPUT_HLT 1

define CONFIG_X86_PSE 1

define CONFIG_X86_SYSENTER 1

define CONFIG_X86_PGE 1

define CONFIG_X86_FXSR 1

define CONFIG_X86_PAT 1

define CONFIG_IS_64BIT 1

define CONFIG_X86_TSC 1

define AUTOCONF_INCLUDED

sigma0 on AMD64

sigma0 issue:

OLD_STYLE_MEMORY_REGIONS works perfect, but NEW_STYLE_MEMORY_REGIONS does not allocate new pages on AMD64

Conflict with multiboot for x86_64.

I ran this kernel for x86_64 and kickstart displayed message about conflict with multiboot 0 (0x00600000-0x401084a8) module. Used tools to compilation and launching:
gcc 4.6.3 and 4.4.7
binutils 2.22
qemu 1.0

Bug at bswap64.

The bswap64 function has the argument with incorrect type at kernel/src/arch/x86/x64/byteorder.h. This argument should have the u64_t type instead of the u32_t type.

L4_BootInfo_t on AMD64

unsigned int                    i;
L4_MemoryDesc_t     *   mbi_desc = 0;

    printf( "L4_NumMemoryDescriptors = %ld\n", L4_NumMemoryDescriptors(kip));
    for(i=0; i < L4_NumMemoryDescriptors(kip); i++)
    {
        L4_MemoryDesc_t * mdesc = L4_MemoryDesc( kip, i );
        if( L4_MemoryDescType (mdesc) == (L4_BootLoaderSpecificMemoryType | 0x10) )
        {
            printf("Found BootLoaderSpecificMemoryType at %p\n", (void*) L4_MemoryDescLow(mdesc));
            mbi_desc = mdesc;
            break;
        }
    }

This code works perfect on x86-32bit, but does not work on AMD64.

Kernel doesn't display anything.

I compiled kernel and user applications for x86-32 and ran under qemu. Used tools to compilation and launching:
gcc 4.6.3 and 4.4.7
binutils 2.22
qemu 1.0

I used qemu monitor to check what heppened. The eip register had value 0x0000000000403591 after launching of kernel. This addres was in memory area of pingpong.

Memory Descriptor Overflow

Hi,

I've just built the latest Git revision under Ubuntu, including the userland, and I receive the following error, when attempting to run l4test under QEMU:

L4Ka::Pistachio - built on May  3 2014 16:59:50 by tyson@tyson-VirtualBox using gcc version 4.8.1
Checking CPU features
virtual memory layout:
    user area            0 - c0000000
    copy area     c4000000 - c4800000
    ktcb area     e0000000 - f0000000
    kernel area   df000000 - ff000000
    cpulocal data f0119000 - f030008c
    utcb pgarea   df000000
    space link    c5000000
Initializing kernel memory (f0307000-f0327000) [128K]
Initializing kernel space
    Switching to CPU local pagetable 00308000 (CPU 0)
CPU local pagetable activated 308000 (CPU 0)
Initializing TCBs
Activating TSS (Preliminary)
Initializing GDT (Preliminary)
Activating IDT (Preliminary)
Initializing kernel interface page (f0118000)
Adding more kernel memory
Initializing memory info
Memory descriptor overflow (max=204, n=204)

My kernel configuration file looks like:

#
# Automatically generated, don't edit
#
# Generated on: tyson-VirtualBox
# At: Sat, 03 May 2014 15:58:57 +0000
# Linux version 3.11.0-12-generic (buildd@komainu) (gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu7) ) #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013

#
# Pistachio Kernel Configuration System
#

#
# Hardware
#

#
# Basic Architecture
#
CONFIG_ARCH_X86=y
# CONFIG_ARCH_POWERPC is not set
# CONFIG_ARCH_POWERPC64 is not set


#
# X86 Processor Architecture
#
CONFIG_SUBARCH_X32=y
# CONFIG_SUBARCH_X64 is not set


#
# Processor Type
#
# CONFIG_CPU_X86_I486 is not set
# CONFIG_CPU_X86_I586 is not set
CONFIG_CPU_X86_I686=y
# CONFIG_CPU_X86_P4 is not set
# CONFIG_CPU_X86_K8 is not set
# CONFIG_CPU_X86_C3 is not set
# CONFIG_CPU_X86_SIMICS is not set


#
# Platform
#
CONFIG_PLAT_PC99=y


#
# Miscellaneous
#
# CONFIG_IOAPIC is not set
CONFIG_MAX_IOAPICS=2
CONFIG_APIC_TIMER_TICK=1000

# CONFIG_SMP is not set


#
# Kernel
#
CONFIG_EXPERIMENTAL=y

#
# Experimental Features
#
CONFIG_X_PAGER_EXREGS=y
CONFIG_X_CTRLXFER_MSG=y
CONFIG_X_EVT_LOGGING=y

#
# Kernel scheduling policy
#
CONFIG_SCHED_RR=y
# CONFIG_X_SCHED_HS is not set


# CONFIG_IPC_FASTPATH is not set
CONFIG_DEBUG=y
# CONFIG_DEBUG_SYMBOLS is not set
# CONFIG_PERFMON is not set
CONFIG_SPIN_WHEELS=y
# CONFIG_NEW_MDB is not set
# CONFIG_STATIC_TCBS is not set
# CONFIG_X86_SMALL_SPACES is not set


#
# Debugger
#

#
# Kernel Debugger Console
#
CONFIG_KDB_CONS_COM=y
CONFIG_KDB_COMPORT=0x0
CONFIG_KDB_COMSPEED=115200
CONFIG_KDB_CONS_KBD=y
CONFIG_KDB_BOOT_CONS=0

# CONFIG_KDB_DISAS is not set
# CONFIG_KDB_ON_STARTUP is not set
# CONFIG_KDB_BREAKIN is not set
# CONFIG_KDB_INPUT_HLT is not set
# CONFIG_KDB_NO_ASSERTS is not set

#
# Trace Settings
#
CONFIG_VERBOSE_INIT=y
# CONFIG_TRACEPOINTS is not set
# CONFIG_KMEM_TRACE is not set
# CONFIG_TRACEBUFFER is not set
# CONFIG_X86_KEEP_LAST_BRANCHES is not set



#
# Code Generator Options
#


#
# Derived symbols
#
# CONFIG_HAVE_MEMORY_CONTROL is not set
CONFIG_X86_PSE=y
# CONFIG_BIGENDIAN is not set
# CONFIG_PPC_MMU_TLB is not set
CONFIG_X86_SYSENTER=y
CONFIG_X86_PGE=y
CONFIG_X86_FXSR=y
CONFIG_IS_32BIT=y
# CONFIG_X86_HTT is not set
CONFIG_X86_PAT=y
# CONFIG_PPC_BOOKE is not set
# CONFIG_IS_64BIT is not set
# CONFIG_MULTI_ARCHITECTURE is not set
# CONFIG_X86_EM64T is not set
# CONFIG_PPC_CACHE_L1_WRITETHROUGH is not set
# CONFIG_PPC_TLB_INV_LOCAL is not set
# CONFIG_PPC_CACHE_ICBI_LOCAL is not set
# CONFIG_X86_SMALL_SPACES_GLOBAL is not set
# CONFIG_X86_HVM is not set
# CONFIG_PPC_MMU_SEGMENTS is not set
CONFIG_X86_TSC=y
#
# That's all, folks!

Please can someone enlighten me on what's going wrong?

TFTP protocol not working for network booting

Hello there,

I have not been able to boot pistachio over the network using TFTP. I have also tried with Pulsar and gPXE. Is this scenario supported in the current version of Pistachio?

Thanks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.