Hi,
> On 5 Jun 2020, at 03:29, CodeWiz2280 wrote:
>
> On Thu, Jun 4, 2020 at 2:24 PM Julien Grall wrote:
>>
>> Hi,
>>
>> On 04/06/2020 13:07, CodeWiz2280 wrote:
>>> On Thu, Jun 4, 2020 at 6:16 AM Julien Grall wrote:
Hi,
On 04/06/2020 10:08, Bertrand Marquis wrote:
>
At some point (maybe PVHv1?) mediated access to the RTC was provided
for PVH dom0 using the PV code paths (guest_io_{write/read}). At some
point this code has been made PV specific and unhooked from the
current PVH IO path. This patch provides such mediated access to the
RTC for PVH dom0, just like
Both match prior generation processors as far as LBR and C-state MSRs
go (SDM rev 072) as well as applicability of the if_pschange_mc erratum
(recent spec updates).
Signed-off-by: Jan Beulich
---
Such changes having been subject to backporting in the past, this
change may want considering for 4.1
On Fri, Jun 05, 2020 at 09:51:09AM +0200, Jan Beulich wrote:
> Both match prior generation processors as far as LBR and C-state MSRs
> go (SDM rev 072) as well as applicability of the if_pschange_mc erratum
> (recent spec updates).
>
> Signed-off-by: Jan Beulich
> ---
> Such changes having been s
> -Original Message-
> From: Roger Pau Monne
> Sent: 05 June 2020 08:50
> To: xen-devel@lists.xenproject.org
> Cc: p...@xen.org; Roger Pau Monne ; Jan Beulich
> ; Andrew
> Cooper ; Wei Liu
> Subject: [PATCH for-4.14] x86/rtc: provide mediated access to RTC for PVH dom0
>
> At some point
On 05.06.2020 10:02, Roger Pau Monné wrote:
> On Fri, Jun 05, 2020 at 09:51:09AM +0200, Jan Beulich wrote:
>> Both match prior generation processors as far as LBR and C-state MSRs
>> go (SDM rev 072) as well as applicability of the if_pschange_mc erratum
>> (recent spec updates).
>>
>> Signed-off-b
On 04.06.2020 22:58, Andrew Cooper wrote:
> On 04/06/2020 21:52, Andrew Cooper wrote:
>> The cronjob which renders https://xenbits.xen.org/docs/ has been broken for a
>> while. commitish_version() pulls an old version of xen/Makefile out of
>> history, and uses the xenversion rule.
>>
>> Currently
On Fri, Jun 05, 2020 at 10:10:01AM +0200, Jan Beulich wrote:
> On 05.06.2020 10:02, Roger Pau Monné wrote:
> > On Fri, Jun 05, 2020 at 09:51:09AM +0200, Jan Beulich wrote:
> >> Both match prior generation processors as far as LBR and C-state MSRs
> >> go (SDM rev 072) as well as applicability of th
On 05.06.2020 09:50, Roger Pau Monne wrote:
> At some point (maybe PVHv1?) mediated access to the RTC was provided
> for PVH dom0 using the PV code paths (guest_io_{write/read}). At some
> point this code has been made PV specific and unhooked from the
> current PVH IO path.
I don't suppose you've
On Fri, Jun 05, 2020 at 09:03:11AM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Roger Pau Monne
> > Sent: 05 June 2020 08:50
> > To: xen-devel@lists.xenproject.org
> > Cc: p...@xen.org; Roger Pau Monne ; Jan Beulich
> > ; Andrew
> > Cooper ; Wei Liu
> > Subject: [PATCH for
On 05.06.2020 10:46, Roger Pau Monné wrote:
> On Fri, Jun 05, 2020 at 10:10:01AM +0200, Jan Beulich wrote:
>> On 05.06.2020 10:02, Roger Pau Monné wrote:
>>> On Fri, Jun 05, 2020 at 09:51:09AM +0200, Jan Beulich wrote:
Both match prior generation processors as far as LBR and C-state MSRs
On 04.06.2020 16:25, Marek Marczykowski-Górecki wrote:
> On Thu, Jun 04, 2020 at 02:36:26PM +0200, Jan Beulich wrote:
>> On 04.06.2020 13:13, Andrew Cooper wrote:
>>> On 04/06/2020 08:08, Jan Beulich wrote:
On 04.06.2020 03:46, Marek Marczykowski-Górecki wrote:
> Then, we get the main issu
Hi,
I'm running a small Xen PVH domain and upgrading from vanilla 5.6.0 to
5.7.0 caused the splat below, really early during boot. The configuration
has not changed, all new "make oldconfig" prompts have been answered with
"N". Old and new config, dmesg are here:
http://nerdbynature.de/bits/
On 05.06.20 10:36, Christian Kujau wrote:
Hi,
I'm running a small Xen PVH domain and upgrading from vanilla 5.6.0 to
5.7.0 caused the splat below, really early during boot. The configuration
has not changed, all new "make oldconfig" prompts have been answered with
"N". Old and new config, dmesg
On Fri, Jun 05, 2020 at 10:54:22AM +0200, Jan Beulich wrote:
> On 05.06.2020 10:46, Roger Pau Monné wrote:
> > On Fri, Jun 05, 2020 at 10:10:01AM +0200, Jan Beulich wrote:
> >> On 05.06.2020 10:02, Roger Pau Monné wrote:
> >>> On Fri, Jun 05, 2020 at 09:51:09AM +0200, Jan Beulich wrote:
> Both
On Fri, Jun 05, 2020 at 10:48:48AM +0200, Jan Beulich wrote:
> On 05.06.2020 09:50, Roger Pau Monne wrote:
> > At some point (maybe PVHv1?) mediated access to the RTC was provided
> > for PVH dom0 using the PV code paths (guest_io_{write/read}). At some
> > point this code has been made PV specific
On 05.06.2020 11:09, Jan Beulich wrote:
> On 04.06.2020 16:25, Marek Marczykowski-Górecki wrote:
>> (XEN) hvm.c:1620:d6v0 All CPUs offline -- powering off.
>> (XEN) d3v0 handle_pio port 0xb004 read 0x
>> (XEN) d3v0 handle_pio port 0xb004 read 0x
>> (XEN) d3v0 handle_pio port 0xb004 write 0x
On 04.06.2020 03:46, Marek Marczykowski-Górecki wrote:
> Hi,
>
> (continuation of a thread from #xendevel)
>
> During system shutdown quite often I hit infinite stream of errors like
> this:
>
> (XEN) d3v0 Weird PIO status 1, port 0xb004 read 0x
> (XEN) domain_crash called from io.c:
On 05.06.2020 11:20, Roger Pau Monné wrote:
> On Fri, Jun 05, 2020 at 10:48:48AM +0200, Jan Beulich wrote:
>> On 05.06.2020 09:50, Roger Pau Monne wrote:
>>> At some point (maybe PVHv1?) mediated access to the RTC was provided
>>> for PVH dom0 using the PV code paths (guest_io_{write/read}). At som
flight 150813 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150813/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 150438
Tests which
Andrew Cooper writes ("Re: [PATCH for-4.14 RFC] docs/support-matrix: Gross
bodge to unbreak docs rendering"):
> Actually - it occurs to me that we only want the major and minor number.
>
> I think it is reasonable to expect that those will always be plain
> numbers, and we can grep them directly
Jan Beulich writes ("Re: [PATCH for-4.14 RFC] docs/support-matrix: Gross bodge
to unbreak docs rendering"):
> I was about to ask why we don't do that.
When I wrote the code in question, I was afraid that this makefile
would change in a way that would break that approach. Unfortunately
it seems I
> On 4. Jun 2020, at 16:12, Andrew Cooper wrote:
>
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
>
>
>
> xenconsoled doesn't automatically convert \n into \r\n, wh
Mediated access to the RTC was provided for PVHv1 dom0 using the PV
code paths (guest_io_{write/read}), but those accesses where never
implemented for PVHv2 dom0. This patch provides such mediated accesses
to the RTC for PVH dom0, just like it's provided for a classic PV
dom0.
Pull out some of the
Sorry, only just catching up with this...
> -Original Message-
> From: Jan Beulich
> Sent: 05 June 2020 10:09
> To: Marek Marczykowski-Górecki
> Cc: Andrew Cooper ; xen-devel
> ; Paul
> Durrant
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
>
On Fri, Jun 05, 2020 at 11:38:17AM +0200, Jan Beulich wrote:
> On 04.06.2020 03:46, Marek Marczykowski-Górecki wrote:
> > Hi,
> >
> > (continuation of a thread from #xendevel)
> >
> > During system shutdown quite often I hit infinite stream of errors like
> > this:
> >
> > (XEN) d3v0 Weird P
> -Original Message-
> From: Paul Durrant
> Sent: 05 June 2020 12:06
> To: 'Jan Beulich' ; 'Marek Marczykowski-Górecki'
>
> Cc: 'Andrew Cooper' ; 'xen-devel'
>
> Subject: RE: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> Sorry, only just catching up with
Its name is "zlib" not "z".
Reported-by: Olaf Hering
Fixes: 86234eafb952 ("libs: add libxenhypfs")
Signed-off-by: Wei Liu
---
Cc: p...@xen.org
Cc: jgr...@suse.com
---
tools/libs/hypfs/xenhypfs.pc.in | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libs/hypfs/xenhypfs.pc
On 05.06.20 13:37, Wei Liu wrote:
Its name is "zlib" not "z".
Reported-by: Olaf Hering
Fixes: 86234eafb952 ("libs: add libxenhypfs")
Signed-off-by: Wei Liu
Reviewed-by: Juergen Gross
Juergen
On Fri, Jun 05, 2020 at 01:02:39PM +0200, Roger Pau Monne wrote:
> Mediated access to the RTC was provided for PVHv1 dom0 using the PV
> code paths (guest_io_{write/read}), but those accesses where never
> implemented for PVHv2 dom0. This patch provides such mediated accesses
> to the RTC for PVH d
flight 150819 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150819/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 8035edbe12f0f2a58e8fa9b06d05c8ee1c69ffae
baseline version:
ovmf bb78cfbec07eda45118b6
> -Original Message-
> From: Roger Pau Monne
> Sent: 05 June 2020 12:03
> To: xen-devel@lists.xenproject.org
> Cc: p...@xen.org; Roger Pau Monne ; Jan Beulich
> ; Andrew
> Cooper ; Wei Liu
> Subject: [PATCH for-4.14 v2] x86/rtc: provide mediated access to RTC for PVH
> dom0
>
> Mediate
> -Original Message-
> From: Jürgen Groß
> Sent: 05 June 2020 12:43
> To: Wei Liu ; Xen Development List
>
> Cc: Olaf Hering ; p...@xen.org; Ian Jackson
>
> Subject: Re: [PATCH for-4.14] libs/hypfs: use correct zlib name in pc file
>
> On 05.06.20 13:37, Wei Liu wrote:
> > Its name is
On Fri, Jun 05, 2020 at 11:22:46AM +0200, Jan Beulich wrote:
> On 05.06.2020 11:09, Jan Beulich wrote:
> > On 04.06.2020 16:25, Marek Marczykowski-Górecki wrote:
> >> (XEN) hvm.c:1620:d6v0 All CPUs offline -- powering off.
> >> (XEN) d3v0 handle_pio port 0xb004 read 0x
> >> (XEN) d3v0 handle_pi
On Fri, Jun 5, 2020 at 3:37 AM Bertrand Marquis
wrote:
>
> Hi,
>
> > On 5 Jun 2020, at 03:29, CodeWiz2280 wrote:
> >
> > On Thu, Jun 4, 2020 at 2:24 PM Julien Grall wrote:
> >>
> >> Hi,
> >>
> >> On 04/06/2020 13:07, CodeWiz2280 wrote:
> >>> On Thu, Jun 4, 2020 at 6:16 AM Julien Grall wrote:
>
Hi,
On 05/06/2020 13:25, CodeWiz2280 wrote:
The Keystone uses the netcp driver, which has interrupts from 40-79
listed in the device tree (arch/arm/boot/keystone-k2e-netcp.dtsi).
I'm using the same device tree between my non-xen standalone kernel
and my dom0 kernel booted by xen. In the standal
> -Original Message-
> From: Marek Marczykowski-Górecki
> Sent: 05 June 2020 13:02
> To: Jan Beulich
> Cc: Andrew Cooper ; Paul Durrant ;
> xen-devel de...@lists.xenproject.org>
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On Fri, Jun 05,
On Fri, Jun 5, 2020 at 8:30 AM Julien Grall wrote:
>
> Hi,
>
> On 05/06/2020 13:25, CodeWiz2280 wrote:
> > The Keystone uses the netcp driver, which has interrupts from 40-79
> > listed in the device tree (arch/arm/boot/keystone-k2e-netcp.dtsi).
> > I'm using the same device tree between my non-xe
On 05/06/2020 13:01, Marek Marczykowski-Górecki wrote:
> On Fri, Jun 05, 2020 at 11:22:46AM +0200, Jan Beulich wrote:
>> On 05.06.2020 11:09, Jan Beulich wrote:
>>> On 04.06.2020 16:25, Marek Marczykowski-Górecki wrote:
(XEN) hvm.c:1620:d6v0 All CPUs offline -- powering off.
(XEN) d3v0 ha
> On 5 Jun 2020, at 13:42, CodeWiz2280 wrote:
>
> On Fri, Jun 5, 2020 at 8:30 AM Julien Grall wrote:
>>
>> Hi,
>>
>> On 05/06/2020 13:25, CodeWiz2280 wrote:
>>> The Keystone uses the netcp driver, which has interrupts from 40-79
>>> listed in the device tree (arch/arm/boot/keystone-k2e-netc
On Fri, Jun 05, 2020 at 01:39:31PM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Marek Marczykowski-Górecki
> > Sent: 05 June 2020 13:02
> > To: Jan Beulich
> > Cc: Andrew Cooper ; Paul Durrant ;
> > xen-devel > de...@lists.xenproject.org>
> > Subject: Re: handle_pio loopi
> -Original Message-
> From: 'Marek Marczykowski-Górecki'
> Sent: 05 June 2020 14:04
> To: p...@xen.org
> Cc: 'Jan Beulich' ; 'Andrew Cooper'
> ; 'xen-devel' de...@lists.xenproject.org>
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On Fri, J
On 05.06.2020 13:05, Paul Durrant wrote:
> Sorry, only just catching up with this...
>
>> -Original Message-
>> From: Jan Beulich
>> Sent: 05 June 2020 10:09
>> To: Marek Marczykowski-Górecki
>> Cc: Andrew Cooper ; xen-devel
>> ; Paul
>> Durrant
>> Subject: Re: handle_pio looping durin
On 05.06.2020 13:25, Paul Durrant wrote:
>> -Original Message-
>> From: Paul Durrant
>> Sent: 05 June 2020 12:06
>> To: 'Jan Beulich' ; 'Marek Marczykowski-Górecki'
>>
>> Cc: 'Andrew Cooper' ; 'xen-devel'
>>
>> Subject: RE: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> -Original Message-
> From: Jan Beulich
> Sent: 05 June 2020 14:32
> To: p...@xen.org
> Cc: 'Marek Marczykowski-Górecki' ; 'Andrew
> Cooper'
> ; 'xen-devel'
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On 05.06.2020 13:05, Paul Durrant wro
> -Original Message-
> From: Jan Beulich
> Sent: 05 June 2020 14:37
> To: p...@xen.org
> Cc: 'Marek Marczykowski-Górecki' ; 'Andrew
> Cooper'
> ; 'xen-devel'
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On 05.06.2020 13:25, Paul Durrant wro
On 05.06.2020 15:43, Paul Durrant wrote:
>> -Original Message-
>> From: Jan Beulich
>> Sent: 05 June 2020 14:37
>> To: p...@xen.org
>> Cc: 'Marek Marczykowski-Górecki' ; 'Andrew
>> Cooper'
>> ; 'xen-devel'
>> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
>>
> -Original Message-
> From: Jan Beulich
> Sent: 05 June 2020 14:47
> To: p...@xen.org
> Cc: 'Marek Marczykowski-Górecki' ; 'Andrew
> Cooper'
> ; 'xen-devel'
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On 05.06.2020 15:43, Paul Durrant wro
On 05.06.2020 15:37, Paul Durrant wrote:
>> -Original Message-
>> From: Jan Beulich
>> Sent: 05 June 2020 14:32
>> To: p...@xen.org
>> Cc: 'Marek Marczykowski-Górecki' ; 'Andrew
>> Cooper'
>> ; 'xen-devel'
>> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
>>
flight 150825 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150825/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 150438
Tests which
On 05.06.2020 13:18, Marek Marczykowski-Górecki wrote:
> On Fri, Jun 05, 2020 at 11:38:17AM +0200, Jan Beulich wrote:
>> On 04.06.2020 03:46, Marek Marczykowski-Górecki wrote:
>>> Hi,
>>>
>>> (continuation of a thread from #xendevel)
>>>
>>> During system shutdown quite often I hit infinite stream
On 05.06.2020 14:01, Marek Marczykowski-Górecki wrote:
> On Fri, Jun 05, 2020 at 11:22:46AM +0200, Jan Beulich wrote:
>> On 05.06.2020 11:09, Jan Beulich wrote:
>>> On 04.06.2020 16:25, Marek Marczykowski-Górecki wrote:
(XEN) hvm.c:1620:d6v0 All CPUs offline -- powering off.
(XEN) d3v0 ha
On Fri, Jun 05, 2020 at 12:05:12PM +0200, Jan Beulich wrote:
> On 05.06.2020 11:20, Roger Pau Monné wrote:
> > On Fri, Jun 05, 2020 at 10:48:48AM +0200, Jan Beulich wrote:
> >> On 05.06.2020 09:50, Roger Pau Monne wrote:
> >>> This patch provides such mediated access to the
> >>> RTC for PVH dom0,
On 05.06.2020 16:16, Roger Pau Monné wrote:
> On Fri, Jun 05, 2020 at 12:05:12PM +0200, Jan Beulich wrote:
>> On 05.06.2020 11:20, Roger Pau Monné wrote:
>>> On Fri, Jun 05, 2020 at 10:48:48AM +0200, Jan Beulich wrote:
On 05.06.2020 09:50, Roger Pau Monne wrote:
> This patch provides such
flight 150814 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150814/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-rtds 18 guest-localmigrate/x10 fail blocked in 150663
test-amd64-amd64-xl-qemut-win7-amd64
While the issue is more general, I noticed that asm-macros.i not getting
re-generated as needed. This was due to its .*.d file mentioning
asm-macros.o instead of asm-macros.i. Use -MQ here as well, and while at
it also use -MQ to avoid the somewhat fragile sed-ary on the *.lds
dependency tracking f
On 05/06/2020 15:22, Jan Beulich wrote:
> While the issue is more general, I noticed that asm-macros.i not getting
> re-generated as needed. This was due to its .*.d file mentioning
> asm-macros.o instead of asm-macros.i. Use -MQ here as well, and while at
> it also use -MQ to avoid the somewhat fr
On 05.06.2020 13:02, Roger Pau Monne wrote:
> Mediated access to the RTC was provided for PVHv1 dom0 using the PV
> code paths (guest_io_{write/read}), but those accesses where never
> implemented for PVHv2 dom0. This patch provides such mediated accesses
> to the RTC for PVH dom0, just like it's p
On Fri, Jun 05, 2020 at 04:20:31PM +0200, Jan Beulich wrote:
> On 05.06.2020 16:16, Roger Pau Monné wrote:
> > On Fri, Jun 05, 2020 at 12:05:12PM +0200, Jan Beulich wrote:
> >> On 05.06.2020 11:20, Roger Pau Monné wrote:
> >>> On Fri, Jun 05, 2020 at 10:48:48AM +0200, Jan Beulich wrote:
> On 0
Paul Durrant writes ("RE: [PATCH for-4.14] libs/hypfs: use correct zlib name in
pc file"):
> > -Original Message-
> > From: Jürgen Groß
> > Sent: 05 June 2020 12:43
> > To: Wei Liu ; Xen Development List
> >
> > Cc: Olaf Hering ; p...@xen.org; Ian Jackson
> >
> > Subject: Re: [PATCH f
On Fri, Jun 05, 2020 at 04:45:28PM +0200, Roger Pau Monné wrote:
> On Fri, Jun 05, 2020 at 04:20:31PM +0200, Jan Beulich wrote:
> > On 05.06.2020 16:16, Roger Pau Monné wrote:
> > > On Fri, Jun 05, 2020 at 12:05:12PM +0200, Jan Beulich wrote:
> > >> On 05.06.2020 11:20, Roger Pau Monné wrote:
> > >
On Fri, Jun 5, 2020 at 8:47 AM Bertrand Marquis
wrote:
>
>
>
> > On 5 Jun 2020, at 13:42, CodeWiz2280 wrote:
> >
> > On Fri, Jun 5, 2020 at 8:30 AM Julien Grall wrote:
> >>
> >> Hi,
> >>
> >> On 05/06/2020 13:25, CodeWiz2280 wrote:
> >>> The Keystone uses the netcp driver, which has interrupts f
> -Original Message-
> From: Xen-devel On Behalf Of Jan
> Beulich
> Sent: 05 June 2020 15:00
> To: Marek Marczykowski-Górecki
> Cc: xen-devel
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On 05.06.2020 13:18, Marek Marczykowski-Górecki wrot
On Fri, Jun 05, 2020 at 04:44:32PM +0200, Jan Beulich wrote:
> On 05.06.2020 13:02, Roger Pau Monne wrote:
> > Mediated access to the RTC was provided for PVHv1 dom0 using the PV
> > code paths (guest_io_{write/read}), but those accesses where never
> > implemented for PVHv2 dom0. This patch provid
> -Original Message-
> From: Jan Beulich
> Sent: 05 June 2020 14:57
> To: p...@xen.org; 'Marek Marczykowski-Górecki'
>
> Cc: 'Andrew Cooper' ; 'xen-devel'
>
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On 05.06.2020 15:37, Paul Durrant wr
> -Original Message-
> From: Paul Durrant
> Sent: 05 June 2020 14:49
> To: 'Jan Beulich'
> Cc: 'Marek Marczykowski-Górecki' ; 'Andrew
> Cooper'
> ; 'xen-devel'
> Subject: RE: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> > -Original Message-
> > F
flight 150848 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150848/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 150438
Tests which
On Fri, Jun 05, 2020 at 04:39:56PM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: Jan Beulich
> > Sent: 05 June 2020 14:57
> > To: p...@xen.org; 'Marek Marczykowski-Górecki'
> >
> > Cc: 'Andrew Cooper' ; 'xen-devel'
> >
> > Subject: Re: handle_pio looping during domain shu
On Fri, Jun 05, 2020 at 04:48:39PM +0100, Paul Durrant wrote:
> This (untested) patch might help:
It is different now. I don't get domain_crash because of
X86EMUL_UNHANDLEABLE anymore, but I still see handle_pio looping for
some time. But it eventually ends, not really sure why.
I've tried the pa
> -Original Message-
> From: 'Marek Marczykowski-Górecki'
> Sent: 05 June 2020 18:14
> To: p...@xen.org
> Cc: 'Jan Beulich' ; 'Andrew Cooper'
> ; 'xen-devel' de...@lists.xenproject.org>
> Subject: Re: handle_pio looping during domain shutdown, with qemu 4.2.0 in
> stubdom
>
> On Fri, J
On 05/06/2020 08:51, Jan Beulich wrote:
> Both match prior generation processors as far as LBR and C-state MSRs
> go (SDM rev 072) as well as applicability of the if_pschange_mc erratum
> (recent spec updates).
>
> Signed-off-by: Jan Beulich
> ---
> Such changes having been subject to backporting
On 05/06/2020 09:54, Jan Beulich wrote:
> On 05.06.2020 10:46, Roger Pau Monné wrote:
>> On Fri, Jun 05, 2020 at 10:10:01AM +0200, Jan Beulich wrote:
>>> On 05.06.2020 10:02, Roger Pau Monné wrote:
On Fri, Jun 05, 2020 at 09:51:09AM +0200, Jan Beulich wrote:
> Both match prior generation p
On Fri, 5 Jun 2020, Jürgen Groß wrote:
> Do you happen to start the guest with vcpus < maxvcpus?
Indeed, I was booting with vcpus=2, maxvcpus=4. Setting both to the same
value made the domU boot.
> If yes there is already a patch pending for 5.8:
> https://git.kernel.org/pub/scm/linux/kernel/git
On 05/06/2020 09:36, Christian Kujau wrote:
> Hi,
>
> I'm running a small Xen PVH domain and upgrading from vanilla 5.6.0 to
>
>
> Note: that "Xen Platform PCI: unrecognised magic value" on the top appears
> in 5.6 kernels as well, but no ill effects so far.
>
> -
On Fri, Jun 5, 2020 at 11:05 AM CodeWiz2280 wrote:
>
> On Fri, Jun 5, 2020 at 8:47 AM Bertrand Marquis
> wrote:
> >
> >
> >
> > > On 5 Jun 2020, at 13:42, CodeWiz2280 wrote:
> > >
> > > On Fri, Jun 5, 2020 at 8:30 AM Julien Grall wrote:
> > >>
> > >> Hi,
> > >>
> > >> On 05/06/2020 13:25, CodeW
flight 150867 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150867/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
On Fri, Jun 05, 2020 at 06:24:20PM +0100, Paul Durrant wrote:
> > -Original Message-
> > From: 'Marek Marczykowski-Górecki'
> > Sent: 05 June 2020 18:14
> > To: p...@xen.org
> > Cc: 'Jan Beulich' ; 'Andrew Cooper'
> > ; 'xen-devel' > de...@lists.xenproject.org>
> > Subject: Re: handle_pi
On 6/3/20 6:40 PM, Agarwal, Anchal wrote:
> CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you can confirm the sender and know
> the content is safe.
>
>
>
> On 5/19/20 7:26 PM, Anchal Agarwal wrote:
> > From: Munehisa
On 6/4/20 7:03 PM, Anchal Agarwal wrote:
> On Sat, May 30, 2020 at 07:02:01PM -0400, Boris Ostrovsky wrote:
>> CAUTION: This email originated from outside of the organization. Do not
>> click links or open attachments unless you can confirm the sender and know
>> the content is safe.
>>
>>
>>
>>
On Fri, 5 Jun 2020, Andrew Cooper wrote:
> PVH domains don't have the emulated platform device, so Linux will be
> finding ~0 when it goes looking in config space.
>
> The diagnostic should be skipped in that case, to avoid giving the false
> impression that something is wrong.
Understood, thanks
flight 150831 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150831/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 7 xen-boot fail REGR. vs. 150694
test-armhf-armhf-
On Fri, Jun 5, 2020 at 4:03 AM Roger Pau Monne wrote:
>
> Mediated access to the RTC was provided for PVHv1 dom0 using the PV
> code paths (guest_io_{write/read}), but those accesses where never
> implemented for PVHv2 dom0. This patch provides such mediated accesses
> to the RTC for PVH dom0, jus
flight 150870 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150870/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 2a8859e87761a0efc119778e094f203dc2ea487a
baseline version:
xtf cce0ffab7cc43c81058088
On Thu, 4 Jun 2020, Julien Grall wrote:
> On 04/06/2020 17:46, Stefano Stabellini wrote:
> > On Thu, 4 Jun 2020, André Przywara wrote:
> > > On 04/06/2020 17:24, Stefano Stabellini wrote:
> > > > On Thu, 4 Jun 2020, André Przywara wrote:
> > > > > On 04/06/2020 09:48, Julien Grall wrote:
> > > > >
flight 150869 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150869/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm 16 guest-start/debian.repeat fail REGR. vs. 150714
Tests which did n
flight 150871 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/150871/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-rtds 18 guest-localmigrate/x10 fail like 150814
test-amd64-amd64-xl-qemut-win7-amd64
86 matches
Mail list logo
