On 05/22/2018 12:44 PM, Jan Beulich wrote: >>>> On 22.05.18 at 13:21, <george.dun...@citrix.com> wrote: >> On 05/22/2018 11:51 AM, Jan Beulich wrote: >>>>>> On 21.05.18 at 16:16, <george.dun...@citrix.com> wrote: >>>> Most server-class hardware doesn't support ACPI S3 suspend; >>> >>> Is that really the case? I though S3 was pretty "normal" these days. >>> >>>> but most bugs we'll run across won't need actual S3 to trigger. >>> >>> Not sure about this one either: In particular the microcode issue >>> addressed recently does require actual S3 to surface. I'm not >>> meaning to put under question the usefulness of this option, >>> though. I'd just like the description to not lead to people drawing >>> wrong conclusions. >> >> Re S3 support, I was just repeating what I'd heard. My judgement is >> still that "most" bugs we end up encountering will be on the Xen side; >> but I'm happy to reword it to take out / moderate both implications. > > Oh, surely issues normally are on the Xen side. It's just that there's a > fair range of issues which still require actually going through S3 to > show up - the ucode issues after XSA-254 are a good example thereof.
Well FWIW with acpi_power=s3_fake on staging+patch, the machine hangs with default bti / xpti settings, and works with bti and xpti disabled. So at least some part of XSA-254 issues can / would be caught without having to actually enter real S3. -George _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
