[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [ANNOUNCE] Xen 4.15 release schedule and feature tracking
- To: "Cooper, Andrew" <andrew.cooper3@xxxxxxxxxx>, Ian Jackson <iwj@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, "committers@xxxxxxxxxxxxxx" <committers@xxxxxxxxxxxxxx>, Tamas K Lengyel <tamas@xxxxxxxxxxxxx>, Michał Leszczyński <michal.leszczynski@xxxxxxx>
- From: "Lengyel, Tamas" <tamas.lengyel@xxxxxxxxx>
- Date: Fri, 15 Jan 2021 15:14:36 +0000
- Accept-language: en-US
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=intel.com; dmarc=pass action=none header.from=intel.com; dkim=pass header.d=intel.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VWj1IybxER1TX5Lrj0+iOiQ/uEzitHkQ3/FkU8riqoE=; b=NY9mdgsSqS2AJ5yOpgOabzUIVNW64nb7msTCwxf0ijJTwMIs+SzZiDhK2H/0HFzSPCfKz/KYh1HUfMKGDTcdYLzNx+BRy3gi5PeZsTYU4ssI0W3wrLiA7z1U8jJIiYiAToZqinmUdzoZAXpgOoiBVbzfEov0xzQjAYc6vBDzi28g8He2+VIbHI4+uX9STKzvNlpJjk5vuW+a94IxkfXAPvCO4ijDTUl4dxYXRh986OCC4smRH+ERV0u3dwSOYyCjGVv6R2CbhhMxHXxsSsFqImuu0mr8z/fxqnx+cpyVLrtvJed45T+Z4Zgh/l3puhP1HrV+0IdmLAqbVq1wcH4rzA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=U5KDJt8PhBlI4OHU7cYD/Cpu6HrtRW+77Pq5EgpGGNfmQeWb5v8/Itfr8MvKyX+0laTS2/WX/PqdWcZfsU5f+9RgTPBMhh0bKJgS+OCKzrnACKZefv+16ETKbZU8Dw5k3pYNlkIIt1PkoPOVYehK/qc4Qof52gvKXRJNyCtr1+WtRhXfdQnJHrMe6DQrdvKdBoIMZcvpcrqRY3/DmmJgQvAAjmGfKA/vYMnECSdCAa9L+E3Rx7vzVkmuuf8khRvCd8mJK6KhAsj0kCfOVv86/54+YLpKvOZvFR92JKzyS3v6QPjrHE5Us5k2KT8fJUe0jh5ehhS6+p0TYl8gv5WNmg==
- Authentication-results: citrix.com; dkim=none (message not signed) header.d=none;citrix.com; dmarc=none action=none header.from=intel.com;
- Delivery-date: Fri, 15 Jan 2021 15:14:47 +0000
- Dlp-product: dlpe-windows
- Dlp-reaction: no-action
- Dlp-version: 11.6.0.76
- Ironport-sdr: Nxif32xmp8/u3nJBYN6VfK2hgAdE3C2PcdD2E5e99P0vr07cqzGT7F/4QVPa7CRorWTkK8XuJt 0XAVRDxX8UIw==
- Ironport-sdr: ZwtG/YofiHAs4fH52mAT2aEOscqJawUo2fUfd1rgy0bQvdokkaXwBZfzdFf2qquOkRf+ofYxWi pRQgpVEW27Eg==
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Thread-index: AQHW5QJqtM8KOPdjlUWz6CGAzwJoLKonVGsAgAAxGgCAAVCLkA==
- Thread-topic: [ANNOUNCE] Xen 4.15 release schedule and feature tracking
> Features:
>
> 1) acquire_resource fixes.
>
> Not really a new feature - entirely bugfixing a preexisting one.
> Developed by me to help 2). Reasonably well acked, but awaiting feedback
> on v3.
>
> 2) External Processor Trace support.
>
> Development by Michał. Depends on 1), and awaiting a new version being
> posted.
>
> As far as I'm aware, both Intel and CERT have production systems deployed
> using this functionality, so it is very highly desirable to get into 4.15.
We are actively using a backported version on top of 4.14.1, having this in
4.15 would be absolutely huge. We've ran over 10 billion fuzz cycles using it
so far using VM forks, works great. Several other researchers in the community
are using it as well.
> 1) HPET/PIT issue on newer Intel systems. This has had literally tens of
> reports across the devel and users mailing lists, and prevents Xen from
> booting at all on the past two generations of Intel laptop. I've finally got
> a
> repro and posted a fix to the list, but still in progress.
We've ran into this on multiple systems, Andrew's patch does fix it.
> 2) "scheduler broken" bugs. We've had 4 or 5 reports of Xen not working,
> and very little investigation on whats going on. Suspicion is that there
> might be two bugs, one with smt=0 on recent AMD hardware, and one
> more general "some workloads cause negative credit" and might or might
> not be specific to credit2 (debugging feedback differs - also might be 3
> underlying issue).
We've also ran into intermittent Xen lockups requiring power-cycling servers.
We switched back to credit1 and had no issues since. Hard to tell if it was
related to the scheduler or the pile of other experimental stuff we are running
with but right now we have stable systems across the board with credit1.
>
> All of these have had repeated bug reports. I'd classify them as blockers,
> given the impact they're having on people.
+1
Thanks,
Tamas
|
