Hello Ian, Thank you for your answer about the GIC. We are doing an experimental porting XEN on a TI OMAP5 based board. Yep, TI OMAP5 is stillborn but it''s a Cortex-A15 based SOC and we have some boards on a table. So far we got XEN up and loading Dom0 Linux. We have a linux 3.4 port for OMAP5. Backported xen/arm patches from git:// xenbits.xen.org/people/sstabellini/linux-pvhvm.git . Currently our Dom0 boot dies at xenbus_init. Getting parameters HVM_PARAM_STORE_EVTCHN and HVM_PARAM_STORE_PFN from XEN returns 0*, *next access to xen_store_evtchn or xen_store_interface fields is blocked by xen. I did find how this parameters are acquired from XEN, but they are not initialized. Could you please clarify how arch.hvm_domain.params should be initialized. Unfortunately I got no clue about this from vexpress or linaro xen sources. One more question: is http://lists.xen.org/archives/html/xen-devel/2012-09/msg01091.html the latest version of the patchset? Is it available as a tarball? Sincerely, Andrii Anisov. On Wed, Mar 6, 2013 at 2:21 AM, Ian Campbell <ian.campbell@citrix.com>wrote:> On Tue, 2013-03-05 at 19:57 +0000, Andrii Anisov wrote: > > > > In a function arch_domain_create() I do see mapping of GIC CPU > > interface registers space of VM to point to the GIC virtual CPU > > interface. But can''t find how XEN handles VM''s accesses to GIC > > Distributor registers. Could you please explain me how is it done, or > > point to the correspondent code. > > It''s handled from the second stage fault handler, see the call to > handle_mmio from do_trap_data_abort_guest. This eventually ends up > calling vgic_distr_mmio_handler->{read,write} AKA vgic_distr_mmio_read > (and ..._write). > > Ian. > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2013-03-13 at 14:55 +0000, Andrii Anisov wrote:> We are doing an experimental porting XEN on a TI OMAP5 based board.Cool! [...]> One more question: is > http://lists.xen.org/archives/html/xen-devel/2012-09/msg01091.html the > latest version of the patchset? Is it available as a tarball?That is an ancient and no doubt very incomplete set of patches, lots has changed since September last year! Everything which you need is in the mainline xen.git repository already: http://xenbits.xen.org/gitweb/?p=xen.git http://wiki.xen.org/wiki/Xen_Repositories The master branch should be your first port of call. I didn''t bother replying to the other bits of your mail since they are almost certainly due to running such an ancient hypervisor. Ian.
Ian, For sure we took the latest hypervisor from xen.git master branch, we have our specific patches ontop of this commit: commit ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc Author: Liu Jinsong <jinsong.liu@intel.com> Date: Thu Feb 28 09:22:41 2013 +0100 What was the master HEAD on start of this March. I ask about the suitable kernel patch set we could port on our 3.4 kernel. Sincerely, Andrii Anisov. On Wed, Mar 13, 2013 at 5:01 PM, Ian Campbell <Ian.Campbell@citrix.com>wrote:> On Wed, 2013-03-13 at 14:55 +0000, Andrii Anisov wrote: > > We are doing an experimental porting XEN on a TI OMAP5 based board. > > Cool! > > [...] > > One more question: is > > http://lists.xen.org/archives/html/xen-devel/2012-09/msg01091.html the > > latest version of the patchset? Is it available as a tarball? > > That is an ancient and no doubt very incomplete set of patches, lots has > changed since September last year! > > Everything which you need is in the mainline xen.git repository already: > http://xenbits.xen.org/gitweb/?p=xen.git > http://wiki.xen.org/wiki/Xen_Repositories > The master branch should be your first port of call. > > I didn''t bother replying to the other bits of your mail since they are > almost certainly due to running such an ancient hypervisor. > > Ian. > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Please can you not top post. On Wed, 2013-03-13 at 15:51 +0000, Andrii Anisov wrote:> For sure we took the latest hypervisor from xen.git master branch, we > have our specific patches ontop of this commit: > commit ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc > Author: Liu Jinsong <jinsong.liu@intel.com> > Date: Thu Feb 28 09:22:41 2013 +0100 > What was the master HEAD on start of this March.Sorry, I misread your link as being to the initial h/v patches.> I ask about the suitable kernel patch set we could port on our 3.4 > kernel.I''m afraid I don''t know this for the kernel side, Stefano is the man to ask. Ian
Ian, Sorry, I misread your link as being to the initial h/v patches. No problem, anyway thank you for answer. Is it still suitable list to discuss kernel side questions? Stefano, We are porting xen for TI OMAP5 (a Cortex-A15 based SoC). We have 3.4 kernel ported for our chip, could you please suggest proper patch set we would need backport to get Dom0 kernel. It looks git:// xenbits.xen.org/people/sstabellini/linux-pvhvm.git branch xenarm-for-linus has the most recent ARMv7V Dom0 sources, but I''m not sure. Sincerely, Andrii Anisov. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On Wed, 2013-03-13 at 16:50 +0000, Andrii Anisov wrote:> Is it still suitable list to discuss kernel side questions?As they relate to running that kernel on Xen, yes.
On Wed, 13 Mar 2013, Andrii Anisov wrote:> Ian, > Sorry, I misread your link as being to the initial h/v patches. > > No problem, anyway thank you for answer. > Is it still suitable list to discuss kernel side questions? > > Stefano, > > We are porting xen for TI OMAP5 (a Cortex-A15 based SoC). We have 3.4 kernel ported for our chip, could you please suggest > proper patch set we would need backport to get Dom0 kernel. It looks git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git > branch xenarm-for-linus has the most recent ARMv7V Dom0 sources, but I''m not sure.Anthony (CC''ed) recently backported all the patches needed to get Linux running on Xen on ARM on Linux 3.4 too, he should be able to tell you the full list of commits and might even be able to give you a git branch to pull from. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
On 14/03/13 16:42, Stefano Stabellini wrote:> On Wed, 13 Mar 2013, Andrii Anisov wrote: >> Ian, >> Sorry, I misread your link as being to the initial h/v patches. >> >> No problem, anyway thank you for answer. >> Is it still suitable list to discuss kernel side questions? >> >> Stefano, >> >> We are porting xen for TI OMAP5 (a Cortex-A15 based SoC). We have 3.4 kernel ported for our chip, could you please suggest >> proper patch set we would need backport to get Dom0 kernel. It looks git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git >> branch xenarm-for-linus has the most recent ARMv7V Dom0 sources, but I''m not sure. > > Anthony (CC''ed) recently backported all the patches needed to get Linux > running on Xen on ARM on Linux 3.4 too, he should be able to tell you > the full list of commits and might even be able to give you a git branch > to pull from.Hi Andrii, Here is a tree with all the backported Xen related patches: git://xenbits.xen.org/people/aperard/linux-chromebook.git Most of the commit from 95851ef3f08627307f86f77a7f99acbfff4d4470.. are the one you will need, with few Exynos related. But just in case, here is the list: ea57973 ARM: 7511/1: opcodes: Opcode definitions for the Virtualization Extensions 1c000c6 xen/events: fix unmask_evtchn for PV on HVM guests e0ea6b8 xen: Introduce xen_pfn_t for pfn and mfn types 56b772f xen: allow privcmd for HVM guests f0eaaa4 xen: clear IRQ_NOAUTOEN and IRQ_NOREQUEST a782478 xen: missing includes e42e7a2 xen: resynchronise grant table status codes with upstream 96cd0eb xen/arm: compile and run xenbus 6d3c663 arm: initial Xen support f02e85e xen/arm: hypercalls 740f966 xen/arm: page.h definitions a5c02b7 xen/arm: sync_bitops be13481 xen/arm: empty implementation of grant_table arch specific functions 9a92b51 docs: Xen ARM DT bindings a883572 xen/arm: Xen detection and shared_info page mapping 9964c0b xen/arm: Introduce xen_ulong_t for unsigned long b05145a xen: do not compile manage, balloon, pci, acpi, pcpu and cpu_hotplug on ARM 642afdb xen/arm: introduce CONFIG_XEN on ARM cb4ecb7 xen/arm: get privilege status 2e4c809 xen/arm: initialize grant_table on ARM 58ffdbb xen/arm: receive Xen events on ARM a24d975 xen/arm: implement alloc/free_xenballooned_pages with alloc_pages/kfree 33d1e73 xen/arm: compile blkfront and blkback dcea9e1 xen/arm: compile netback cd5afc5 MAINTAINERS: add myself as Xen ARM maintainer 94874cd arm: introduce a DTS for Xen unprivileged virtual machines c3ae4bd xen/arm: Fix compile errors when drivers are compiled as modules (export more). 03c4c21 xen/arm: use the __HVC macro 67169ec xen/xen_initial_domain: check that xen_start_info is initialized 2f56f83 xen: mark xen_init_IRQ __init 19fee1a xen/Makefile: fix dom-y build 1f70737 compile fixes f6647e4 ioremap_cache 22a8d4d xen/privcmd: add PRIVCMD_MMAPBATCH_V2 ioctl d613a45 xen/privcmd: Fix mmap batch ioctl error status copy back. f57e320 xen/privcmd: return -EFAULT on error c21ce28 xen/privcmd: Correctly return success from IOCTL_PRIVCMD_MMAPBATCH b09bc43 xen: add pages parameter to xen_remap_domain_mfn_range 117c19c xen: privcmd: support autotranslated physmap guests. 9310c3a xen: balloon: don''t include e820.h 2a884ae xen: balloon: use correct type for frame_list a22a025 xen: balloon: allow PVMMU interfaces to be compiled out 2f7fc7b xen: arm: enable balloon driver 78e9bed xen: correctly use xen_pfn_t in remap_domain_mfn_range. f1a593a xen: arm: make p2m operations NOPs 4d8f044 xen: arm: implement remap interfaces needed for privcmd mappings. Also, the next two commit are fixing the GIC in the DT, so you will maybe need something similair: adba8c3 DEBUG Xen: have proper gic 21a3d8a fixup! DEBUG Xen: have proper gic Hopefully, all those will be enough. Have fun, -- Anthony PERARD
On Wed, 13 Mar 2013, Ian Campbell wrote:> Please can you not top post. > > On Wed, 2013-03-13 at 15:51 +0000, Andrii Anisov wrote: > > > > For sure we took the latest hypervisor from xen.git master branch, we > > have our specific patches ontop of this commit: > > commit ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc > > Author: Liu Jinsong <jinsong.liu@intel.com> > > Date: Thu Feb 28 09:22:41 2013 +0100 > > What was the master HEAD on start of this March. > > Sorry, I misread your link as being to the initial h/v patches. > > > I ask about the suitable kernel patch set we could port on our 3.4 > > kernel. > > I''m afraid I don''t know this for the kernel side, Stefano is the man to > ask.Sorry for the late reply. We already have a 3.4 Linux tree with the Xen patches backported on it: it''s actually Google''s Linux tree for the Chromebook, but I think you should find it useful anyway because starting from it, it should be very easy to rebase the Xen patches on a vanilla 3.4. Anthony, can you please point Andrii to your 3.4 Linux tree?
On Fri, Mar 22, 2013 at 01:56:50PM +0000, Stefano Stabellini wrote:> On Wed, 13 Mar 2013, Ian Campbell wrote: > > Please can you not top post. > > > > On Wed, 2013-03-13 at 15:51 +0000, Andrii Anisov wrote: > > > > > > > For sure we took the latest hypervisor from xen.git master branch, we > > > have our specific patches ontop of this commit: > > > commit ba9ef879973f9bee4b72c8f1d3ef816bc58e5fdc > > > Author: Liu Jinsong <jinsong.liu@intel.com> > > > Date: Thu Feb 28 09:22:41 2013 +0100 > > > What was the master HEAD on start of this March. > > > > Sorry, I misread your link as being to the initial h/v patches. > > > > > I ask about the suitable kernel patch set we could port on our 3.4 > > > kernel. > > > > I''m afraid I don''t know this for the kernel side, Stefano is the man to > > ask. > > Sorry for the late reply. > > We already have a 3.4 Linux tree with the Xen patches backported on it: > it''s actually Google''s Linux tree for the Chromebook, but I think you > should find it useful anyway because starting from it, it should be very > easy to rebase the Xen patches on a vanilla 3.4.Hi Stefano, I''ve rebuilt Anthony''s 3.4 Linux kernel and Xen for ARM on my Chromebook. (If I''m right, the repo is git://xenbits.xen.org/people/aperard/linux-chromebook.git) But I''ve no idea how to wrap the xen into u-boot format image properly. Is there any brief introductions about it? Thanks, - Chen Baozi> > Anthony, can you please point Andrii to your 3.4 Linux tree? > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
On 22/03/13 15:17, Chen Baozi wrote:> > I''ve rebuilt Anthony''s 3.4 Linux kernel and Xen for ARM on my Chromebook. (If > I''m right, the repo is git://xenbits.xen.org/people/aperard/linux-chromebook.git) > But I''ve no idea how to wrap the xen into u-boot format image properly. Is > there any brief introductions about it?Not yet, sorry for that. I will write some on the wiki soon, hopefully by Monday. -- Anthony PERARD
On Fri, Mar 22, 2013 at 03:30:34PM +0000, Anthony PERARD wrote:> On 22/03/13 15:17, Chen Baozi wrote: > > > > I''ve rebuilt Anthony''s 3.4 Linux kernel and Xen for ARM on my Chromebook. (If > > I''m right, the repo is git://xenbits.xen.org/people/aperard/linux-chromebook.git) > > But I''ve no idea how to wrap the xen into u-boot format image properly. Is > > there any brief introductions about it? > > Not yet, sorry for that. > > I will write some on the wiki soon, hopefully by Monday.Hi Anthony, Since Julien has updated the wiki about running Xen on Arndale board, I made a little progress to boot Xen on Chromebook right now. (It seems that u-boot has loaded Xen''s image and switch the control to it.) However the problem is still there that it is impossible to get the console output after. Is there any good ways to catch the booting information to debug? Thanks, - Chen Baozi> -- > Anthony PERARD
Hello, For those who are looking for Dom0 patch set for LK 3.4, attached patches will save some time for you. These patches are borrowed from Arndale. Sincerely, Andrii Anisov. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel