[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/2] exec/memory: Enforce checking MemTxResult values
|
From: |
Peter Maydell |
|
Subject: |
Re: [PATCH 0/2] exec/memory: Enforce checking MemTxResult values |
|
Date: |
Mon, 18 May 2020 10:46:42 +0100 |
On Sun, 17 May 2020 at 17:48, Philippe Mathieu-Daudé <address@hidden> wrote:
>
> Various places ignore the MemTxResult indicator of
> transaction failed. Some cases might be justified
> (DMA?) while other are probably bugs. To avoid
> ignoring transaction errors, suggestion is to mark
> functions returning MemTxResult with
> warn_unused_result attribute.
Not necessarily a bad idea, but don't we have an awful
lot of places that ignore the result that we'd need
to fix first?
thanks
-- PMM
- [PATCH 0/2] exec/memory: Enforce checking MemTxResult values, Philippe Mathieu-Daudé, 2020/05/17
- [PATCH 1/2] exec/memory: Let address_space_read/write_cached() propagate MemTxResult, Philippe Mathieu-Daudé, 2020/05/17
- [RFC PATCH 2/2] exec/memory: Emit warning when MemTxResult is ignored, Philippe Mathieu-Daudé, 2020/05/17
- Re: [PATCH 0/2] exec/memory: Enforce checking MemTxResult values, no-reply, 2020/05/17
- Re: [PATCH 0/2] exec/memory: Enforce checking MemTxResult values, no-reply, 2020/05/17
- Re: [PATCH 0/2] exec/memory: Enforce checking MemTxResult values, no-reply, 2020/05/17
- Re: [PATCH 0/2] exec/memory: Enforce checking MemTxResult values,
Peter Maydell <=