flight 72403 distros-debian-squeeze real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/72403/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-amd64-squeeze-netboot-pygrub 10 debian-di-install fail like
72350
test-amd64-i386-amd
Hi,
On 01/11/17 04:31, Christoffer Dall wrote:
> On Wed, Nov 1, 2017 at 9:58 AM, Stefano Stabellini
> wrote:
>
> []
Christoffer, many thanks for answering this!
I think we have a lot of assumptions about the whole VGIC life cycle
floating around, but it would indeed be good to get some numb
flight 115460 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115460/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 114507
build-amd64-xsm
On Tue, Oct 31, 2017 at 06:42:28PM +, Wei Liu wrote:
> On Tue, Oct 31, 2017 at 01:51:44PM +, Wei Liu wrote:
> > First version of this series can be found at [0].
> >
> > This version contains workaround for Arndale boards. They are now
> > functional.
> >
> > A bunch of test cases failed
Cc Julien and change tag. I think this is safe to be applied to 4.10.
On Tue, Oct 31, 2017 at 01:58:07PM -0700, Elena Ufimtseva wrote:
> On Tue, Oct 31, 2017 at 03:25:39PM +, Wei Liu wrote:
> > On Tue, Oct 31, 2017 at 10:20:11AM -0500, Doug Goldstein wrote:
> > > Prefer using the character dev
flight 115450 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115450/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stopfail REGR. vs. 114644
test-amd64-amd64-x
On Tue, Oct 31, 2017 at 04:52:37PM +, Roger Pau Monné wrote:
>
> I have to admit I have no idea why Windows clears the STS power bit
> and then completely ignores it on certain occasions.
>
> I'm also afraid I have no idea how to debug Windows in order to know
> why this event is acknowledged
> -Original Message-
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: 01 November 2017 10:48
> To: Roger Pau Monne
> Cc: Julien Grall ; committ...@xenproject.org; xen-
> devel ; Lars Kurth ;
> Paul Durrant ; Wei Liu
> Subject: Re: Commit moratorium to staging
>
> On Tue, Oct 31, 2017
If the domain has XENFEAT_auto_translated_physmap then use of the PV-
specific HYPERVISOR_mmu_update hypercall is clearly incorrect.
This patch adds checks in xen_remap_domain_gfn_array() and
xen_unmap_domain_gfn_array() which call through to the approprate
xlate_mmu function if the feature is pre
On Mon, Oct 30, 2017 at 04:01:54PM +, Wei Liu wrote:
> +git rev-list $BASE..$TIP | nl -ba | tac | \
> +while read num rev; do
> +echo "Testing $num $rev"
> +
> +git checkout $rev
> +ret=$?
> +if test $ret -ne 0; then
> +echo "Failed to checkout $num $rev with $ret"
I do
flight 115457 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115457/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 114814
Tests which are faili
flight 115463 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115463/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 114507
build-amd64-xsm
On 01/11/17 12:31, Paul Durrant wrote:
> If the domain has XENFEAT_auto_translated_physmap then use of the PV-
> specific HYPERVISOR_mmu_update hypercall is clearly incorrect.
>
> This patch adds checks in xen_remap_domain_gfn_array() and
> xen_unmap_domain_gfn_array() which call through to the ap
> -Original Message-
> From: Juergen Gross [mailto:jgr...@suse.com]
> Sent: 01 November 2017 13:40
> To: Paul Durrant ; x...@kernel.org; xen-
> de...@lists.xenproject.org; linux-ker...@vger.kernel.org
> Cc: Boris Ostrovsky ; Thomas Gleixner
> ; Ingo Molnar ; H. Peter Anvin
>
> Subject: Re:
The file common/tmem_xen.c is now converted to use typesafe. This is
requiring to override the macro page_to_mfn to make it work with mfn_t.
Note that all variables converted to mfn_t havem there initial value,
when set, switch from 0 to INVALID_MFN. This is fine because the initial
values was alw
- Remove spurious ()
- Add missing spaces
- Turn 1 << to 1UL <<
- Rename spfn to smfn and switch to mfn_t
Signed-off-by: Julien Grall
---
Cc: Stefano Stabellini
Changes in v2:
- Remove double space
- s/spfn/smfn/ and switch to mfn_t
---
xen/arch/arm/domain
Most of the users of page_to_mfn and mfn_to_page are either overriding
the macros to make them work with mfn_t or use mfn_x/_mfn because the
rest of the function use mfn_t.
So make __page_to_mfn and __mfn_to_page return mfn_t by default.
Only reasonable clean-ups are done in this patch because it
Hi all,
Most of the users of page_to_mfn and mfn_to_page are either overriding
the macros to make them work with mfn_t or use mfn_x/_mfn becaue the rest
of the function use mfn_t.
So I think it is time to make __page_to_mfn and __mfn_to_page using typesafe
MFN.
The first 3 patches will convert o
The arm32 version of the function is_xen_heap_page currently define a
variable _mfn. This will lead to a compiler when use typesafe MFN in a
follow-up patch:
called object '_mfn' is not a function or function pointer
Fix it by renaming the local variable _mfn to mfn_.
Signed-off-by: Julien Grall
So, investigations (mostly by Roger, and also a bit of archaeology in
the osstest db by me) have determined:
* This bug is 100% reproducible on affected hosts. The repro is
to boot the Windows guest, save/restore it, then migrate it,
then shut down. (This is from an IRL conversation with Rog
flight 115459 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115459/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail REGR. vs. 114682
Tests which did not
Hi Stefano,
On 01/11/17 01:58, Stefano Stabellini wrote:
> On Wed, 11 Oct 2017, Andre Przywara wrote:
many thanks for going through all of this!
>> (CC:ing some KVM/ARM folks involved in the VGIC)
>>
>> starting with the addition of the ITS support we were seeing more and
>> more issues with th
The PoD subsystem only have pool of 4KB and 2MB pages. When it comes
accross a 1GB mapping, it will be splitted in 2MB one using
p2m_set_entry and request the caller to retry (see ept_get_entry for
instance).
p2m_set_entry may fail to shatter if it is not possible to
allocate memory for the new pa
Hi Ian,
Thank you for the detailed e-mail.
On 11/01/2017 02:07 PM, Ian Jackson wrote:
So, investigations (mostly by Roger, and also a bit of archaeology in
the osstest db by me) have determined:
* This bug is 100% reproducible on affected hosts. The repro is
to boot the Windows guest, save
From: Oleksandr Grytsov
Add getting vsnd list amd info API
Signed-off-by: Oleksandr Grytsov
---
tools/libxl/libxl.h | 10 ++
tools/libxl/libxl_types.idl | 19 +++
tools/libxl/libxl_utils.h | 3 +
tools/libxl/libxl_vsnd.c| 375 +++-
4 fi
From: Oleksandr Grytsov
Update documentation with virtual sound device
Signed-off-by: Oleksandr Grytsov
---
docs/man/xl.cfg.pod.5.in | 150 +++
docs/man/xl.pod.1.in | 30 ++
2 files changed, 180 insertions(+)
diff --git a/docs/man/xl.cf
From: Oleksandr Grytsov
Add CLI commands to attach, detach and list virtual sound devices
Signed-off-by: Oleksandr Grytsov
Acked-by: Wei Liu
---
tools/xl/Makefile | 2 +-
tools/xl/xl.h | 3 +
tools/xl/xl_cmdtable.c | 15
tools/xl/xl_vsnd.c | 203 +++
From: Oleksandr Grytsov
Add config parser for virtual sound devices
Signed-off-by: Oleksandr Grytsov
---
tools/xl/xl_parse.c | 246
tools/xl/xl_parse.h | 1 +
2 files changed, 247 insertions(+)
diff --git a/tools/xl/xl_parse.c b/tools/xl/
From: Oleksandr Grytsov
This patch set adds PV sound device support to xl.cfg and xl.
See sndif.h for protocol implementation details.
Changes since initial:
* fix code style
* change unique-id from int to string (to make id more user readable)
Oleksandr Grytsov (5):
libxl: add PV sound dev
From: Oleksandr Grytsov
Add PV sound device described in sndif.h
Signed-off-by: Oleksandr Grytsov
---
tools/libxl/Makefile | 2 +-
tools/libxl/libxl.h | 14 ++
tools/libxl/libxl_create.c | 1 +
tools/libxl/libxl_internal.h | 1 +
tools/
From: Oleksandr Grytsov
Changes since initial:
* add setting backend-type to xenstore
* add id field to indentify the vkb device on backend side
Oleksandr Grytsov (6):
libxl: move vkb device to libxl_vkb.c
libxl: fix vkb XS entry and type
libxl: add backend type and id to vkb
libxl: vk
From: Oleksandr Grytsov
New field backend_type is added to vkb device
in order to have QEMU and user space backend
simultaneously. Each vkb backend shall read
appropriate XS entry and service only own
frontends.
Id is a string field which used by the backend
to indentify the frontend.
Signed-off
From: Oleksandr Grytsov
Logically it is better to move vkb to
separate file as vkb device used not only by vfb
and console.
Signed-off-by: Oleksandr Grytsov
Acked-by: Wei Liu
---
tools/libxl/Makefile| 1 +
tools/libxl/libxl_console.c | 53 -
tools/libx
From: Oleksandr Grytsov
Signed-off-by: Oleksandr Grytsov
---
tools/libxl/libxl.h | 10
tools/libxl/libxl_types.idl | 11
tools/libxl/libxl_utils.h | 3 ++
tools/libxl/libxl_vkb.c | 129 ++--
4 files changed, 150 insertions(+),
From: Oleksandr Grytsov
Signed-off-by: Oleksandr Grytsov
---
docs/man/xl.cfg.pod.5.in | 28
docs/man/xl.pod.1.in | 22 ++
2 files changed, 50 insertions(+)
diff --git a/docs/man/xl.cfg.pod.5.in b/docs/man/xl.cfg.pod.5.in
index 4948dd7..18595
From: Oleksandr Grytsov
vkb has vkbd name in XS.
Signed-off-by: Oleksandr Grytsov
Acked-by: Wei Liu
---
tools/libxl/libxl_vkb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxl_vkb.c b/tools/libxl/libxl_vkb.c
index 0d01262..ea6fca8 100644
--- a/tools/l
From: Oleksandr Grytsov
Signed-off-by: Oleksandr Grytsov
---
tools/xl/Makefile | 2 +-
tools/xl/xl.h | 3 ++
tools/xl/xl_cmdtable.c | 15 ++
tools/xl/xl_parse.c| 75 +-
tools/xl/xl_parse.h| 2 +-
tools/xl/xl_vkb.c | 142
Currently, there are 3 different lock types that can be chosen for
the x86 architecture:
- qspinlock
- pvqspinlock
- unfair lock
One of the above lock types will be chosen at boot time depending on
a number of different factors.
Ideally, the hypervisors should be able to pick the best perform
> -Original Message-
> From: Julien Grall [mailto:julien.gr...@linaro.org]
> Sent: 01 November 2017 14:03
> To: xen-devel@lists.xen.org
> Cc: Julien Grall ; Stefano Stabellini
> ; Julien Grall ; Andrew
> Cooper ; George Dunlap
> ; Ian Jackson ; Jan
> Beulich ; Konrad Rzeszutek Wilk
> ; Tim
On 01/11/17 14:45, Paul Durrant wrote:
>> -Original Message-
>> From: Juergen Gross [mailto:jgr...@suse.com]
>> Sent: 01 November 2017 13:40
>> To: Paul Durrant ; x...@kernel.org; xen-
>> de...@lists.xenproject.org; linux-ker...@vger.kernel.org
>> Cc: Boris Ostrovsky ; Thomas Gleixner
>> ;
On 11/01/2017 04:03 PM, Julien Grall wrote:
> Most of the users of page_to_mfn and mfn_to_page are either overriding
> the macros to make them work with mfn_t or use mfn_x/_mfn because the
> rest of the function use mfn_t.
>
> So make __page_to_mfn and __mfn_to_page return mfn_t by default.
>
> O
On 01/11/17 16:32, Waiman Long wrote:
> Currently, there are 3 different lock types that can be chosen for
> the x86 architecture:
>
> - qspinlock
> - pvqspinlock
> - unfair lock
>
> One of the above lock types will be chosen at boot time depending on
> a number of different factors.
>
> Idea
On Thu, Oct 19, 2017 at 10:36:33AM +0800, Zhongze Liu wrote:
> Add libxl__sshm_del to unmap static shared memory areas mapped by
> libxl__sshm_add during domain creation. The unmapping process is:
>
> * For a master: decrease the refcount of the sshm region, if the refcount
> reaches 0, cleanup
On Thu, Oct 19, 2017 at 10:36:32AM +0800, Zhongze Liu wrote:
> Add libxl__sshm_add to map shared pages from one DomU to another, The mapping
> process involves the follwing steps:
>
> * Set defaults and check for further errors in the static_shm configs:
> overlapping areas, invalid ranges,
flight 115462 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115462/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-examine 8 reboot fail REGR. vs. 114658
test-armhf-armhf-xl-
On Wed, Nov 01, 2017 at 02:07:48PM +, Ian Jackson wrote:
> So, investigations (mostly by Roger, and also a bit of archaeology in
> the osstest db by me) have determined:
>
> * This bug is 100% reproducible on affected hosts. The repro is
> to boot the Windows guest, save/restore it, then mi
On 11/01/2017 11:51 AM, Juergen Gross wrote:
> On 01/11/17 16:32, Waiman Long wrote:
>> Currently, there are 3 different lock types that can be chosen for
>> the x86 architecture:
>>
>> - qspinlock
>> - pvqspinlock
>> - unfair lock
>>
>> One of the above lock types will be chosen at boot time de
(add mercurial-devel and xen-devel to cc's)
On Tue, 2017-10-31 at 16:37 -0500, Tom Saeger wrote:
> Add "--pattern-checks" option to get_maintainer.pl to warn about invalid
> "F" and "X" patterns found in MAINTAINERS file(s).
Hey again Tom.
About mercurial/hg.
While as far as I know there hasn't
Hi, I have removed (00:02.0) from the grub argument line and been using:
xen-pciback.hide=(00:14.0) modprobe.blacklist=i915,xhci_pci,xhci_hcd
with DomU.cfg containing: gfx_passthru=1pci=['00:02.0','00:14.0']
Now I am seeing the VGA passthrough working, but the Windows DomU is stuck
at 10
Julien Grall writes ("Re: Commit moratorium to staging"):
> Hi Ian,
>
> Thank you for the detailed e-mail.
>
> On 11/01/2017 02:07 PM, Ian Jackson wrote:
> > Furthermore, the test is not intermittent, so a force push will be
> > effective in the following sense: we would only get a "spurious" pas
On 09/12/2017 11:39 AM, Roger Pau Monné wrote:
> On Mon, Sep 11, 2017 at 06:01:59PM +0100, George Dunlap wrote:
>> +## Toolstack
>> +
>> +### xl
>> +
>> +Status: Supported
>> +
>> +### Direct-boot kernel image format
>> +
>> +Supported, x86: bzImage
>
> ELF
>
>> +Supported, ARM32: zIm
On 10/31/2017 06:03 PM, brian.wo...@amd.com wrote:
> From: Brian Woods
>
> x86/svm: virtual VMLOAD/VMSAVE
>
> On AMD family 17h server processors, there is a feature called virtual
> VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLOAD or
> VMSAVE without needing to be intercepted b
Hi Ian,
On 11/01/2017 04:54 PM, Ian Jackson wrote:
Julien Grall writes ("Re: Commit moratorium to staging"):
Hi Ian,
Thank you for the detailed e-mail.
On 11/01/2017 02:07 PM, Ian Jackson wrote:
Furthermore, the test is not intermittent, so a force push will be
effective in the following sen
On 09/12/2017 08:52 PM, Stefano Stabellini wrote:
>>> +### Xen Framebuffer
>>> +
>>> +Status, Linux: Supported
>>
>> Frontend?
>
> Yes, please. If you write "Xen Framebuffer" I only take it to mean the
> protocol as should be documented somewhere under docs/. Then I read
> Linux, and I don't u
On Tue, Oct 24, 2017 at 04:22:38PM +0100, George Dunlap wrote:
> On Fri, Sep 15, 2017 at 3:51 PM, Konrad Rzeszutek Wilk
> wrote:
> >> +### Soft-reset for PV guests
> >
> > s/PV/HVM/
>
> Is it? I thought this was for RHEL 5 PV guests to be able to do crash
> kernels.
>
> >> +### Transcendent Me
On Wed, Nov 01, 2017 at 09:50:05AM -0700, Joe Perches wrote:
> (add mercurial-devel and xen-devel to cc's)
>
> On Tue, 2017-10-31 at 16:37 -0500, Tom Saeger wrote:
> > Add "--pattern-checks" option to get_maintainer.pl to warn about invalid
> > "F" and "X" patterns found in MAINTAINERS file(s).
>
Hi Christoffer,
On 12/10/17 13:05, Christoffer Dall wrote:
> Hi Andre,
>
> On Wed, Oct 11, 2017 at 03:33:03PM +0100, Andre Przywara wrote:
>> Hi,
>>
>> (CC:ing some KVM/ARM folks involved in the VGIC)
>
> Very nice writeup!
>
> I added a bunch of comments, mostly for the writing and clarity, I
Add "--self-test" option to get_maintainer.pl to show potential
issues in MAINTAINERS file(s) content.
Pattern check warnings are shown for "F" and "X" patterns found in
MAINTAINERS file(s) which do not match any files known by git.
Signed-off-by: Tom Saeger
Cc: Joe Perches
---
v2:
Incorporat
On 11/01/2017 11:37 AM, Juergen Gross wrote:
>
> TBH I like V1 better, too.
>
> Boris, do you feel strong about the #ifdef part?
Having looked at what this turned into I now like V1 better too ;-)
Sorry, Paul.
-boris
___
Xen-devel mailing list
Xen-de
On Wed, 2017-11-01 at 13:13 -0500, Tom Saeger wrote:
> Add "--self-test" option to get_maintainer.pl to show potential
> issues in MAINTAINERS file(s) content.
This patch subject should be:
get_maintainer: Add --self-test for internal consistency tests
Andrew, can you please change the subject i
flight 115468 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115468/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 114507
build-amd64-xsm
On 11/01/2017 10:03 AM, Julien Grall wrote:
> Most of the users of page_to_mfn and mfn_to_page are either overriding
> the macros to make them work with mfn_t or use mfn_x/_mfn because the
> rest of the function use mfn_t.
>
> So make __page_to_mfn and __mfn_to_page return mfn_t by default.
>
> Onl
On Wed, Nov 01, 2017 at 02:03:15PM +, Julien Grall wrote:
> The file common/tmem_xen.c is now converted to use typesafe. This is
> requiring to override the macro page_to_mfn to make it work with mfn_t.
>
> Note that all variables converted to mfn_t havem there initial value,
> when set, switc
On 11/01/2017 12:28 PM, Waiman Long wrote:
> On 11/01/2017 11:51 AM, Juergen Gross wrote:
>> On 01/11/17 16:32, Waiman Long wrote:
>>> Currently, there are 3 different lock types that can be chosen for
>>> the x86 architecture:
>>>
>>> - qspinlock
>>> - pvqspinlock
>>> - unfair lock
>>>
>>> One
On 10/31/2017 09:46 PM, Dongli Zhang wrote:
> After guest live migration on xen, steal time in /proc/stat
> (cpustat[CPUTIME_STEAL]) might decrease because steal returned by
> xen_steal_lock() might be less than this_rq()->prev_steal_time which is
> derived from previous return value of xen_steal_c
On Fri, Oct 27, 2017 at 10:18:04PM +0800, Yang Zhong wrote:
> Intel IceLake cpu has added new cpu features: AVX512VBMI2/GFNI/
> VAES/AVX512VNNI/AVX512BITALG/VPCLMULQDQ. Those new cpu features
> need expose to guest.wq
s/wq//
>
> The bit definition:
> CPUID.(EAX=7,ECX=0):ECX[bit 06] AVX512VBMI2
>
On 01/11/17 17:00, Boris Ostrovsky wrote:
> On 10/31/2017 06:03 PM, brian.wo...@amd.com wrote:
>> From: Brian Woods
>>
>> x86/svm: virtual VMLOAD/VMSAVE
>>
>> On AMD family 17h server processors, there is a feature called virtual
>> VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLO
On 11/01/2017 03:01 PM, Boris Ostrovsky wrote:
> On 11/01/2017 12:28 PM, Waiman Long wrote:
>> On 11/01/2017 11:51 AM, Juergen Gross wrote:
>>> On 01/11/17 16:32, Waiman Long wrote:
Currently, there are 3 different lock types that can be chosen for
the x86 architecture:
- qspin
Hi Dongli,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.14-rc7 next-20171018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/l
On Wed, 2017-11-01 at 16:05 -0400, Augie Fackler wrote:
> > On Nov 1, 2017, at 13:11, Tom Saeger wrote:
> >
> > On Wed, Nov 01, 2017 at 09:50:05AM -0700, Joe Perches wrote:
> > > (add mercurial-devel and xen-devel to cc's)
> > >
> > > On Tue, 2017-10-31 at 16:37 -0500, Tom Saeger wrote:
> > > >
Currently, there are 3 different lock types that can be chosen for
the x86 architecture:
- qspinlock
- pvqspinlock
- unfair lock
One of the above lock types will be chosen at boot time depending on
a number of different factors.
Ideally, the hypervisors should be able to pick the best perform
With the new pvlock_type kernel parameter, xen_nopvspin is no longer
needed. This patch deprecates the xen_nopvspin parameter by removing
its documentation and treating it as an alias of "pvlock_type=queued".
Signed-off-by: Waiman Long
---
Documentation/admin-guide/kernel-parameters.txt | 4 ---
v1->v2:
- Make pv_spinlock_type a bit mask for easier checking.
- Add patch 2 to deprecate xen_nopvspin
v1 - https://lkml.org/lkml/2017/11/1/381
Patch 1 adds a new pvlock_type parameter for the administrators to
specify the type of lock to be used in a para-virtualized kernel.
Patch 2 deprecat
flight 115464 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115464/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stopfail REGR. vs. 114644
test-amd64-amd64-x
On Wed, 1 Nov 2017, Andre Przywara wrote:
> Hi Stefano,
>
>
> On 01/11/17 01:58, Stefano Stabellini wrote:
> > On Wed, 11 Oct 2017, Andre Przywara wrote:
>
> many thanks for going through all of this!
No problems, and thanks for your work and for caring about doing the
best thing for the projec
On 11/01/2017 04:58 PM, Waiman Long wrote:
> +/* TODO: To be removed in a future kernel version */
> static __init int xen_parse_nopvspin(char *arg)
> {
> - xen_pvspin = false;
> + pr_warn("xen_nopvspin is deprecated, replace it with
> \"pvlock_type=queued\"!\n");
> + if (!pv_spinloc
Hi Dongli,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on xen-tip/linux-next]
[also build test ERROR on v4.14-rc7 next-20171018]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/l
flight 115470 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115470/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 114507
build-amd64-xsm
On Wed, Nov 01, 2017 at 03:29:16PM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Oct 27, 2017 at 10:18:04PM +0800, Yang Zhong wrote:
> > Intel IceLake cpu has added new cpu features: AVX512VBMI2/GFNI/
> > VAES/AVX512VNNI/AVX512BITALG/VPCLMULQDQ. Those new cpu features
> > need expose to guest.wq
>
Hi Boris,
I have received from l...@intel.com that the prior version of patch hit issue
during compilation with aarch64-linux-gnu-gcc. I think this patch reviewed by
you would hit the same compiling issue on arm64 (there is no issue with x86_64).
--
flight 115466 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115466/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 114814
Tests which are faili
flight 115472 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115472/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 114507
build-amd64-xsm
> From: Julien Grall [mailto:julien.gr...@linaro.org]
> Sent: Wednesday, November 1, 2017 10:03 PM
>
> Most of the users of page_to_mfn and mfn_to_page are either overriding
> the macros to make them work with mfn_t or use mfn_x/_mfn because the
> rest of the function use mfn_t.
>
> So make __pag
flight 115469 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115469/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail REGR. vs. 114682
Tests which did not
> From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
> Sent: Monday, October 23, 2017 5:33 PM
>
> Running "./xtf_runner vvmx" in L1 Xen under L0 Xen produces the
> following result on H/W with VMCS shadowing:
>
> Test: vmxon
> Failure in test_vmxon_in_root_cpl0()
> Expected 0x820
> On Nov 1, 2017, at 13:11, Tom Saeger wrote:
>
> On Wed, Nov 01, 2017 at 09:50:05AM -0700, Joe Perches wrote:
>> (add mercurial-devel and xen-devel to cc's)
>>
>> On Tue, 2017-10-31 at 16:37 -0500, Tom Saeger wrote:
>>> Add "--pattern-checks" option to get_maintainer.pl to warn about invalid
>
flight 115474 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/115474/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3866 xen-buildfail REGR. vs. 114507
build-amd64-xsm
87 matches
Mail list logo
