similar to: Re: [XenARM] Question about booting parameter of Mini-OS for ARM

Hi all, I noticed that upstream UEFI is now supported ARMv8 on FastModel. I’ve tried it to boot Linux with it. And it works. But it seems it still cannot load Xen hypervisor properly. I’m now looking for the reasons. Is there any difference for a firmware to load Xen and Linux kernel? Cheers, Baozi

Hi Xen Developers, I had tested new XenARM for Arndale board that is updated in Anthony''s tree from 2 days ago. I expected that will be working. But, I can not boot Dom0 Kernel. I used kernel and XenARM both are from Xen Wiki(http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Arndale). It (seems) stopped after "(XEN) Freed 212kB init memory" message. When I

I last posted this back in April to critical acclaim (AKA near total silence). I''m not sure who looks after tools/include/xen-foreign. I had thought it was Jan but I think I was confused and was thinking of the semi-related xen/include/compat stuff. IOW I think nobody felt "responsible". Unless there''s any objection lets just treat this as coming under tools. The

Hi all, This is a trivial patch which adds the two fields to start_info_t for the shared page and event channel port for the share. Feel free to destroy this in any way. The python binding just fills zeros in for the moment, making it harmless. Mike Wray has a nicer version in his tree, but this is the minimal version. (Thanks to Mike for the .esp fix, too). Cheers, Rusty. diff -ur

Not just dom0. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> --- xen/arch/arm/domain.c | 3 +++ xen/arch/arm/domain_build.c | 3 --- xen/arch/arm/p2m.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/xen/arch/arm/domain.c b/xen/arch/arm/domain.c index 5702399..4b38790 100644 --- a/xen/arch/arm/domain.c +++ b/xen/arch/arm/domain.c @@

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 ++++++++++++++++++++++++

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.

Add a thread watching the xenbus shutdown control path and notifies a wait queue. Add HYPERVISOR_shutdown convenient inline for minios shutdown. Add proper shutdown to the minios test application. Signed-off-by: Samuel Thibault <samuel.thibault@ens-lyon.org> diff -r fdf241ea6ff4 extras/mini-os/include/kernel.h --- a/extras/mini-os/include/kernel.h Wed Nov 28 21:29:18 2012 +0100 +++

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

(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

Hi Gregor, on ia64 the start_info_t pointer is stored within shared_info_t structure. So it makes sense to initialize the pointer within arch_init(), which is different from x86. With this patch the &si is given to arch_init(). Please have a look! Thanks. Dietmar. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

I''m having trouble switching into user mode with my domU kernel -- everytime I call __HYPERVISOR_iret, the hypervisor calls into my kernel via the registered callback handler. None of the bits in the event channel pending arrays are set. If I return via the iret call, the hypervisor immediately calls back into the handler. The user RIP never changes, so it is clearly not making forward

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

Changes from v3: - mini-os configuration files moved into stubdom/ - mini-os extra console support now a config option - Fewer #ifdefs - grant table setup uses hypercall bounce - Xenstore stub domain syslog support re-enabled Changes from v2: - configuration support added to mini-os build system - add mini-os support for conditionally compiling frontends, xenbus -

Hi Ian, I am trying to add supporting dumping 32-bit guest on arm32 to see what happened in my dom0 kernel when booting. It seems gvirt_to_maddr() is not workable under arm32. But why has it been implemented both in include/asm-arm/arm{32,64}/page.h? Thanks. Baozi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

Hi, I''m trying to boot up with lot more than 32 vcpus on this very large box. I overcame vcpu_info[MAX_VIRT_CPUS] by doing vcpu placement hypercall in guest, but now running into evt channel limit (lots of devices): unsigned long evtchn_pending[sizeof(unsigned long) * 8]; which limits to 512 max for my 64bit dom0. The only recourse seems to create a new struct shared_info_v2{},

This set of patches adds the support for acceleration plugins to the netfront/netback drivers. These plugins are intended to support virtualisable network hardware that can be directly accessed from the guest, bypassing dom0. This is in response to the RFC we posted to xen-devel with an outline of our approach at the end of September. To follow will be another set of patches to provide our

Samsung Enterprise Portal mySingle Hi, I am happy to announce that a patch for a new emulator platform Goldfish (QEMU 0.82 based Android emulator) is released at wiki.xensource.com/xenwiki/XenARM. Sang-bum _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hello, I would like to know if the ARM architecture is well supported. At Xen.org it is mentionned in available architectures, but does it work really well ? I''m looking at CPU like "Tile64" from Tilera : http://www.tilera.com/products/processors/TILE64 The wiki http://wiki.xensource.com/xenwiki/XenARM doesn''t seem to be up to date. Is it ? Any advice ? Thanks,

Hi Julien, Since Ian has merged most my OMAP5 patches, I decide to try to update my working tree to it today. However, it seems it doesn't work as expected. There mainly two kind of problems that I met: 1. It seems that xen no longer maps some of io memory regions described in dts. For example, the memory regions in "ocp" node of omap5.dtsi. 2. commit c88d32f4 seems to be conflict