Re: [External] [PATCH] hostmem: Add clear option to file backend

2023-03-02 Thread Feiran Zheng
> On 2 Mar 2023, at 11:54, David Hildenbrand wrote: > > On 02.03.23 12:48, Feiran Zheng wrote: >>> On 2 Mar 2023, at 11:39, David Hildenbrand wrote: >>> >>> On 02.03.23 12:37, Feiran Zheng wrote: >>>>> On 2 Mar 2023, at 11:31, David Hild

Re: [External] [PATCH] hostmem: Add clear option to file backend

2023-03-02 Thread Feiran Zheng
> On 2 Mar 2023, at 11:44, Daniel P. Berrangé wrote: > > On Thu, Mar 02, 2023 at 12:31:46PM +0100, David Hildenbrand wrote: >> On 02.03.23 12:09, Fam Zheng wrote: >>> This adds a memset to clear the backing memory. This is useful in the >>> case of PMEM DAX to drop dirty data, if the backing m

Re: [External] [PATCH] hostmem: Add clear option to file backend

2023-03-02 Thread Feiran Zheng
> On 2 Mar 2023, at 11:39, David Hildenbrand wrote: > > On 02.03.23 12:37, Feiran Zheng wrote: >>> On 2 Mar 2023, at 11:31, David Hildenbrand wrote: >>> >>> On 02.03.23 12:09, Fam Zheng wrote: >>>> This adds a memset to clear the backing mem

Re: [External] [PATCH] hostmem: Add clear option to file backend

2023-03-02 Thread Feiran Zheng
> On 2 Mar 2023, at 11:31, David Hildenbrand wrote: > > On 02.03.23 12:09, Fam Zheng wrote: >> This adds a memset to clear the backing memory. This is useful in the >> case of PMEM DAX to drop dirty data, if the backing memory is handed >> over from a previous application or firmware which did

Re: [Qemu-devel] [PATCH] qemu-iotest: test 005, don't run on raw

2011-05-27 Thread Feiran Zheng
Does this mean one must have that large fs space? On Fri, May 27, 2011 at 6:47 PM, Christoph Hellwig wrote: > On Fri, May 27, 2011 at 06:45:03PM +0800, Feiran Zheng wrote: >> Patch on qemu-iotest. >> >> 005, test of creating 5TB images, not practical on raw format, so not ru

[Qemu-devel] [PATCH] qemu-iotest: test 005, don't run on raw

2011-05-27 Thread Feiran Zheng
Patch on qemu-iotest. 005, test of creating 5TB images, not practical on raw format, so not run on it. Signed-off-by: Fam Zheng --- 005 |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/005 b/005 index 74537db..e086b6f 100755 --- a/005 +++ b/005 @@ -46,7 +46,7 @@ _suppor

[Qemu-devel] [PATCH V2] hw/xen_disk: ioreq not finished on error

2011-03-28 Thread Feiran Zheng
Bug fix: routines 'ioreq_runio_qemu_sync' and 'ioreq_runio_qemu_aio' won't call 'ioreq_unmap' or 'ioreq_finish' on errors, leaving ioreq in the blkdev->inflight list and a leak. Signed-off-by: Feiran Zheng --- hw/xen_disk.c | 10 -

[Qemu-devel] Re: [PATCH]hw/xen_disk: ioreq not finished on error

2011-03-28 Thread Feiran Zheng
Sorry for the confusing, I'll clean up it. On Tue, Mar 29, 2011 at 2:16 AM, Stefano Stabellini wrote: > On Mon, 28 Mar 2011, Feiran Zheng wrote: >> On Mon, Mar 28, 2011 at 9:42 PM, Stefano Stabellini >> wrote: >> > On Sun, 27 Mar 2011, Feiran Zheng w

[Qemu-devel] Re: [PATCH]hw/xen_disk: ioreq not finished on error

2011-03-28 Thread Feiran Zheng
On Mon, Mar 28, 2011 at 9:42 PM, Stefano Stabellini wrote: > On Sun, 27 Mar 2011, Feiran Zheng wrote: >> Bug fix: routines 'ioreq_runio_qemu_sync' and 'ioreq_runio_qemu_aio' >> won't call 'ioreq_unmap' or 'ioreq_finish' on erro

Re: [Qemu-devel] qemu not starting

2011-03-27 Thread Feiran Zheng
Did you install from src? Try add --enable-sdl when configure and run qemu with "-vga std". On Mon, Mar 28, 2011 at 12:15 PM, chandra shekar wrote: > hi friends after installing qemu when i try to start qemu then i get an > error as "Could not open SDL display" > plz someone help,thanks > > -- >

[Qemu-devel] [PATCH]hw/xen_disk: ioreq not finished on error

2011-03-27 Thread Feiran Zheng
Bug fix: routines 'ioreq_runio_qemu_sync' and 'ioreq_runio_qemu_aio' won't call 'ioreq_unmap' or 'ioreq_finish' on errors, leaving ioreq in the blkdev->inflight list and a leak. Signed-off-by: Feiran Zheng --- hw/xen_disk.c | 22

[Qemu-devel] [PATCH]hw/xen_disk: aio_inflight not released in handling ioreq when nr_segments==0

2011-03-09 Thread Feiran Zheng
In hw/xen_disk.c, async writing ioreq is leaked when ioreq->req.nr_segments==0, because `aio_inflight` flag is not released properly (skipped by misplaced "break"). Signed-off-by: Feiran Zheng --- hw/xen_disk.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) di