On Sat, 2015-05-23 at 07:58 +0100, Ian Campbell wrote:
> On Sat, 2015-05-23 at 14:46 +0800, Robert Hu wrote:
> > On Sat, 2015-05-23 at 11:35 +0800, Robert Hu wrote:
> > > On Fri, 2015-05-22 at 15:21 +0100, Ian Campbell wrote:
> > > > On Fri, 2015-05-22 at 14:42 +0100, Ian Campbell wrote:
> > > > >
Saturday, May 23, 2015, 3:53:37 AM, you wrote:
> On 05/22/2015 04:11 AM, Sander Eikelenboom wrote:
>> Hello Sander,
>>
>> Friday, May 15, 2015, 12:47:27 AM, you wrote:
>>
>>> Sorry for the resend, i messed up the to's en from's.
>>
>>> Hi Konrad / David,
>>
>>> One big snip on this thread, got so
To match the hypervisor default which was introduced in
9da0c5b63933b9912e3903190601661813954d0d, bump the limit.
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/analyze.h | 2 +-
1
Having xenalyze in the source tree makes it much easier to keep private
debug code in hypervisor and xenalyze in sync. It helped alot while
debugging the root cause for commit 607e8494c42397fb249191904066cace6ac9a880.
changes between v3 and v4:
- install existing binaries in sbindir
- install xe
Collecting the trace buffer requires root permissions. Adjust Makefile
to install xentrace and xentrace_setsize into sbindir. Leave the
existing support for BIN in place for upcoming changes.
Signed-off-by: Olaf Hering
Cc: George Dunlap
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Signed-off-by: Olaf Hering
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/xenalyze.c | 75 ++-
1 file changed, 68 insertions(+), 7 deletions(-)
diff --git a/tools/xentrace/xenalyze.c b/tool
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/xenalyze.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
in
Since xenalyze is now upstream its Open Source and part of the given
release.
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/xenalyze.c | 1 -
1 file changed, 1 deletion(-)
diff --
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/xenalyze.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
index 58e8456..0
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/xenalyze.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/xentrace/xenalyze.c b/tools/xentrace/xenalyze.c
in
On Sat, 2015-05-23 at 15:52 +0800, Robert Hu wrote:
> On Sat, 2015-05-23 at 07:58 +0100, Ian Campbell wrote:
> > On Sat, 2015-05-23 at 14:46 +0800, Robert Hu wrote:
> > > On Sat, 2015-05-23 at 11:35 +0800, Robert Hu wrote:
> > > > On Fri, 2015-05-22 at 15:21 +0100, Ian Campbell wrote:
> > > > > On
Result of "sed -i 's@[[:blank:]]\+$@@' tools/xentrace/xenalyze.c"
Signed-off-by: Olaf Hering
Acked-by: George Dunlap
Acked-by: Wei Liu
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
Cc: Wei Liu
---
tools/xentrace/xenalyze.c | 350 +++---
1 f
On Sat, 2015-05-23 at 09:25 +0100, Ian Campbell wrote:
> On Sat, 2015-05-23 at 15:52 +0800, Robert Hu wrote:
> > On Sat, 2015-05-23 at 07:58 +0100, Ian Campbell wrote:
> > > On Sat, 2015-05-23 at 14:46 +0800, Robert Hu wrote:
> > > > On Sat, 2015-05-23 at 11:35 +0800, Robert Hu wrote:
> > > > > On
On Fri, 2015-05-22 at 15:21 +0100, Ian Campbell wrote:
> On Fri, 2015-05-22 at 14:42 +0100, Ian Campbell wrote:
> > From my particular grub.cfg. For real usage setupboot_grub2 will
> > obviously need to become cleverer to count things correctly.
>
> I've not tested extensively but the following in
On Sat, 2015-05-23 at 16:31 +0800, Robert Hu wrote:
> On Fri, 2015-05-22 at 15:21 +0100, Ian Campbell wrote:
> > On Fri, 2015-05-22 at 14:42 +0100, Ian Campbell wrote:
> > > From my particular grub.cfg. For real usage setupboot_grub2 will
> > > obviously need to become cleverer to count things corr
flight 57032 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57032/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 11 guest-start fail REGR. vs. 53854
test-amd64-i386-libvirt
On Fri, 2015-05-22 at 15:21 +0100, Ian Campbell wrote:
> On Fri, 2015-05-22 at 14:42 +0100, Ian Campbell wrote:
> > From my particular grub.cfg. For real usage setupboot_grub2 will
> > obviously need to become cleverer to count things correctly.
>
> I've not tested extensively but the following in
From: Chen Baozi
[Sorry for the incorrect list address previously.]
Currently the number of vcpus on arm64 with GICv3 is limited up to 8 due
to the fixed size of redistributor mmio region. Increasing the size
makes the number expand to 16 because of AFF0 restriction on GICv3.
To create a guest u
From: Chen Baozi
GIC-500 supports up to 128 cores in a single SoC. Increase MAX_VIRT_CPUS
to 128 on arm64.
Signed-off-by: Chen Baozi
---
xen/arch/arm/vgic-v3.c | 2 +-
xen/include/asm-arm/config.h | 4
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/vgic-v
From: Chen Baozi
Currently it only supports up to 8 vCPUs. Increase the region to hold
up to 128 vCPUs, which is the maxium number that GIC-500 supports.
Signed-off-by: Chen Baozi
---
xen/include/public/arch-arm.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/xen/incl
From: Chen Baozi
GICv3 restricts that the maximum number of CPUs in affinity 0 (one
cluster) is 16. That is to say the upper 4 bits of affinity 0 is unused.
Current implementation considers that AFF0 is equal to vCPUID, which
makes all vCPUs in one cluster, limiting its number to 16. If we would
From: Chen Baozi
There are 3 places to change:
* Initialise vMPIDR value in vcpu_initialise()
* Find the vCPU from vMPIDR affinity information when accessing GICD
registers in vGIC
* Find the vCPU from vMPIRR affinity information when booting with vPSCI
in vGIC
Signed-off-by: Chen Baozi
--
From: Chen Baozi
Use the AFF1 value of ICC_SGI1R_EL1 when injecting SGI in vGIC,
which expands the number of supported vCPU more than 16 that
target list bitmap can hold independently.
Signed-off-by: Chen Baozi
---
xen/arch/arm/vgic.c | 10 --
1 file changed, 8 insertions(+), 2 deletio
From: Chen Baozi
Linux kernel sometimes uses the 'hwid' which is fetched from DT node
of CPU as the MPIDR. We set the logical CPUID in the corresponding DT
node to MPIDR to keep consistency.
Signed-off-by: Chen Baozi
---
tools/libxl/libxl_arm.c | 11 +--
1 file changed, 9 insertions(+)
From: Chen Baozi
Since the size of GICR is determined by the number of CPU
cores, add 'nr_cpus' parameter when creating its DT node
and set gicr0_size dynamically.
Signed-off-by: Chen Baozi
---
tools/libxl/libxl_arm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/to
From: Chen Baozi
This patch does the same thing as the previous one but for dom0 kernel.
Signed-off-by: Chen Baozi
---
xen/arch/arm/domain_build.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index a15
flight 56989 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/56989/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-amd64 12 guest-saverestore fail REGR. vs. 56831
Regressions which a
Hi Chen,
On 23/05/2015 14:52, Chen Baozi wrote:
From: Chen Baozi
GIC-500 supports up to 128 cores in a single SoC. Increase MAX_VIRT_CPUS
to 128 on arm64.
This series have to be bisectable. Although, this patch will break
compilation on ARM64 because you increased MAX_VIRT_CPUS without the
Hi Chen,
On 23/05/2015 14:52, Chen Baozi wrote:
From: Chen Baozi
Currently it only supports up to 8 vCPUs. Increase the region to hold
up to 128 vCPUs, which is the maxium number that GIC-500 supports.
Signed-off-by: Chen Baozi
Reviewed-by: Julien Grall
Regards,
--
Julien Grall
___
Hi Chen,
Title: s/funtions/functions/
On 23/05/2015 14:52, Chen Baozi wrote:
From: Chen Baozi
GICv3 restricts that the maximum number of CPUs in affinity 0 (one
cluster) is 16. That is to say the upper 4 bits of affinity 0 is unused.
Current implementation considers that AFF0 is equal to vCPU
flight 57005 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57005/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-amd64 14 guest-saverestore.2fail REGR. vs. 56375
test-armhf-armhf-xl-
flight 57013 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57013/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 56492
test-amd64-i386-xl-qemuu-win
flight 57024 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57024/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 9 debian-install fail REGR. vs. 52209-bisect
test-amd64-amd64-pair
flight 57031 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57031/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail like 56964
test-amd64-i386-freebsd10-amd6
flight 57078 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57078/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 15 guest-start/debian.repeat fail REGR. vs. 56784
test-amd64-i386-fre
flight 57093 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57093/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 17 leak-check/check fail REGR. vs. 56375
Tests which are fail
flight 57103 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57103/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail REGR. vs. 56492
test-amd64-i386-xl-qemuu-win
flight 57125 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/57125/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866
build-i386-rumpuserxe
On 18 May 2015 at 18:42, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > +#ifndef _ASM_ARM64_ACPI_H
> > +#define _ASM_ARM64_ACPI_H
>
> s/_ASM_ARM64_ACPI_H/_ASM_ARM_ACPI_H/
>
> > +
> > +#include
> > +
> > +#define COMPILER_DEPENDENT_INT64 long long
> > +#define COM
On 18 May 2015 at 19:41, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > acpi_boot_table_init() will be called in start_xen
> > to get the RSDP and all the table pointers. with this patch,
> > we can get ACPI boot-time tables from firmware on ARM64.
> >
> > Signed-of
On 18 May 2015 at 19:59, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > The Power State Coordination Interface (PSCI) defines an API that
> > can be used to coordinate power control amongst the various supervisory
> > systems concurrently running on a device. ACPI s
On 18 May 2015 at 20:28, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
> > the former signals to the OS that the hardware is PSCI compliant.
> > The latter selects the appropriate conduit for PSCI call
On 18 May 2015 at 20:41, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > With ACPI 5.0, we got per-processor timer support in GTDT,
> > and ACPI 5.1 introduced the support for platform (memory-mapped)
> > timers: GT Block and SBSA watchdog timer, add the code needed
On 18 May 2015 at 20:36, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > From: Naresh Bhat
> >
> > When MADT is parsed, print GIC information to make the boot
> > log look pretty.
> >
> > Signed-off-by: Hanjun Guo
> > Signed-off-by: Tomasz Nowicki
> > Signed-off-b
On 20 May 2015 at 20:42, Jan Beulich wrote:
> >>> On 17.05.15 at 22:03, wrote:
> > Pmstat is currently not supported for arm in xen.
> > Configure and build pmstat for x86 architecture only.
>
> Same here as for patch 1. If the architecture can be expected to
> eventually support a feature, I'd
On 20 May 2015 at 21:46, Jan Beulich wrote:
> >>> On 17.05.15 at 22:03, wrote:
> > --- a/xen/include/xen/efi.h
> > +++ b/xen/include/xen/efi.h
> > @@ -8,7 +8,7 @@
> > extern const bool_t efi_enabled;
> >
> > #define EFI_INVALID_TABLE_ADDR (~0UL)
> > -
> > +#define EFI_MEM_DESC_V1 1
> > /* Add
On 18 May 2015 at 18:56, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/15 21:03, Parth Dixit wrote:
> > diff --git a/xen/arch/arm/Makefile b/xen/arch/arm/Makefile
> > index 935999e..096e9ef 100644
> > --- a/xen/arch/arm/Makefile
> > +++ b/xen/arch/arm/Makefile
> > @@ -2,6 +2,7 @@ subdir-$(arm32) +
47 matches
Mail list logo
