On 24.04.2023 17:25, Jason Andryuk wrote: > On Mon, Apr 24, 2023 at 10:19 AM Jan Beulich <jbeul...@suse.com> wrote: >> Jason - any chance of getting a Tested-by: from you? > > I'm building v3 now. v2 worked for clearing MASKALL on initial boot. > > I posted in these two messages - a summary is below. > https://lore.kernel.org/xen-devel/cakf6xpto87qrskt2qc1yapnfaw2srllxpoytyjv_jebytab...@mail.gmail.com/ > https://lore.kernel.org/xen-devel/CAKf6xptHALLR-Qjf=p5y0o9ud2v7efmjub8ap-pljv-n7pa...@mail.gmail.com/ > > OpenXT has a patch that performs an extra reset after domain shutdown, > and that causes Xen to set MASKALL. I confirmed by removing it. So > this patch helps with clearing MASKALL on host boot, but with the > OpenXT patch, rebooting a domain fails. MASKALL gets set on VM > shutdown and then the subsequent boot can't assign the device. > > So this patch is helpful in some scenarios, but it was also an issue > caused by the OpenXT patch. Does that make it unsuitable for > inclusion?
What is "it" here? If I get your reply right, there is a similar issue left unaddressed by this version of the change (and as was said before, a device reset changing state that Xen tracks or otherwise cares about needs to be reported to Xen). Yet that doesn't really fit with the question, at least the way I read it ... Jan > I assume the OpenXT patch wasn't an issue previously since > MSI-X was never enabled. > > Regards, > Jason
