>>> On 29.03.19 at 21:40, wrote:
> I can't think of any instruction which uses %rbp in this way.
> ENTER/LEAVE/PUSHA/POPA use/modify it, but only in its integer form - not
> as a memory address.
ENTER with a nesting level above 1 will use %rbp as a memory
address (or to be precise, %rbp minus so
On 01/04/2019 08:41, Jan Beulich wrote:
On 29.03.19 at 16:08, wrote:
>> Via boot parameter sched_granularity=core (or sched_granularity=socket)
>> it is possible to change the scheduling granularity from thread (the
>> default) to either whole cores or even sockets.
>
> One further general q
>>> On 29.03.19 at 16:08, wrote:
> Via boot parameter sched_granularity=core (or sched_granularity=socket)
> it is possible to change the scheduling granularity from thread (the
> default) to either whole cores or even sockets.
One further general question came to mind: How about also having
"sch
On 22/03/2019 08:37, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> This is the ABI for the two halves of a para-virtualized
> camera driver which extends Xen's reach multimedia capabilities even
> farther enabling it for video conferencing, In-Vehicle Infotainment,
> high def
flight 134236 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134236/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 broken
build-arm64-xsm
On 30/03/2019 11:24, Juergen Gross wrote:
> On 29/03/2019 19:42, Andrew Cooper wrote:
>> On 29/03/2019 15:08, Juergen Gross wrote:
>>> diff --git a/xen/common/schedule.c b/xen/common/schedule.c
>>> index 6b5d454630..d1a958143a 100644
>>> --- a/xen/common/schedule.c
>>> +++ b/xen/common/schedule.c
>
On 30/03/2019 10:59, Juergen Gross wrote:
> On 29/03/2019 22:33, Andrew Cooper wrote:
>> On 29/03/2019 15:09, Juergen Gross wrote:
>>> diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
>>> index 8d579e2cf9..5d8f3255cb 100644
>>> --- a/xen/arch/x86/domain.c
>>> +++ b/xen/arch/x86/domain.c
>
Hi Andrew,
On Tue, Mar 19, 2019 at 7:47 AM Souptick Joarder wrote:
>
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
> be g
flight 134231 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134231/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64
I hit an issue generating a livepatch for a recent xsa. I saw the
following lines from the create-diff-object.log ...
/livepatch-build-tools/create-diff-object: ERROR: grant_table.o:
kpatch_regenerate_special_section: 1162: group size mismatch for section
.altinstructions
This looks really s
flight 134246 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134246/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-xs
> So this is the 3rd variant of v2 that you've sent, without making it clear
> what the difference is. I suppose you've addressed my one remaining
> cosmetic request and added my R-b, but we should be at v4 then.
Yes. Since these are all style change, I kept the version number 2.
Sorry for the con
flight 134192 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134192/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 broken
build-arm64-xsm
flight 134233 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134233/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-xs
flight 134228 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134228/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64-xsm
flight 134219 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134219/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
flight 134218 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134218/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64
flight 134186 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134186/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-pvops
flight 134209 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134209/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-pvopsbroken
build-arm64-xsm
flight 134234 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134234/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
coverity-amd647 coverity-upload fail REGR. vs. 133615
version t
flight 134229 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134229/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm broken
build-arm64-xs
flight 134208 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/134208/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 broken
build-arm64-xsm
Hello.
There is problem in PCI device allocation algorithm (pci_setup()).
Algorithm allocates PCI BAR sorted by size and this allows
mixed allocation of prefetchable and non-prefetchable PCI MEM BAR.
This leads to wrong config of PCI root port (see "Type 1 Configuration
Space Registers (Root Por
23 matches
Mail list logo
