On Tue, 7 Apr 2020 at 12:24, Peter Maydell wrote:
>
> On Fri, 3 Apr 2020 at 09:44, Andrew Jones wrote:
> >
> > On Mon, Mar 23, 2020 at 11:32:27AM +, Beata Michalska wrote:
> > > Injecting external data abort through KVM might trigger
> > > an issue on kernels that do not get updated to includ
On Fri, 3 Apr 2020 at 09:44, Andrew Jones wrote:
>
> On Mon, Mar 23, 2020 at 11:32:27AM +, Beata Michalska wrote:
> > Injecting external data abort through KVM might trigger
> > an issue on kernels that do not get updated to include the KVM fix.
> > For those and aarch32 guests, the injected a
On Fri, 3 Apr 2020 at 09:44, Andrew Jones wrote:
>
> On Mon, Mar 23, 2020 at 11:32:27AM +, Beata Michalska wrote:
> > Injecting external data abort through KVM might trigger
> > an issue on kernels that do not get updated to include the KVM fix.
> > For those and aarch32 guests, the injected a
On Mon, Mar 23, 2020 at 11:32:27AM +, Beata Michalska wrote:
> Injecting external data abort through KVM might trigger
> an issue on kernels that do not get updated to include the KVM fix.
> For those and aarch32 guests, the injected abort gets misconfigured
> to be an implementation defined ex
On Mon, 23 Mar 2020 at 18:44, Richard Henderson
wrote:
>
> On 3/23/20 4:32 AM, Beata Michalska wrote:
> > uint8_t ext_dabt_pending; /* Request for injecting ext DABT */
> > +uint8_t ext_dabt_raised; /* Tracking/verifying injection of ext DABT */
>
> Is there a reason these are uint8_t and
On 3/23/20 4:32 AM, Beata Michalska wrote:
> uint8_t ext_dabt_pending; /* Request for injecting ext DABT */
> +uint8_t ext_dabt_raised; /* Tracking/verifying injection of ext DABT */
Is there a reason these are uint8_t and not bool?
r~
Injecting external data abort through KVM might trigger
an issue on kernels that do not get updated to include the KVM fix.
For those and aarch32 guests, the injected abort gets misconfigured
to be an implementation defined exception. This leads to the guest
repeatedly re-running the faulting instr
