On Mon, Dec 10, 2018 at 06:32:49PM +, Peter Maydell wrote:
> On Mon, 10 Dec 2018 at 18:31, Peter Maydell wrote:
> >
> > On Mon, 10 Dec 2018 at 17:57, Peter Maydell
> > wrote:
> > >
> > > Switch the microblaze target from the old unassigned_access hook
> > > to the transaction_failed hook.
>
On Mon, Dec 10, 2018 at 06:32:49PM +, Peter Maydell wrote:
> On Mon, 10 Dec 2018 at 18:31, Peter Maydell wrote:
> >
> > On Mon, 10 Dec 2018 at 17:57, Peter Maydell
> > wrote:
> > >
> > > Switch the microblaze target from the old unassigned_access hook
> > > to the transaction_failed hook.
>
On Mon, 10 Dec 2018 at 18:31, Peter Maydell wrote:
>
> On Mon, 10 Dec 2018 at 17:57, Peter Maydell wrote:
> >
> > Switch the microblaze target from the old unassigned_access hook
> > to the transaction_failed hook.
> >
> > The notable difference is that rather than it being called
> > for all
On Mon, 10 Dec 2018 at 17:57, Peter Maydell wrote:
>
> Switch the microblaze target from the old unassigned_access hook
> to the transaction_failed hook.
>
> The notable difference is that rather than it being called
> for all physical memory accesses which fail (including
> those made by DMA
Switch the microblaze target from the old unassigned_access hook
to the transaction_failed hook.
The notable difference is that rather than it being called
for all physical memory accesses which fail (including
those made by DMA devices or by the gdbstub), it is only
called for those made by the
