On Mon, Dec 22, 2014 at 6:59 AM, Zhang Haoyu zhhy.zhangha...@gmail.com wrote:
Hi,
How to get the guest physical memory usage from host?
I don't want to introduce a guest-agent to get the info.
Thanks,
Zhang Haoyu
There`s probably one approach, simular to (currently abandoned)
virt-dmesg,
From: Gonglei arei.gong...@huawei.com
It will be useful for checking when we change traditional
boot order dynamically and propagate error message
to the monitor.
Signed-off-by: Gonglei arei.gong...@huawei.com
Reviewed-by: Markus Armbruster arm...@redhat.com
---
bootdevice.c| 14
From: Gonglei arei.gong...@huawei.com
It will be useful for checking when we change traditional
boot order dynamically and propagate error message
to the monitor.
Signed-off-by: Gonglei arei.gong...@huawei.com
Reviewed-by: Markus Armbruster arm...@redhat.com
---
bootdevice.c| 10
From: Gonglei arei.gong...@huawei.com
It will be useful for checking when we change traditional
boot order dynamically and propagate error message
to the monitor.
For x86 architecture, we pass local_err to set_boot_dev()
when vm startup in pc_coms_init().
Cc: Michael S. Tsirkin m...@redhat.com
tags/bootdevice-next-20141222
for you to fetch changes up to ddcd55316fb2851e144e719171621ad2816487dc:
bootdevice: add Error **errp argument for QEMUBootSetHandler (2014-12-22
14:39:21 +0800)
bootdevice: Refactor and improvement
From: Gonglei arei.gong...@huawei.com
Signed-off-by: Gonglei arei.gong...@huawei.com
Reviewed-by: Markus Armbruster arm...@redhat.com
---
bootdevice.c |8
1 file changed, 8 insertions(+)
diff --git a/bootdevice.c b/bootdevice.c
index 7f07507..9de34ba 100644
--- a/bootdevice.c
+++
From: Gonglei arei.gong...@huawei.com
First, we can downsize vl.c, make it simpler by
little and little. Second, I can maintain those code
and make some improvement.
Cc: Jan Kiszka jan.kis...@siemens.com
Signed-off-by: Gonglei arei.gong...@huawei.com
Reviewed-by: Markus Armbruster
On 2014/12/22 16:41, Andrey Korolyov wrote:
On Mon, Dec 22, 2014 at 6:59 AM, Zhang Haoyu zhhy.zhangha...@gmail.com
wrote:
Hi,
How to get the guest physical memory usage from host?
I don't want to introduce a guest-agent to get the info.
Thanks,
Zhang Haoyu
There`s probably one
In KVM ARM/ARM64 one can run cross-endian guset with respect to host kernel.
For virtio to work with this we need to make virtio code aware of
guest's endianness.
This patchset adds the guest endianness determination for KVM ARM/ARM64
and related small fix in KVM ARM64.
V2:
- Change the patch to
From: Simon Zolin szo...@parallels.com
Moved the code that sets non-blocking flag on fd into a separate function.
Signed-off-by: Simon Zolin szo...@parallels.com
Acked-by: Roman Kagan rka...@parallels.com
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Michael Roth mdr...@linux.vnet.ibm.com
This patch implements a fucntion pointer virtio_is_big_endian()
from CPUClass structure for arm/arm64.
Function arm_cpu_virtio_endianness() is added to determine and
return the guest cpu endianness to virtio.
This is required for running cross endian guests with virtio on ARM/ARM64.
Changelog:
From: Simon Zolin szo...@parallels.com
Creates a FIFO pair that can be used with existing file read/write
interfaces to communicate with processes spawned via the forthcoming
guest-file-exec interface.
Signed-off-by: Simon Zolin szo...@parallels.com
Acked-by: Roman Kagan rka...@parallels.com
This patch adds:
1. Call write_kvmstate_to_list() and write_list_to_cpustate()
in kvm_arch_get_registers() to sync guest register state.
2. Call write_list_to_kvmstate() in kvm_arch_put_registers()
to sync guest register state.
These changes are already there for kvm32 in
From: Simon Zolin szo...@parallels.com
Interfaces to execute/manage processes in the guest. Child process'
stdin/stdout/stderr can be associated with handles for communication
via read/write interfaces.
Signed-off-by: Simon Zolin szo...@parallels.com
Acked-by: Roman Kagan rka...@parallels.com
These patches for guest-agent add the functionality to execute commands on
a guest UNIX machine.
These patches add the following interfaces:
guest-pipe-open
guest-exec
guest-exec-status
With these interfaces it's possible to:
* Open an anonymous pipe and work with it as with a file using
On Mon, Dec 22, 2014 at 11:57 AM, Zhang Haoyu zhhy.zhangha...@gmail.com wrote:
On 2014/12/22 16:41, Andrey Korolyov wrote:
On Mon, Dec 22, 2014 at 6:59 AM, Zhang Haoyu zhhy.zhangha...@gmail.com
wrote:
Hi,
How to get the guest physical memory usage from host?
I don't want to introduce a
On 2014/12/22 17:16, Andrey Korolyov wrote:
On Mon, Dec 22, 2014 at 11:57 AM, Zhang Haoyu zhhy.zhangha...@gmail.com
wrote:
On 2014/12/22 16:41, Andrey Korolyov wrote:
On Mon, Dec 22, 2014 at 6:59 AM, Zhang Haoyu zhhy.zhangha...@gmail.com
wrote:
Hi,
How to get the guest physical memory
On 22/12/2014 07:39, Zhang Haoyu wrote:
Hi,
When I perform P2V from native servers with win2008 to kvm vm,
some cases failed due to the physical disk was using GPT for partition,
and QEMU doesn't support GPT by default.
And, I see in below site that OVMF can be used to enable UEFI to
On 15/12/14 13:03, Denis V. Lunev wrote:
On 27/11/14 15:44, Denis V. Lunev wrote:
Excessive virtio_balloon inflation can cause invocation of OOM-killer,
when Linux is under severe memory pressure. Various mechanisms are
responsible for correct virtio_balloon memory management.
Nevertheless it
Yes, it should depends on guest os implementation,
because physical memory is managed by OS, which have the full knowledge of
memory usage,
so I'm afraid that windows dose not friendly support it.
Could you detail the peeking techniques mentioned above?
Thanks,
Zhang Haoyu
Generally I
On 12/19/2014 at 06:38 PM, in message
1418985490.20028.27.ca...@citrix.com,
Ian Campbell ian.campb...@citrix.com wrote:
On Thu, 2014-12-18 at 23:58 -0700, Chun Yan Liu wrote:
On 12/18/2014 at 11:27 PM, in message
1418916436.11882.101.ca...@citrix.com,
Ian Campbell
On 2014/12/22 17:28, Paolo Bonzini wrote:
On 22/12/2014 07:39, Zhang Haoyu wrote:
Hi,
When I perform P2V from native servers with win2008 to kvm vm,
some cases failed due to the physical disk was using GPT for partition,
and QEMU doesn't support GPT by default.
And, I see in below
hi,all,
when i use `qemu-img snapshot -c test-s sheepdog:test` to create a
snapshot of sheepdog vdi,the snapshot's lock not be released.
root@hty-compute1:~/qemu# ./qemu-img create sheepdog:test 1G
Formatting 'sheepdog:test', fmt=raw size=1073741824
root@hty-compute1:~/qemu# dog vdi list
Hi,
I cannot receive qemu-dev/kvm-dev mails sent by myself,
but mails from others can be received,
any helps?
Thanks,
Zhang Haoyu
On 22/12/2014 10:40, Zhang Haoyu wrote:
2) the FAT driver is not free, which prevents distribution in Fedora and
several other distributions
Sorry, I cannot follow you,
the FAT mentioned above means FAT filesystem?
what's the relationship between OVMF and FAT?
I want to use OVMF to
On 22/12/2014 10:48, Zhang Haoyu wrote:
Hi,
I cannot receive qemu-dev/kvm-dev mails sent by myself,
but mails from others can be received,
any helps?
For qemu-devel, you need to configure mailman to send messages even if
they are yours. For the kvm mailing list I'm not sure how it works
On 2014/12/22 17:52, Paolo Bonzini wrote:
On 22/12/2014 10:40, Zhang Haoyu wrote:
2) the FAT driver is not free, which prevents distribution in Fedora and
several other distributions
Sorry, I cannot follow you,
the FAT mentioned above means FAT filesystem?
what's the relationship
On 2014/12/22 4:10, Michael Roth wrote:
Quoting zhanghailiang (2014-12-06 00:59:14)
Introduce three new guest commands:
guest-get-memory-blocks, guest-set-memory-blocks, guest-get-memory-block-size.
With these three commands, we can support online/offline guest's memory block
(logical memory
On 2014/12/22 4:58, Michael Roth wrote:
Quoting zhanghailiang (2014-12-06 00:59:15)
Signed-off-by: zhanghailiang zhang.zhanghaili...@huawei.com
---
qga/commands-posix.c | 130 +++
1 file changed, 130 insertions(+)
diff --git
On 2014/12/22 5:17, Michael Roth wrote:
Quoting zhanghailiang (2014-12-06 00:59:16)
We can get guest's memory block information by using command
guest-get-memory-blocks, the returned value contains a list of memory block
info, such as phys_index, online state, can-offline info.
Signed-off-by:
On 2014/12/22 5:23, Michael Roth wrote:
Quoting zhanghailiang (2014-12-06 00:59:17)
Signed-off-by: zhanghailiang zhang.zhanghaili...@huawei.com
---
qga/commands-posix.c | 42 +++---
1 file changed, 35 insertions(+), 7 deletions(-)
diff --git
On 2014/12/22 5:41, Michael Roth wrote:
Quoting zhanghailiang (2014-12-06 00:59:18)
The size of a memory block is architecture dependent,
For example, power uses 16MiB, ia64 uses 1GiB, x86 uses 128M.
That's the minimum for Power, but the size can be set via device tree and
can differ from one
On 19 December 2014 at 09:16, Gerd Hoffmann kra...@redhat.com wrote:
Hi,
So, here we go with the sdl2 pull request, no changes to v2
patches series other than adding the two fixes from Max.
please pull,
Gerd
The following changes since commit dfa9c2a0f4d0a0c8b2c1449ecdbb1297427e1560:
On 19 December 2014 at 16:34, Kevin Wolf kw...@redhat.com wrote:
The following changes since commit dfa9c2a0f4d0a0c8b2c1449ecdbb1297427e1560:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
staging (2014-12-15 16:43:42 +)
are available in the git repository at:
On 2014/12/22 17:54, Paolo Bonzini wrote:
On 22/12/2014 10:48, Zhang Haoyu wrote:
Hi,
I cannot receive qemu-dev/kvm-dev mails sent by myself,
but mails from others can be received,
any helps?
For qemu-devel, you need to configure mailman to send messages even if
they are yours. For
On 22/12/2014 12:40, Zhang Haoyu wrote:
On 2014/12/22 17:54, Paolo Bonzini wrote:
On 22/12/2014 10:48, Zhang Haoyu wrote:
Hi,
I cannot receive qemu-dev/kvm-dev mails sent by myself,
but mails from others can be received,
any helps?
For qemu-devel, you need to configure mailman to send
On 22 December 2014 at 11:14, Peter Maydell peter.mayd...@linaro.org wrote:
Hi. I'm afraid this fails make check on MacOSX:
/Users/pm215/src/qemu/tests/qemu-iotests-quick.sh
/Users/pm215/src/qemu/tests/qemu-iotests/common.config: line 158:
/bin/true: No such file or directory
check: failed to
The only change from v5 to v6 is that sysbus_mmio_map is moved to
fw_cfg_init_mem. (And fw_cfg_init1 returns void because it's now
simpler that way).
This causes changes in patches 1, 5 and 6.
I did not have the ARM firmware built, so I tested on PPC to check
for compatibility, and played with
From: Laszlo Ersek ler...@redhat.com
We are going to introduce a wide data register for fw_cfg, but only for
the MMIO mapped device. The wide data register will also require the
tightening of endiannesses.
However we don't want to touch the I/O port mapped fw_cfg device at all.
Currently QEMU
From: Laszlo Ersek ler...@redhat.com
fw_cfg already supports exposure over MMIO (used in ppc/mac_newworld.c,
ppc/mac_oldworld.c, sparc/sun4m.c); we can easily add it to the virt
board.
Because MMIO access is slow on ARM KVM, we enable the guest, with
fw_cfg_init_mem_wide(), to transfer up to 8
From: Laszlo Ersek ler...@redhat.com
This allows us to drop the fw_cfg_init() shim and to enforce the possible
mappings at compile time.
Signed-off-by: Laszlo Ersek ler...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
hw/i386/pc.c | 4 ++--
hw/nvram/fw_cfg.c
From: Laszlo Ersek ler...@redhat.com
Make it clear that the maximum access size to the MMIO data register
determines the full size of the memory region.
Currently the max access size is 1.
This patch doesn't change behavior.
Signed-off-by: Laszlo Ersek ler...@redhat.com
Signed-off-by: Paolo
Otherwise fw_cfg accesses are split into 4-byte ones before they reach the
fw_cfg ops / handlers.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
Signed-off-by: Laszlo Ersek ler...@redhat.com
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
exec.c | 13 +++--
1 file changed, 11
From: Laszlo Ersek ler...@redhat.com
In the next patch we'd like to reuse the image decompression facility
without installing the output as a ROM at a specific guest-phys address.
In addition, expose LOAD_IMAGE_MAX_GUNZIP_BYTES, because that's a
straightforward max_sz argument for the new
From: Laszlo Ersek ler...@redhat.com
The standalone selector port (fw_cfg_ctl_mem_ops) is only used by big
endian guests to date (*), hence this change doesn't regress them. Paolo
and Alex have suggested / requested an explicit DEVICE_BIG_ENDIAN setting
here, for clarity.
(*) git grep -l
From: Laszlo Ersek ler...@redhat.com
The data_width property is capable of changing the maximum valid access
size to the MMIO data register, and resizes the memory region similarly,
at device realization time.
The default value of data_memwidth is set so that we don't yet diverge
from
From: Laszlo Ersek ler...@redhat.com
We rebase fw_cfg_init_mem() to the new function for compatibility with
current callers.
The behavior of the (big endian) multi-byte data reads is best shown
with a qtest session. Here, we are reading the first six bytes of
the UUID
$
From: Laszlo Ersek ler...@redhat.com
Introduce the new boolean field arm_boot_info.firmware_loaded. When this
field is set, it means that the portion of guest DRAM that the VCPU
normally starts to execute, or the pflash chip that the VCPU normally
starts to execute, has been populated by
From: Laszlo Ersek ler...@redhat.com
The virt board already ensures mutual exclusion between -bios and -pflash
unit#0; we only need to set bootinfo.firmware_loaded, introduced in the
previous patch, if either of those options was used to load the guest
firmware.
Signed-off-by: Laszlo Ersek
On 2014/12/22 20:05, Paolo Bonzini wrote:
On 22/12/2014 12:40, Zhang Haoyu wrote:
On 2014/12/22 17:54, Paolo Bonzini wrote:
On 22/12/2014 10:48, Zhang Haoyu wrote:
Hi,
I cannot receive qemu-dev/kvm-dev mails sent by myself,
but mails from others can be received,
any helps?
For
On 22 December 2014 at 12:07, Peter Maydell peter.mayd...@linaro.org wrote:
Something very odd is happening here: why are all the rs apparently
missing from those error messages?
Looks like the result of using GNU sed-isms in some of the filters. On OSX:
$ echo art trick | sed -e 's/\r//g'
at
On 2014/12/16 23:01, Dr. David Alan Gilbert wrote:
* Amit Shah (amit.s...@redhat.com) wrote:
On (Wed) 10 Dec 2014 [08:03:33], Amit Shah wrote:
On (Mon) 24 Nov 2014 [19:55:46], arei.gong...@huawei.com wrote:
From: ChenLiang chenlian...@huawei.com
Hi,
This set of patches rebase on
This patchset provides an ability to create of/write to Parallels
images and some testing of the new code. Writes are not optimized
now at all, we just modify catalog_bitmap and write those changes
to the image itself at once. This will be improved in next steps.
This patchset consists of not
Main approach is taken from qcow2_co_readv.
The patch drops coroutine lock for the duration of IO operation and
peforms normal scatter-gather IO using standard QEMU backend.
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
this follows QEMU coding convention
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
block/parallels.c | 8
1 file changed, 4 insertions(+),
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
tests/qemu-iotests/076 | 5 +
tests/qemu-iotests/076.out | 10 ++
2 files changed,
From: Roman Kagan rka...@parallels.com
Switch the .bdrv_read method implementation from using bdrv_pread() to
bdrv_read() on the underlying file, since the latter is subject to i/o
throttling while the former is not.
Besides, since bdrv_read() operates in sectors rather than bytes, adjust
the
simple purification..
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
block/parallels.c | 8
1 file changed, 4 insertions(+), 4
suggested by Jeff Cody
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
tests/qemu-iotests/076 | 10 +-
1 file changed, 5 insertions(+), 5
Support write on Parallels images. The code is almost the same as one
in the previous patch implemented scatter-gather IO for read.
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan
From: Roman Kagan rka...@parallels.com
Teach parallels_read() to do reads in coarser granularity than just a
single sector: if requested, read up to the cluster end in one go.
Signed-off-by: Roman Kagan rka...@parallels.com
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Jeff Cody
From: Roman Kagan rka...@parallels.com
Implement VFS method for get_block_status to Parallels format driver.
Signed-off-by: Roman Kagan rka...@parallels.com
Signed-off-by: Denis V. Lunev d...@openvz.org
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi
Do not even care to create WithoutFreeSpace image, it is obsolete.
Always create WithouFreSpacExt one.
The code also does not spend a lot of efforts to fill cylinders and
heads fields, they are not used actually in a real life neither in
QEMU nor in Parallels products.
Signed-off-by: Denis V.
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
CC: Jeff Cody jc...@redhat.com
CC: Kevin Wolf kw...@redhat.com
CC: Stefan Hajnoczi stefa...@redhat.com
---
tests/qemu-iotests/115 | 68 ++
Signed-off-by: Denis V. Lunev d...@openvz.org
Acked-by: Roman Kagan rka...@parallels.com
---
block/parallels.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/block/parallels.c b/block/parallels.c
index bea1217..e3abf4e 100644
--- a/block/parallels.c
+++
On 19 December 2014 at 16:56, Eduardo Otubo
eduardo.ot...@profitbricks.com wrote:
The following changes since commit b574f602680d41c4cf4a9c106e3e2244bed01cdd:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20141216-1' into
staging (2014-12-17 19:22:42 +)
are available in
OSes typically write 0xdd/0xdf to turn the A20 line off and on. This
has bits 2-3-6-7 on, so that the output port subsection is migrated.
Change the reset value and migration default to include those four
bits, thus avoiding that the subsection is migrated.
This strictly speaking changes guest
If the THR interrupt is disabled, there is no need to migrate thr_ipending
because LSR.THRE will be sampled again when the interrupt is enabled.
(This is the behavior that is not documented in the datasheet, but
relied on by Windows!)
Note that in this case IIR will never be 0x2 so, if
Two more changes. The first is a bit of a shot in the dark, because I
cannot reproduce it, but it's obviously an improvement.
Paolo Bonzini (2):
serial: refine serial_thr_ipending_needed
pckbd: set bits 2-3-6-7 of the output port by default
hw/char/serial.c | 13 +++--
On 21 December 2014 at 18:47, Bastian Koppelmann
kbast...@mail.uni-paderborn.de wrote:
The following changes since commit c4e7c17a8ecb41cdbb81374a128161c614ba1f1e:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-roms-20141217-1'
into staging (2014-12-20 21:28:53 +)
are
** Changed in: qemu
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1402802
Title:
target-tricore/translate.c:3812: possible bad expression ?
Status in
Signed-off-by: Don Slutz dsl...@verizon.com
---
qemu-char.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/qemu-char.c b/qemu-char.c
index ef84b53..6eec1d2 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -1387,6 +1387,7 @@ static CharDriverState *qemu_chr_open_pty(const char *id,
}
I never have a problem when using virsh snapshot-create or delete.
Problem started with one VM when I use qemu-img snapshot. Thank you Todd
for work-around. It's helped me too. VM working again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Hello,
I am interested in learning the qemu emulation technology, But I don't know
where to start. I have some knowledge/experience in device modeling.
While walking through the qemu.org, I couldn't found proper documentation or
guide to start working with QEMU.
So, I am seeking some helps
The following series add VFIO support for AMBA devices.
It introduces multiple compatible string support to deal with arm,primecell
compatible string.
The VFIOPlatformDevice now checks for this string and performs amba specific
operations if it is present (change path of the device, add clock in
Add VFIO_DEVICE_TYPE_AMBA.
Differentiate amba and platform devices according to compatible string.
Signed-off-by: Baptiste Reynal b.rey...@virtualopensystems.com
---
hw/vfio/platform.c| 15 ---
include/hw/vfio/vfio-common.h | 1 +
2 files changed, 13 insertions(+), 3
Create a meta-device for PL330 DMA.
Add add_arm_pl330_fdt_node function, with multiple compatible string
and clocks support.
Signed-off-by: Baptiste Reynal b.rey...@virtualopensystems.com
---
hw/arm/sysbus-fdt.c | 84
hw/vfio/Makefile.objs
Creates set_interrupts_fdt_node and set_regions_fdt_node
for code reusability.
Signed-off-by: Baptiste Reynal b.rey...@virtualopensystems.com
---
hw/arm/sysbus-fdt.c | 102 +---
1 file changed, 73 insertions(+), 29 deletions(-)
diff --git
)
are available in the git repository at:
https://github.com/gongleiarei/qemu.git tags/bootdevice-next-20141222
for you to fetch changes up to ddcd55316fb2851e144e719171621ad2816487dc:
bootdevice: add Error **errp argument for QEMUBootSetHandler (2014-12-22
14:39:21 +0800
On 22 December 2014 at 16:08, Ronex Dicapriyo ronex...@yahoo.in wrote:
I am interested in learning the qemu emulation technology, But I don't know
where to start. I have some knowledge/experience in device modeling.
While walking through the qemu.org, I couldn't found proper documentation or
Thanks for the explanations, I have some more doubts on the same, Kindly
clarify.
On Monday, 22 December 2014 10:10 PM, Peter Maydell
peter.mayd...@linaro.org wrote:
1) the basic execution flow of QEMU simulation engine
2) Notion of time, events in QEMU
We don't have quite the
I have a fix for this (our code for setting up the signal return
trampoline used the wrong types and only worked on 32 bit hosts).
I notice that /bin/ls can't ls directories (it seems ok with single
files) but that's a different bug.
--
You received this bug notification because you are a
The m68k signal frame setup code which writes the signal return
trampoline code to the stack was assuming that a 'long' was 32 bits;
on 64 bit systems this meant we would end up writing the 32 bit
(2 insn) trampoline sequence to retaddr+4,retaddr+6 instead of
the intended retaddr+0,retaddr+2,
Hello,
I am interested in learning the qemu emulation technology, But I don't know
where to start. I have some knowledge/experience in device modeling.
While walking through the qemu.org, I couldn't found proper documentation or
guide to start working with QEMU.
So, I am seeking some helps from
On 22 December 2014 at 17:05, Ronex Dicapriyo ronex...@yahoo.in wrote:
[Ronex] Ok, As I can understand, QEMU is functional accurate, rather than
cycle for fast simulation. But there must be some kind of reference clock,
like say for example any timer device which raises an interrupt after
Patch fixing this: https://patchwork.ozlabs.org/patch/423460/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1404690
Title:
Qemu crashes with chrooted m68k
Status in QEMU:
New
Bug description:
The following changes since commit b574f602680d41c4cf4a9c106e3e2244bed01cdd:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20141216-1' into
staging (2014-12-17 19:22:42 +)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git
From: Frank Blaschka blasc...@linux.vnet.ibm.com
Depending on the device, container-space-as contains the valid AddressSpace.
Using address_space_memory breaks devices sitting behind an iommu (and using
a separate address space).
Signed-off-by: Frank Blaschka blasc...@linux.vnet.ibm.com
From: Eric Auger eric.au...@linaro.org
This patch removes all DPRINTF and replace them by trace points.
A few DPRINTF used in error cases were transformed into error_report.
Signed-off-by: Eric Auger eric.au...@linaro.org
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
From: Eric Auger eric.au...@linaro.org
Add 3 new fields in the VFIODevice struct. Type is set to
VFIO_DEVICE_TYPE_PCI. The type enum value will later be used
to discriminate between VFIO PCI and platform devices. The name is
set to domain:bus:slot:function. Currently used to test whether
the
From: Eric Auger eric.au...@linaro.org
To prepare for platform device introduction, rename vfio_mask_intx
and vfio_unmask_intx into vfio_mask_single_irqindex and respectively
unmask_single_irqindex. Also use a nex index parameter.
With that name and prototype the function will be usable for
From: Eric Auger eric.au...@linaro.org
This prepares for the introduction of VFIOPlatformDevice
Signed-off-by: Eric Auger eric.au...@linaro.org
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/vfio/pci.c | 210 +
1 file
From: Eric Auger eric.au...@linaro.org
Introduce a new base VFIODevice strcut that will be used by both PCI
and Platform VFIO device. Move VFIOPCIDevice fd field there. Obviously
other fields from VFIOPCIDevice will be moved there but this patch
file is introduced to ease the review.
Also
From: Eric Auger eric.au...@linaro.org
This structure is going to be shared by VFIOPCIDevice and
VFIOPlatformDevice. VFIOBAR includes it.
vfio_eoi becomes an ops of VFIODevice specialized by parent device.
This makes possible to transform vfio_bar_write/read into generic
vfio_region_write/read
From: Eric Auger eric.au...@linaro.org
Since we can potentially have both PCI and platform devices in
the same VFIO group, this latter now owns a list of VFIODevices.
A unified reset handler, vfio_reset_handler, is registered, looping
through this VFIODevice list. 2 specialized operations are
With the conversion to tracepoints, a couple previous DPRINTKs are
now quite a bit more visible and are really just informational.
Remove these and add a bit more description to another.
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/vfio/common.c |2 +-
hw/vfio/pci.c|
From: Eric Auger eric.au...@linaro.org
better fit in the rest of the namespace
Signed-off-by: Eric Auger eric.au...@linaro.org
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/vfio/pci.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git
From: Eric Auger eric.au...@linaro.org
Signed-off-by: Eric Auger eric.au...@linaro.org
Signed-off-by: Alex Williamson alex.william...@redhat.com
---
hw/vfio/pci.c | 213 -
trace-events | 109 +++--
2 files
From: Eric Auger eric.au...@linaro.org
vfio_get_device now takes a VFIODevice as argument. The function is split
into 2 parts: vfio_get_device which is generic and vfio_populate_device
which is bus specific.
3 new fields are introduced in VFIODevice to store dev_info.
vfio_put_base_device is
From: Eric Auger eric.au...@linaro.org
A new common module is created. It implements all functions
that have no device specificity (PCI, Platform).
This patch only consists in move (no functional changes)
Signed-off-by: Kim Phillips kim.phill...@linaro.org
Signed-off-by: Eric Auger
1 - 100 of 158 matches
Mail list logo
