On 09/11/2014 05:20 PM, Michael Roth wrote:
> If the .data field of a QAPI Union is NULL, we don't need to free
> any of the union fields..
intentional double dot?
>
> Make use of the new visit_start_union interface to access this
> information and instruct the generated code to not visit these
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/087 | 17 +
tests/qemu-iotests/087.out | 13 +
2 files changed, 30 insertions(+)
diff --git a/tests/qemu-iotests/087 b/tests/qemu-iotests/087
index 82c56b1..d7454d1 100755
--- a/tests/qemu-iotests/087
+++ b/tests/qem
On Thu, 09/11 18:20, Michael Roth wrote:
> This series introduces visit_start_enum and visit_end_enum as a way
> of allowing visitors to trigger generated code to bail out on visiting
> union fields if the visitor implementation deems doing so to be unsafe.
>
> See patch 1 for the circumstances th
On 09/12/2014 12:18 AM, Michael S. Tsirkin wrote:
> On vm stop, vm_running state set to stopped
> before device is notified, so callbacks can get envoked with
> vm_running = false; and this is not an error.
This is consistent with virtio-blk which also has such kinds of
callbacks. This fixes the i
On 09/12/2014 12:18 AM, Michael S. Tsirkin wrote:
> This reverts commit a1bc7b827e422e1ff065640d8ec5347c4aadfcd8.
> virtio: don't call device on !vm_running
> It turns out that virtio net assumes that vm_running
> is updated before device status callback in many places,
> so this change leads t
Hi Igor,
On 09/10/2014 09:55 PM, Igor Mammedov wrote:
> On Wed, 3 Sep 2014 17:06:16 +0800
> Gu Zheng wrote:
>
>> Add cpu hotplug handler to PC_MACHINE, which will perform the acpi
>> cpu hotplug callback via hotplug_handler API.
>>
>> Signed-off-by: Gu Zheng
>> ---
>> hw/i386/pc.c | 26
>>> > > If virtio-blk and virtio-serial share an IRQ, the guest operating
>>> > > system has to check each virtqueue for activity. Maybe there is some
>>> > > inefficiency doing that.
>>> > > AFAIK virtio-serial registers 64 virtqueues (on 31 ports + console)
>>> > > even if everything is unused
On Tue, 09/09 14:28, Benoît Canet wrote:
> On Tue, Sep 09, 2014 at 01:56:46PM +0200, Kevin Wolf wrote:
> > Am 22.08.2014 um 18:11 hat Benoît Canet geschrieben:
> > > Since the block layer code is starting to modify the BDS graph right in
> > > the
> > > middle of BDS chains (block-mirror's replace
On 09/11/2014 09:02 PM, Alexey Kardashevskiy wrote:
> On 09/11/2014 08:38 PM, Gerd Hoffmann wrote:
>> Hi,
>>
>>> Another question - I noticed that XHCI migration is broken in quite recent
>>> upstream QEMU, smells like memory corruption. Is it just me or just PPC or
>>> is it known issue?
>>
>> 2
On 09/11/2014 09:04 PM, Fam Zheng wrote:
> Signed-off-by: Fam Zheng
> ---
> tests/qemu-iotests/087 | 17 +
> tests/qemu-iotests/087.out | 13 +
> 2 files changed, 30 insertions(+)
Reviewed-by: Eric Blake
--
Eric Blake eblake redhat com+1-919-301-3266
Libv
The PCI MMIO might be disabled or the device in the reset state.
Make sure we do not dump these memory regions.
Signed-off-by: Nikunj A Dadhania
---
hw/misc/vfio.c| 2 +-
include/exec/memory.h | 27 +++
memory.c | 16
memory_mapping.
On Fri, 2014-09-12 at 10:12 +0530, Nikunj A Dadhania wrote:
> The PCI MMIO might be disabled or the device in the reset state.
> Make sure we do not dump these memory regions.
>
> Signed-off-by: Nikunj A Dadhania
> ---
If you don't want to dump a memory region then add the ability to set a
no-du
On 2014/9/4 21:28, Igor Mammedov wrote:
On Wed, 27 Aug 2014 16:08:36 +0800
Tang Chen wrote:
From: Hu Tao
Implement unrealize function for pc-dimm device. It delete subregion from
s/delete/removes/
hotplug region, and delete ram address range from guest ram list.
Signed-off-by: Hu Tao
Sign
Since we have supported memory hotplug, VM's ram include pc.ram
and hotplug-memory.
Fix the confused description for rdma migration: pc.ram -> VM's ram
Signed-off-by: zhanghailiang
---
docs/rdma.txt| 6 +++---
migration-rdma.c | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
diff
It should be valid for the follow configure:
-m 256,slots=0
-m 256,maxmem=256M
-m 256,slots=0,maxmem=256M
-m 256,slots=x,maxmem=y where x > 0 and y > 256M
Fix the confused code logic and use error_report instead of fprintf.
Printing the maxmem in hex, same with ram_size.
Signed-off-by: zhanghai
在 08/01/2014 11:03 PM, Dr. David Alan Gilbert 写道:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
implement colo checkpoint protocol.
Checkpoint synchronzing points.
Primary Secondary
NEW @
Suspend
在 08/01/2014 11:10 PM, Dr. David Alan Gilbert 写道:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
The ram cache was initially the same as PVM's memory. At
checkpoint, we cache the dirty memory of PVM into ram cache
(so that ram cache always the same as PVM's memory at every
checkpoint), flush c
> > pixman-0.21.8 is the oldest release which has PIXMAN_TYPE_RGBA.
> > We don't check for a minimum version.
> > RHEL-6 is probably older.
Uhm, well, it isn't (any more):
[root@rhel6 ~]# rpm -q pixman
pixman-0.26.2-5.1.el6_5.x86_64
Seems to be rebased somewhen (used to be 0.16 for RHEL-6.0 IIRC
在 08/01/2014 10:43 PM, Dr. David Alan Gilbert 写道:
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
migrate colo info to migration target to tell the target colo is
enabled.
If I understand this correctly this means that you send a 'colo info' device
information for migrations that don't have C
Eric Blake writes:
> On 09/11/2014 01:34 PM, Benoît Canet wrote:
>> The Thursday 11 Sep 2014 à 21:12:44 (+0200), Markus Armbruster wrote :
>>> Benoît Canet writes:
>>>
> + blk_bs(blk_by_legacy_dinfo(dinfo)));
This seems to be a fairly common patter
Benoît Canet writes:
>> EOF
>> ---
>> If you have feedback or questions, let us know. The process can be
>> tweaked as time goes on so we can continue to improve.
>
> Great mail.
Yup. Let's see how it works out.
> Now we need a wiki entry describing the process.
> Also we need something remin
> Subject: Re: [Qemu-devel] [PATCH v8 00/30] modify boot order of guest, and
> take effect after rebooting
>
> Am 11.09.2014 um 07:58 schrieb Gonglei (Arei):
> >>> ./qemu-system-x86_64 -enable-kvm -m 4096 -smp 4 -name redhat6.2
> -drive \
> >>> file=/home/win7_32_2U,if=none,id=drive-ide0-0-0 -devi
Hi,
> With OVMF, I have EHCI with the high-speed (and working)
> keyboard+mouse, but ONLY ONE UHCI device (UHCI3). UHCI1 UHCI2 do not
> get detected.
Now *that* is really strange, especially as UHCI1 is pci function 0,
without probing that successfully you wouldn't see the other pci
functions (1
On 2014/9/12 13:58, zhanghailiang wrote:
> It should be valid for the follow configure:
> -m 256,slots=0
> -m 256,maxmem=256M
> -m 256,slots=0,maxmem=256M
> -m 256,slots=x,maxmem=y where x > 0 and y > 256M
>
> Fix the confused code logic and use error_report instead of fprintf.
>
> Printing th
You neglected to cc maintainers.
Stratos Psomadakis writes:
> Hi,
>
> the first patch fixes an issue with HMP monitors, which was exposed
> with v2.1.0 (commits cdaa86a and 812c10).
Copying Luiz.
> The second one fixes a typo in a helper C program used in
> qemu-iotests.
Copying Kevin and Ste
Stratos Psomadakis writes:
> Commit cdaa86a54 ("Add G_IO_HUP handler for socket chardev") exposed a
> bug in the way the HMP monitor handles its input. When a client closes
> the connection to the monitor, tcp_chr_read() will catch the HUP
> 'signal' and call tcp_chr_disconnect() to close the se
201 - 226 of 226 matches
Mail list logo
