similar to: Re: [PATCH v4 1/9] xen/arm: Implement hvm save and restore

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

Mr. Domicile, I was reading your error and believe I just hit exactly the same condition with FC5. The problem that I had turned out to be the MAC address of the ethernet adapter. In your post, it showed a HWADDR of FE:FF:FF:FF:FF:FF. You should see a real MAC address here. What was happening on my server was that "sometimes" the system would not read the HW address from the

I searched the archives and did not find a solution, so I pose this question to those well-versed in the use of plotmath and expressions. I have a list of strings in an external CSV file which I wish to use sometimes as plot axis labels and sometimes as plot titles. These strings combine plaintext and a few mathematical expressions (Greek letters, subscripts). Moreover, I sometimes need to

Hi, all: I am considering contructing Interprocedural Control Flow Graph(ICFG) in LLVM, but really have no idea about how much work should I do? Is there someone have done this work before? Expecting your suggestions. Thanks. --William -------------- next part -------------- An HTML attachment was scrubbed... URL:

Implements tool interfaces for scheduling domains. libxenctrl, xm, and xend. signed-off-by: Mike D. Day <ncmike@us.ibm.com> -- libxc/xc_domain.c | 85 +++++++++++++++++++++++++++++++++--- libxc/xenctrl.h | 43 ++++++++++++++++-- python/xen/xend/XendDomain.py | 78 +++++++++++++++++++++++++++++++++ python/xen/xend/server/SrvDomain.py |

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.

We need to write the irq number to GICC_DIR on the physical cpu that previously received the interrupt, but currently we are doing it on the pcpu that received the maintenance interrupt. As a consequence if a vcpu is migrated to a different pcpu, the irq is going to be EOI''ed on the wrong pcpu. This covers the case where dom0 vcpu0 is running on pcpu1 for example (you can test this

Hi all, this small patch series implement guest SMP support for ARM, using the ARM PSCI interface for secondary cpu bringup. Stefano Stabellini (4): xen/arm: basic PSCI support, implement cpu_on xen/arm: support for guest SGI xen/arm: support vcpu_op hypercalls xen: move VCPUOP_register_vcpu_info to common code xen/arch/arm/domain.c | 66 ++++++++++++++++++++++++