search for: vtimer

...e user version of the registers. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- v2: Fix r8 vs r8_fiq thinko. --- xen/arch/arm/traps.c | 62 ++++++++++++++++++++++++++++++++++++++++++- xen/arch/arm/vgic.c | 4 +- xen/arch/arm/vpl011.c | 4 +- xen/arch/arm/vtimer.c | 7 +++-- xen/include/asm-arm/regs.h | 6 ++++ 5 files changed, 74 insertions(+), 9 deletions(-) diff --git a/xen/arch/arm/traps.c b/xen/arch/arm/traps.c index bddd7d4..f42e4e9 100644 --- a/xen/arch/arm/traps.c +++ b/xen/arch/arm/traps.c @@ -73,6 +73,64 @@ static void print_xen_info(...

...urn 0; >> +} >> + >> +HVM_REGISTER_SAVE_RESTORE(GIC, gic_save, gic_load, 1, HVMSR_PER_VCPU); >> + >> +static int timer_save(struct domain *d, hvm_domain_context_t *h) >> +{ >> + struct hvm_hw_timer ctxt; >> + struct vcpu *v; >> + struct vtimer *t; >> + int i; >> + >> + /* Save the state of vtimer and ptimer */ >> + for_each_vcpu( d, v ) >> + { >> + t = &v->arch.virt_timer; >> + for ( i = 0; i < 2; i++ ) >> + { >> + ctxt.cval = t-&g...

...00 Generic Interrupt Controller arm: mmio handlers arm: irq arm: mm and p2m arm: pl011 UART driver arm: early setup code arm: shutdown, smp and smpboot arm: driver for the generic timer for ARMv7 arm: trap handlers arm: vgic emulation arm: vtimer arm: makefiles config/arm.mk | 18 + tools/libxc/xc_dom_elfloader.c | 8 +- tools/libxc/xc_hvm_build.c | 5 +- xen/arch/arm/Makefile | 76 ++++ xen/arch/arm/Rules.mk | 29 ++ xen/arch/arm/asm-offsets....

...00 Generic Interrupt Controller arm: mmio handlers arm: irq arm: mm and p2m arm: pl011 UART driver arm: early setup code arm: shutdown, smp and smpboot arm: driver for the generic timer for ARMv7 arm: trap handlers arm: vgic emulation arm: vtimer config/arm.mk | 18 + xen/arch/arm/Makefile | 76 +++ xen/arch/arm/Rules.mk | 29 ++ xen/arch/arm/asm-offsets.c | 76 +++ xen/arch/arm/domain.c | 269 +++++++++...

...Thread "xenstore": pointer: 0xc002d05c, stack: 0xc0032000 Xenbus initialised. Thread "init_xs" exited. -------------------------------- I have inserted some debug printk''s into do_hypervisor_callback() to see whether any callbacks are made at all. According to this, a vtimer interrupt does happen, but only every 10 seconds, which -as I guess- is far less frequent than it should be (The timer handler prints out the current time for every 1000th timer event, so it would take almost three hours before the first message ist printed). Also interesting is that whenever...

I''ve addressed all (I think/hope) of the review comments. The main change is to expose the guest virtual platform (e.g. memory layout and interrupt usage etc) to the toolstack via the public interface. This is then used during FDT generation. I have just codified the current defacto standard layout, it''s probably not the best layout but any change can be a separate patch/series.

Biggest change is to switch the new DTB node to /xen-core-devices instead of /xen at Stefano''s request. I also dropped the few patches title HACK etc which weren''t supposed to be there and fixed up some bits and pieces which folks commented on. George, WRT the freeze I think this is functionality which we cannot ship Xen 4.4 without. The impact is entirely constrained to the

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.

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

(moving to xen-devel, xen-arm is for the older PV ARM port) On Tue, 2013-06-25 at 23:59 +0000, Eric Trudeau wrote: > Hi, I am trying to build the XEN tools for our port of XEN to our > Cortex A15-based platform. > > I am using the repo at git://xenbits.xenproject.org/xen.git to > cross-compile the tools into our rootfs. Which branch/changeset are you using? I've heard that

This series of patches makes Xen pass a (somewhat) valid device tree to dom0. The device tree for dom0 is the same as the one supplied to Xen except the memory and chosen nodes are adjusted appropriately. We don''t yet make use of the device tree to map MMIO regions or setup interrupts for the guest and we still include the UART used for Xen''s console. Note that loading Linux

Hello, This is the second version of this patch series. I only implement the VPF context switch support for arm32 and add dummy function to avoid compilation on arm64. I have switched the order of the patch because the old second one can be applied alone and the patch are cleaner :). For all the changes see each patch. Cheers, Julien Grall (2): xen/arm: don''t enable VFP on XEN

I''m afraid this series is rather a grab bag and it is distressingly large at this stage. With this series I can boot an Xgene board until it fails to find its SATA controller. This is a dom0 issue for which patches are pending from APM (/me nudges Anup). As well as the APM specific platform stuff there are also some generic improvements which were either necessary or useful during this

George has release acked all of these. Otherwise mostly minor updates this time around. Summary: A == acked, M == modified A xen: arm64: Add 8250 earlyprintk support A xen: arm64: Add Basic Platform support for APM X-Gene Storm. A xen: arm64: Add APM implementor id to processor implementers. M xen: arm: add a quirk to handle platforms with unusual GIC layout A xen: arm: allow platform