Re: [Xen-devel] [PATCH for-4.11 1/2] XSM: adjust Kconfig names

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 18.06.19 at 16:44, <julien.grall@xxxxxxx> wrote:
> On 18/06/2019 15:26, Jan Beulich wrote:
>> What I'd like to ask for in the future in any case though is that after
>> pushing stuff to stable trees you would please check the osstest
>> reports, and in case of regressions invest at least some time into
>> figuring out what broke. Right now, even with the XSM tests
>> (hopefully) taken care of there's still a flood of armhf failures, which
>> may or may not be due to environmental issues.
> 
> I usually look over osstest but fail to detect this was an issue because of 
> the 
> XSAs. Regarding the other armhf failure, Ian already pointed out on IRC.
> 
> However, I will not have time to look at it before Xen Summit. Maybe Stefano 
> can?

Not before the summit? That's still almost a month out. We really want
to get 4.11.2 and also 4.10.4 out the door before that.

>>> Also, do we need to update the advisory?
>> 
>> Dunno. I didn't do full analysis of what may go wrong, I've just worked
>> my way far enough to understand what needs fixing. Whether an
>> update is needed imo largely depends on whether the purpose of the
>> patches wasn't fulfilled. People actually using XSM will notice very
>> quickly that things don't work anymore, as can be seen from the
>> osstest cases.
> 
> AFAICT, Arm does not seem to be affected by the problem (at least osstest 
> does 
> not complain). I would not expect x86 users to merge those patch, so maybe it 
> should be ok.

Well, the breakage was in the one case where SILO mode actually
disallows what the test is specifically about - qemu running in a
stubdom, and hence needing to communicate with the actual guest.
I don't think there's any similar test to this for Arm in osstest.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel