Hi!
Found 2 problems while I was debugging qemu/ppc64-softmmu/qemu-system-ppc64.exe
WindowsXP SP3 Pro, 32bit, i686-pc-mingw32-gcc (GCC) 4.5.2.
1. The size of the following is 7 bytes on linux and 8 bytes on Windows:
struct {
uint32_t hi;
uint64_t child;
uint64_t parent;
uint64_t
Will merge Igors corrections into v6
Regards,
Peter
On Wed, Jul 18, 2012 at 1:04 AM, Peter Maydell peter.mayd...@linaro.org wrote:
On 17 July 2012 15:58, Igor Mitsyanko i.mitsya...@samsung.com wrote:
On 07/17/2012 05:37 PM, Peter Maydell wrote:
I would suggest two functions:
int
On 18 July 2012 07:30, Alexey Kardashevskiy a...@ozlabs.ru wrote:
1. The size of the following is 7 bytes on linux and 8 bytes on Windows:
struct {
uint32_t hi;
uint64_t child;
uint64_t parent;
uint64_t size;
} __attribute__((packed)) ranges[];
The structure is used
By default mingw-gcc is trying to pack structures the way to
preserve binary compatibility with MS Visual C what leads to
incorrect and unexpected padding in the PCI bus ranges property of
the sPAPR PHB.
The patch replaces __attribute__((packed)) with more strict QEMU_PACKED
which actually is
Ping again?
On 09/07/12 13:10, Alexey Kardashevskiy wrote:
Ping?
On 02/07/12 05:48, Alexey Kardashevskiy wrote:
QEMU uses IO handlers to run select() in the main loop. The handlers list is
managed by qemu_set_fd_handler() helper which works fine when called from
the main thread as it is
On 07/17/2012 08:58 PM, Stefano Stabellini wrote:
On Tue, 17 Jul 2012, Avi Kivity wrote:
On 07/17/2012 04:30 PM, Anthony PERARD wrote:
This command is used during a migration of a guest under Xen. It calls
memory_global_dirty_log_start or memory_global_dirty_log_stop according to
the
On 07/17/2012 09:36 PM, Stefano Stabellini wrote:
On Tue, 17 Jul 2012, Avi Kivity wrote:
On 07/17/2012 04:59 PM, Anthony PERARD wrote:
This is pretty ugly. An alternative is to set up a periodic bitmap scan
that looks at the qemu dirty bitmap and calls xen_modified_memory() for
dirty
Hi, following is API draft, prototypes were taken from qemu/block.h,
and the API prefix is changed frpm bdrv to qbdrvs, to declare related
object is BlockDriverState, not BlockDriver. One issue here is it may
require include block_int.h, which is not LGPL2 licensed yet.
API format is kept
On Tue, Jul 17, 2012 at 8:51 PM, Harsh Bora ha...@linux.vnet.ibm.com wrote:
On 07/17/2012 08:53 PM, Stefan Hajnoczi wrote:
On Tue, Jul 3, 2012 at 10:20 AM, Harsh Prateek Bora
ha...@linux.vnet.ibm.com wrote:
Existing simpletrace backend allows to trace at max 6 args and does not
support
On Tue, Jul 17, 2012 at 8:01 PM, Harsh Bora ha...@linux.vnet.ibm.com wrote:
On 07/17/2012 08:51 PM, Stefan Hajnoczi wrote:
On Tue, Jul 3, 2012 at 10:20 AM, Harsh Prateek Bora
ha...@linux.vnet.ibm.com wrote:
Existing simpletrace backend allows to trace at max 6 args and does not
support
On Tue, Jul 17, 2012 at 9:08 PM, Harsh Bora ha...@linux.vnet.ibm.com wrote:
On 07/18/2012 12:31 AM, Harsh Bora wrote:
On 07/17/2012 08:51 PM, Stefan Hajnoczi wrote:
On Tue, Jul 3, 2012 at 10:20 AM, Harsh Prateek Bora
ha...@linux.vnet.ibm.com wrote:
@@ -75,16 +96,31 @@ static char
Il 18/07/2012 10:51, Wenchao Xia ha scritto:
Hi, following is API draft, prototypes were taken from qemu/block.h,
and the API prefix is changed frpm bdrv to qbdrvs, to declare related
object is BlockDriverState, not BlockDriver. One issue here is it may
require include block_int.h, which is
On 2012-07-18 03:54, Wen Congyang wrote:
At 07/06/2012 07:05 PM, Jan Kiszka Wrote:
On 2012-07-06 11:41, Wen Congyang wrote:
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_PORT when it is panciked. This patch introduces a new qom
device kvm_pv_ioport to
On 2012-07-18 11:19, Jan Kiszka wrote:
On 2012-07-18 03:54, Wen Congyang wrote:
At 07/06/2012 07:05 PM, Jan Kiszka Wrote:
On 2012-07-06 11:41, Wen Congyang wrote:
If the target is x86/x86_64, the guest's kernel will write 0x01 to the
port KVM_PV_PORT when it is panciked. This patch introduces
On 12 March 2012 20:12, Stefan Weil s...@weilnetz.de wrote:
We also need more resources for technical maintenance of the
QEMU infrastructure. For example, the official mirror of the
QEMU git repository (https://github.com/qemu/QEMU) is several
months behind,
On 2012-07-18 10:44, Mao, Junjie wrote:
Hi, Avi
Any comments on this patch? :)
Always include qemu-devel when your are changing QEMU, qemu-kvm is just
staging for the latter. This patch can actually go into upstream
directly, maybe even via qemu-trivial as it just makes that flag selectable.
On Wed, Jul 18, 2012 at 9:51 AM, Wenchao Xia xiaw...@linux.vnet.ibm.com wrote:
/* sync access */
int qbdrvs_read(BlockDriverState *bs, int64_t sector_num,
uint8_t *buf, int nb_sectors);
int qbdrvs_write(BlockDriverState *bs, int64_t sector_num,
const uint8_t *buf,
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable number of args including strings.
Sample trace:
v9fs_version 0.000 tag=0x id=0x64 msize=0x2000
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable number of args including strings.
Sample trace with strings:
v9fs_version 0.000 tag=0x id=0x64 msize=0x2000
Support new tracelog format for multiple arguments and strings.
Signed-off-by: Harsh Prateek Bora ha...@linux.vnet.ibm.com
---
scripts/simpletrace.py | 116 +++-
1 file changed, 75 insertions(+), 41 deletions(-)
diff --git a/scripts/simpletrace.py
Going forward with simpletrace v2 variable size trace records, we cannot
have a generic function to print trace event info and therefore this
interface becomes invalid.
As per Stefan Hajnoczi:
This command is only available from the human monitor. It's not very
useful because it historically
Rather than hardcoding the list of architectures in the kernel
header update script, just import headers for every architecture
which supports KVM (with a blacklist exception for ia64 which
has KVM headers but is dead). This reduces the number of QEMU
files which need to be updated to add support
On 2012-07-18 12:11, Peter Maydell wrote:
Rather than hardcoding the list of architectures in the kernel
header update script, just import headers for every architecture
which supports KVM (with a blacklist exception for ia64 which
has KVM headers but is dead). This reduces the number of QEMU
Am 16.07.2012 17:25, schrieb Peter Maydell:
Add a new QError QERR_PROPERTY_SET_AFTER_REALIZE for attempts
to set a QOM or qdev property after the object/device has been
realized. This allows a slightly more informative diagnostic
than the previous permission denied message.
Signed-off-by:
n 18 July 2012 11:20, Andreas Färber afaer...@suse.de wrote:
Am 16.07.2012 17:25, schrieb Peter Maydell:
Add a new QError QERR_PROPERTY_SET_AFTER_REALIZE for attempts
to set a QOM or qdev property after the object/device has been
realized. This allows a slightly more informative diagnostic
Whether to provide sync and/or async access is a key question.
Indeed.
Synchronous APIs are great for writing dedicated tools like dd, cp,
convert, etc.
Asynchronous APIs are essential for integrating image file I/O into
event-driven programs like libvirt. Here, the ability to do other
It literally does the following:
1. POWERPC IOMMU support (the kernel counterpart is required)
2. The patch assumes that IOAPIC calls are going to be replaced
with something generic.
3. Added sPAPRVFIOData (hw/spapr_iommu_vfio.h) which describes
the interface between VFIO and sPAPR IOMMU.
4.
The code creating the symlink from linux-headers/asm to the
architecture specific linux-headers/asm-$arch directory was
implicitly hardcoding a list of KVM supporting architectures.
Add a default case for the common Linux architecture name and
QEMU CPU name match case, so future architectures will
Peter Maydell peter.mayd...@linaro.org writes:
n 18 July 2012 11:20, Andreas Färber afaer...@suse.de wrote:
Am 16.07.2012 17:25, schrieb Peter Maydell:
Add a new QError QERR_PROPERTY_SET_AFTER_REALIZE for attempts
to set a QOM or qdev property after the object/device has been
realized. This
On 18 July 2012 12:19, Markus Armbruster arm...@redhat.com wrote:
Peter Maydell peter.mayd...@linaro.org writes:
n 18 July 2012 11:20, Andreas Färber afaer...@suse.de wrote:
Am 16.07.2012 17:25, schrieb Peter Maydell:
Add a new QError QERR_PROPERTY_SET_AFTER_REALIZE for attempts
to set a QOM
On 18 July 2012 12:36, Peter Maydell peter.mayd...@linaro.org wrote:
That's interesting but I'm not sure how it's relevant. We already
have QERR_PROPERTY values just this new one, so I don't see why
this is any worse than the ones we have.
just like.
-- PMM
On Mon, Jul 02, 2012 at 05:48:16AM +1000, Alexey Kardashevskiy wrote:
Subject: Re: [PATCH] eventfd: making it rhread safe
typo in the subject
QEMU uses IO handlers to run select() in the main loop. The handlers list is
managed by qemu_set_fd_handler() helper which works fine when called from
Peter Maydell peter.mayd...@linaro.org writes:
On 18 July 2012 12:19, Markus Armbruster arm...@redhat.com wrote:
Peter Maydell peter.mayd...@linaro.org writes:
n 18 July 2012 11:20, Andreas Färber afaer...@suse.de wrote:
Am 16.07.2012 17:25, schrieb Peter Maydell:
Add a new QError
QEMU uses IO handlers to run select() in the main loop.
The handlers list is managed by qemu_set_fd_handler() helper
which works fine when called from the main thread as it is
called not when select() is waiting.
However IO handlers list can be changed in the thread other than
the main one doing
On Monday 16 July 2012 01:26:50 Stefan Weil wrote:
Am 15.07.2012 23:54, schrieb Mike Frysinger:
On Sunday 15 July 2012 15:34:33 Stefan Weil wrote:
Am 15.07.2012 22:25, schrieb Mike Frysinger:
This file uses the define HOST_LONG_BITS, but doesn't explicitly
include qemu-common.h for it
On Monday 16 July 2012 11:58:55 Stefan Weil wrote:
Am 16.07.2012 17:39, schrieb Eric Blake:
On 07/15/2012 01:54 PM, Stefan Weil wrote:
Am 15.07.2012 22:26, schrieb Mike Frysinger:
We should not quote the PKG_CONFIG setting as this deviates from the
canonical upstream behavior that gets
On Wed, Jul 18, 2012 at 10:08:53PM +1000, Alexey Kardashevskiy wrote:
QEMU uses IO handlers to run select() in the main loop.
The handlers list is managed by qemu_set_fd_handler() helper
which works fine when called from the main thread as it is
called not when select() is waiting.
when
On Mon, Jul 16, 2012 at 11:24 PM, Peter Maydell
peter.mayd...@linaro.org wrote:
Make the RAM size in arm_boot_info a uint64_t so it can express
the larger RAM sizes that may be seen in LPAE systems.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Peter A. G. Crosthwaite
On Mon, Jul 16, 2012 at 11:24 PM, Peter Maydell
peter.mayd...@linaro.org wrote:
The legacy ATAGS format for passing information to the kernel only
allows RAM sizes which fit in 32 bits; enforce this restriction
rather than silently doing something weird.
Signed-off-by: Peter Maydell
On Mon, Jul 16, 2012 at 11:24 PM, Peter Maydell
peter.mayd...@linaro.org wrote:
Add support for reading device tree properties (both generic
and single-cell ones) to QEMU's convenience wrapper layer.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
Reviewed-by: Peter A. G. Crosthwaite
On Thu, Jun 21, 2012 at 09:39:10PM +1000, Alexey Kardashevskiy wrote:
Added (msi|msix)_set_message() functions.
Currently msi_notify()/msix_notify() write to these vectors to
signal the guest about an interrupt so the correct values have to
written there by the guest or QEMU.
For example,
On Wed, Jul 18, 2012 at 06:42:24AM -0400, Paolo Bonzini wrote:
Synchronous APIs are great for writing dedicated tools like dd, cp,
convert, etc.
Asynchronous APIs are essential for integrating image file I/O into
event-driven programs like libvirt. Here, the ability to do other
QEMU uses IO handlers to run select() in the main loop.
The handlers list is managed by qemu_set_fd_handler() helper
which works fine when called from the main thread as it is
called when select() is not waiting.
However IO handlers list can be changed in the thread other than
the main one doing
On 12/07/12 23:09, Luiz Capitulino wrote:
Hi Luiz,
On Thu, 5 Jul 2012 20:48:44 +0800
Amos Kongak...@redhat.com wrote:
Convert 'sendkey' to use QAPI. do_sendkey() depends on some
variables/functions in monitor.c, so reserve qmp_sendkey()
to monitor.c
key_defs[] in console.h is the
On 18/07/12 22:22, Michael S. Tsirkin wrote:
On Wed, Jul 18, 2012 at 10:08:53PM +1000, Alexey Kardashevskiy wrote:
QEMU uses IO handlers to run select() in the main loop.
The handlers list is managed by qemu_set_fd_handler() helper
which works fine when called from the main thread as it is
On Wed, 18 Jul 2012 13:59:06 +0200
Markus Armbruster arm...@redhat.com wrote:
Peter Maydell peter.mayd...@linaro.org writes:
On 18 July 2012 12:19, Markus Armbruster arm...@redhat.com wrote:
Peter Maydell peter.mayd...@linaro.org writes:
n 18 July 2012 11:20, Andreas Färber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 18.07.2012 14:13, schrieb Mike Frysinger:
On Monday 16 July 2012 01:26:50 Stefan Weil wrote:
Am 15.07.2012 23:54, schrieb Mike Frysinger:
On Sunday 15 July 2012 15:34:33 Stefan Weil wrote:
Am 15.07.2012 22:25, schrieb Mike Frysinger:
This file
On 18/07/12 22:43, Michael S. Tsirkin wrote:
On Thu, Jun 21, 2012 at 09:39:10PM +1000, Alexey Kardashevskiy wrote:
Added (msi|msix)_set_message() functions.
Currently msi_notify()/msix_notify() write to these vectors to
signal the guest about an interrupt so the correct values have to
This patch separates qemu-nbd's options in logical groups, thus making
the help message easier to read.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
qemu-nbd.c | 33 ++---
1 file changed, 22 insertions(+), 11 deletions(-)
diff --git a/qemu-nbd.c
Two simple patches that let qemu-nbd use native AIO and --cache=unsafe
mode.
Paolo Bonzini (2):
qemu-nbd: reorganize help message
qemu-nbd: add --cache and --aio options
qemu-nbd.c | 75 +---
1 file changed, 62 insertions(+), 13
Add two options to tune the I/O implementation of qemu-nbd, matching
the possibilities given by the QEMU -drive option.
Signed-off-by: Paolo Bonzini pbonz...@redhat.com
---
qemu-nbd.c | 42 --
1 file changed, 40 insertions(+), 2 deletions(-)
diff --git
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Wanpeng Li liw...@linux.vnet.ibm.com
---
hw/pci_host.c | 26 ++
hw/pci_host.h |5 +
2 files changed, 31 insertions(+), 0 deletions(-)
diff
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Wanpeng Li liw...@linux.vnet.ibm.com
---
memory.c | 94 ++
memory.h |8 +
2 files changed, 78
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
The HPET usually sits on the LPC bus (which replaces ISA in modern systems).
It's sometimes a dedicated chip but can certain co-exist in a Super IO chip.
I think in terms of where it would live in this hypothetical device model,
putting it
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
The big picture about the patch is shown as follows:
1) pc_init creates an I440FX, any bus devices (ISA serial port, PCI
vga and nics, etc.), sets properties appropriately, and realizes the
devices.
2) I440FX is-a PCIHost, has-a I440FX-PMC,
qemu-img not only suports k/K/M/G/T/b, but also supports m/g/t/B. So correct
it in help message.
Also use the same parser in parse_option_size function.
Signed-off-by: Dong Xu Wang wdon...@linux.vnet.ibm.com
CC: riegama...@gmail.com
---
v1-v2: also correct error reporting.
v2-v3: use the same
Am 18.07.2012 15:23, schrieb Dong Xu Wang:
qemu-img not only suports k/K/M/G/T/b, but also supports m/g/t/B. So correct
it in help message.
Also use the same parser in parse_option_size function.
This is not what the patch does. It uses a parser that seems slightly
more compatible with
The current command line I'm using something such as:
$ /usr/local/bin/qemu-system-x86_64 -name f16 -M pc_q35 -m 1G -smp 4
-hda ./f16.img --enable-kvm -bios path/q35-seabios/out/bios.bin
-acpitable file=path/q35-seabios/out/q35-acpi-dsdt.aml -monitor stdio
So it might be nice to avoid
[CCing ML]
This series aggressively refactors the PC machine initialization to be more
modelled and less ad-hoc. The highlights of this series are:
1) Things like -m and -bios-name are now device model properties
2) The i440fx and piix3 are now modelled in a thorough fashion
3) Most of the
On 07/18/2012 07:23 AM, Dong Xu Wang wrote:
qemu-img not only suports k/K/M/G/T/b, but also supports m/g/t/B. So correct
it in help message.
+++ b/qemu-img.c
@@ -69,8 +69,9 @@ static void help(void)
options are: 'none', 'writeback' (default, except for
convert),
On 07/17/12 21:12, Michael Roth wrote:
On Tue, Jul 17, 2012 at 01:33:32PM -0500, Anthony Liguori wrote:
Let's stop screwing up releases by having a script do the work that Anthony's
fat fingers can't seem to get right.
Cc: Michael Roth mdr...@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori
On Wed, 18 Jul 2012 20:56:54 +0800
Amos Kong ak...@redhat.com wrote:
+} KeyDef;
+
+static const KeyDef key_defs[] = {
We can't have an array defined in a header file because it will be defined
in
each .c file that includes it.
Please, define it in input.c (along with
Am 18.07.2012 10:51, schrieb Wenchao Xia:
Hi, following is API draft, prototypes were taken from qemu/block.h,
and the API prefix is changed frpm bdrv to qbdrvs, to declare related
object is BlockDriverState, not BlockDriver. [...]
So let the bikeshedding begin: ;)
What about qbds_ prefix
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Wanpeng Li liw...@linux.vnet.ibm.com
---
hw/i386/Makefile.objs |1 -
hw/pc.c | 753 +++--
hw/pc.h |
Gerd Hoffmann kra...@redhat.com writes:
On 07/17/12 21:12, Michael Roth wrote:
On Tue, Jul 17, 2012 at 01:33:32PM -0500, Anthony Liguori wrote:
Let's stop screwing up releases by having a script do the work that
Anthony's
fat fingers can't seem to get right.
Cc: Michael Roth
Am 18.07.2012 15:51, schrieb Andreas Färber:
Am 18.07.2012 10:51, schrieb Wenchao Xia:
Hi, following is API draft, prototypes were taken from qemu/block.h,
and the API prefix is changed frpm bdrv to qbdrvs, to declare related
object is BlockDriverState, not BlockDriver. [...]
After the
On Wed, Jul 18, 2012 at 04:51:03PM +0800, Wenchao Xia wrote:
Hi, following is API draft, prototypes were taken from qemu/block.h,
and the API prefix is changed frpm bdrv to qbdrvs, to declare related
object is BlockDriverState, not BlockDriver. One issue here is it may
require include
Hi,
QEMU can now distinguish between S4 and power off for the guest OSes that
suspends to disk through S4. This means that we can have a QMP event for S4
(so that QMP clients can distinguish between S3 and S4).
However, as we already emit the SHUTDOWN event for this, it turns out that
there are
Il 18/07/2012 15:58, Daniel P. Berrange ha scritto:
How is error reporting dealt with
These APIs just return errno values.
, and what is the intent around
thread safety of the APIs ? I'd like to see a fully thread safe
API - multiple threads can use the same 'BlockDriverState *'
Am 18.07.2012 15:19, schrieb Wanpeng Li:
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
Signed-off-by: Wanpeng Li liw...@linux.vnet.ibm.com
---
hw/pci_host.c | 26 ++
hw/pci_host.h |5 +
2 files
This patch series:
1. turns off -Werror for configure tests
2. fixes a large pile of warnings in various configure tests
3. turns on -Werror for configure tests again, but in a way that means
that errors mean configure stops so the warnings are as obvious
to developers as they would be
From: Stefan Weil s...@weilnetz.de
+= does not work with dash and other simple /bin/sh implementations.
The new code prepends the flag while the old code either did not work
(it continued after an error message which typically was not read) or
appended the flag. That difference should not matter
On Tue, Jul 17, 2012 at 01:33:32PM -0500, Anthony Liguori wrote:
Let's stop screwing up releases by having a script do the work that Anthony's
fat fingers can't seem to get right.
Cc: Michael Roth mdr...@linux.vnet.ibm.com
Signed-off-by: Anthony Liguori aligu...@us.ibm.com
---
v1 - v2
-
On Wed, Jul 18, 2012 at 04:02:15PM +0200, Paolo Bonzini wrote:
Il 18/07/2012 15:58, Daniel P. Berrange ha scritto:
How is error reporting dealt with
These APIs just return errno values.
Which has led to somewhat unhelpful error reporting in the past. If we're
designing a library API it'd be
Add support for checking whether test case code can compile without
warnings, by recompiling each successful test with -Werror. If the
-Werror version doesn't pass, we bail out. This gives us the same
level of visibility of warnings in test code as --enable-werror
provides for the main compile.
On 07/18/2012 08:02 AM, Luiz Capitulino wrote:
Hi,
QEMU can now distinguish between S4 and power off for the guest OSes that
suspends to disk through S4. This means that we can have a QMP event for S4
(so that QMP clients can distinguish between S3 and S4).
However, as we already emit the
On Wed, 2012-07-18 at 21:09 +1000, Alexey Kardashevskiy wrote:
It literally does the following:
1. POWERPC IOMMU support (the kernel counterpart is required)
2. The patch assumes that IOAPIC calls are going to be replaced
with something generic.
3. Added sPAPRVFIOData
Fix compile warning in the utimensat/futimens test (implicit
declaration of function 'utimensat', ditto futimens) by
adding a missing include.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
configure |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/configure
Fix compile warnings in the VDE library probe (passing argument 1 of
'vde_open_real' discards 'const' qualifier from pointer target type,
ditto argument 2).
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
configure |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff
It allows to disable memory merge support (KSM on Linux), which is
enabled by default otherwise.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
IMPORTANT: this is on top of this series:
http://lists.gnu.org/archive/html/qemu-devel/2012-07/msg01798.html
o v4
- rename option to
'make dist' creates a tarball for the current checkout.
'make qemu-${version}.tar.bz2' creates a tarball for git tag v${version}.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
Makefile |5 ++---
scripts/make-release |8 +++-
2 files changed, 9 insertions(+), 4
From: Stefan Weil s...@weilnetz.de
Since commit 417c9d72d48275d19c60861896efd4962d21aca2 all configure tests
normally run with -Werror. Some of these tests now fail because they
raised a compiler warning.
This patch fixes support for capabilities.
Signed-off-by: Stefan Weil s...@weilnetz.de
From: Stefan Weil s...@weilnetz.de
The old test code raises two compiler warnings which are errors since
commit 417c9d72d48275d19c60861896efd4962d21aca2.
These errors could result in compilations with compiler flag
-march486 (so all nice features of newer processors got lost).
Signed-off-by:
The distinction between QEMU_CFLAGS and CFLAGS is that the
former is for flags without which QEMU can't compile, whereas
the latter is for flags like -g -O2 which the user can
safely override. -march=i486 is in the former category, and
so belongs in QEMU_CFLAGS.
Signed-off-by: Peter Maydell
Wanpeng Li liw...@linux.vnet.ibm.com writes:
[CCing ML]
From: Anthony Liguori aligu...@us.ibm.com
The HPET usually sits on the LPC bus (which replaces ISA in modern systems).
It's sometimes a dedicated chip but can certain co-exist in a Super IO chip.
I think in terms of where it would
On 07/18/2012 08:31 AM, Gerd Hoffmann wrote:
'make dist' creates a tarball for the current checkout.
'make qemu-${version}.tar.bz2' creates a tarball for git tag v${version}.
Signed-off-by: Gerd Hoffmann kra...@redhat.com
---
Makefile |5 ++---
scripts/make-release |8
Don't run configure tests with -Werror in the compiler flags. The idea
of -Werror is that it makes problems very obvious to developers, so
they get fixed quickly. However, when running configure tests, failures
due to -Werror are far from obvious -- they simply result in the test
quietly failing
From: Stefan Weil s...@weilnetz.de
Since commit 417c9d72d48275d19c60861896efd4962d21aca2,
all configure tests normally run with -Werror.
Some of these tests now fail because they raised a compiler warning.
Here a build breakage for ALSA (configure --audio-drv-list=alsa) is fixed.
CC'ed to Blue, since he is bsd-user maintainer as MAINTAINER said.
On Mon, Jul 16, 2012 at 07:07:38PM -0700, Paramjot Oberoi wrote:
Hey all,
I'm having trouble building user mode BSD emulation on FreeBSD. I've tried
1.0.1, 1.1.1, and stable from GIT. I build by doing a: ./configure
Set up the virtqueue notify ioeventfd that the data plane will monitor.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
hw/virtio-blk.c | 37 +
1 file changed, 37 insertions(+)
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index
---
hw/dataplane/iosched.h | 78
hw/virtio-blk.c|5
2 files changed, 83 insertions(+)
create mode 100644 hw/dataplane/iosched.h
diff --git a/hw/dataplane/iosched.h b/hw/dataplane/iosched.h
new file mode 100644
index
Commit 9507e305ec54062fccc88fcf6fccf1898a7e7141 changed the
kvm_set_irq() function to kvm_irqchip_set_irq().
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
hw/msix.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/msix.c b/hw/msix.c
index
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
hw/virtio-blk.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index 8734029..cff2298 100644
--- a/hw/virtio-blk.c
+++ b/hw/virtio-blk.c
@@ -131,7 +131,7 @@ static void
This series implements a dedicated thread for virtio-blk processing using Linux
AIO for raw image files only. It is based on qemu-kvm.git a0bc8c3 and somewhat
old but I wanted to share it on the list since it has been mentioned on mailing
lists and IRC recently.
These patches can be used for
The data plane thread isn't allowed to call virtio_irq() directly
because that function is not thread-safe. Use the guest notifier just
like virtio-net to handle IRQs.
When MSI-X is in use and the vector is unmasked, the guest notifier
directly sets the IRQ inside the host kernel. If the vector
Khoa Huynh k...@us.ibm.com discovered that request merging is broken.
The merged iocb is not updated to reflect the total number of iovecs and
the offset is also outdated.
This patch fixes request merging.
Signed-off-by: Stefan Hajnoczi stefa...@linux.vnet.ibm.com
---
hw/virtio-blk.c | 10
If the smartcard configure check passes, add '-I\$(SRC_PATH)/libcacard'
to QEMU_INCLUDES, not QEMU_CFLAGS. Otherwise the unexpanded SRC_PATH
will cause a warning in every following configure test.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
configure |5 +++--
1 files changed,
---
hw/dataplane/vring.h | 28 +++-
hw/virtio-blk.c | 47 +++
2 files changed, 58 insertions(+), 17 deletions(-)
diff --git a/hw/dataplane/vring.h b/hw/dataplane/vring.h
index 44ef4a9..cdd4d4a 100644
---
Fix compile warning (variable 'png_ptr' set but not used) in the
PNG detection test code.
Signed-off-by: Peter Maydell peter.mayd...@linaro.org
---
configure |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/configure b/configure
index aced52e..784325a 100755
---
---
hw/virtio-blk.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/hw/virtio-blk.c b/hw/virtio-blk.c
index 1616be5..d75c187 100644
--- a/hw/virtio-blk.c
+++ b/hw/virtio-blk.c
@@ -339,8 +339,7 @@ static void virtio_blk_handle_output(VirtIODevice *vdev,
VirtQueue *vq)
1 - 100 of 184 matches
Mail list logo
