From: Li Liu john.li...@huawei.com
This irq handler will get the interrupt reason from a
shared memory. And will be assigned only while irqfd
enabled.
Signed-off-by: Li Liu john.li...@huawei.com
---
drivers/virtio/virtio_mmio.c | 34 --
1 file changed, 32
From: Li Liu john.li...@huawei.com
This set of patches try to implemet irqfd support of vhost-net
based on virtio-mmio.
I had posted a mail to talking about the status of vhost-net
on kvm-arm refer to http://www.spinics.net/lists/kvm-arm/msg10804.html.
Some dependent patches are listed in the
From: Li Liu john.li...@huawei.com
Add a new register offset VIRTIO_MMIO_ISRMEM which help to
estblish a shared memory region between virtio-mmio driver
and qemu with two purposes:
1.Guest virtio-mmio driver can get the interrupt reason.
2.Check irqfd enabled or not to register different irq
From: Li Liu john.li...@huawei.com
qtest_log_fp should be inited before qemu_chr_add_handlers.
If not the log dumped from callback functions may be lost.
easy to reproduce it by command:
QTEST_LOG=1 QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64
gtester -k --verbose -m=quick
From: Li Liu john.li...@huawei.com
Eeay to reproduce, just try qemu -monitor stdio -nographic
and type quit, then the terminal will be crashed.
There are two pathes try to call tcgetattr of stdio in vl.c:
1) Monitor_parse(optarg, readline);
.
qemu_opts_foreach(qemu_find_opts(chardev),
From: Li Liu john.li...@huawei.com
qtest_log_fp should be inited before qemu_chr_add_handlers.
If not the log dumped from callback functions may be lost.
easy to reproduce it by command:
QTEST_LOG=1 QTEST_QEMU_BINARY=x86_64-softmmu/qemu-system-x86_64
gtester -k --verbose -m=quick
From: Li Liu john.li...@huawei.com
Reviewed-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Signed-off-by: Li Liu john.li...@huawei.com
---
changes v1 - v2:
1) fix indent issue as peter suggested.
2) dump all err mesages with error_report.
---
device_tree.c | 15 ---
1 file
From: Li Liu john.li...@huawei.com
Signed-off-by: Li Liu john.li...@huawei.com
---
device_tree.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/device_tree.c b/device_tree.c
index 9d47195..df9eed9 100644
--- a/device_tree.c
+++
From: Li Liu john.li...@huawei.com
Eeay to reproduce, just try qemu -monitor stdio -nographic
and type quit, then the terminal will be crashed.
There are two pathes try to call tcgetattr of stdio in vl.c:
1) Monitor_parse(optarg, readline);
.
qemu_opts_foreach(qemu_find_opts(chardev),
From: Li Liu john.li...@huawei.com
Signed-off-by: Li Liu john.li...@huawei.com
---
device_tree.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/device_tree.c b/device_tree.c
index ca83504..ccdb039 100644
--- a/device_tree.c
+++ b/device_tree.c
@@ -79,7 +79,7 @@
From: Li Liu john.li...@huawei.com
The outputed stream format is compatile with
'dtc -I dtb -O dts xxx.dtb'.
Signed-off-by: Li Liu john.li...@huawei.com
---
device_tree.c | 80 +
1 file changed, 80 insertions(+)
diff --git
From: Li Liu john.li...@huawei.com
dts property's value can be multiple strings. So introduce a function
to check a data with a given length to see if it is all printable and
has a valid terminator. It can contain either a single string, or
multiple strings each of non-zero length.
From: Li Liu john.li...@huawei.com
This patchset let qemu can convert dtb file to dts for two demands:
Some archtectures may generate the dtb file dynamically through
qemu device tree functions. So this let it's possiable to dump final
dtb to dts and save it as a reference.
For novices to
From: Li Liu john.li...@huawei.com
dump three kind data types 'strings', 'cell' and 'bytes' of dts
to a file desciptor.
Signed-off-by: Li Liu john.li...@huawei.com
---
device_tree.c | 39 +++
1 file changed, 39 insertions(+)
diff --git a/device_tree.c
From: Li Liu john.li...@huawei.com
add the main function to analyse the parameter 'dumpdts' as a
filename the dts will be dumped to.
Signed-off-by: Li Liu john.li...@huawei.com
---
device_tree.c| 21 +
include/sysemu/device_tree.h |1 +
2 files changed,
From: Li Liu john.li...@huawei.com
Signed-off-by: Li Liu john.li...@huawei.com
---
vl.c |4
1 file changed, 4 insertions(+)
diff --git a/vl.c b/vl.c
index b796c67..853f748 100644
--- a/vl.c
+++ b/vl.c
@@ -357,6 +357,10 @@ static QemuOptsList qemu_machine_opts = {
.type =
From: Li Liu john.li...@huawei.com
By calling qemu_fdt_dumdts before qemu_fdt_dumpdtb.
Signed-off-by: Li Liu john.li...@huawei.com
---
hw/arm/boot.c |1 +
1 file changed, 1 insertion(+)
diff --git a/hw/arm/boot.c b/hw/arm/boot.c
index e32f2f4..18cc8ac 100644
--- a/hw/arm/boot.c
+++
libfdt_env.h is missing in some stable installs (1.3.0-3),
some released linux distributions(e.g. Ubuntu 12.04) depending
on it still complain missing libfdt even if already installed.
So give more detailed hint for such OS users.
Signed-off-by: Liu Li john.li...@huawei.com
---
configure |5
On 2014/4/22 17:38, john.liuli wrote:
john.liuli john.li...@huawei.com writes:
libfdt_env.h is missing in some stable installs (1.3.0-3), some
released linux distributions(e.g. Ubuntu 12.04) depending on it still
complain missing libfdt even if already installed.
So give more detailed hint
On 2014/4/22 19:56, john.liuli wrote:
On 21 April 2014 07:18, john.liuli john.li...@huawei.com wrote:
libfdt_env.h is missing in some stable installs (1.3.0-3), some
released linux distributions(e.g. Ubuntu 12.04) depending on it still
complain missing libfdt even if already installed.
So
libfdt_env.h is missing in some stable installs (1.3.0-3),
some released linux distributions(e.g. Ubuntu 12.04) depending
on it still complain missing libfdt even if already installed.
So give more detailed hint for such OS users.
Signed-off-by: Liu Li john.li...@huawei.com
---
configure |4
21 matches
Mail list logo
