search for: __context_switch

Hi all, I am having confusion regarding the way a newly created domain is allocated vcpu. Initially during dom0 creation alloc_vcpu is called to create vcpu structs for all the available cpu''s and assigned to dom0. But its not the case for domU creation. 1. So how will dom0 relinquish/share vcpu to/with a newly created domU. Does this happen as part of the shared_info page mapping??

...possible nasty races when interrupts need to be injected after is_running is set to the next vcpu but before the currently running gic state has been saved from the previous vcpu. Use current instead of is_running to check which one is the currently running vcpu: set_current is called right before __context_switch and schedule_tail with interrupt disabled. Re-enabled interrupts after ctxt_switch_from, so that all the context switch saving functions don''t have to worry about receiving interrupts while saving state. Changes in v2: - rework the patch to run ctxt_switch_from with interrupt disabled,...

Hi, I''m a PhD student trying to add some load balancing code to the credit scheduler in order to fit some specific necessities. I''m trying to understand the credit scheduler code and I don''t quite get in which part of it a pcpu starts running a vcpu. I need to keep track of when a vpcu starts running in a cpu and when it stops. Any hint on that? I think that it would

Hi, Dan, This patch fixes strange behavior on IA64, that IDLE is scheduled more than Dom0 with default sEDF scheduler. The key point is reprogram_ac_timer at the end of ac_timer dispatcher, which programs local apic timer with expire of next ac_timer on x86. Higher precision lapic timer can trigger ac_timer more precisely than simply done in PIT interrupt handler. That works perfectly on x86

...39; /home/test1/xen-unstable/xen/drivers/built_in.o: In function `panic'': /home/test1/xen-unstable/xen/drivers/char/console.c:648: relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `__stack_chk_fail'' /home/test1/xen-unstable/xen/arch/x86/built_in.o: In function `__context_switch'': /home/test1/xen-unstable/xen/arch/x86/domain.c:703: relocation truncated to fit: R_X86_64_PLT32 against undefined symbol `__stack_chk_fail'' /home/test1/xen-unstable/xen/arch/x86/built_in.o: In function `do_platform_op'': /home/test1/xen-unstable/xen/arch/x86/platform_hyp...

The first patch really isn''t as much of a follow-up than what triggered the security issues to be noticed in the first place. 1: x86: preserve FPU selectors for 32-bit guest code 2: x86: fix XCR0 handling 3: x86/xsave: adjust state management 4: x86/fxsave: bring in line with recent xsave adjustments The first two I would see as candidates for 4.3 (as well as subsequent backporting,

This round implements all of the review comments from V2 and all patches are now acked. Unless there are any objections I intend to apply later this morning. Ian.

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

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

First off, Apologies for the massive patch series... This series boots a 32-bit dom0 kernel to a command prompt on an ARMv8 (AArch64) model. The kernel is the same one as I am currently using with the 32 bit hypervisor I haven''t yet tried starting a guest or anything super advanced like that ;-). Also there is not real support for 64-bit domains at all, although in one or two places I