Re: [PATCH] arinc653 support for virtualpok bsp

Hi Janek, I finally came around to review this patch. Can you make your own testsuite/sample folder with the ARINC calls and not patch the hello/init.c? Please fix all trailing whitespace errors in the patch. virtualpok/Makefile.am produces an error at compile time: cat libpart.list | rename 's

Re: [GSoC2014] arinc653 on rtems (using pok) patches

I already fixed that in my current version of virtualpok, but Janek's patches were created against his version from April. He already has the new version. I maintain an own linkcmds in virtualpok, as I added a 0x1000 offset to the start of the binary. It confused me to see some strange code in GD

[PATCH v2] cpukit/cpu/i386: RTEMS_PARAVIRT guards, functionality and virt.layer

/* end of Fatal Error manager macros */ diff --git a/cpukit/score/cpu/i386/rtems/score/interrupts.h b/cpukit/score/cpu/i386/rtems/score/interrupts.h index 5ae172a..4233a34 100644 --- a/cpukit/score/cpu/i386/rtems/score/interrupts.h +++ b/cpukit/score/cpu/i386/rtems/score/interrupts.h @@ -8,6 +8

Re: [PATCH] cpukit/cpu/i386: RTEMS_PARAVIRT guards, functionality and virt.layer

On 07/18/2014 05:57 PM, Gedare Bloom wrote: > On Fri, Jul 18, 2014 at 11:37 AM, Philipp Eppelt > wrote: >> --- >> This is an updated version of an earlier unmerged patch, which extends the >> cpukit/score/cpu/i386/ model with guards to distinguish between >> para

[PATCH] cpukit/cpu/i386: RTEMS_PARAVIRT guards, functionality and virt.layer

*/ /* end of Fatal Error manager macros */ diff --git a/cpukit/score/cpu/i386/rtems/score/interrupts.h b/cpukit/score/cpu/i386/rtems/score/interrupts.h index 5ae172a..4233a34 100644 --- a/cpukit/score/cpu/i386/rtems/score/interrupts.h +++ b/cpukit/score/cpu/i386/rtems/score/interrupts.h @@ -8,6 +8

Re: 回复：Re: The design of vCPU.

On 06/12/2014 04:34 PM, shenyouren wrote: > Philipp Eppelt <mailto:philipp.epp...@mailbox.tu-dresden.de>>于 2014年6月12日 下午9:50 > 写道： >> >> Hi, >> >> can you please evaluate, which pieces already implemented in >> pok/kernel/* can be reused to build the

Re: The design of vCPU.

Hi, can you please evaluate, which pieces already implemented in pok/kernel/* can be reused to build the vCPU structure? Also, how the vCPU structure can be build on top of / merged into the partition structure. Cheers, Philipp On 06/12/2014 12:00 PM, Philipp Eppelt wrote: > Hi, > > I

Re: The design of vCPU.

Hi, I think we have to chose the 'host model'. In order to provide separation POK puts (at least some) device drivers (network card) into their own partitions and offers a kernel supervised communication interface. (If this is new, read the POK paper by Julien.) This also implies some restriction