On 2012年06月15日 17:04, Paolo Bonzini wrote:
It just forces libqtest to read any pending events.
Ok, Thank you very much! :)
In the code of libqtest.c have a function :
bool qtest_get_irq(QTestState *s, int num)
{
/* dummy operation in order to make sure irq is up to date */
qtest_inb(s, 0);
return s->irq_level[num];
}
but I don't know how it can make the irq up to date
and why we will read from the a
On 2012年06月11日 23:37, Jeff Cody wrote:
On 06/11/2012 10:24 AM, Stefan Hajnoczi wrote:
On Mon, Jun 11, 2012 at 1:50 PM, Kevin Wolf wrote:
Am 11.06.2012 14:09, schrieb Stefan Hajnoczi:
On Fri, Jun 8, 2012 at 6:46 PM, Jeff Cody wrote:
On 06/08/2012 12:11 PM, Kevin Wolf wrote:
Am 08.06.2012 16
On 2012年06月12日 03:12, Paolo Bonzini wrote:
Il 11/06/2012 17:37, Jeff Cody ha scritto:
It sounds like Zhi Hui is working on live block commit patches, and
Supriya is working on the bdrv_reopen() portion - I don't want to
duplicate any effort, but if there is anything I can do to help with
either
On 2012年05月15日 17:38, Paolo Bonzini wrote:
Il 15/05/2012 11:33, Kevin Wolf ha scritto:
which blindly overwrites status2. Hence the new code was not written
based on it. However, the new code is untested as far as I know.
In the thread of an earlier version of this series, I said that a qtest
When I use gtest.
Compiler did not have a problem, the use of gtester implementation and
generate xml file testlog also no problem, but in the use of
gterster-report, the output is as follows:
gtester-report test.log > test-report.html
Traceback (most recent call last):
File "/usr/bin/gt
On 2012年05月15日 17:27, Paolo Bonzini wrote:
Il 15/05/2012 11:17, Li Zhi Hui ha scritto:
Signed-off-by: Paolo Bonzini
Signed-off-by: Li Zhi Hui
---
hw/fdc.c | 313 +
1 files changed, 210 insertions(+), 103 deletions(-)
To reviewers,
On 2012年04月23日 16:21, Paolo Bonzini wrote:
Il 23/04/2012 10:13, Zhi Hui Li ha scritto:
Ater I git pull to the newest version,
I make qemu, the error happen:
CCx86_64-softmmu/vga.o
CCx86_64-softmmu/memory.o
CCx86_64-softmmu/savevm.o
CCx86_64-softmmu/xen-all.o
cc1
Ater I git pull to the newest version,
I make qemu, the error happen:
CCx86_64-softmmu/vga.o
CCx86_64-softmmu/memory.o
CCx86_64-softmmu/savevm.o
CCx86_64-softmmu/xen-all.o
cc1: warnings being treated as errors
/home/mm/code-new/qemu-2012-3-19/test-new/qemu/xen-all.c: In fu
+
+void DMA_set_return(int nret, int nchan)
+{
+struct dma_regs *r;
+struct dma_cont *d;
+int icont, ichan;
+
+icont = nchan> 3;
+ichan = nchan& 3;
+d = dma_controllers;
+r =&d[icont].regs[ichan];
+r->now[COUNT] = nret;
+assert(r->channel_is_asynchronous);
+
On 2012年04月17日 16:46, Paolo Bonzini wrote:
Il 16/04/2012 14:14, Stefan Hajnoczi ha scritto:
Why are you removing the rearm behavior? I'm pretty sure other ISA
devices rely on this otherwise the code wouldn't exist.
Li is correct in that the code can be simplified a lot, but indeed his
axe wen
On 2012年04月16日 17:50, Stefan Hajnoczi wrote:
On Mon, Apr 16, 2012 at 3:58 AM, Zhi Hui Li wrote:
when I git pull to the newest branch, then
gdb ./x86_64-softmmu/qemu-system-x86_64
set args, then run the gdb, but have the error:
Warning:
Cannot insert breakpoint -1.
Error accessing memory
when I git pull to the newest branch, then
gdb ./x86_64-softmmu/qemu-system-x86_64
set args, then run the gdb, but have the error:
Warning:
Cannot insert breakpoint -1.
Error accessing memory address 0x2b6688: Input/output error.
I don't know why, can you have me?
Thank you very much !
On 2012年04月02日 20:07, Stefan Hajnoczi wrote:
On Sat, Mar 31, 2012 at 09:15:10PM +0800, Li Zhi Hui wrote:
Replace bdrv_* to bdrv_aio_* functions in pio mode in fdc.c.
Signed-off-by: Li Zhi Hui
---
hw/fdc.c | 123 +-
1 files changed,
I think what you say up is right, I will correct them, thank you very much!
+bdrv_aio_readv(cur_drv->bs, fd_sector(cur_drv),
+&fdctrl->qiov, fdc_sector_num, fdctrl_read_DMA_cb, opaque_cb);
+return dma_len;
Should be return 0 since we haven't completed I/O yet.
Stefan
I th
when I use the command :
1: mkdir /my_directory
2: qemu linux.img -fda fat:floppy:/my_directory
when I write to the floppy(just "mkdir test.dir" in the floppy), the
error occur:
"FLOPPY ERROR: fdctrl_transfer_handler: writing sector 1"
and nothing is written to the /my_directory.
I don'
I am read the code of fdc.c ,
I feel it was difficult to understand.
Can somebody give me some help: thank you very much!
1: explain the difference between :
type_register_static(&isa_fdc_info);
type_register_static(&sysbus_fdc_info);
type_register_static(&sun4m_fdc_info);
2: e
On 2011年12月15日 17:36, Stefan Hajnoczi wrote:
On Thu, Dec 15, 2011 at 04:28:28PM +0800, 陳韋任 wrote:
I found this in HACKING:
Please note that NULL check for the g_malloc result is redundant and
that g_malloc() call with zero size is not allowed.
So we have:
1. You should not request 0
I am not sure whether it is need to check the return of g_malloc in
qemu ?
Thank you very much !
2011/12/6 Stefan Hajnoczi
> On Tue, Dec 6, 2011 at 10:01 AM, Zhi Hui Li
> wrote:
> > On 2011年12月06日 17:40, Stefan Hajnoczi wrote:
> >>
> >> On Tue, Dec 6, 2011 at 9:07 AM, Zhi Hui Li
> >> wrote:
> >>>
> >>>
> >>&
On 2011年12月06日 17:40, Stefan Hajnoczi wrote:
On Tue, Dec 6, 2011 at 9:07 AM, Zhi Hui Li wrote:
1) :
for example:
BDRVQcowState *s = bs->opaque;
s->snapshots
s->nb_snapshots
1:use the command: qemu-img snapshot ./test.qcow2 -c aa
the memory of the s->snapshot don'
1) :
for example:
BDRVQcowState *s = bs->opaque;
s->snapshots
s->nb_snapshots
1:use the command: qemu-img snapshot ./test.qcow2 -c aa
the memory of the s->snapshot don't free,
if the s->nb_snapshots is large, Does it have some problems.
2: use the command: qemu-system-x86_64 ./test.qco
Thank you very much!
On 2011年12月02日 11:47, Mark Wu wrote:
On 12/02/2011 11:23 AM, Li Zhi Hui wrote:
Signed-off-by: Li Zhi Hui
---
hw/smbus_eeprom.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/smbus_eeprom.c b/hw/smbus_eeprom.c
index 5d080ab..d66fbbc 100644
--- a/hw/smbus_eeprom.c
+++ b/hw
I do not receive this signal. But I think you can try
> handle SIG38 noprint pass
> to ignore this signal.
>
> thank you, I found the problom, just like you say,
enter this command will solve it.
"handle SIG38 pass noprint nonstop"
the problem maybe is my libthread_db.* don't involve the debug
when I gdb the ./x86_64-softmmu/qemu-system-x86_64
It always receive the signal,
"Program received signal SIG38, Real-time event 38.",
can you tell the reason and how to solve it ?
Thank you very much!
string is allocated by g_malloc, will not be used after putenv, should be
free before return.
Signed-off-by: Li Zhi Hui
---
os-win32.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/os-win32.c b/os-win32.c
index 8ad5fa1..e6e9143 100644
--- a/os-win32.c
+++ b/os-win32.c
Signed-off-by: Li Zhi Hui
---
net/socket.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/net/socket.c b/net/socket.c
index e9ef128..0f09164 100644
--- a/net/socket.c
+++ b/net/socket.c
@@ -409,6 +409,7 @@ static int net_socket_listen_init(VLANState *vlan,
fd = qe
On 2011年11月14日 18:00, Stefan Hajnoczi wrote:
On Mon, Nov 14, 2011 at 01:47:41PM +0800, Zhi Hui Li wrote:
1) In qcow2.c, in function: qcow2_co_readv
In qcow2.h, in struct BDRVQcowState
I want to know the relations between sector_num in function
qcow2_co_readv and cluster_sectors in struct
questions:
1) In qcow2.c, in function: qcow2_co_readv
In qcow2.h, in struct BDRVQcowState
I want to know the relations between sector_num in function
qcow2_co_readv and cluster_sectors in struct BDRVQcowState ?
2) In qcow2.c, in function; qcow2_co_writev
at line 547:
index_in_cluster =
when I trace the code of qemu-img.c， I found in the image file, the
backing_file use the relative path, I think Maybe it has some problems.
for example:
1: qemu-img create -o backing_file=../ aa.img 5G
2: qemu-system-x86_64 aa.img
if you change aa.img's the path, the exec is wrong,it
/* Read nvram contents */
-qemu_get_buffer(file, s->contents, s->chip_size);
-qemu_fclose(file);
+if (fread(s->contents, s->chip_size, 1, file) != 1) {
+printf("nvram_sysbus_initfn: short read\n");
+}
+fclose(file);
}
nvram_post_load(s, 0);
Tested-by: Zhi Hui Li
34 matches
Mail list logo
