On 15.12.19 21:13, Aditya Pakki wrote:
grow_gnttab_list() checks for NULL on gnttab_interface immediately
after gnttab_expand() check. The patch removes the redundant assertion
and replaces the BUG_ON call with recovery code.
Signed-off-by: Aditya Pakki
---
drivers/xen/grant-table.c | 9
flight 144855 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144855/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 144637
build-amd64
On 16.12.19 06:58, Tian, Kevin wrote:
From: Jürgen Groß
Sent: Friday, December 13, 2019 11:36 PM
On 13.12.19 15:45, Jan Beulich wrote:
On 13.12.2019 15:24, Jürgen Groß wrote:
On 13.12.19 15:11, Jan Beulich wrote:
On 13.12.2019 14:46, Jürgen Groß wrote:
On 13.12.19 14:38, Jan Beulich wrote:
On 16/12/2019 2:17 pm, Tian, Kevin wrote:
>> From: Jin Nan Wang
>> Sent: Monday, December 16, 2019 1:48 PM
>>
>> Fix a issue when user disable ETP exec-sp, xen missed a prompt
>> log in dmesg.
>>
>> Signed-off-by: James Wang
>> ---
>> xen/arch/x86/hvm/vmx/vmx.c | 4 +++-
>> 1 file changed, 3
> From: Tian, Kevin
> Sent: Monday, December 16, 2019 1:58 PM
>
> > From: Jürgen Groß
> > Sent: Friday, December 13, 2019 11:36 PM
> >
> > On 13.12.19 15:45, Jan Beulich wrote:
> > > On 13.12.2019 15:24, Jürgen Groß wrote:
> > >> On 13.12.19 15:11, Jan Beulich wrote:
> > >>> On 13.12.2019 14:46,
flight 144854 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144854/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 144637
build-amd64
> From: Jin Nan Wang
> Sent: Monday, December 16, 2019 1:48 PM
>
> Fix a issue when user disable ETP exec-sp, xen missed a prompt
> log in dmesg.
>
> Signed-off-by: James Wang
> ---
> xen/arch/x86/hvm/vmx/vmx.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git
> From: Roger Pau Monné
> Sent: Friday, December 13, 2019 10:13 PM
>
> On Fri, Dec 13, 2019 at 01:53:29PM +0100, Jan Beulich wrote:
> > Containing still in flight DMA was introduced to work around certain
> > devices / systems hanging hard upon hitting an IOMMU fault. Passing
> > through (such)
> From: Jürgen Groß
> Sent: Friday, December 13, 2019 11:36 PM
>
> On 13.12.19 15:45, Jan Beulich wrote:
> > On 13.12.2019 15:24, Jürgen Groß wrote:
> >> On 13.12.19 15:11, Jan Beulich wrote:
> >>> On 13.12.2019 14:46, Jürgen Groß wrote:
> On 13.12.19 14:38, Jan Beulich wrote:
> > On
Fix a issue when user disable ETP exec-sp, xen missed a prompt
log in dmesg.
Signed-off-by: James Wang
---
xen/arch/x86/hvm/vmx/vmx.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
index 7970ba93e1..9c1f0f645d
grow_gnttab_list() checks for NULL on gnttab_interface immediately
after gnttab_expand() check. The patch removes the redundant assertion
and replaces the BUG_ON call with recovery code.
Signed-off-by: Aditya Pakki
---
drivers/xen/grant-table.c | 9 ++---
1 file changed, 6 insertions(+), 3
flight 144852 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144852/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 144637
build-amd64
flight 144851 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144851/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm6 xen-buildfail REGR. vs. 144637
build-amd64
flight 144849 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144849/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144848 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144848/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144847 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144847/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
Since reading hyperv-timer clocksource requires reading cntvct,
userspace should be allowed to read it, otherwise reading cntvct will
result in traps, which makes vsyscall's cost similar compared to
syscall's.
So enable it on every cpu when a Hyper-V guest booting up.
Signed-off-by: Boqun Feng
Hi,
This is the RFC patchset for vDSO support in ARM64 Hyper-V guest. To
test it, Michael's ARM64 support patchset:
https://lore.kernel.org/linux-arm-kernel/1570129355-16005-1-git-send-email-mikel...@microsoft.com/
is needed.
Similar as x86, Hyper-V on ARM64 use a TSC page for guests
Similar to x86, add a new vclock_mode VCLOCK_HVCLOCK, and reuse the
hv_read_tsc_page() for userspace to read tsc page clocksource.
Signed-off-by: Boqun Feng (Microsoft)
---
arch/arm64/include/asm/clocksource.h | 3 ++-
arch/arm64/include/asm/mshyperv.h | 2 +-
On Hyper-V, a tsc page has the data for adjusting cntvct numbers to
clocksource cycles, and that's how Hyper-V guest kernel reads the
clocksource. In order to allow userspace to read the same clocksource
directly, the tsc page has to been mapped into userspace via vDSO.
Use the framework for vDSO
Split __vdso_abi::vdso_pages into nr_vdso_{data,code}_pages, so that
__setup_additional_pages() could work with multiple vDSO data pages with
the setup from __vdso_init().
Multiple vDSO data pages are required when running in a virtualized
environment, where the cycles read from cntvct at
Similar to x86, use a vclock_mode in arch_clocksource_data to differ
clocksoures use different read function in vDSO.
No functional changes, only preparation for support vDSO in ARM64 on
Hyper-V.
Note: the changes for arm are only because arm and arm64 share the same
code in the arch timer
In order to support vDSO, hv_read_tsc_page() should be able to be called
from userspace if tsc page mapped. As a result, hv_get_raw_timer(),
called by hv_read_tsc_page() requires to be called by both kernel and
vDSO. Currently, it's defined as arch_timer_read_counter(), which is a
function pointer
flight 144846 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144846/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144845 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144845/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
The pull request you sent on Sun, 15 Dec 2019 07:06:21 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.5b-rc2-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/b01d7cb41ff51b7779977de601a984406e2a5ba9
Thank you!
--
Deet-doot-dot,
flight 144844 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144844/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144843 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144843/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
On Fri, 13 Dec 2019 13:20:40 +, Paul Durrant wrote:
> In function xenvif_disconnect_queue(), the value of queue->rx_irq is
> zeroed *before* queue->task is stopped. Unfortunately that task may call
> notify_remote_via_irq(queue->rx_irq) and calling that function with a
> zero value results in
flight 144842 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144842/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144841 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144841/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144840 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144840/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
> > For DRTM I don't think it makes much
> > difference, I believe the active microcode info is already part of the
> > measurement, so having it measured as part of the Xen blob doesn't add
> > anything.
>
> I couldn't possibly comment on timelines, but if I could, the answer
> might be "not for
flight 144839 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144839/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144838 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144838/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144837 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144837/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144836 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144836/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144827 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144827/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-rtds 16 guest-localmigrate fail pass in 144813
flight 144828 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144828/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt16 guest-start/debian.repeat fail REGR. vs. 144517
Tests which did not
flight 144835 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144835/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
flight 144833 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144833/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen c9115affa6f83aebe29ae9cbf503aa163911a5bb
baseline version:
xen
flight 144834 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144834/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
On Fri, Dec 13, 2019 at 05:47:28PM +0100, Philippe Mathieu-Daudé wrote:
> On 12/13/19 5:17 PM, Philippe Mathieu-Daudé wrote:
> > Historically, QEMU started with only one X86 machine: the PC.
> > The 'hw/i386/pc.h' header was used to store all X86 and PC
> > declarations. Since we have now multiple
flight 144832 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/144832/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 144637
build-i386-xsm
44 matches
Mail list logo
