[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/13] dma: Let the DMA API take MemTxAttrs argument and prop
From: |
Philippe Mathieu-Daudé |
Subject: |
Re: [PATCH 00/13] dma: Let the DMA API take MemTxAttrs argument and propagate MemTxResult |
Date: |
Wed, 16 Sep 2020 15:48:00 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.11.0 |
On 9/4/20 5:44 PM, Philippe Mathieu-Daudé wrote:
> Salvaging cleanups patches from the RFC series "Forbid DMA write
> accesses to MMIO regions" [*], propagating MemTxResult and
> adding documentation.
>
> Philippe Mathieu-Daudé (12):
> dma: Let dma_memory_valid() take MemTxAttrs argument
> dma: Let dma_memory_set() take MemTxAttrs argument
> dma: Let dma_memory_rw_relaxed() take MemTxAttrs argument
> dma: Let dma_memory_rw() take MemTxAttrs argument
> dma: Let dma_memory_read/write() take MemTxAttrs argument
> dma: Let dma_memory_map() take MemTxAttrs argument
Talking with Laszlo, he wonders if we shouldn't enforce setting
MemTxAttrs attrs.secure = 0 in these calls.
Is there a concept of "secure DMA controller" in QEMU?
Thanks,
Phil.
- Re: [PATCH 11/13] dma: Let dma_memory_rw() take MemTxAttrs argument, (continued)
- [PATCH 13/13] dma: Let dma_memory_map() take MemTxAttrs argument, Philippe Mathieu-Daudé, 2020/09/04
- [PATCH 12/13] dma: Let dma_memory_read/write() take MemTxAttrs argument, Philippe Mathieu-Daudé, 2020/09/04
- Re: [PATCH 00/13] dma: Let the DMA API take MemTxAttrs argument and propagate MemTxResult, Edgar E. Iglesias, 2020/09/07
- Re: [PATCH 00/13] dma: Let the DMA API take MemTxAttrs argument and propagate MemTxResult, Philippe Mathieu-Daudé, 2020/09/15
- Re: [PATCH 00/13] dma: Let the DMA API take MemTxAttrs argument and propagate MemTxResult,
Philippe Mathieu-Daudé <=
- Re: [PATCH 00/13] dma: Let the DMA API take MemTxAttrs argument and propagate MemTxResult, John Snow, 2020/09/23