In command definition, 'default' is now parsed as a dict of default
values. Only optional parameters will have effect in generated code.
'str' and 'int' are supported, both need single quote in the schema. In
generated code, 'str' will be converted to g_strdup'ed pointer, 'int'
will be
Alexander Graf ag...@suse.de writes:
Am 15.04.2014 um 18:56 schrieb Markus Armbruster arm...@redhat.com:
Alexander Graf ag...@suse.de writes:
On 04/15/2014 04:00 PM, Markus Armbruster wrote:
Juan Quintela quint...@redhat.com writes:
Juan Quintela quint...@redhat.com wrote:
Hi
On Di, 2014-04-15 at 19:33 -0400, Ján Veselý wrote:
Hi,
I found some more time to work on this. However, I'm not sure I
understand the purpose of compat property:
I noticed that the only place it's set is in PC_COMPAT_1_3 (is this
what you meant by older devices?),
Older machine types,
Kevin O'Connor ke...@koconnor.net writes:
On Tue, Apr 15, 2014 at 10:29:26AM +0200, Gerd Hoffmann wrote:
Leave the old interface code basically as-is. type0 and type1
individual fields are passed like they are passed today. We don't
change to to pass full tables, and we don't extend that to
Hi,
Add void smbios_get_tables() as a separate function to generate the
entry point and aggregate smbios table, and then:
if machine_type 2.1 then
insert smbios_get_table() into fw_cfg (compat mode)
else
insert smbios_get_tables() blob + entry point (new
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
On Wed, Apr 16, 2014 at 2:16 AM, Andreas Färber afaer...@suse.de wrote:
Am 15.04.2014 04:21, schrieb Peter Crosthwaite:
So clients can set the top level id string.
Signed-off-by: Peter Crosthwaite peter.crosthwa...@xilinx.com
Anthony
Eduardo Habkost ehabk...@redhat.com writes:
Currently it is very easy to crash QEMU by issuing an object-add command
using an abstract class or a class that doesn't support
TYPE_USER_CREATABLE as parameter.
Example: with the following QMP command:
(QEMU) object-add qom-type=cpu id=foo
Amos Kong ak...@redhat.com writes:
QEMU crashed when I try to list device parameters, the driver name is
actually the available bus name.
# qemu -device virtio-pci-bus,?
# qemu -device virtio-bus,?
# qemu -device virtio-serial-bus,?
qdev-monitor.c:212:qdev_device_help: Object
Fam Zheng f...@redhat.com writes:
More often it is that bdrv_ioctl fails due to not supported by driver or
whatever reason, in this case we should be specific, because interface
too old is very confusing.
Signed-off-by: Fam Zheng f...@redhat.com
---
hw/scsi/scsi-disk.c | 9 +++--
1
Chen Gang gang.chen.5...@gmail.com writes:
In vl.c, at least, we can simplify the code below, so can let readers
read professional C code (especially for new readers, which often start
reading code at main function).
- Remove useless 'continue' in main().
- Eliminate a superfluous local
The 2108 chip supports MSI and MSI-X, so update the emulation
to support both chips.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c| 95 ++--
hw/scsi/mfi.h| 7
include/hw/pci/pci_ids.h | 1 +
3 files
MSI-X support has been fixed in qemu, so we can enable it again.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
index e6e1ffd..496bab8 100644
---
Some hardware instances do support MSI, so we should do likewise.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 49 +++--
trace-events | 5 -
2 files changed, 47 insertions(+), 7 deletions(-)
diff --git
Hi all,
here's an update to the megasas driver.
I've re-enabled MSI-X support and added a new emulation mode
'megasas-gen2' which emulates the MegaRAID SAS 2108 HBA.
The advantage here is that the original silicon supports both MSI-X and MSI,
so some drivers (most notably windows) will refuse to
The trace events already contain the function name, so the actual
message doesn't need to contain any of these informations.
Signed-off-by: Hannes Reinecke h...@suse.de
---
trace-events | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/trace-events
New drivers implement a LD_LIST_QUERY command, and due to a driver
issue no drives might be detected if this command isn't supported.
So add emulation for this command, too.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 17 +
hw/scsi/mfi.h | 9 +
To ease debugging we should be decoding
the register names.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 22 +++---
trace-events | 4 ++--
2 files changed, 21 insertions(+), 5 deletions(-)
diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
index
Signed-off-by: Hannes Reinecke h...@suse.de
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c66946f..f1d3f09 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -651,6 +651,12 @@ S: Supported
F: hw/block/nvme*
F: tests/nvme-test.c
+megasas
Am 16.04.2014 um 08:26 schrieb Markus Armbruster arm...@redhat.com:
Alexander Graf ag...@suse.de writes:
Am 15.04.2014 um 18:56 schrieb Markus Armbruster arm...@redhat.com:
Alexander Graf ag...@suse.de writes:
On 04/15/2014 04:00 PM, Markus Armbruster wrote:
Juan Quintela
Peter Crosthwaite peter.crosthwa...@xilinx.com writes:
Hi Markus,
This series introduces qemu_get_boot_opts(), in much the same way as
was done for qemu_get_machine_opts().
As usual, I have out-of-scope and out-of-tree usages :) But P3 does
clean up the one existing instance of the
* Rick Vernam (rtver...@hobi.com) wrote:
On Tuesday 15 April 2014 19:25:22 Rick Vernam wrote:
Looks like it's in Spice:
snip old backtrace without symbols
I'll see if I can build spice with debugging symbols and what not and write
back with findings. Are others have problems with Qemu 2.0
Hi Serge,
I'm running on pure amd64 too so the problem is not arch-specific.
The simplest way to recreate:
$ kvm -cdrom /usr/lib/memtest86+/memtest86+.iso -m 512
Just hold down control+alt and frantically toggle the monitor using the
'2' and '1'. Within a couple of seconds it hangs.
--
You
Hi, all
I provide host's memory to guest by remap_pfn_range host page to qemu, and when
guest access the page, host paniced.
host code:
static int my_mmap(struct file *filep, struct vm_area_struct *vma)
{
int ret;
unsigned long page;
if (vma-vm_end vma-vm_start)
return
The last version is here:
http://lists.nongnu.org/archive/html/qemu-devel/2014-04/msg00018.html
ChangLog:
Changes from v7 to v8:
1. add a patch to fix doc of dump-guest-memory
Qiao Nuohan (2):
HMP: fix doc of dump-guest-memory
HMP: support specifying dump format for dump-guest-memory
Signed-off-by: Qiao Nuohan qiaonuo...@cn.fujitsu.com
---
hmp-commands.hx | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/hmp-commands.hx b/hmp-commands.hx
index 0da8f28..ca5737b 100644
--- a/hmp-commands.hx
+++ b/hmp-commands.hx
@@ -1000,10 +1000,10 @@ ETEXI
Dumping guest memory is available to specify the dump format now. This patch
adds options '-z|-l|-s' to HMP command dump-guest-memory to specify dumping in
kdump-compression format, with zlib/lzo/snappy compression. And without these
options ELF format will be used.
The discussion about this
On Fri, Apr 04, 2014 at 03:36:38PM +0200, Igor Mammedov wrote:
initialize and map hotplug memory address space container
into guest's RAM address space.
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
hw/i386/pc.c | 19 +--
include/hw/i386/pc.h | 10 ++
On Tue, Apr 15, 2014 at 05:55:22PM +0200, Igor Mammedov wrote:
On Tue, 15 Apr 2014 14:37:01 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Mon, Apr 14, 2014 at 06:44:42PM +0200, Igor Mammedov wrote:
On Mon, 14 Apr 2014 15:25:01 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, Apr
Fix OOB access via malformed incoming_posn parameters
and check that requested memory is actually alloced.
Signed-off-by: Sebastian Krahmer krah...@suse.de
---
diff --git a/hw/misc/ivshmem.c b/hw/misc/ivshmem.c
index 8d144ba..f58356e 100644
--- a/hw/misc/ivshmem.c
+++ b/hw/misc/ivshmem.c
@@
Public bug reported:
The test case is in the attachment. To reproduce as following (I tried both GCC
and Clang):
$aarch64-linux-gnu-gcc qemu.c -o test
$./test
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction (core dumped)
In the test case, 3 intrinsics are
** Description changed:
The test case is in the attachment. To reproduce as following (I tried both
GCC and Clang):
$aarch64-linux-gnu-gcc qemu.c -o test
$./test
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction (core dumped)
-
In the test
I am trying to add smp support in octeon-mips by usnig QEM-1.0.1. My octeon
guest is not initializing secondary cores.
QEMU monitor show
(qemu) info cpus
* CPU #0: PC=0xc0031d04 thread_id=12661
CPU #1: PC=0xbfc00380 thread_id=12660
Can anyone have any idea about this issue?
--
Can you attach a statically linked test case binary, please?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1308381
Title:
illegal instructions for AArch64 ARMv8
Status in QEMU:
New
Bug
On 15.04.14 19:21, Tom Musta wrote:
Use MSR mnemonics from cpu.h instead of magic numbers for the
CPUPPCState.msr_mask
initialization.
There is one bit in the 401x2 (and subsequent) model that I could not find any
documentation for. It is open coded at little endian bit position 20:
On 15.04.14 17:32, Eric Auger wrote:
On 04/15/2014 04:55 PM, Alexander Graf wrote:
On 04/15/2014 04:00 PM, Markus Armbruster wrote:
Juan Quintela quint...@redhat.com writes:
Juan Quintela quint...@redhat.com wrote:
Hi
Please, send any topic that you are interested in covering.
Thanks,
On 15.04.14 07:06, Alexey Kardashevskiy wrote:
Currently migration fails if CPU version (PVR register) is different
even a bit. This check is performed at the very end of migration when
device states are sent. This is too late for management software and
we need to provide a way for the user to
Peter Maydell peter.mayd...@linaro.org writes:
Can you attach a statically linked test case binary, please?
I can reproduce with the source file. It looks like:
@@ -7553,12 +7555,9 @@ static void disas_simd_scalar_two_reg_misc(DisasContext
*s, uint32_t insn)
}
break;
On 16 April 2014 11:55, Alex Bennée alex.ben...@linaro.org wrote:
Peter Maydell peter.mayd...@linaro.org writes:
Can you attach a statically linked test case binary, please?
I can reproduce with the source file. It looks like:
@@ -7553,12 +7555,9 @@ static void
On 2014-04-16 11:59:58 +0100, Peter Maydell wrote:
On 16 April 2014 11:55, Alex Bennée alex.ben...@linaro.org wrote:
Peter Maydell peter.mayd...@linaro.org writes:
Can you attach a statically linked test case binary, please?
I can reproduce with the source file. It looks like:
@@
On 14.04.14 14:53, Alexey Kardashevskiy wrote:
This allows guests to have a different timebase origin from the host.
This is needed for migration, where a guest can migrate from one host
to another and the two hosts might have a different timebase origin.
However, the timebase seen by the
On 14.04.14 18:48, Cornelia Huck wrote:
Provide helper functions for enabling capabilities (on a vcpu and on a vm).
Reviewed-by: Thomas Huth th...@linux.vnet.ibm.com
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
include/sysemu/kvm.h |4
kvm-all.c| 33
On 14.04.14 18:48, Cornelia Huck wrote:
Make kvm_s390_enable_css_support() use new interface.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
What I was trying to indicate with the convert users comment last time
was to convert non-s390 users :). After all, ENABLE_CAP is a
On 14.04.14 18:48, Cornelia Huck wrote:
Register an I/O adapter interrupt source for when virtio-ccw devices start
using adapter interrupts.
Reviewed-by: Thomas Huth th...@linux.vnet.ibm.com
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
hw/intc/s390_flic.c | 59
The test for the U bit was incorrectly inverted in the scalar case of SQXTUN.
This doesn't affect the vector case as the U bit is used to select XTN(2).
Reported-by: Hao Liu hao@arm.com
Signed-off-by: Alex Bennée alex.ben...@linaro.org
---
target-arm/translate-a64.c | 2 +-
1 file changed, 1
On 14.04.14 18:48, Cornelia Huck wrote:
Make use of the new s390 adapter irq routing support to enable real
in-kernel irqfds for virtio-ccw with adapter interrupts.
Note that s390 doesn't provide the common KVM_CAP_IRQCHIP capability, but
rather needs KVM_CAP_S390_IRQCHIP to be enabled. This
On 14.04.14 18:48, Cornelia Huck wrote:
From: Christian Borntraeger borntrae...@de.ibm.com
We also need to sync guest breaking event address and program parameter
register for migration support.
Signed-off-by: Christian Borntraeger borntrae...@de.ibm.com
Reviewed-by: Jason J. Herne
On 16.04.2014 13:29, Alex Bennée wrote:
The test for the U bit was incorrectly inverted in the scalar case of SQXTUN.
This doesn't affect the vector case as the U bit is used to select XTN(2).
Reported-by: Hao Liu hao@arm.com
Signed-off-by: Alex Bennée alex.ben...@linaro.org
---
On 14.04.14 18:48, Cornelia Huck wrote:
Convert existing users of KVM_ENABLE_CAP to new helper.
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
Ah, you made the ppc patch separate. I would prefer if we had one patch
set that introduces the helper and converts every arch in follow-up
On 16.04.2014, at 13:22, Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck wrote:
Provide helper functions for enabling capabilities (on a vcpu and on a vm).
Reviewed-by: Thomas Huth th...@linux.vnet.ibm.com
Signed-off-by: Cornelia Huck cornelia.h...@de.ibm.com
---
@pmaydell: yeah vector is unaffected as U is used to select another
opcode.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1308381
Title:
illegal instructions for AArch64 ARMv8
Status in QEMU:
Fix identified
** Changed in: qemu
Assignee: (unassigned) = Alex Bennée (ajbennee)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1308381
Title:
illegal instructions for AArch64 ARMv8
Status
I've sent this patch to the mailing list but it fixes the attached test
case and has been tested with risu patterns.
** Patch added: fix
https://bugs.launchpad.net/qemu/+bug/1308381/+attachment/4085353/+files/0001-target-arm-A64-fix-unallocated-test-of-scalar-SQXTUN.patch
--
You received
On 16 April 2014 12:29, Alex Bennée alex.ben...@linaro.org wrote:
The test for the U bit was incorrectly inverted in the scalar case of SQXTUN.
This doesn't affect the vector case as the U bit is used to select XTN(2).
Reported-by: Hao Liu hao@arm.com
Signed-off-by: Alex Bennée
On 16.04.14 09:16, Hannes Reinecke wrote:
MSI-X support has been fixed in qemu, so we can enable it again.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 20 ++--
1 file changed, 6 insertions(+), 14 deletions(-)
diff --git a/hw/scsi/megasas.c
On 16.04.14 09:17, Hannes Reinecke wrote:
New drivers implement a LD_LIST_QUERY command, and due to a driver
issue no drives might be detected if this command isn't supported.
So add emulation for this command, too.
Signed-off-by: Hannes Reinecke h...@suse.de
Should this go into stable?
On 16.04.14 09:16, Hannes Reinecke wrote:
Hi all,
here's an update to the megasas driver.
I've re-enabled MSI-X support and added a new emulation mode
'megasas-gen2' which emulates the MegaRAID SAS 2108 HBA.
The advantage here is that the original silicon supports both MSI-X and MSI,
so some
On 04/16/2014 01:45 PM, Alexander Graf wrote:
On 16.04.14 09:17, Hannes Reinecke wrote:
New drivers implement a LD_LIST_QUERY command, and due to a driver
issue no drives might be detected if this command isn't supported.
So add emulation for this command, too.
Signed-off-by: Hannes
On 16.04.14 13:47, Hannes Reinecke wrote:
On 04/16/2014 01:45 PM, Alexander Graf wrote:
On 16.04.14 09:17, Hannes Reinecke wrote:
New drivers implement a LD_LIST_QUERY command, and due to a driver
issue no drives might be detected if this command isn't supported.
So add emulation for this
On 04/16/2014 01:43 PM, Alexander Graf wrote:
On 16.04.14 09:16, Hannes Reinecke wrote:
MSI-X support has been fixed in qemu, so we can enable it again.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 20 ++--
1 file changed, 6 insertions(+), 14
On 16.04.14 13:49, Hannes Reinecke wrote:
On 04/16/2014 01:43 PM, Alexander Graf wrote:
On 16.04.14 09:16, Hannes Reinecke wrote:
MSI-X support has been fixed in qemu, so we can enable it again.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 20 ++--
On Wed, 16 Apr 2014 13:38:27 +0200
Alexander Graf ag...@suse.de wrote:
On 16.04.2014, at 13:22, Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck wrote:
Provide helper functions for enabling capabilities (on a vcpu and on a vm).
Reviewed-by: Thomas Huth
On Fri, Apr 11, 2014 at 11:14:00AM +0200, Igor Mammedov wrote:
On Mon, 7 Apr 2014 18:14:51 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Apr 07, 2014 at 04:32:16PM +0200, Igor Mammedov wrote:
On Mon, 7 Apr 2014 13:23:54 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Apr 16, 2014 3:07 AM, Dr. David Alan Gilbert dgilb...@redhat.com
wrote:
* Rick Vernam (rtver...@hobi.com) wrote:
On Tuesday 15 April 2014 19:25:22 Rick Vernam wrote:
Looks like it's in Spice:
snip old backtrace without symbols
I'll see if I can build spice with debugging symbols
On 15.04.14 04:21, Peter Crosthwaite wrote:
Add a sysbus device consisting of a single ram. This allows for
instantiation of RAM just like any other device. There are a number
of good reasons to want to do this this:
1: Consistency. RAM is not that special where board level files should
have
On Di, 2014-04-15 at 20:47 -0400, Kevin O'Connor wrote:
On Tue, Apr 15, 2014 at 10:29:26AM +0200, Gerd Hoffmann wrote:
Leave the old interface code basically as-is. type0 and type1
individual fields are passed like they are passed today. We don't
change to to pass full tables, and we
Am 15.04.2014 um 16:55 hat Shehbaz Jaffer geschrieben:
Thankyou for your reply. I do not face the error using qemu.1.7.1 version.
1 quick question:
I want to create a qcow2 image file after my VM has completed booting; i.e.,
when I boot from this new snapshot, I should directly get to my
Kevin Wolf (3):
block: Fix nb_sectors check in bdrv_check_byte_request()
block: Limit size to INT_MAX in bdrv_check_byte_request()
block: Catch integer overflow in bdrv_rw_co()
block.c| 10 +-
tests/qemu-iotests/084.out | 5 +
2 files changed, 10
Commit 8f4754ed intended to protect against integer overflow bugs in
block drivers by making sure that a single request that is passed to
drivers is no longer than INT_MAX bytes.
However, meanwhile there are some callers that don't use that code path
any more but call bdrv_check_byte_request()
nb_sectors is signed, check for negative values.
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block.c b/block.c
index 75c3948..8be40bb 100644
--- a/block.c
+++ b/block.c
@@ -2609,7 +2609,7 @@ static int
Insanely large requests could cause an integer overflow in
bdrv_rw_co() while converting sectors to bytes. This patch catches the
problem and returns an error (if we hadn't overflown the integer here,
bdrv_check_byte_request() would have rejected the request, so we're not
breaking anything that
Signed-off-by: Kevin Wolf kw...@redhat.com
---
block.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/block.c b/block.c
index d268ece..8510ba2 100644
--- a/block.c
+++ b/block.c
@@ -2757,10 +2757,16 @@ int bdrv_write_zeroes(BlockDriverState *bs, int64_t
sector_num,
On 04/11/2014 03:34 AM, Kim Phillips wrote:
On Wed, 9 Apr 2014 16:33:07 +0100
Eric Auger eric.au...@linaro.org wrote:
This work is inspired of PCI INTx. The code was prepared to support
multiple IRQs but this was not tested at that stage. Similarly to what
is done on PCI, the device
Am 16.04.2014 09:16, schrieb Hannes Reinecke:
The 2108 chip supports MSI and MSI-X, so update the emulation
to support both chips.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c| 95
++--
hw/scsi/mfi.h|
hi,all
1.
what is the differences between file and block disk?
which is better?
it seems that qemu always use pread and pwrite , does not care about the type
of vm's disk. am i right?
thanks
Am 16.04.2014 09:16, schrieb Hannes Reinecke:
MSI-X support has been fixed in qemu, so we can enable it again.
QEMU fwiw
Signed-off-by: Hannes Reinecke h...@suse.de
We had discussed enabling MSI-X before, and what I am missing here is a
change to the VMStateDescription. As long as no
On Wed, 16 Apr 2014 15:02:40 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Fri, Apr 11, 2014 at 11:14:00AM +0200, Igor Mammedov wrote:
On Mon, 7 Apr 2014 18:14:51 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Mon, Apr 07, 2014 at 04:32:16PM +0200, Igor Mammedov wrote:
On
Add remove_boot_device_path() function to remove bootindex when hot-unplug
a device. This patch fixed virtio-blk/virtio-net/scsi-disk/scsi-generic device.
So it has fixed bug1086603, ref:
https://bugzilla.redhat.com/show_bug.cgi?id=1086603
Make some changes based on Andreas's good suggestion.
Seems there is a bug in qemu where the APIC version is being checked as
value 3. However, it should be 1.
static uint32_t apic_mem_readl(void *opaque, hwaddr addr)
{
...
switch(index) {
case 0x03: /* version */
val = 0x11 | ((APIC_LVT_NB - 1) 16); /* version 0x11 */
Am 02.09.2013 13:31, schrieb Michael S. Tsirkin:
On Mon, Jul 29, 2013 at 02:27:01AM +0200, Andreas Färber wrote:
Use it conditional on msix_present() and drop msix_{save,load}() calls
following pci_device_{save,load}().
This reorders the msix_save() and msix_unuse_all_vectors() calls for
hi,all
libvirt supply default, none, writethrough, writeback, directsync,
unsafe disk cache options
1.
as for qemu, how qemu uses those options? and what are the differences?
better tell me where are the codes corresponding to those options?
2.
after a long time of running , it seems
On Wed, 16 Apr 2014 16:59:25 +0800
Hu Tao hu...@cn.fujitsu.com wrote:
On Fri, Apr 04, 2014 at 03:36:38PM +0200, Igor Mammedov wrote:
initialize and map hotplug memory address space container
into guest's RAM address space.
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
On Wed, 16 Apr 2014 13:58:31 +0200
Cornelia Huck cornelia.h...@de.ibm.com wrote:
On Wed, 16 Apr 2014 13:38:27 +0200
Alexander Graf ag...@suse.de wrote:
On 16.04.2014, at 13:22, Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck wrote:
Provide helper
On 16.04.14 16:25, Cornelia Huck wrote:
On Wed, 16 Apr 2014 13:58:31 +0200
Cornelia Huck cornelia.h...@de.ibm.com wrote:
On Wed, 16 Apr 2014 13:38:27 +0200
Alexander Graf ag...@suse.de wrote:
On 16.04.2014, at 13:22, Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck
On Wed, 16 Apr 2014 16:26:30 +0200
Alexander Graf ag...@suse.de wrote:
On 16.04.14 16:25, Cornelia Huck wrote:
On Wed, 16 Apr 2014 13:58:31 +0200
Cornelia Huck cornelia.h...@de.ibm.com wrote:
On Wed, 16 Apr 2014 13:38:27 +0200
Alexander Graf ag...@suse.de wrote:
On 16.04.2014, at
On 15/04/14 14:33, Egger, Christoph wrote:
On 15.04.14 10:33, Roger Pau Monne wrote:
ENODATA doesn't exist on FreeBSD, so ENODATA errors returned by the
hypervisor are translated to ENOENT.
Also, the error code is returned in errno if the call returns -1, so
compare the error code with the
On Wed, 16 Apr 2014 13:25:49 +0200
Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck wrote:
Register an I/O adapter interrupt source for when virtio-ccw devices start
using adapter interrupts.
Reviewed-by: Thomas Huth th...@linux.vnet.ibm.com
Signed-off-by:
Am 12.04.2014 um 20:57 hat Max Reitz geschrieben:
qemu-img should use QMP commands whenever possible in order to ensure
feature completeness of both online and offline image operations. As
qemu-img itself has no access to QMP (since this would basically require
just everything being linked
Am 12.04.2014 um 20:57 hat Max Reitz geschrieben:
Implement block_job_complete_sync() by doing the exact same thing as
block_job_cancel_sync() does, only with calling block_job_complete()
instead of block_job_cancel().
Signed-off-by: Max Reitz mre...@redhat.com
---
blockjob.c
On 16.04.14 16:38, Cornelia Huck wrote:
On Wed, 16 Apr 2014 13:25:49 +0200
Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck wrote:
Register an I/O adapter interrupt source for when virtio-ccw devices start
using adapter interrupts.
Reviewed-by: Thomas Huth
Newer firmware implement a LD_LIST_QUERY command, and due to a driver
issue no drives might be detected if this command isn't supported.
So add emulation for this command, too.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 17 +
Hi all,
here is now the second iteration of my megasas update.
Changes to the previous version:
- Keep original emulation backwards-compatible by not changing
defaults and keeping the original version number
- Save MSIX vmstate
- Reshuffle patches
- Add different defaults for megasas and
Some hardware instances do support MSI, so we should do likewise.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 49 +++--
trace-events | 5 -
2 files changed, 47 insertions(+), 7 deletions(-)
diff --git
MSI-X support has been fixed in qemu, so we can enable it again.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 19 ++-
1 file changed, 6 insertions(+), 13 deletions(-)
diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
index 1781525..df45286 100644
---
On Wed, 16 Apr 2014 13:29:05 +0200
Alexander Graf ag...@suse.de wrote:
On 14.04.14 18:48, Cornelia Huck wrote:
Make use of the new s390 adapter irq routing support to enable real
in-kernel irqfds for virtio-ccw with adapter interrupts.
Note that s390 doesn't provide the common
The 2108 chip supports MSI and MSI-X, so update the emulation
to support both chips.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c| 118 ++-
hw/scsi/mfi.h| 7 +++
include/hw/pci/pci_ids.h | 1 +
3 files
The trace events already contain the function name, so the actual
message doesn't need to contain any of these informations.
Signed-off-by: Hannes Reinecke h...@suse.de
---
trace-events | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git
Signed-off-by: Hannes Reinecke h...@suse.de
---
MAINTAINERS | 6 ++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index c66946f..f1d3f09 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -651,6 +651,12 @@ S: Supported
F: hw/block/nvme*
F: tests/nvme-test.c
+megasas
To ease debugging we should be decoding
the register names.
Signed-off-by: Hannes Reinecke h...@suse.de
---
hw/scsi/megasas.c | 22 +++---
trace-events | 4 ++--
2 files changed, 21 insertions(+), 5 deletions(-)
diff --git a/hw/scsi/megasas.c b/hw/scsi/megasas.c
index
On Thu, Apr 10, 2014 at 09:55:20PM +0300, Marcel Apfelbaum wrote:
If a pci-2-pci bridge supports hot-plug functionality but there are no devices
connected to it, reserve IO/mem in order to be able to attach devices
later. Do not waste space, use minimum allowed.
Thanks - I have committed this
Am 12.04.2014 um 20:57 hat Max Reitz geschrieben:
Implement progress output for the commit command by querying the
progress of the block job.
Signed-off-by: Max Reitz mre...@redhat.com
---
qemu-img-cmds.hx | 4 ++--
qemu-img.c | 44 ++--
1 - 100 of 209 matches
Mail list logo
