Hello, all!
I would like to bring back this old thread as it seems it has stuck long
time ago
without clear NAck or Ack. I didn't rebase the changes because the
change itself
requires answers on the way we should go here: new ioctl (seems to be
better) or
extension of the existing one (not s
flight 162535 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162535/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
flight 162532 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162532/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
flight 162538 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162538/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 162327
Tests which
On 08/06/2021 07:18, Jan Beulich wrote:
> On 07.06.2021 14:41, Andrew Cooper wrote:
>> While the ! annotation is useful to indicate that something special is
>> happening, an array of bits is not. Drop it, to prevent mistakes.
>>
>> Signed-off-by: Andrew Cooper
>> ---
>> CC: Jan Beulich
>> CC: R
Am Wed, 2 Jun 2021 09:10:44 +0200
schrieb Juergen Gross :
> MiB_sec = ((ctx->save.pages_sent * PAGE_SIZE * 1000) / ms) /
>(1024U * 1024U);
I'm not sure: how does this improve the patch?
Olaf
pgplvhBZ3WWt2.pgp
Description: Digitale Signatur von OpenPGP
Hi Jan,
On 28/05/2021 14:29, Jan Beulich wrote:
On 26.05.2021 17:21, Julien Grall wrote:
From: Julien Grall
Since XSA-288 (commit 02cbeeb62075 "gnttab: split maptrack lock to make
XSA-228 I suppose?
Yes, I will update in the next version.
it fulfill its purpose again"), v->maptrack_head
On 08.06.2021 10:46, Andrew Cooper wrote:
> On 08/06/2021 07:18, Jan Beulich wrote:
>> On 07.06.2021 14:41, Andrew Cooper wrote:
>>> While the ! annotation is useful to indicate that something special is
>>> happening, an array of bits is not. Drop it, to prevent mistakes.
>>>
>>> Signed-off-by: A
On 08.06.21 10:58, Olaf Hering wrote:
Am Wed, 2 Jun 2021 09:10:44 +0200
schrieb Juergen Gross :
MiB_sec = ((ctx->save.pages_sent * PAGE_SIZE * 1000) / ms) /
(1024U * 1024U);
I'm not sure: how does this improve the patch?
The scattered calculation makes it much harder to verify i
From: Julien Grall
Since XSA-228 (commit 02cbeeb62075 "gnttab: split maptrack lock
to make it fulfill its purpose again"), v->maptrack_head,
v->maptrack_tail and the content of the freelist are accessed with
the lock v->maptrack_freelist_lock held.
Therefore it is not necessary to update the fie
Anthony PERARD writes ("[XEN PATCH] tools/firmware/ovmf: Use OvmfXen platform
file is exist"):
> A platform introduced in EDK II named OvmfXen is now the one to use for
> Xen instead of OvmfX64. It comes with PVH support.
>
> Also, the Xen support in OvmfX64 is deprecated,
> "deprecation noti
On Tue, Jun 08, 2021 at 11:29:58AM +0100, Ian Jackson wrote:
> Anthony PERARD writes ("[XEN PATCH] tools/firmware/ovmf: Use OvmfXen platform
> file is exist"):
> > A platform introduced in EDK II named OvmfXen is now the one to use for
> > Xen instead of OvmfX64. It comes with PVH support.
> >
>
On 04.06.2021 04:14, Connor Davis wrote:
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -456,6 +456,15 @@ F: tools/libs/light/libxl_nonetbuffer.c
> F: tools/hotplug/Linux/remus-netbuf-setup
> F: tools/hotplug/Linux/block-drbd-probe
>
> +RISCV
> +M: Bob Eshleman
> +M: Alistair Franc
flight 162541 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162541/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 162327
Tests which
L.S.,
I seem to be running into a build error with current xen-unstable.
--
Sander
echo '#if 0' >>/usr/src/new/xen-unstable/xen/include/asm-x86/asm-macros.h.new
echo '.endif' >>/usr/src/new/xen-unstable/xen/include/asm-x86/asm-macros.h.new
cat asm-macros.i
>>/usr/src/new/xen-unstable/xen/inclu
On 08/06/2021 12:28, Sander Eikelenboom wrote:
> L.S.,
>
> I seem to be running into a build error with current xen-unstable.
Yeah - that's my fault.
https://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=69e1472d21cf7e5cf0795ef38b99d00de78a910e
went a little too far, and shouldn't have dropped
For replication I used gcc 10.3 on an Alpine system. In order to replicate the
redefinition error for PAGE_SIZE one should install the 'fortify-headers'
package which will change the chain of included headers by indirectly including
/usr/include/limits.h where PAGE_SIZE and PATH_MAX are defined.
C
If PAGE_SIZE is already defined in the system (e.g. in /usr/include/limits.h
header) then gcc will trigger a redefinition error because of -Werror. This
patch replaces usage of PAGE_* macros with KDD_PAGE_* macros in order to avoid
confusion between control domain page granularity (PAGE_* definitio
If PATH_MAX is already defined in the system (e.g. in /usr/include/limits.h
header) then gcc will trigger a redefinition error because of -Werror.
Signed-off-by: Costin Lupu
Reviewed-by: Julien Grall
---
tools/libfsimage/ext2fs/fsys_ext2fs.c | 2 ++
tools/libfsimage/reiserfs/fsys_reiserfs.c
If PAGE_SIZE is already defined in the system (e.g. in /usr/include/limits.h
header) then gcc will trigger a redefinition error because of -Werror. This
patch replaces usage of PAGE_* macros with XC_PAGE_* macros in order to avoid
confusion between control domain page granularity (PAGE_* definition
If PAGE_SIZE is already defined in the system (e.g. in /usr/include/limits.h
header) then gcc will trigger a redefinition error because of -Werror. This
patch replaces usage of PAGE_* macros with XC_PAGE_* macros in order to avoid
confusion between control domain page granularity (PAGE_* definition
If PAGE_SIZE is already defined in the system (e.g. in /usr/include/limits.h
header) then gcc will trigger a redefinition error because of -Werror. This
patch replaces usage of PAGE_* macros with XC_PAGE_* macros in order to avoid
confusion between control domain page granularity (PAGE_* definition
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow
testid guest-saverestore
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qem
Hi Julien,
On 5/17/21 9:12 PM, Julien Grall wrote:
> Hi Costin,
>
> On 10/05/2021 09:35, Costin Lupu wrote:
>> @@ -168,7 +168,7 @@ void
>> *osdep_xenforeignmemory_map(xenforeignmemory_handle *fmem,
>> size_t i;
>> int rc;
>> - addr = mmap(addr, num << PAGE_SHIFT, prot, flags | MA
Hi Julien,
On 5/17/21 9:16 PM, Julien Grall wrote:
> Hi Costin,
>
> On 10/05/2021 09:35, Costin Lupu wrote:
>> If PAGE_SIZE is already defined in the system (e.g. in
>> /usr/include/limits.h
>> header) then gcc will trigger a redefinition error because of -Werror.
>> This
>> patch replaces usage
On 8 Jun 2021, at 13:35, Costin Lupu
mailto:costin.l...@cs.pub.ro>> wrote:
For replication I used gcc 10.3 on an Alpine system. In order to replicate the
redefinition error for PAGE_SIZE one should install the 'fortify-headers'
package which will change the chain of included headers by indirect
flight 162533 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162533/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 162475
test-amd64-amd64-qemuu-nested-amd 20
> Von: Jan Beulich
> Gesendet: Dienstag, 8. Juni 2021 08:24
>
> On 08.06.2021 01:44, Paul Leiber wrote:
> > After more testing, I have come to the following conclusion: It seems that
> every time I do a _reboot_ from within a Windows DomU, the PCI device
> does not get attached to the DomU. After
flight 162544 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162544/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 162327
Tests which
xen-cpuid does print out the list of special features, and this is helpful to
keep.
Fixes: ba6950fb070 ("x86/cpuid: Drop special_features[]")
Reported-by: Jan Beulich
Reported-by: Sander Eikelenboom
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Roger Pau Monné
CC: Wei Liu
CC: Sander E
On 08.06.2021 18:19, Andrew Cooper wrote:
> xen-cpuid does print out the list of special features, and this is helpful to
> keep.
>
> Fixes: ba6950fb070 ("x86/cpuid: Drop special_features[]")
> Reported-by: Jan Beulich
> Reported-by: Sander Eikelenboom
> Signed-off-by: Andrew Cooper
Acked-by:
Am Tue, 8 Jun 2021 07:58:39 +0200
schrieb Juergen Gross :
> +#XENSTORED_MAX_N_DOMAINS=32768
This will break fillup.
Provide an empty variable like it is done for a few others in that file.
Olaf
pgpV5bgbdAXTR.pgp
Description: Digitale Signatur von OpenPGP
Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
for-linus-5.13b-rc6-tag
xen: branch for v5.13-rc6
It contains a single patch fixing a Xen related security bug: a malicious
guest might be able to trigger a "use after free" issue in the xen-ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2021-28693 / XSA-372
version 3
xen/arm: Boot modules are not scrubbed
UPDATES IN VERSION 3
Public release.
ISSUE DESCRIPTION
===
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2021-28691 / XSA-374
version 2
Guest triggered use-after-free in Linux xen-netback
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2021-0089 / XSA-375
version 2
Speculative Code Store Bypass
UPDATES IN VERSION 2
New 4.12 backport (also targeting 4.11), addressing a bui
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2021-28690 / XSA-377
version 2
x86: TSX Async Abort protections not restored after S3
UPDATES IN VERSION 2
Public release.
ISSUE DESCRIPTION
===
The June 2021 microcode is formally de-featuring TSX on the older Skylake
client CPUs. The workaround from the March 2019 microcode is being dropped,
and replaced with additions to MSR_TSX_FORCE_ABORT to hide the HLE/RTM CPUID
bits.
With this microcode in place, TSX is disabled by default on thes
The pull request you sent on Tue, 8 Jun 2021 19:02:53 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> for-linus-5.13b-rc6-tag
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/368094df48e680fa51cedb68537408cfa64b788e
Thank you!
--
Deet-doot-dot,
flight 162537 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162537/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-rtds broken
test-amd64-amd64-xl-credit2
flight 162542 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162542/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
test-amd64-amd64-xl-qemuu
Design Session - Hyperlaunch
Wednesday 26th May, at the Xen Design and Developer Summit 2021
Session Hosts: Christopher Clark & Daniel Smith
tl;dr:
- use cases for Hyperlaunch include supporting bare metal apps
- latency is a critical requirement for workloads
- de
On 6/3/21 7:14 PM, Connor Davis wrote:
> Add arch-specific makefiles and configs needed to build for
> riscv. Also add a minimal head.S that is a simple infinite loop.
> head.o can be built with
>
> $ make XEN_TARGET_ARCH=riscv64 SUBSYSTEMS=xen -C xen tiny64_defconfig
> $ make XEN_TARGET_ARCH=risc
flight 162545 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162545/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 162327
Tests which
flight 162539 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162539/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
flight 162554 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162554/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
flight 162546 xen-4.15-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162546/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 19 guest-stopfail like 162366
test-amd64-amd64-xl-qemut-win7-a
flight 162547 xen-4.14-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162547/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds18 guest-start/debian.repeat fail REGR. vs. 162365
Tests which did not suc
On 08.06.2021 19:05, Andrew Cooper wrote:
> --- a/xen/arch/x86/tsx.c
> +++ b/xen/arch/x86/tsx.c
> @@ -60,6 +60,38 @@ void tsx_init(void)
> */
>
> /*
> + * Probe for the June 2021 microcode which de-features TSX on
> + * client parts. (Note - thi
49 matches
Mail list logo
