Hi Shanker,
On 31 May 2016 at 22:02, Shanker Donthineni wrote:
> The ARM Server Base System Architecture describes a generic UART
> interface. It doesn't support clock control registers, modem
> control, DMA and hardware flow control features. So, extend the
> driver probe() to handle SBSA interf
flight 95093 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95093/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REG
flight 95086 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95086/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 16 guest-start.2 fail REGR. vs. 94959
test-amd64-amd64-xl-rtds
On 05/27/16 17:16, Wei Liu wrote:
> On Fri, May 27, 2016 at 05:14:08PM +0100, Wei Liu wrote:
> > On Fri, May 27, 2016 at 10:06:31AM -0600, Jan Beulich wrote:
> > > >>> On 27.05.16 at 17:31, wrote:
> > > > On Fri, May 27, 2016 at 03:06:08PM +0100, Wei Liu wrote:
> > > >> On Fri, May 27, 2016 at 08:
flight 95095 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95095/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 5 kernel-build fail REGR. vs. 94970
Tests which did not succe
On 05/31/2016 08:15 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote:
>> The dma-mapping core and the implementations do not change the
>> DMA attributes passed by pointer. Thus the pointer can point to const
>> data. However the attributes do
On Wed, 2016-06-01 at 12:58 +0800, Luwei Kang wrote:
> CPUID.0XD.0X0.EAX is from machine value for dom0, and dom0 kernel will xsetbv
> with xfeatures_mask that is from CPUID.0XD.0X0.EAX, but handle_xsetbv has
> ingored XSTATE_PKRU with hardware protection fault emulation, so dom0 kernel
> will cras
On 06/01/2016 04:33 AM, Konrad Rzeszutek Wilk wrote:
> On Tue, May 31, 2016 at 04:59:16PM +0800, Bob Liu wrote:
>> Sometimes blkfont may receive twice blkback_changed() notification after
>> migration, then talk_to_blkback() will be called twice too and confused
>> xen-blkback.
>
> Could you enli
System workqueues have been able to handle high level of concurrency
for a long time now and there's no reason to use dedicated workqueues
just to gain concurrency. Replace dedicated xenbus_frontend_wq with the
use of system_wq.
Unlike a dedicated per-cpu workqueue created with create_workqueue()
Sorry about that. Will make the corrections in v2.
Thanks,
Bhaktipriya
On Tue, May 31, 2016 at 9:48 PM, David Vrabel wrote:
> On 27/05/16 19:50, Bhaktipriya Shridhar wrote:
>> With concurrency managed workqueues, use of dedicated workqueues can be
>> replaced by using system_wq. Drop xenbus_fro
On 05/31/2016 07:04 PM, Christoph Hellwig wrote:
> On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote:
>> The dma-mapping core and the implementations do not change the
>> DMA attributes passed by pointer. Thus the pointer can point to const
>> data. However the attributes do not
CPUID.0XD.0X0.EAX is from machine value for dom0, and dom0 kernel will xsetbv
with xfeatures_mask that is from CPUID.0XD.0X0.EAX, but handle_xsetbv has
ingored XSTATE_PKRU with hardware protection fault emulation, so dom0 kernel
will crash on skylake machine with PKRU support.
Signed-off-by: Luwei
flight 95090 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95090/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REG
Virtualization exception is a fault exception caused by specific type of
EPT violations. The vector is 20, which is not defined in linux kernel
(traps.h), also no exception handling function is defined (traps.c). So is
there any way to implement it as a LKM? As it is needed to
set virtualization-ex
flight 95082 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95082/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 94748
test-amd64-amd64-
flight 95085 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95085/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REG
flight 94994 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94994/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-amd 9 debian-hvm-install fail REGR. vs. 94856
test-amd64-amd64-qe
flight 95084 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95084/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
On 5/26/2016 10:44 AM, Jan Beulich wrote:
Suravee Suthikulanit 05/25/16 9:01 PM >>>
On 5/23/2016 6:54 AM, Jan Beulich wrote:
On 22.05.16 at 01:42, wrote:
From: Suravee Suthikulpanit
The guest_iommu_init() is currently called by the following code path:
arch/x86/domain.c: arch_domain_c
On Mon, May 30, 2016 at 09:46:02AM +0800, Dongli Zhang wrote:
> Local variable "j" would be used only when "i == ARRAY_SIZE(main_options)"
> is true. Thus, it is not necessary to update "j" when "i ==
> ARRAY_SIZE(main_options)" is false.
>
> Signed-off-by: Dongli Zhang
Reviewed-by: Konrad Rzesz
On 05/31/2016 03:42 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, May 31, 2016 at 12:43:22PM +0800, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> The design of this feature is described as below.
>> Firstly, the toolstack (libxl) generates the ACPI tables according the
>> number of vcpus and gic co
On Tue, May 31, 2016 at 07:27:24PM +0100, George Dunlap wrote:
> On Fri, May 13, 2016 at 4:23 PM, Konrad Rzeszutek Wilk
> wrote:
> > On Fri, May 13, 2016 at 03:25:52PM +0100, M A Young wrote:
> >> On Fri, 13 May 2016, Jan Beulich wrote:
> >>
> >> > >>> On 13.05.16 at 15:49, wrote:
> >> > > ...
>
On Tue, May 31, 2016 at 1:53 PM, Wei Liu wrote:
> On Tue, May 31, 2016 at 11:43:13AM -0400, Chris Patterson wrote:
>> On Tue, May 31, 2016 at 6:42 AM, George Dunlap
>> wrote:
>> > On Mon, May 30, 2016 at 3:32 AM, Chris Patterson wrote:
>> >> From: Chris Patterson
>> >>
>> >> Replace the usage
On Tue, May 31, 2016 at 04:59:16PM +0800, Bob Liu wrote:
> Sometimes blkfont may receive twice blkback_changed() notification after
> migration, then talk_to_blkback() will be called twice too and confused
> xen-blkback.
Could you enlighten the patch description by having some form of
state transi
flight 94996 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94996/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REG
flight 95081 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95081/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
On Tue, May 31, 2016 at 12:43:22PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> The design of this feature is described as below.
> Firstly, the toolstack (libxl) generates the ACPI tables according the
> number of vcpus and gic controller.
CC-ing Boris - who has been working on exposing
On Tue, May 31, 2016 at 6:42 PM, Wei Liu wrote:
> From: Vitaly Kuznetsov
>
> Commit 56fb5fd623 ("libxl: adjust PoD target by memory fudge, too")
> introduced target_memkb adjustment for HVM PoD domains on create. The
> adjustment is however being reset on reload_domain_config() (e.g. when
> we re
flight 94993 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94993/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 94748
test-amd64-amd64-xl-qemuu-ov
On Fri, May 13, 2016 at 4:23 PM, Konrad Rzeszutek Wilk
wrote:
> On Fri, May 13, 2016 at 03:25:52PM +0100, M A Young wrote:
>> On Fri, 13 May 2016, Jan Beulich wrote:
>>
>> > >>> On 13.05.16 at 15:49, wrote:
>> > > ...
>> > >
>> > > Still an issue - with 4.7.0-rc1.
>> >
>> > And I don't recall any
On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote:
> The dma-mapping core and the implementations do not change the
> DMA attributes passed by pointer. Thus the pointer can point to const
> data. However the attributes do not have to be a bitfield. Instead
> unsigned long will d
On Tue, May 31, 2016 at 11:43:13AM -0400, Chris Patterson wrote:
> On Tue, May 31, 2016 at 6:42 AM, George Dunlap
> wrote:
> > On Mon, May 30, 2016 at 3:32 AM, Chris Patterson wrote:
> >> From: Chris Patterson
> >>
> >> Replace the usage of readdir_r() with readdir() to address
> >> a compilati
On Tue, May 31, 2016 at 10:22:41AM -0600, Jan Beulich wrote:
> >>> On 31.05.16 at 17:13, wrote:
> > From: Chris Patterson
> >
> > In some cross-compilation environments, the CC/CXX variables may
> > expand out to more than one argument (to include things
> > like --sysroot=...). Quote these to
From: Vitaly Kuznetsov
Commit 56fb5fd623 ("libxl: adjust PoD target by memory fudge, too")
introduced target_memkb adjustment for HVM PoD domains on create. The
adjustment is however being reset on reload_domain_config() (e.g. when
we reboot the guest). For example:
I'm trying to create HVM PoD
On Tue, May 31, 2016 at 10:26:30PM +0530, Bhaktipriya Shridhar wrote:
> System workqueues have been able to handle high level of concurrency
> for a long time now and there's no reason to use dedicated workqueues
> just to gain concurrency. Replace dedicated xenbus_frontend_wq with the
> use of sy
Hi Peng,
On 31/05/16 10:58, Peng Fan wrote:
So, need to make sure boot pages are ready before setup xenheap mappings.
init_boot_pages is using mfn_to_virt (see bootmem_region_add), which cannot
work until xenheap_mfn_start is initialized. This is done by
setup_xenheap_mappings.
My bad. I d
Signed-off-by: Andrew Cooper
---
CC: Ian Jackson
CC: Wei Liu
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
---
docs/features/feature-levelling.pandoc | 211 +
1 file changed, 211 insertions(+)
create mode 100644 docs/features/feature-levelling.pandoc
diff --git a
On Mon, May 30, 2016 at 01:54:06PM +0200, Krzysztof Kozlowski wrote:
> The dma-mapping core and the implementations do not change the
> DMA attributes passed by pointer. Thus the pointer can point to const
> data. However the attributes do not have to be a bitfield. Instead
> unsigned long will d
On May 31, 2016 01:48, "Jan Beulich" wrote:
>
> >>> On 30.05.16 at 21:47, wrote:
> > On Mon, May 30, 2016 at 5:50 AM, Jan Beulich wrote:
> > On 30.05.16 at 00:37, wrote:
> >>> +struct vm_event_regs_arm32 {
> >>> +uint32_t r0_usr;
> >>> +uint32_t r1_usr;
> >>> +uint32_t r2_usr;
>
>>> On 31.05.16 at 17:13, wrote:
> From: Chris Patterson
>
> In some cross-compilation environments, the CC/CXX variables may
> expand out to more than one argument (to include things
> like --sysroot=...). Quote these to safely pass along.
>
> Signed-off-by: Chris Patterson
Acked-by: Jan Be
On May 31, 2016 01:54, "Jan Beulich" wrote:
>
> >>> On 30.05.16 at 22:37, wrote:
> > On Mon, May 30, 2016 at 2:20 PM, Julien Grall
wrote:
> >> On 30/05/2016 20:47, Tamas K Lengyel wrote:
> >>> On Mon, May 30, 2016 at 5:50 AM, Jan Beulich
wrote:
> > +struct vm_event_regs_arm64 {
> > +
From: Suravee Suthikulpanit
Along with the IVHD block type 10h, newer AMD platforms also come with
types 11h, which is a superset of the older one. Having multiple IVHD
block types in the same platform allows backward compatibility of newer
systems to work with existing drivers. The driver shoul
On 27/05/16 19:50, Bhaktipriya Shridhar wrote:
> With concurrency managed workqueues, use of dedicated workqueues can be
> replaced by using system_wq. Drop xenbus_frontend_wq by using system_wq.
>
> Since there is only a single work item, increase of concurrency level by
> switching to system_wq
Xen Developers,
On Ubuntu 16.04, when I clone from Xenbits and then checkout RELEASE-4.6.1,
‘make world’ breaks
when it gets to qemu-xen-traditional, with the error shown below. This looks
like a problem that was patched back at the end of April, but somehow is not
taking effect for the older c
On Tue, May 31, 2016 at 01:16:14PM +0200, Olaf Hering wrote:
> On Tue, May 31, George Dunlap wrote:
>
> > On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
> > > With staging-4.6 this domU boots from xvda, qemu creates an emulated
> > > disk. With staging no disk is found, unless the name is ch
flight 94989 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94989/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REG
On 31/05/16 13:44, Jan Beulich wrote:
On 31.05.16 at 12:30, wrote:
>> On 30/05/16 14:48, Jan Beulich wrote:
>>> --- a/xen/arch/x86/setup.c
>>> +++ b/xen/arch/x86/setup.c
>>> @@ -1044,13 +1044,19 @@ void __init noreturn __start_xen(unsigne
>>> }
>>>
>>> #ifdef CONFIG_KEXEC
>>> -
On Tue, May 31, 2016 at 6:42 AM, George Dunlap wrote:
> On Mon, May 30, 2016 at 3:32 AM, Chris Patterson wrote:
>> From: Chris Patterson
>>
>> Replace the usage of readdir_r() with readdir() to address
>> a compilation error due to the deprecation of readdir_r.
>>
>> glibc has deprecated this fo
From: Chris Patterson
In some cross-compilation environments, the CC/CXX variables may
expand out to more than one argument (to include things
like --sysroot=...). Quote these to safely pass along.
Signed-off-by: Chris Patterson
---
xen/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3
flight 94983 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94983/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 3 host-install(3) broken REGR. vs. 94856
test-amd64-amd64-qe
Hi Julien,
On 2016年05月31日 18:47, Julien Grall wrote:
> Hi Shannon,
>
> On 31/05/16 06:02, Shannon Zhao wrote:
>> From: Shannon Zhao
>>
>> The design of this feature is described as below.
>> Firstly, the toolstack (libxl) generates the ACPI tables according the
>> number of vcpus and gic control
>>> On 31.05.16 at 15:41, wrote:
> On Tue, May 31, 2016 at 1:10 PM, Jan Beulich wrote:
> On 31.05.16 at 13:32, wrote:
>>> On Tue, May 31, 2016 at 12:16 PM, Olaf Hering wrote:
On Tue, May 31, George Dunlap wrote:
> On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
> > Wi
On Fri, May 20, 2016 at 7:05 PM, Edgar E. Iglesias
wrote:
> Hi,
>
> We have similar needs (not exactly the same) in some of our setups.
> We need to map certain OCMs (On Chip Memories) to dom0. Among other things,
> these are used to communicate with remote accelerators/CPUs that have
> "hardcoded
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Kevin Tian
CC: Feng Wu
CC: Jan Beulich
CC: Andrew Cooper
---
xen/drivers/passthrough/arm/smmu.c| 2 +-
xen/drivers/passthrough/vtd/iommu.c
From: Quan Xu
Treat IOMMU mapping and unmapping failures as a fatal to the DomU
If IOMMU mapping and unmapping failed, crash the DomU and propagate
the error up to the call trees.
No spamming of the log can occur. For DomU, we avoid logging any
message for already dying domains. For Dom0, that'l
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
CC: Suravee Suthikulpanit
CC: Stefano Stabellini
CC: Julien Grall
CC: Kevin Tian
CC: Feng Wu
CC: Jan Beulich
v6:
1. Add __must_check annotation to amd_iommu_map_page().
2. Return the first error instead of the last one.
---
From: Quan Xu
When IOMMU mapping is failed, we issue a best effort rollback, stopping
IOMMU mapping, unmapping the previous IOMMU maps and then reporting the
error up to the call trees. When rollback is not feasible (in early
initialization phase or trade-off of complexity) for the hardware domai
From: Quan Xu
This patch set is a prereq patch set for Patch:'VT-d Device-TLB flush issue'.
While IOMMU Device-TLB flush timed out, xen calls panic() at present. However
the existing panic()
is going to be eliminated, so we must propagate the IOMMU Device-TLB flush
error up to the call trees.
From: Quan Xu
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Kevin Tian
CC: Feng Wu
v6: Add __must_check annotation to intel_iommu_iotlb_flush_all().
---
xen/drivers/passthrough/arm/smmu.c | 13 -
From: Quan Xu
Signed-off-by: Quan Xu
CC: Jan Beulich
CC: Kevin Tian
CC: Feng Wu
---
xen/drivers/passthrough/vtd/iommu.c | 40 ++--
xen/drivers/passthrough/vtd/iommu.h | 11 ++
xen/drivers/passthrough/vtd/qinval.c | 14 ++---
3 files changed,
From: Quan Xu
Signed-off-by: Quan Xu
CC: Jan Beulich
CC: Liu Jinsong
CC: Keir Fraser
CC: Andrew Cooper
CC: Suravee Suthikulpanit
CC: Stefano Stabellini
CC: Julien Grall
CC: Kevin Tian
CC: Feng Wu
v6:
1. Drop comments in enum dev_power_saved.
2. If console_suspend() fails, return S
From: Quan Xu
Signed-off-by: Quan Xu
Reviewed-by: Jan Beulich
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Kevin Tian
v6: Remove __must_check annotation from xenmem_add_to_physmap().
---
xen/arch/arm/p2m.c | 4 +++-
xen/common/memory.c | 1
From: Quan Xu
Propagate the IOMMU Device-TLB flush error up to the ept_set_entry(),
when VT-d shares EPT page table.
Signed-off-by: Quan Xu
Acked-by: Kevin Tian
Reviewed-by: Jan Beulich
CC: Jun Nakajima
CC: Kevin Tian
CC: George Dunlap
CC: Jan Beulich
CC: Andrew Cooper
CC: Feng Wu
---
From: Quan Xu
Signed-off-by: Quan Xu
Reviewed-by: Jan Beulich
CC: Jan Beulich
CC: Kevin Tian
CC: Feng Wu
v6: Don't needlessly split the function header onto two lines.
---
xen/drivers/passthrough/vtd/extern.h | 3 ++-
xen/drivers/passthrough/vtd/iommu.c | 8
xen/drivers/passth
The ARM Server Base System Architecture describes a generic UART
interface. It doesn't support clock control registers, modem
control, DMA and hardware flow control features. So, extend the
driver probe() to handle SBSA interface and skip the accessing
PL011 registers that are not described in SBSA
From: Quan Xu
The propagation value from IOMMU flush interfaces may be positive, which
indicates callers need to flush cache, not one of faliures.
when the propagation value is positive, this patch fixes this flush issue
as follows:
- call iommu_flush_write_buffer() to flush cache.
- return
On Tue, May 31, 2016 at 1:10 PM, Jan Beulich wrote:
On 31.05.16 at 13:32, wrote:
>> On Tue, May 31, 2016 at 12:16 PM, Olaf Hering wrote:
>>> On Tue, May 31, George Dunlap wrote:
>>>
On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
> With staging-4.6 this domU boots from xvda,
flight 94971 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94971/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 94748
test-amd64-amd64-
On Tue, May 31, 2016 at 06:48:48AM -0600, Jan Beulich wrote:
> >>> On 31.05.16 at 14:25, wrote:
> > On Mon, May 30, 2016 at 03:52:57AM -0600, Jan Beulich wrote:
> >> Commit 7fb252bd41 ("build/xen: fix assembler instruction tests") added
> >> $(AFLAGS) here, which results in all of those tests now
>>> On 31.05.16 at 14:25, wrote:
> On Mon, May 30, 2016 at 03:52:57AM -0600, Jan Beulich wrote:
>> Commit 7fb252bd41 ("build/xen: fix assembler instruction tests") added
>> $(AFLAGS) here, which results in all of those tests now failing.
>> Certain items need to be removed for things to work again
>>> On 31.05.16 at 12:30, wrote:
> On 30/05/16 14:48, Jan Beulich wrote:
>> --- a/xen/arch/x86/setup.c
>> +++ b/xen/arch/x86/setup.c
>> @@ -1044,13 +1044,19 @@ void __init noreturn __start_xen(unsigne
>> }
>>
>> #ifdef CONFIG_KEXEC
>> -/* Don't overlap with modules. */
>> -
On Mon, May 30, 2016 at 03:52:57AM -0600, Jan Beulich wrote:
> Commit 7fb252bd41 ("build/xen: fix assembler instruction tests") added
> $(AFLAGS) here, which results in all of those tests now failing.
> Certain items need to be removed for things to work again.
>
> Signed-off-by: Jan Beulich
>
>>> On 31.05.16 at 14:00, wrote:
> Really 'vdev' string in the the guest config file is only meant to
> tell libxl how it should behave -- it should ideally not have any
> effect on what devices you see in the backend. And furthermore, it
> seems to me that when Linux upstream rejected the idea o
flight 94979 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94979/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken REG
>>> On 31.05.16 at 13:32, wrote:
> On Tue, May 31, 2016 at 12:16 PM, Olaf Hering wrote:
>> On Tue, May 31, George Dunlap wrote:
>>
>>> On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
>>> > With staging-4.6 this domU boots from xvda, qemu creates an emulated
>>> > disk. With staging no disk i
On Tue, May 31, George Dunlap wrote:
> Do you have a concrete proposal?
I have to give it some more thought what the impact really is, what
config variants are affected.
Olaf
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-
On Tue, May 31, 2016 at 12:41 PM, Olaf Hering wrote:
> On Tue, May 31, George Dunlap wrote:
>
>> Sorry, can you expand on this a bit? Are you saying that on SuSE, if
>> you specify "vdev=xvda" in your config file, that you'll get PV
>> devices named "/dev/xvda", but that if you specify "vdev=hda"
>>> On 31.05.16 at 12:27, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Friday, May 27, 2016 10:00 PM
>> >>> On 26.05.16 at 15:39, wrote:
>> > Normally, in vmx_cpu_block() 'NDST' filed should have the same
>> > value with 'dest' or 'MASK_INSR(dest, PI_xAPIC_NDST_MASK)' depending
>>> On 31.05.16 at 12:22, wrote:
>
>> -Original Message-
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Friday, May 27, 2016 9:49 PM
>> To: Wu, Feng
>> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
>> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>> de...@lists.x
>>> On 31.05.16 at 12:22, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Friday, May 27, 2016 9:43 PM
>> >>> On 26.05.16 at 15:39, wrote:
>> > --- a/xen/arch/x86/hvm/vmx/vmx.c
>> > +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> > @@ -113,7 +113,19 @@ static void vmx_vcpu_block(struct vcpu *
On Tue, May 31, George Dunlap wrote:
> Sorry, can you expand on this a bit? Are you saying that on SuSE, if
> you specify "vdev=xvda" in your config file, that you'll get PV
> devices named "/dev/xvda", but that if you specify "vdev=hda", that
> you'll get PV devices but named "/dev/hda"?
Yes, t
On Tue, May 31, 2016 at 10:40:13AM +0100, Stefano Stabellini wrote:
> On Mon, 30 May 2016, Julien Grall wrote:
> > (CC Wei Liu)
> >
> > Hi Stefano,
> >
> > On 30/05/2016 14:16, Stefano Stabellini wrote:
> > > On Fri, 27 May 2016, Julien Grall wrote:
> > > > Hello Shanker,
> > > >
> > > > On 27/0
On Mon, May 30, 2016 at 03:52:57AM -0600, Jan Beulich wrote:
> Commit 7fb252bd41 ("build/xen: fix assembler instruction tests") added
> $(AFLAGS) here, which results in all of those tests now failing.
> Certain items need to be removed for things to work again.
>
> Signed-off-by: Jan Beulich
Ack
On Tue, May 31, 2016 at 12:16 PM, Olaf Hering wrote:
> On Tue, May 31, George Dunlap wrote:
>
>> On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
>> > With staging-4.6 this domU boots from xvda, qemu creates an emulated
>> > disk. With staging no disk is found, unless the name is changed to hd
flight 94967 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/94967/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-rtds 6 xen-boot fail in 94959 pass in 94967
test-armhf-armhf-xl-rtds 15 gu
On Tue, May 31, George Dunlap wrote:
> On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
> > With staging-4.6 this domU boots from xvda, qemu creates an emulated
> > disk. With staging no disk is found, unless the name is changed to hda.
> > Looks like qemu-2.6 does not handle xvda either.
>
>
Hi Shanker,
On 27/05/16 19:32, Shanker Donthineni wrote:
The current driver ACPI probe fails on hardware which has GICv4
version, even though it is fully compatible to GICv3. This patch
fixed the issue by registering the same probe function for GICv4
hardware.
Signed-off-by: Shanker Donthineni
Hi Peng,
On 27/05/16 11:23, Peng Fan wrote:
To ARM64, we should use '(VMAP_VIRT_START + GB(1))' as VMAP_VIRT_END,
s/To/For/
but not '(VMAP_VIRT_START + GB(1) - 1)'.
Seeing 'vm_end[type] = PFN_DOWN(end - start);' in vm_init_type,
if not correct VMAP_VIRT_END, one page is wasted.
I find dif
On Mon, May 30, 2016 at 9:42 PM, Olaf Hering wrote:
> With staging-4.6 this domU boots from xvda, qemu creates an emulated
> disk. With staging no disk is found, unless the name is changed to hda.
> Looks like qemu-2.6 does not handle xvda either.
This was intentional; see this thread:
https://m
>>> On 31.05.16 at 12:31, wrote:
> On Tue, May 31, 2016 at 02:16:49AM -0600, Jan Beulich wrote:
>> >>> On 30.05.16 at 18:27, wrote:
>> > For all the build process, not only the assembly-only files.
>> >
>> > This prevents assembling certain code with the integrated assembler, while
>> > other co
>>> On 31.05.16 at 12:24, wrote:
> On 30/05/16 14:48, Jan Beulich wrote:
>> Rather than just allowing a fixed address or fully automatic placement,
>> also allow for specifying an upper bound. Especially on EFI systems,
>> where firmware memory use is commonly less predictable than on legacy
>> BI
Hi Shannon,
On 31/05/16 06:02, Shannon Zhao wrote:
From: Shannon Zhao
The design of this feature is described as below.
Firstly, the toolstack (libxl) generates the ACPI tables according the
number of vcpus and gic controller.
Then, it copies these ACPI tables to DomU memory space and passes
Hello Dirk,
On 27/05/16 13:34, Dirk Behme wrote:
On 26.05.2016 11:00, Julien Grall wrote:
On 25/05/2016 16:10, Dirk Behme wrote:
On 24.05.2016 22:05, Julien Grall wrote:
On 24/05/2016 14:39, Dirk Behme wrote:
On 23.05.2016 22:15, Julien Grall wrote:
All the devices (UART included) used by X
On Mon, May 30, 2016 at 3:32 AM, Chris Patterson wrote:
> From: Chris Patterson
>
> Replace the usage of readdir_r() with readdir() to address
> a compilation error due to the deprecation of readdir_r.
>
> glibc has deprecated this for their next release (2.24):
> https://sourceware.org/bugzilla/
Hi Stefano,
On 31/05/16 10:34, Stefano Stabellini wrote:
On Mon, 30 May 2016, Julien Grall wrote:
On 30/05/2016 17:19, Stefano Stabellini wrote:
"Erratum #834220: Xen needs to check that the Stage 1 translation does not
generate a fault before handling Stage 2 fault. If it is a stage 1
transla
Hi Stefano,
On 31/05/16 10:27, Stefano Stabellini wrote:
On Mon, 30 May 2016, Julien Grall wrote:
On 30/05/2016 16:02, Stefano Stabellini wrote:
On Mon, 23 May 2016, Julien Grall wrote:
After each CPU has been started, we iterate through a list of CPU
errata to detect CPUs which need from hyp
On 05/31/16 06:59, Shannon Zhao wrote:
> From: Shannon Zhao
>
> Add ACPI support for Virt Xen ARM and it gets the ACPI tables through
> Xen ARM multiboot protocol.
>
> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Shannon Zhao
> ---
> The corresponding Xen patches can
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Friday, May 27, 2016 10:57 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
> de...@lists.xen.org; konrad.w...@oracle.com; k...@xen.o
On Tue, May 31, 2016 at 02:16:49AM -0600, Jan Beulich wrote:
> >>> On 30.05.16 at 18:27, wrote:
> > For all the build process, not only the assembly-only files.
> >
> > This prevents assembling certain code with the integrated assembler, while
> > other code would be assembled by the external ass
On 30/05/16 14:48, Jan Beulich wrote:
> Rather than just allowing a fixed address or fully automatic placement,
> also allow for specifying an upper bound. Especially on EFI systems,
> where firmware memory use is commonly less predictable than on legacy
> BIOS ones, this makes success of the reser
1 - 100 of 133 matches
Mail list logo
