Signed-off-by: Markus Armbruster
---
tests/libqtest.c | 5 +++--
tests/libqtest.h | 5 +++--
2 files changed, 6 insertions(+), 4 deletions(-)
diff --git a/tests/libqtest.c b/tests/libqtest.c
index c52ceb2..fa314e1 100644
--- a/tests/libqtest.c
+++ b/tests/libqtest.c
@@ -760,14 +760,15 @@ void qt
On Fri, Dec 04, 2015 at 02:42:36PM +0800, Lan, Tianyu wrote:
>
> On 12/2/2015 10:31 PM, Michael S. Tsirkin wrote:
> >>>We hope
> >>>to find a better way to make SRIOV NIC work in these cases and this is
> >>>worth to do since SRIOV NIC provides better network performance compared
> >>>with PV NIC.
David Gibson writes:
> On Thu, Dec 03, 2015 at 04:30:31PM +0100, Markus Armbruster wrote:
>> 1. Before commit 94649d4 "spapr: Don't use QOM [*] syntax for DR
>>connectors", the indexes were small integers:
>>
>>(qemu) info qom-tree
>>/machine (pseries-2.4-machine)
>>
Eric Blake writes:
> On 12/03/2015 04:54 PM, David Gibson wrote:
>> On Thu, Dec 03, 2015 at 05:37:39PM +0100, Markus Armbruster wrote:
>>> prop_get_fdt() misuses the visitor API: when fdt is null, it doesn't
>>> visit anything. object_property_get_qobject() happily
>>> object_property_get_qobjec
On 2015-12-03 13:19, Aurelien Jarno wrote:
> On 2015-12-02 10:36, Richard Henderson wrote:
> > On 12/01/2015 08:32 AM, Aurelien Jarno wrote:
> > >On 2015-12-01 08:19, Richard Henderson wrote:
> > >>If there are a lot of guest memory ops in the TB, the amount of
> > >>code generated by tcg_out_tb_fi
On 12/02/2015 11:26 PM, Shmulik Ladkani wrote:
> Place device reported PCI capabilities at the same offsets as placed by
> the VMware virtual hardware: MSI at [84], MSI-X at [9c].
>
> For compatability, preserve old offsets using 'x-old-msi-offsets' toggle.
>
> Signed-off-by: Shmulik Ladkani
> -
On 12/02/2015 11:26 PM, Shmulik Ladkani wrote:
> Report the 'express endpoint' capability if on a PCIE bus.
>
> The 'x-disable-pcie' property is used for backwards compatability.
>
> Signed-off-by: Shmulik Ladkani
> ---
> hw/net/vmxnet3.c| 55
> +
On Wed, Dec 02, 2015 at 05:36:49AM -0500, Marc-André Lureau wrote:
> Hi
>
> - Original Message -
> > ae31fb5 "vhost-user-test: wrap server in TestServer struct" cleaned up
> > the handling of the test server in vhost-user-test. Unfortunately it
> > introduced a subtle use-after-free if a
* Zhang Chen (zhangchen.f...@cn.fujitsu.com) wrote:
> Hi,Dave
>
>
> On 12/03/2015 05:09 PM, Dr. David Alan Gilbert wrote:
> >* Zhang Chen (zhangchen.f...@cn.fujitsu.com) wrote:
> >>Hi,Dave
> >>
> >>On 12/02/2015 12:12 AM, Dr. David Alan Gilbert wrote:
> >>>* Zhang Chen (zhangchen.f...@cn.fujitsu.
Macro VMW_SHPRN(...) is already defined vmxnet3_debug.h,
so remove the duplication
Signed-off-by: Miao Yan
---
hw/net/vmware_utils.h | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/hw/net/vmware_utils.h b/hw/net/vmware_utils.h
index 1099df6..c2c2f90 100644
--- a/hw/net/vm
Vmxnet3 uses the following debug macro style:
#ifdef SOME_DEBUG
# define debug(...) do{ printf(...); } while (0)
# else
# define debug(...) do{ } while (0)
#endif
If SOME_DEBUG is undefined, then format string inside the
debug macro will never be checked by compiler. Code will
likely to br
On Fri, Dec 04, 2015 at 09:05:51AM +0100, Markus Armbruster wrote:
> David Gibson writes:
>
> > On Thu, Dec 03, 2015 at 04:30:31PM +0100, Markus Armbruster wrote:
> >> 1. Before commit 94649d4 "spapr: Don't use QOM [*] syntax for DR
> >>connectors", the indexes were small integers:
> >>
> >>
David Gibson writes:
> On Fri, Dec 04, 2015 at 09:05:51AM +0100, Markus Armbruster wrote:
>> David Gibson writes:
>>
>> > On Thu, Dec 03, 2015 at 04:30:31PM +0100, Markus Armbruster wrote:
>> >> 1. Before commit 94649d4 "spapr: Don't use QOM [*] syntax for DR
>> >>connectors", the indexes w
Hi,
> btw some questions here:
>
> for non-gl and gl rendering in Qemu, are they based on dma-buf already?
> once we can export guest framebuffer in dma-buf, is there additional work
> required or just straightforward to integrate with SPICE?
Right now we are busy integrating dma-buf support
On Fri, 4 Dec 2015 10:06:58 +0800
Jason Wang wrote:
> The problem is for pci: without this patch, guest may always see modern
> bar is "disable-modern=false". But with this patch, on an old kernel
> that does not support VERSION_1, even "disable-modern=false" were
> specified, guest can not see m
2015-12-04 0:40 GMT+08:00 Markus Armbruster :
> Eric Blake writes:
>
>> On 12/02/2015 10:08 PM, Miao Yan wrote:
>>> Macro MAC_FMT and MAC_ARG are not defined, but used in vmxnet3_net_init().
>>> This will cause build error when debug level is raised in
>>> vmxnet3_debug.h (enable all VMXNET3_DEBUG
son/qemu.git tags/ppc-for-2.5-20151204
>
> for you to fetch changes up to ab8bf1d735133df5b5847bef0b0bea496d614a5a:
>
> spapr_drc: Change value of property "fdt" from null back to {} (2015-12-04
> 16:50:59 +1100)
>
>
> Peter,
>
> Not sure if you need a
On 4 December 2015 at 07:30, Markus Armbruster wrote:
> Peter Maydell writes:
>
>> On 7 September 2015 at 17:57, Markus Armbruster wrote:
>>> Peter Maydell writes:
>>>
On 7 September 2015 at 17:40, Markus Armbruster wrote:
> Peter Maydell writes:
>
>> Convert the pxa2xx_mmci
Liang Li wrote:
> This patch fixed the flaws in qemu_put_compression_data function.
> and cleanup the code based on the change.
Hi
We are in hard freeze. My understanding is that this are
"optimizations" that can wait for 2.6:
- my understanding from commit from message one and from quick look
Liang Li wrote:
> There are some flaws in qemu_put_compression_data, this patch tries
> to fix it. Now it can be used by other code.
>
> Signed-off-by: Liang Li
> ---
> migration/qemu-file.c | 10 +-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/migration/qemu-file.c
On 04/12/15 00:02, Peter Maydell wrote:
> On 3 December 2015 at 23:24, Programmingkid wrote:
>> I would like to make a little tutorial on how to make networking
>> work for a Mac OS X guest. Where would you suggest I put such
>> documentation? The qemu-doc file is what I was thinking about using.
On 4 December 2015 at 06:57, Michael Tokarev wrote:
> Hello.
>
> During the freeze period, let me please add my trivial pull request too ;)
>
> There are just 9 patches this time, which are either (small) bugfixes,
> or just prettifying one or another part of code to look nicely in the
> release t
On 4 December 2015 at 11:36, Mark Cave-Ayland
wrote:
> Is it worth setting up per-arch homepages on the wiki? This is something
> I've thought about recently since most of the information out on the
> internet regarding QEMU's ability to run various systems is badly out of
> date with regard to SP
On 4 December 2015 at 10:11, Markus Armbruster wrote:
> If you want it to be null in 2.5, NAK "[PATCH for-2.5 2/3] spapr_drc:
> Change value of property "fdt" from null back to {}".
That commit is now in master, so if you don't want it you need to
actively send a revert for it.
thanks
-- PMM
阎淼 writes:
> 2015-12-04 0:40 GMT+08:00 Markus Armbruster :
>> Eric Blake writes:
>>
>>> On 12/02/2015 10:08 PM, Miao Yan wrote:
Macro MAC_FMT and MAC_ARG are not defined, but used in vmxnet3_net_init().
This will cause build error when debug level is raised in
vmxnet3_debug.h (ena
On 12/4/2015 4:05 PM, Michael S. Tsirkin wrote:
I haven't read it, but I would like to note you can't rely on research
papers. If you propose a patch to be merged you need to measure what is
its actual effect on modern linux at the end of 2015.
Sure. Will do that.
This is a first baby step towards removing widespread inclusion of
cpu.h and compiling more devices once (so that arm, aarch64 and
in the future target-multi can share the object files).
Signed-off-by: Paolo Bonzini
---
hw/dma/soc_dma.c | 37 -
1 file changed,
ARM softmmu is always compiled as little endian; BE8/BE32 can be
done as part of CPU emulation. Thus, devices need not use the
endian-dependent loads and swaps.
Signed-off-by: Paolo Bonzini
---
hw/display/omap_lcd_template.h | 4 ++--
hw/display/pxa2xx_lcd.c| 8
2 files changed
On 4 December 2015 at 12:28, Paolo Bonzini wrote:
> This is a first baby step towards removing widespread inclusion of
> cpu.h and compiling more devices once (so that arm, aarch64 and
> in the future target-multi can share the object files).
>
> Signed-off-by: Paolo Bonzini
> ---
> hw/dma/soc_d
On 04/12/2015 13:33, Peter Maydell wrote:
> On 4 December 2015 at 12:28, Paolo Bonzini wrote:
>> This is a first baby step towards removing widespread inclusion of
>> cpu.h and compiling more devices once (so that arm, aarch64 and
>> in the future target-multi can share the object files).
>>
>>
Ensure that the error is printed with the proper timestamp.
Signed-off-by: Paolo Bonzini
---
v1->v2: remove reference to -net dump, dumping can be a network filter
---
net/dump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/dump.c b/net/dump.c
index ce16a4b..1c
On (Fri) 04 Dec 2015 [11:53:09], Liang Li wrote:
> There are some flaws in qemu_put_compression_data, this patch tries
> to fix it. Now it can be used by other code.
Can you please write a better description here? What are the flaws?
What is being fixed? What other users, and how is it now safer
Peter Maydell writes:
> On 4 December 2015 at 07:30, Markus Armbruster wrote:
>> Peter Maydell writes:
>>
>>> On 7 September 2015 at 17:57, Markus Armbruster wrote:
Peter Maydell writes:
> On 7 September 2015 at 17:40, Markus Armbruster wrote:
>> Peter Maydell writes:
On 4 December 2015 at 12:28, Paolo Bonzini wrote:
> ARM softmmu is always compiled as little endian; BE8/BE32 can be
> done as part of CPU emulation. Thus, devices need not use the
> endian-dependent loads and swaps.
The patch code is right, but I think the more significant point
here is that th
On 4 December 2015 at 12:50, Markus Armbruster wrote:
> To finally answer your question: the proper owner of the property
> connecting the backend is the frontend half of the split device. So, if
> we have separate device models for controller and the block devices
> connected to it, the block ba
Paolo Bonzini writes:
> This is a first baby step towards removing widespread inclusion of
> cpu.h and compiling more devices once (so that arm, aarch64 and
> in the future target-multi can share the object files).
Sounds like something that should be covered in
http://qemu-project.org/CodeTrans
Peter Maydell writes:
> On 4 December 2015 at 12:50, Markus Armbruster wrote:
>> To finally answer your question: the proper owner of the property
>> connecting the backend is the frontend half of the split device. So, if
>> we have separate device models for controller and the block devices
>>
The following exception is threw:
Python Exception name 'long' is not defined:
Error occurred in Python command: name 'long' is not defined
Python 2.4+, int()/long() have been unified, so replace long
with int.
Signed-off-by: Yang Wei
---
scripts/qemugdb/mtree.py | 10 +-
1 file change
On 4 December 2015 at 12:36, Paolo Bonzini wrote:
>
>
> On 04/12/2015 13:33, Peter Maydell wrote:
>> On 4 December 2015 at 12:28, Paolo Bonzini wrote:
>>> This is a first baby step towards removing widespread inclusion of
>>> cpu.h and compiling more devices once (so that arm, aarch64 and
>>> in
Am 30.11.2015 um 15:51 hat Alberto Garcia geschrieben:
> On Mon 23 Nov 2015 04:59:42 PM CET, Kevin Wolf wrote:
>
> > @@ -370,11 +371,22 @@ static void mirror_exit(BlockJob *job, void *opaque)
> > if (s->to_replace) {
> > to_replace = s->to_replace;
> > }
> > +
> > +
On 12/04/2015 02:19 AM, Miao Yan wrote:
> Vmxnet3 uses the following debug macro style:
>
When sending a patch series, it's best to include a 0/2 cover letter
(some of the maintainer tooling works better if it can reply to the
cover letter).
Also, this patch depends on your earlier patch "net/vm
Hi
On Fri, Dec 4, 2015 at 4:52 AM, Tetsuya Mukawa wrote:
> If virtio-net driver allocates memory in vishmem shared memory,
s/vishmem/ivshmem
How can virtio-net allocate memory in ivshmem memory bar?
What's the use case or test case?
> vhost-net will work correctly, but vhost-user will not wor
On 12/03/2015 10:55 AM, Markus Armbruster wrote:
> I'm incapable of proof-reading anything I wrote myself %-}
I know the feeling :)
>
> prop_get_fdt() misuses the visitor API: when fdt is null, it doesn't
> visit anything. object_property_get_qobject() happily calls
> qmp_output_ge
On Thu, 3 Dec 2015 15:16:21 -0200
Eduardo Habkost wrote:
> On Thu, Dec 03, 2015 at 04:19:19PM +0100, Igor Mammedov wrote:
> > On Wed, 2 Dec 2015 20:22:45 -0200
> > Eduardo Habkost wrote:
> >
> > > This series removes piix-specific and q35-specific code from
> > > acpi-build.c, making it generi
On 12/03/2015 11:42 PM, Denis V. Lunev wrote:
> From: Olga Krishtal
>
> Our QA team wants to preserve serial output of the guest in between QEMU
> runs to perform post-analysis.
>
> By default this behavior is off (file is truncated each time QEMU is
> started or device is plugged).
>
> Signed-
On 04/12/2015 07:42, Denis V. Lunev wrote:
> From: Olga Krishtal
>
> Our QA team wants to preserve serial output of the guest in between QEMU
> runs to perform post-analysis.
>
> By default this behavior is off (file is truncated each time QEMU is
> started or device is plugged).
>
> Signed-o
This fixes bdrv_reopen() calls like the following one:
qemu-io -c 'open -o overlap-check.template=all /tmp/test.qcow2' \
-c 'reopen -o overlap-check=none'
The approach taken so far would result in an options QDict that has both
"overlap-check.template=all" and "overlap-check=none", which
The interesting part of reopening an image is from which sources the
effective options should be taken, i.e. which options take precedence
over which other options. This patch documents the precedence that will
be implemented in the following patches.
It also refactors bdrv_reopen_queue(), so that
bdrv_replace_in_backing_chain() asserts that not both old and new
BlockDdriverState have a BlockBackend attached to them because both
would have to end up pointing to the new BDS and we don't support more
than one BB per BDS yet.
Before we can safely allow references to existing nodes as backing
f
qcow2 accepts a few driver-specific options that overlap semantically
(e.g. "overlap-check" is an alias of "overlap-check.template", and any
missing cache size option is derived from the given ones).
When bdrv_reopen() merges the set of updated options with left out
options that should be kept at
In order to decide whether a blkdebug: filename can be produced or a
json: one is necessary, blkdebug checked whether bs->options had more
options than just "config", "x-image" or "image" (the latter including
nested options). That doesn't work well when generic block layer options
are present.
Th
Instead of passing a separate drv argument to bdrv_open_common(), just
make sure that a "driver" option is set in the QDict. This also means
that a "driver" entry is consistently present in bs->options now.
This is another step towards keeping all options in the QDict (which is
the represenation o
This is part three (or four, depending on whether you count the bdrv_swap
removal) of what I had sent earlier as "[PATCH 00/34] block: Cache mode for
children, reopen overhaul and more". Most of the patches were actually already
reviewed in v1.
This part contains the remaining functional changes t
For bs->file, using references to existing BDSes has been possible for a
while already. This patch enables the same for bs->backing.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
block.c | 48 +---
block/mirror.c| 2 +-
i
Creating an empty drive while specifying 'format' doesn't make sense.
The specified format driver would simply be ignored.
Make a set 'format' option an indication that a non-empty drive should
be created. This makes 'format' consistent with 'driver' and allows
using it with a block driver that do
Some drivers have nested options (e.g. blkdebug rule arrays), which
don't belong to a child node and shouldn't be removed. Don't remove all
options with "." in their name, but check for the complete prefixes of
actually existing child nodes.
Signed-off-by: Kevin Wolf
---
block.c
The code already special-cased "node-name", which is currently the only
option passed in the QDict that isn't driver-specific. Generalise the
code to take all general block layer options into consideration.
Signed-off-by: Kevin Wolf
Reviewed-by: Eric Blake
Reviewed-by: Max Reitz
Reviewed-by: Al
This adds the cache mode options to the QDict, so that they can be
specified for child nodes (e.g. backing.cache.direct=off).
The cache modes are not removed from the flags at this point; instead,
options and flags are kept in sync. If the user specifies both flags and
options, the options take pr
This patch adds a QemuOpts for generic block layer options to
bdrv_reopen_prepare(). The only two options that currently exist
(node-name and driver) cannot be changed, so the only thing we do is
putting them right back into the QDict so that we check at the end that
they are indeed unchanged.
We
If the child was defined in the same context (-drive argument or
blockdev-add QMP command) as its parent, a reopen of the parent should
work the same and allow changing options of the child.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
Reviewed-by: Alberto Garcia
---
block.c | 12 +
On Fri, Dec 04, 2015 at 11:15:48AM +0100, Cornelia Huck wrote:
> On Fri, 4 Dec 2015 10:06:58 +0800
> Jason Wang wrote:
>
> > The problem is for pci: without this patch, guest may always see modern
> > bar is "disable-modern=false". But with this patch, on an old kernel
> > that does not support V
The next patch distinguishes options that were explicitly set and
options that were derived. bdrv_fill_option() added options of both
types: Options given by json: syntax should be counted as explicit, but
the rest is derived.
In preparation for the distinction, move json: parse to a separate
func
Specifying the cache mode for a driver without a medium is not a useful
thing to do: As long as there is no medium, the cache mode doesn't make
a difference, and once the 'change' command is used to insert a medium,
it ignores the old cache mode and makes the new medium use
cache=writethrough.
Lat
Options are not actually inherited from the parent node yet, but this
commit lays the grounds for doing so.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
block.c | 52 ---
include/block/block_int.h | 3 ++-
2 files changed, 3
On 12/04/2015 02:19 AM, Miao Yan wrote:
> Macro VMW_SHPRN(...) is already defined vmxnet3_debug.h,
> so remove the duplication
>
> Signed-off-by: Miao Yan
> ---
> hw/net/vmware_utils.h | 5 +
> 1 file changed, 1 insertion(+), 4 deletions(-)
Reviewed-by: Eric Blake
>
> diff --git a/hw/net
Just reopening the children (as block.c does now) is enough.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
Reviewed-by: Alberto Garcia
---
block/blkdebug.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/block/blkdebug.c b/block/blkdebug.c
index 48b0812..7132e2c 100644
--- a/bloc
bs->options doesn't only contain options that the user explicitly
requested, but also option that were derived from flags, the filename or
inherited from the parent node.
For reopen, it is important to know the difference because reopening the
parent can change inherited values in child nodes, but
'node-name' and 'driver' should not be changed during a reopen
operation. It is, however, valid to specify them with the same value as
they already had.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
tests/qemu-iotests/133 | 90 ++
tests/qem
This is a basic test for specifying cache modes for child nodes on the
command line. It doesn't take much time and works without O_DIRECT
support.
Signed-off-by: Kevin Wolf
Reviewed-by: Max Reitz
---
tests/qemu-iotests/051 | 10 +++-
tests/qemu-iotests/051.out | 60 +
This is doing a more complete test on setting cache modes both while
opening an image (i.e. in a -drive command line) and in reopen
situations. It checks that reopen can specify options for child nodes
and that cache modes are correctly inherited from parent nodes where
they are not specified.
Sig
> Hi
>
> We are in hard freeze. My understanding is that this are "optimizations" that
> can wait for 2.6:
> - my understanding from commit from message one and from quick look at
> the code is that this change is not needed for current users, is that
> correct?
> - we avoid a copy at the begi
On 12/03/2015 10:53 AM, Didier Pallard wrote:
Hi,
I recently did some stress tests of a vhost-user interface using an UDP
traffic generator. Traffic generator was connected to 2 physical ports
that are in turn connected to 2 virtio ports through a linux bridge, VM
(running linux) doing routing t
We made it unavailable in commit 1910913 because its use of
drive_get_next() instead of a property. Commit 5ec911c replaced
drive_get_next() and made the device available, but the property isn't
quite right, and the code dangerously ignores blk_attach_dev()
failure. Disable it again before the pr
On Fri, Dec 04, 2015 at 02:24:41PM +0100, Igor Mammedov wrote:
> On Thu, 3 Dec 2015 15:16:21 -0200
> Eduardo Habkost wrote:
>
> > On Thu, Dec 03, 2015 at 04:19:19PM +0100, Igor Mammedov wrote:
> > > On Wed, 2 Dec 2015 20:22:45 -0200
> > > Eduardo Habkost wrote:
> > >
> > > > This series remove
On Mon, 16 Nov 2015 21:23:07 +0800
shannon.z...@linaro.org wrote:
> From: Shannon Zhao
>
> Here GPIO pin 3 is used for Power Button, add _E03 in ACPI DSDT table.
>
> Signed-off-by: Shannon Zhao
> Signed-off-by: Shannon Zhao
> Tested-by: Wei Huang
> ---
> hw/arm/virt-acpi-build.c | 13 ++
> > There are some flaws in qemu_put_compression_data, this patch tries to
> > fix it. Now it can be used by other code.
> >
> > Signed-off-by: Liang Li
> > ---
> > migration/qemu-file.c | 10 +-
> > 1 file changed, 9 insertions(+), 1 deletion(-)
> >
> > diff --git a/migration/qemu-file.c
> On (Fri) 04 Dec 2015 [11:53:09], Liang Li wrote:
> > There are some flaws in qemu_put_compression_data, this patch tries to
> > fix it. Now it can be used by other code.
>
> Can you please write a better description here? What are the flaws?
> What is being fixed? What other users, and how is
On 12/02/2015 03:22 PM, Paolo Bonzini wrote:
On 30/11/2015 17:22, Andrey Smetanin wrote:
enum hv_message_type inside struct hv_message, hv_post_message
is not size portable. Replace enum by u32.
It's only non-portable inside structs. Okay to apply just these:
@@ -172,7 +174,7 @@ union hv_mes
On 04/12/2015 15:07, Markus Armbruster wrote:
> We made it unavailable in commit 1910913 because its use of
> drive_get_next() instead of a property. Commit 5ec911c replaced
> drive_get_next() and made the device available, but the property isn't
> quite right, and the code dangerously ignores b
On 04/12/2015 15:33, Denis V. Lunev wrote:
> On 12/02/2015 03:22 PM, Paolo Bonzini wrote:
>>
>> On 30/11/2015 17:22, Andrey Smetanin wrote:
>>> enum hv_message_type inside struct hv_message, hv_post_message
>>> is not size portable. Replace enum by u32.
>> It's only non-portable inside structs.
The Xen toolstack uses "vhd" to specify a disk in VHD format, however
the name of the driver in QEMU is "vpc". Replace "vhd" with "vpc", so
that QEMU can find the right driver to use for it.
Signed-off-by: Stefano Stabellini
diff --git a/hw/block/xen_disk.c b/hw/block/xen_disk.c
index 267d8a8..3
This would be useful in the next step when QMP version of this call will
be introduced.
Signed-off-by: Denis V. Lunev
Reviewed-by: Juan Quintela
CC: Amit Shah
CC: Markus Armbruster
CC: Eric Blake
---
migration/savevm.c | 38 +++---
1 file changed, 23 insertion
EFI based VM with pflash storage for NVRAM could not be snapshoted as
libvirt configures storage as 'raw' and writable. OK, this is a libvirt
problem.
Another problem is that libvirt can not detect this failure at all
as it uses HMP for this operation. This create snapshot/delete snapshot
sequence
Unfortunately load_vmstate has a return code (int) and this code is checked
in the other places. Thus we could not just rename it to qmp_loadvm as
returns void.
Signed-off-by: Denis V. Lunev
CC: Juan Quintela
CC: Amit Shah
CC: Markus Armbruster
CC: Eric Blake
---
migration/savevm.c | 12
'name' attribute is made mandatory in distinction with HMP command.
The patch also moves hmp_savevm implementation into hmp.c. This function
is just a simple wrapper now and does not have knowledge about
migration internals.
Signed-off-by: Denis V. Lunev
CC: Juan Quintela
CC: Amit Shah
CC: Mar
The patch also moves hmp_delvm implementation into hmp.c. This function
is just a simple wrapper now and does not have knowledge about
migration internals.
Signed-off-by: Denis V. Lunev
CC: Juan Quintela
CC: Amit Shah
CC: Markus Armbruster
CC: Eric Blake
---
hmp.c | 11 +
The patch adds Error ** parameter to load_vmstate call and fills error
inside. The caller after that properly reports error either through
monitor or via local stderr facility during VM start.
This helper will be useful too for qmp_loadvm implementation.
Signed-off-by: Denis V. Lunev
CC: Juan Qu
2015-12-04 22:20 GMT+09:00 Marc-André Lureau :
> Hi
>
> On Fri, Dec 4, 2015 at 4:52 AM, Tetsuya Mukawa wrote:
>> If virtio-net driver allocates memory in vishmem shared memory,
>
> s/vishmem/ivshmem
Thanks, I will fix it.
>
> How can virtio-net allocate memory in ivshmem memory bar?
>
> What's t
On Wed, Nov 18, 2015 at 10:20:14AM +0800, Huaitong Han wrote:
> Changes in v3:
> *Fix cpuid_7_0_ecx_feature_name error.
>
> Changes in v2:
> *Fix memcpy error for xsave state.
> *Fix TCG_7_0_ECX_FEATURES to 0.
> *Make subjects more readable.
>
> The protection-key feature provides an additional m
Paolo Bonzini writes:
> On 04/12/2015 15:07, Markus Armbruster wrote:
>> We made it unavailable in commit 1910913 because its use of
>> drive_get_next() instead of a property. Commit 5ec911c replaced
>> drive_get_next() and made the device available, but the property isn't
>> quite right, and th
target-i386/cpu.c:ext_save_area uses magic numbers for the xsave
area offets and sizes, and target-i386/kvm.c:kvm_{put,get}_xsave()
uses offset macros and bit manipulation to access the xsave area.
This series changes both to use C structs for those operations.
I still need to figure out a way to
This doesn't introduce any change in the code, as the offsets and
struct sizes match what was present in the table. This can be
validated by the QEMU_BUILD_BUG_ON lines on target-i386/cpu.h,
which ensures the struct sizes and offsets match the existing
values in ext_save_area.
Signed-off-by: Eduar
Add structs that define the layout of the xsave areas used by
Intel processors. Add some QEMU_BUILD_BUG_ON lines to ensure the
structs match the XSAVE_* macros in target-i386/kvm.c and the
offsets and sizes at target-i386/cpu.c:ext_save_areas.
Signed-off-by: Eduardo Habkost
---
Changes v1 -> v2:
Instead of using offset macros and bit operations in a uint32_t
array, use the X86XSaveArea struct to perform the loading/saving
operations in kvm_put_xsave() and kvm_get_xsave().
Signed-off-by: Eduardo Habkost
---
Changes v1 -> v2:
* Use uint8_t pointers when loading/saving xmm, ymmh, zmmh,
ke
On Thu, 3 Dec 2015, Ian Campbell wrote:
> diff --git a/include/hw/xen/xen_common.h b/include/hw/xen/xen_common.h
> index 2cadd4f..8fbaf07 100644
> --- a/include/hw/xen/xen_common.h
> +++ b/include/hw/xen/xen_common.h
> @@ -41,6 +41,7 @@ static inline void *xc_map_foreign_bulk(int xc_handle,
> uint
On Thu, 3 Dec 2015, Ian Campbell wrote:
> In Xen 4.7 we are refactoring parts libxenctrl into a number of
> separate libraries which will provide backward and forward API and ABI
> compatiblity.
>
> One such library will be libxenforeignmemory which provides access to
> privileged foreign mappings
From: Gabriel Somlo
Signed-off-by: Gabriel Somlo
---
lib/kobject.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/kobject.c b/lib/kobject.c
index 7cbccd2..90d1be6 100644
--- a/lib/kobject.c
+++ b/lib/kobject.c
@@ -861,6 +861,7 @@ struct kobject *kset_find_obj(struct kset *kset, const c
From: Gabriel Somlo
Remove fw_cfg hardware interface details from
Documentation/devicetree/bindings/arm/fw-cfg.txt,
and replace them with a pointer to the authoritative
documentation in the QEMU source tree.
Signed-off-by: Gabriel Somlo
Cc: Laszlo Ersek
Acked-by: Rob Herring
Reviewed-by: Lasz
From: Gabriel Somlo
Each fw_cfg entry of type "file" has an associated 56-char,
nul-terminated ASCII string which represents its name. While
the fw_cfg device doesn't itself impose any specific naming
convention, QEMU developers have traditionally used path name
semantics (i.e. "etc/acpi/rsdp") t
From: Gabriel Somlo
Make fw_cfg entries of type "file" available via sysfs. Entries
are listed under /sys/firmware/qemu_fw_cfg/by_key, in folders
named after each entry's selector key. Filename, selector value,
and size read-only attributes are included for each entry. Also,
a "raw" attribute all
1 - 100 of 148 matches
Mail list logo
