On 15.01.2020 10:40, Jan Beulich wrote:
> On 14.01.2020 18:27, Andrew Cooper wrote:
>> On 14/01/2020 17:02, Jan Beulich wrote:
>>> Even when that remaining issue got addressed, I think it would be better
>>> to keep it, altering the bound to GB(1).
>>
>> A 1G check wouldn't be correct.
>>
>> We've
On 15.01.2020 11:00, Roger Pau Monné wrote:
> On Wed, Jan 15, 2020 at 10:56:37AM +0100, Roger Pau Monné wrote:
>> On Fri, Dec 20, 2019 at 05:26:34PM +0100, Jan Beulich wrote:
>>> On 17.07.2019 08:47, Jan Beulich wrote:
With non-empty CONFIG_DOM0_MEM clang5 produces
flight 146108 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146108/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen b4194711ffaffa5e63d986338fb8d4020fa6bad1
baseline version:
xen
On Wed, Jan 15, 2020 at 10:56:37AM +0100, Roger Pau Monné wrote:
> On Fri, Dec 20, 2019 at 05:26:34PM +0100, Jan Beulich wrote:
> > On 17.07.2019 08:47, Jan Beulich wrote:
> > > With non-empty CONFIG_DOM0_MEM clang5 produces
> > >
> > > dom0_build.c:344:24: error: use of logical '&&' with
On 12/27/19 5:06 PM, Andrew Cooper wrote:
> On 02/12/2019 08:22, Andy Smith wrote:
>> Hi,
>>
>> I've been looking into live patching for the first time.
>
> CC'ing livepatch maintainers.
>
>>
>> Starting with a 4.12.1 build:
>>
>> $ cd ~/dev
>> $ ls -l
>> total 8
>> drwxr-xr-x 3 andy andy 4096
On Fri, Dec 20, 2019 at 05:26:34PM +0100, Jan Beulich wrote:
> On 17.07.2019 08:47, Jan Beulich wrote:
> > With non-empty CONFIG_DOM0_MEM clang5 produces
> >
> > dom0_build.c:344:24: error: use of logical '&&' with constant operand
> > [-Werror,-Wconstant-logical-operand]
> > if (
flight 146090 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146090/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs. 145767
On Tue, Jan 14, 2020 at 07:36:21PM +, Igor Druzhinin wrote:
> If ITSC is not available on CPU (e.g if running nested as PV shim)
> then X86_FEATURE_NONSTOP_TSC is not advertised in certain cases, i.e.
> all AMD and some old Intel processors. In which case TSC would need to
> be restored on CPU
On 14.01.2020 18:27, Andrew Cooper wrote:
> On 14/01/2020 17:02, Jan Beulich wrote:
>> On 13.01.2020 18:50, Andrew Cooper wrote:
>>> --- a/xen/arch/x86/boot/head.S
>>> +++ b/xen/arch/x86/boot/head.S
>>> @@ -687,14 +687,19 @@ trampoline_setup:
>>> * handling/walking), and identity map Xen
flight 146095 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146095/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 144861
build-arm64
On 19/12/2019 16:14, Jürgen Groß wrote:
> On 19.12.19 13:45, Sergey Dyasli wrote:
>> Hi Juergen,
>>
>> We recently did another quick test of core scheduling mode, and the following
>> failures were found:
>>
>> 1. live-patch apply failures:
>>
>> (XEN) [ 1058.751974] livepatch: lp_1_1: Timed
On 14.01.2020 20:31, Andrew Cooper wrote:
> On 14/01/2020 16:45, Jan Beulich wrote:
>> On 13.01.2020 18:50, Andrew Cooper wrote:
>>> --- a/xen/arch/x86/boot/head.S
>>> +++ b/xen/arch/x86/boot/head.S
>>> @@ -668,6 +668,20 @@ trampoline_setup:
>>> add
flight 146079 xen-4.13-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/146079/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-prev 6 xen-buildfail REGR. vs. 145145
> -Original Message-
>
> > Linux PCI subsytem has an option resource_alignment that can be
> > applied to either a single device or all devices. Booting with
> > pci=resource_aligment=4096 will align each device to a page. Do you
> > think pciback should force resource_alignment=4096
101 - 114 of 114 matches
Mail list logo
