[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 0/9] memory: Sanity checks memory transaction when releasi
|
From: |
Peter Xu |
|
Subject: |
Re: [PATCH v2 0/9] memory: Sanity checks memory transaction when releasing BQL |
|
Date: |
Tue, 27 Jul 2021 12:35:53 -0400 |
On Tue, Jul 27, 2021 at 02:41:17PM +0200, David Hildenbrand wrote:
> Functions that silently drop the BQL are really nasty. I once fall into a
> similar trap calling pause_all_vcpus() from within
> memory_region_transaction_begin(), while resizing RAM blocks.
Yes, hopefull the series can help all these cases too. Thanks for reviewing!
--
Peter Xu
- Re: [PATCH v2 8/9] memory: Assert on no ongoing memory transaction before release BQL, (continued)
- [PATCH v2 9/9] memory: Delay the transaction pop() until commit completed, Peter Xu, 2021/07/23
- [PATCH v2 6/9] cpus: Remove the mutex parameter from do_run_on_cpu(), Peter Xu, 2021/07/23
- [PATCH v2 7/9] cpus: Introduce qemu_mutex_unlock_iothread_prepare(), Peter Xu, 2021/07/23
- Re: [PATCH v2 0/9] memory: Sanity checks memory transaction when releasing BQL, Peter Xu, 2021/07/23
- Re: [PATCH v2 0/9] memory: Sanity checks memory transaction when releasing BQL, David Hildenbrand, 2021/07/27
- Re: [PATCH v2 0/9] memory: Sanity checks memory transaction when releasing BQL,
Peter Xu <=