similar to: [PATCH] Use stddef.h in Mini-OS to define size_t

Hi, I''ve been googling quite a bit - but up until now to no use :( My problem is how to configure Apache conf (and perhaps Passenger) for this setup to work: <VirtualHost *:80> ServerName oxen.company_A.com DocumentRoot /var/www/html/oxen/sites/company_A/public PassengerAppRoot /var/www/html/oxen SetEnv OXID 23 </VirtualHost> <VirtualHost *:80>

I sent this patch directly to Gregor, and neglected to CC this list. Sorry about that. I''d like to make it so that there is no need to modify any Mini-OS source files when extending it with an application. All that is required is a change to Makefile, and a small change to kernel.c, printf.c, and string.c. I have enclosed the patch. With this patch, one could write an application in a

Hello there, I'm building a Linux distribution based on musl and LLVM as default toolchain (including lld/libc++/libc++abi/libunwind rather than GNU). For most of the time this works pretty well. However I'm having troubles with few packages, webkit for instance fails because of max_align_t being redeclared in musl's stddef.h I see that stddef.h is provided by both musl and in the

This patch protects against redefinitions of size_t. There are currently at least two different definitions provided with klibc: unistd.h -> stddef.h -> bits32/bitsize/stddef.h sys/times.h -> linux/times.h -> linux/types.h both define size_t, causing gcc to complain. I suspect ptrdiff_t has a similar problem; not covered by this patch. Regards, Erik diff -urN

See MAINTAINERS file Signed-off-by: Matthew Fioravante <matthew.fioravante@jhuapl.edu> diff --git a/MAINTAINERS b/MAINTAINERS index 094fe9e..f562efa 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -261,6 +261,21 @@ S: Supported F: tools/xentrace/ F: xen/common/trace.c +VTPM +M: Matthew Fioravante <matthew.fioravante@jhuapl.edu> +S: Supported +F: tools/vtpm +F:

Hi Ian, Natasha and I are interested in helping with the io emulation work for fully virtualized HVM guests you mentioned in your March 12th email: http://lists.xensource.com/archives/html/xen-devel/2006-03/msg00394.html In the post, you mentioned the following tasks: - get minios running on x86_64 - port xenbus/netfront/blkfront to minios - compile qemu-dm into minios - redirect IO to qemu-dm

For a while I''ve been intending to provide a better environment for PV baremetal guests. The current arrangements, based on newlib, take quite a bit of porting for many programs. My plan is to take the FreeBSD libc, and write a set of functions implementing the "system calls" in terms of facilities provided by the Xen PV environment, frontend drivers, etc. As part of this I

I'm getting compile errors because size_t is getting redefined. My "forced include file" starts with: #if BUILDING_FOR_WINDOWS #define NOMINMAX /* deal with the fact that windef.h also defines BOOL */ #define BOOL WINBOOL #include <windows.h> #include <intrin.h> #undef BOOL #endif Looking at the preprocessor expansion of a typical .cpp file, I see that crtdefs.h

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Hi, Let me start a new thread for this. I contacted the Grub people, and they seem more interested in creating a native Xen port of Grub than piggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources?

Syslinux fail to build with gnu-efi >= 3.0.16 with error: In file included from /host/i686-buildroot-linux-gnu/sysroot/usr/include/efi/efi.h:44, from /build/syslinux-6.03/efi/efi.h:23, from /build/syslinux-6.03/efi/adv.h:4, from /build/syslinux-6.03/efi/adv.c:29:

Hi folks, I am new to install xen 4.1.0-rc6-pre version on RHEL 6.2. When installing xen tools flask, I got an error said “No rule to make target ‘/usr/lib/gcc/x86-64-redhat-linux/4.1.2/include/stddef.h”, but I am using gcc 4.4..6. How to fix this? Thanks & Best Regards Shengkai _______________________________________________ Xen-users mailing list Xen-users@lists.xen.org

Hello, sorry to bother you with this: while trying to compile mini-os from xen-unstable.hg, I noticed that compilation failed like this: gcc -fno-builtin -Wall -Werror -Wredundant-decls -Wno-format -Wstrict-prototypes -Wnested-externs -Wpointer-arith -Winline -m32 -march=i686 -g -Iinclude -Iinclude/x86 -Iinclude/x86/x86_32 -c gnttab.c -o gnttab.o gnttab.c: In Funktion »init_gnttab«:

Hi Reid, I copied the x64 toolsets by hand; they got installed to C:\Program Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly by install.bat. I just verified that the LLVM-vs2013 toolset.props is correct. If it is a bitness problem, perhaps I'm failing to define something correctly? Regards, Eric On 9/30/14, 11:29 AM, Reid Kleckner wrote: > This looks

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

I believe that we provide a definition of size_t inside the compiler itself when clang is in MSVC compatibility mode. On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote: > I did some more investigation of the size_t size error. I misunderstood > what was happening. It turns out that size_t is already defined before my > prefix header is included. I added the

Hello everyone, I''m studying XEN these days, and totally a newbie for XEN world. Recently, I''m assigned to move our OS to run on XEN, I means, paravitualization. I know a bit about XEN technique, and I tried to look into Linux code, but it seems too many threads to get understood it ... Now, I have no idea how to proceed my project... Can anyone give some advice? Any suggestion

Hi all, I am trying to find out why the minimum memory allocation for a domu is 4MB. I am running MiniOS and a small application that requires no more than 8 KB or RAM. Can anyone give me a comprehensive answer to this question, i am really looking to get to grips with this in detail. Is this an arbitrary decision, or is there something more meaningful at work here? Thanks Paul

From: Ben Cressey <bcressey@amazon.com> The commit "minios: refactor xenbus state machine" caused "/state" to be appended to the local value of nodename. Previously the nodename variable pointed to dev->nodename. The xenbus_rm() calls were not updated to reflect this change, and refer to paths that do not exist. For example, shutdown_blkfront() for vbd 2049 would

Hi, I''m trying to use the SYSCALL/SYSRET opcodes with a minios kernel without much success. Going by the manuals (and linux sources) I first have to setup the STAR and LSTAR registers to define the segment and instruction pointer to be used for SYSCALL: /* * LSTAR and STAR live in a bit strange symbiosis. * They both write to the same internal register. STAR allows