search for: itargets

...gi; >> + /* ICFG */ >> + ext->icfg[0] = rank->icfg[0]; >> + ext->icfg[1] = rank->icfg[1]; >Can you use memcpy? OK. > >> + /* IPRIORITY */ >> + memcpy(ext->ipriority, rank->ipriority, sizeof(rank->ipriority)); >> + /* ITARGETS */ >> + memcpy(ext->itargets, rank->itargets, sizeof(rank->itargets)); >> + spin_unlock(&rank->lock); >> +} >> + >> +static void vgic_irq_rank_restore(struct vgic_irq_rank *rank, >> + struct vgic_rank *ext) &...

From: Sylvain Gault <sylvain.gault at gmail.com> The System V ABI for x86-64 specify that a "red zone" is an area of 128 bytes above the current stack frame. This area can be used by a called function in order to avoid the overhead of modifying the stack pointer. The direct effect is that interrupt/event/signal handlers must not write to this area. In the UEFI calling convention,

Is this in rsync and I just can't find it, or if not, is there a way to fake this OR, third possibility, is anyone working to add it? For those who've never used this option - for the GNU cp & mv type commands they have the --target-dir="dir" option. It lets you put the destination directory as the first argument to cp and mv instead of the last argument. They added the

I'm just curious. The older klibc tarballs had a syslinux dir used to build a syslinux image with klibc. While I haven't used it, I was planning on messing with it at some point in the future. However, the syslinux stuff was removed from recent klibc images. Is there a technical reson for this, or would is still be acceptable to use the old Makefiles from that dir to build syslinux?

Hi, I've tried to compile syslinux under mandriva, and the compilation always bails out because it hasn't created win32/syslinux.exe. As far as I understand, the build will work fine on a Windows / mingw installation, but not Linux. I've modified my Makefile to remove the win32/syslinux.exe from the build, and it now builds OK. This happened on 3.3.6 and also on 4.0pre.

Hello everyone, this is the fourth version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See

Hello everyone, this is the very first version of the patch series that introduces ARMv7 with virtualization extensions support in Xen. The series allows Xen and Dom0 to boot on a Cortex-A15 based Versatile Express simulator. See the following announce email for more informations about what we are trying to achieve, as well as the original git history: See