Displaying 20 results from an estimated 800 matches similar to: "Re: [XenARM] XEN tools for ARM with Virtualization Extensions"
2013 Nov 25
22
[PATCH v3 00/13] xen: arm initial support for xgene arm64 platform
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
2012 Jan 09
39
[PATCH v4 00/25] xen: ARMv7 with virtualization extensions
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
2013 Apr 24
3
[PATCH] xen/arm: Missing +1 when then number of interrupt lines for the GIC is computed
In the GIC manual, the number of interrupt lines is computed with the following
formula: 32(N + 1) where N is the value retrieved from GICD_TYPER.
Signed-off-by: Julien Grall <julien.grall@linaro.org>
---
xen/arch/arm/gic.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/arch/arm/gic.c b/xen/arch/arm/gic.c
index 760c86b..389c217 100644
---
2011 Dec 06
57
[PATCH RFC 00/25] xen: ARMv7 with virtualization extensions
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
2013 May 06
2
[PATCH v2] xen/gic: EOI irqs on the right pcpu
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
2013 Feb 18
2
[PATCH v2 2/4] xen/arm: do not use is_running to decide whether we can write directly to the LR registers
During context switch is_running is set for the next vcpu before the
gic state is actually saved.
This leads to 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
2013 Apr 23
2
arm: network throughput decreases 5Mbps (Arndale Exynos5250)
Hello,
While I was doing some tests in Arndale board, the network (iperf)
throughput suddenly decreases to 5Mbps (from 100Mbps) out of nowhere.
This typically happens when I generate traffic using iperf (100Mbps)
while installing some packages using apt-get in dom0.
Whenever this behavior happens, I can not see any distinguishable logs
from any places.
After some debugging, I found that
2013 Mar 21
27
[PATCH 0/4] xen/arm: guest SMP support
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 ++++++++++++++++++++++++
2018 Mar 21
4
[PATCH 1/4] iommu: Add virtio-iommu driver
> From: Jean-Philippe Brucker [mailto:jean-philippe.brucker at arm.com]
> Sent: Wednesday, February 14, 2018 10:54 PM
>
> The virtio IOMMU is a para-virtualized device, allowing to send IOMMU
> requests such as map/unmap over virtio-mmio transport without
> emulating
> page tables. This implementation handles ATTACH, DETACH, MAP and
> UNMAP
> requests.
>
> The
2018 Mar 21
4
[PATCH 1/4] iommu: Add virtio-iommu driver
> From: Jean-Philippe Brucker [mailto:jean-philippe.brucker at arm.com]
> Sent: Wednesday, February 14, 2018 10:54 PM
>
> The virtio IOMMU is a para-virtualized device, allowing to send IOMMU
> requests such as map/unmap over virtio-mmio transport without
> emulating
> page tables. This implementation handles ATTACH, DETACH, MAP and
> UNMAP
> requests.
>
> The
2013 Nov 19
23
[PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration
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
2012 Dec 12
2
[PATCH v7 1/2] xen: unify domain locking in domctl code
These two patches were originally part of the XSM series that I have
posted, and remain prerequisites for that series. However, they are
independent of the XSM changes and are a useful simplification
regardless of the use of XSM.
The Acked-bys on these patches were provided before rebasing them over
the copyback changes in 26268:1b72138bddda, which had minor conflicts
that I resolved.
[PATCH
2013 Nov 01
17
[PATCH v2 00/14] xen: arm: 64-bit guest support and domU FDT autogeneration
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.
2018 Mar 21
2
[virtio-dev] [RFC] virtio-iommu version 0.6
Hi Kevin,
Thanks for the comments
On 19/03/18 10:03, Tian, Kevin wrote:
> BYPASS feature bit is not covered in "2.3.1/2.3.2/2.3.3"". Is it
> intended?
In my opinion BYPASS is a bit different from the other features: while the
others are needed for correctness, this one is optional and even if the
guest supports BYPASS, it should be allowed not to accept it. For security
2018 Mar 21
2
[virtio-dev] [RFC] virtio-iommu version 0.6
Hi Kevin,
Thanks for the comments
On 19/03/18 10:03, Tian, Kevin wrote:
> BYPASS feature bit is not covered in "2.3.1/2.3.2/2.3.3"". Is it
> intended?
In my opinion BYPASS is a bit different from the other features: while the
others are needed for correctness, this one is optional and even if the
guest supports BYPASS, it should be allowed not to accept it. For security
2010 Aug 09
5
[XenARM] ARM support ?
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,
2013 Feb 15
1
[PATCH 3/4] xen/arm: dump gic debug info from arch_dump_domain_info
Print some useful GIC debug information when arch_dump_domain_info is
called (''q'' debug key).
Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
---
xen/arch/arm/domain.c | 6 ++++++
xen/arch/arm/gic.c | 27 +++++++++++++++++++++++++++
xen/include/asm-arm/gic.h | 3 +++
3 files changed, 36 insertions(+), 0 deletions(-)
diff --git
2013 Mar 25
6
Can not boot Dom0 when using Anthony's new XenARM source for Arndale.
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
2012 Mar 09
10
[PATCH 0 of 9] (v2) arm: SMP boot
This patch series implements SMP boot for arch/arm, as far as getting
all CPUs up and running the idle loop.
Changes from v1:
- moved barriers out of loop in udelay()
- dropped broken GIC change in favour of explanatory comment
- made the increment of ready_cpus atomic (I couldn''t move the
increment to before signalling the next CPU because the PT
switch has to happen between
2006 Feb 11
1
Spammers on the mailing list?
In respose to my "when is update 3 coming out?" I received the
following mail from brian.trudeau at eastek-intl.com offlist.
Thank you for submitting a ticket to support.
Your ticket number is [04E-0B7CC3CC-3842].
Please keep this ticket number for your records and include it in the
subject (including brackets) of all future emails regarding this
issue.
Thank You,
Support Staff