Add mhp_pc_dimm_assigned_slot & mhp_pc_dimm_assigned_address
events to trace which address and slot where assigned to
plugged in DIMM device on target-i386 machine.
Signed-off-by: Igor Mammedov
---
hw/i386/pc.c |3 +++
trace-events |4
2 files changed, 7 insertions(+), 0 deletions(-
From: Vasilis Liaskovitis
Each hotplug-able memory slot is a DimmDevice.
A hot-add operation for a DIMM:
- creates a new DimmDevice and makes hotplug controller to map it into
guest address space
Hotplug operations are done through normal device_add commands.
For migration case, all hotplugged
Add following parameters:
"slots" - total number of hotplug memory slots
"maxmem" - maximum possible memory
"slots" and "maxmem" should go in pair and "maxmem" should be greater
than "mem" for memory hotplug to be enabled.
Signed-off-by: Igor Mammedov
---
v4:
- store maxmem & slots values i
Propeties of object should be available after its instances_init()
callback is finished and not added in PCIDeviceClass.init which is
roughly corresponds to realize() method.
Moving properties adding into instances_init will fix missing
property error when global/compat property mechanism is used.
it will be used for PC specific options/variables
Signed-off-by: Igor Mammedov
---
hw/i386/pc.c | 57 ++
hw/i386/pc_piix.c| 36 +++---
hw/i386/pc_q35.c | 12 +-
include/hw/i386/pc.h | 24 +
... which is imposed by current naming scheme of ACPI memory devices.
Signed-off-by: Igor Mammedov
---
v2:
* use define for amount of supported slots, requested by Eduardo Habkost
---
hw/i386/pc.c |6 ++
include/hw/acpi/acpi.h |6 ++
2 files changed, 12 insertions(+),
to make it more generic, so it could be used for memory hotplug
as well.
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-dsdt.dsl |2 +-
hw/i386/q35-acpi-dsdt.dsl |2 +-
include/hw/acpi/acpi_defs.h| 33 +
include/hw/acpi/cpu_h
which allows to check if MemoryRegion is already mapped.
Signed-off-by: Igor Mammedov
---
include/exec/memory.h |8
memory.c | 15 ++-
2 files changed, 22 insertions(+), 1 deletions(-)
diff --git a/include/exec/memory.h b/include/exec/memory.h
index 1d55a
that will perform mapping of DIMM device into guest's RAM address space
Signed-off-by: Igor Mammedov
---
hw/i386/pc.c | 59 ++
include/hw/i386/pc.h |8 ++
2 files changed, 67 insertions(+), 0 deletions(-)
diff --git a/hw/i386/pc.
using the same memdev backend more than once will cause
assersion at MemoryRegion mapping time becase it's already
mapped. Prevent it by checking that associated MemoryRegion
is not mapped.
Signed-off-by: Igor Mammedov
---
hw/mem/dimm.c | 17 -
1 files changed, 16 insertions(+)
- if 'addr' property is not specified on -device/device_add command,
treat default value as request for assigning DimmDevice to
the first free memory region.
- if 'addr' is provided with -device/device_add command, attempt to
use it or fail command if it's already occupied or falls inside
of an ex
'etc/reserved-memory-end' will allow QEMU to tell BIOS where PCI
BARs mapping could safely start in high memory.
Allowing BIOS to start mapping 64-bit PCI BARs at address where it
wouldn't conflict with other mappings QEMU might place before it.
That permits QEMU to reserve extra address space be
- if slot property is not specified on -device/device_add command,
treat default value as request for assigning DimmDevice to
the first free slot.
- if slot is provided with -device/device_add command, attempt to
use it or fail command if it's already occupied.
Signed-off-by: Igor Mammedov
---
- provides static SSDT object for memory hotplug that can handle
upto 4095 hotplugable memory slots
- SSDT template for memory devices and runtime generator
of them in SSDT table.
Signed-off-by: Vasilis Liaskovitis
Signed-off-by: Igor Mammedov
---
v2:
* use define for amount of supported sl
- implements QEMU hardware part of memory hotplug protocol
described at "docs/specs/acpi_mem_hotplug.txt"
- handles only memory add notification event for now
Signed-off-by: Igor Mammedov
---
docs/specs/acpi_mem_hotplug.txt | 44 +++
hw/acpi/Makefile.objs|1 +
hw/acp
also make handler edge based to avoid losing events, the same as
it has been done for PCI and CPU hotplug handlers.
Signed-off-by: Igor Mammedov
---
v2:
* use memory hotplug crtl located under PCI0
---
hw/i386/acpi-dsdt.dsl |5 -
hw/i386/q35-acpi-dsdt.dsl |5 -
2 files chang
On Tue, May 20, 2014 at 05:15:21PM +0200, Igor Mammedov wrote:
> to make it more generic, so it could be used for memory hotplug
> as well.
>
> Signed-off-by: Igor Mammedov
These are actually qemu pc specific hotplug registers,
this name makes one think these are generic defines.
How about ./inc
On Tue, May 20, 2014 at 05:15:33PM +0200, Igor Mammedov wrote:
> Needed for Windows to use hotplugged memory device, otherwise
> it complains that server is not configured for memory hotplug.
> Tests shows that aftewards it uses dynamically provided
> proximity value from _PXM() method if available
Add events for tracing accesses to memory hotplug IO ports.
Signed-off-by: Igor Mammedov
---
hw/acpi/memory_hotplug.c | 13 +
trace-events | 13 +
2 files changed, 26 insertions(+), 0 deletions(-)
diff --git a/hw/acpi/memory_hotplug.c b/hw/acpi/memory_hot
On 04/28/2014 09:25 AM, Tomoki Sekiyama wrote:
> When an array of mount point paths is specified as 'mountpoints' argument
> of guest-fsfreeze-freeze, qemu-ga with this patch will only freeze the file
> systems mounted on specified paths in Linux.
How does the management application learn the set
so that management could detect via QOM interface if device was
hotplugged
Signed-off-by: Igor Mammedov
---
v2:
- fix typo in commit message (afaerber)
---
hw/core/qdev.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/hw/core/qdev.c b/hw/core/qdev.c
in
initialize and map hotplug memory address space container
into guest's RAM address space.
Signed-off-by: Igor Mammedov
---
v2:
* fix uint64_t overflow reported by Hu Tao
* rebase on top of Marcel's patch
"machine: Conversion of QEMUMachineInitArgs to MachineState"
---
hw/i386/pc.c
On Tue, 20 May 2014 18:35:33 +0300
"Michael S. Tsirkin" wrote:
> On Tue, May 20, 2014 at 05:15:21PM +0200, Igor Mammedov wrote:
> > to make it more generic, so it could be used for memory hotplug
> > as well.
> >
> > Signed-off-by: Igor Mammedov
>
> These are actually qemu pc specific hotplug
On Tue, 2014-05-20 at 17:15 +0200, Igor Mammedov wrote:
> it will be used for PC specific options/variables
>
> Signed-off-by: Igor Mammedov
> ---
> hw/i386/pc.c | 57
> ++
> hw/i386/pc_piix.c| 36 +++---
>
Add sclpMemoryHotplugDev to contain associated data structures, etc.
Signed-off-by: Matthew Rosato
---
hw/s390x/sclp.c | 38 ++
include/hw/s390x/sclp.h | 20
2 files changed, 58 insertions(+)
diff --git a/hw/s390x/sclp.c b/hw/
When determining the memory increment size, use the maxmem size if
it was specified.
Signed-off-by: Matthew Rosato
---
hw/s390x/s390-virtio-ccw.c | 46
qemu-options.hx|3 ++-
target-s390x/cpu.h |3 +++
3 files changed, 43
This patchset adds support in s390 for a pool of standby memory,
which can be set online/offline by the guest (ie, via chmem).
New options, maxmem and slots, are added to the QEMU command line
memory parameter to specify the total amount of memory available
to the guest as well as the number of me
From: Igor Mammedov
From: Igor Mammedov
Add following parameters:
"slots" - total number of hotplug memory slots
"maxmem" - maximum possible memory
"slots" and "maxmem" should go in pair and "maxmem" should be greater
than "mem" for memory hotplug to be enabled.
Signed-off-by: Igor Mammed
Add memory information to read SCP info and add handlers for
Read Storage Element Information, Attach Storage Element,
Assign Storage and Unassign Storage.
Signed-off-by: Matthew Rosato
---
hw/s390x/sclp.c| 259 ++--
target-s390x/cpu.h | 15
Needed for Windows to use hotplugged memory device, otherwise
it complains that server is not configured for memory hotplug.
Tests shows that aftewards it uses dynamically provided
proximity value from _PXM() method if available.
Signed-off-by: Igor Mammedov
---
hw/i386/acpi-build.c | 14 +
In general QMP command parameter values are specified by consumers of the
QMP/HMP interface, but in the case of optional parameters these values may
be left uninitialized.
It is considered a bug for code to make use of optional parameters that have
not been flagged as being present by the marshall
Hi,
This is the first part of my gsoc work.
Following patches add the support of dirty bitmap logging and dumping
to a specified file. These patches provide the mechanism to get the
dirty bitmap if the user wants to log the VM besides migration. This
can be useful in case of learning about the wr
This patch introduces both hmp and qmp (log-dirty-bitmap-cancel) interface
to cancel an already executing dump process.
Signed-off-by: Sanidhya Kashyap
---
hmp-commands.hx | 14 ++
hmp.c| 5 +
hmp.h| 1 +
qapi-schema.json | 5 +
qmp-commands.hx |
Added another flag - DIRTY_MEMORY_LOG_BITMAP for the purpose of logging
the dirty bitmap. The dumping bitmap process will utilize this flag for
dumping the data in the file.
Signed-off-by: Sanidhya Kashyap
---
exec.c | 4
include/exec/memory.h | 3 ++-
include/exec/ram_
This patch introduces the mechanism of dumping the dirty bitmap either
in an ascii format or binary format. The implementation is almost
similar to the migration one. A separate thread is created for the
dumping process.
The bitmap is obtained with the help of ramlist blocks. I have used almost
si
This patch introduces both qmp and hmp (log-dirty-bitmap-set-frequency)
interface to update the value of the frequency.
Signed-off-by: Sanidhya Kashyap
---
hmp-commands.hx | 15 +++
hmp.c| 12
hmp.h| 1 +
qapi-schema.json | 8
qmp-comm
This script extracts the bitmap only from a binary file. It takes only
a single input as file. This will be useful to users for exploring the
writable working set for the VM.
Signed-off-by: Sanidhya Kashyap
---
scripts/extract-bitmap.py | 68 +++
1 fil
Michael Roth writes:
> In general QMP command parameter values are specified by consumers of the
> QMP/HMP interface, but in the case of optional parameters these values may
> be left uninitialized.
>
> It is considered a bug for code to make use of optional parameters that have
> not been flagge
Added the log-dirty-bitmap or ldb hmp interface.
Signed-off-by: Sanidhya Kashyap
---
hmp-commands.hx | 17 +
hmp.c | 19 +++
hmp.h | 1 +
3 files changed, 37 insertions(+)
diff --git a/hmp-commands.hx b/hmp-commands.hx
index 8971f1b..032a320
Il 20/05/2014 16:00, Gerd Hoffmann ha scritto:
+ -device pci-bridge,addr=12.0,chassis_nr=2,id=head.2 \
+ -device secondary-vga,bus=head.2,addr=02.0,id=video.2 \
+ -device nec-usb-xhci,bus=head.2,addr=0f.0,id=usb.2 \
+ -device usb-kbd,bus=usb.2.0,port=1,display=video.2 \
+
From: Markus Armbruster
For clarity, and to hush up Coverity.
Signed-off-by: Markus Armbruster
Signed-off-by: Paolo Bonzini
---
hw/scsi/scsi-bus.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/scsi/scsi-bus.c b/hw/scsi/scsi-bus.c
index ae921a6..26770fb 100644
--- a/hw/scsi/scsi-bus
Peter,
The following changes since commit 6a86dec61921163b6ab582df988416a6f0ca0ed5:
[PATCH] block/iscsi: bump year in copyright notice (2014-05-05 10:04:30 +0200)
are available in the git repository at:
git://github.com/bonzini/qemu.git scsi-next
for you to fetch changes up to 5a7733b0b728
From: Markus Armbruster
Spotted by Coverity.
Signed-off-by: Markus Armbruster
Cc: qemu-sta...@nongnu.org
Signed-off-by: Paolo Bonzini
---
hw/scsi/virtio-scsi.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/hw/scsi/virtio-scsi.c b/hw/scsi/virtio-scsi.c
index b0d7517..91
From: Olaf Hering
Using __DATE__ or __TIME__ in binary pkgs changes the checksum of
compiled binaries if they get rebuilt, even if there are no other
source changes. Replace the dynamic strings with some equally
informative static strings.
Signed-off-by: Olaf Hering
Signed-off-by: Paolo Bonzin
From: Jeff Cody
Commit b03c380 introduced the function
iscsi_allocationmap_is_allocated(), however it is only used within a
code block that is conditionally compiled. This produces a warning
(error with -werror) of "defined but not used" for the the function, if
LIBISCSI_FEATURE_IOVECTOR is not
On 20 May 2014 18:20, Michael Roth wrote:
> In general QMP command parameter values are specified by consumers of the
> QMP/HMP interface, but in the case of optional parameters these values may
> be left uninitialized.
>
> It is considered a bug for code to make use of optional parameters that ha
The Python "except Foo as x" syntax was only introduced in
Python 2.6, but we aim to support Python 2.4 and later.
Use the old-style "except Foo, x" syntax instead, thus
fixing configure/compile on systems with older Python.
Reported-by: Peter Maydell
Signed-off-by: Luiz Capitulino
---
scripts/
On Fri, 16 May 2014 10:40:47 -0400
pe...@gridcentric.ca wrote:
> From: Peter Feiner
>
> On a slow VM (e.g., nested), you see the "setup" state when you query the
> migration status.
>
> Signed-off-by: Peter Feiner
Applied to the qmp branch, thanks.
> ---
> qapi-schema.json |2 +-
> qmp-
Quoting Peter Maydell (2014-05-20 13:21:15)
> On 20 May 2014 18:20, Michael Roth wrote:
> > In general QMP command parameter values are specified by consumers of the
> > QMP/HMP interface, but in the case of optional parameters these values may
> > be left uninitialized.
> >
> > It is considered a
On Mon, May 19, 2014 at 10:44:48PM +0300, Michael S. Tsirkin wrote:
> Thanks!
> One question: we don't seem to have unit-test for this
> interface in qemu, do we?
> I would like to see at least a basic test along the lines of
> tests/acpi-test.c: run bios to load tables from QEMU,
> then do some ba
On 05/20/2014 11:47 AM, Sanidhya Kashyap wrote:
> This patch introduces the mechanism of dumping the dirty bitmap either
> in an ascii format or binary format. The implementation is almost
> similar to the migration one. A separate thread is created for the
> dumping process.
>
> The bitmap is obt
On 05/20/2014 03:07 AM, Fam Zheng wrote:
> Please first take a look at patch 7 to see what is supported by this series.
>
> Patch 1 ~ 3 allows some useful basic types in schema.
>
> Patch 4 ~ 6 implements the new syntax.
>
> Note: The introduced '@arg' sigil, just like the preexisting '*arg', is
On Mon, 19 May 2014 08:41:21 +0200
Ján Tomko wrote:
> If the guest hasn't updated the stats yet, instead of returning
> an error, return '-1' for the stats and '0' as 'last-update'.
>
> This lets applications ignore this without parsing the error message.
>
> Related libvirt patch and discussio
On Mon, 19 May 2014 15:26:03 +0800
wrote:
> From: Gonglei
>
> token should be closed in all conditions.
> So move CloseHandle(token) to "out" branch.
Looks good to me. Michael, are you going to pick this one?
>
> Signed-off-by: Wang Rui
> Signed-off-by: Gonglei
> ---
> qga/commands-win32.
On 05/20/2014 03:07 AM, Fam Zheng wrote:
> Signed-off-by: Fam Zheng
> ---
> scripts/qapi.py | 24 +---
> 1 file changed, 17 insertions(+), 7 deletions(-)
I applied this patch and tried to break things.
Pre-patch,
{ 'random': tru } => foo.json:1:13: Stray "t"
{ 'random': true
>> +#define QERR_LOG_DIRTY_BITMAP_ACTIVE \
>> +ERROR_CLASS_GENERIC_ERROR, "Dirty bitmap dump already in progress"
>> +
>
> Please don't add new ERROR_CLASS macros. Instead, just use error_setg()
> and directly output the error message at the call site that produces the
> error.
>
will keep in
On 05/20/2014 11:47 AM, Sanidhya Kashyap wrote:
> This patch introduces both hmp and qmp (log-dirty-bitmap-cancel) interface
> to cancel an already executing dump process.
>
> Signed-off-by: Sanidhya Kashyap
> ---
> +++ b/qapi-schema.json
> @@ -4710,3 +4710,8 @@
> '*epochs'
On 05/20/2014 11:47 AM, Sanidhya Kashyap wrote:
> This patch introduces both qmp and hmp (log-dirty-bitmap-set-frequency)
> interface to update the value of the frequency.
>
> Signed-off-by: Sanidhya Kashyap
> ---
> +++ b/qapi-schema.json
> @@ -4715,3 +4715,11 @@
> # cancel the dirty bitmap log
On 05/20/2014 11:47 AM, Sanidhya Kashyap wrote:
> This script extracts the bitmap only from a binary file. It takes only
> a single input as file. This will be useful to users for exploring the
> writable working set for the VM.
>
> Signed-off-by: Sanidhya Kashyap
> ---
> scripts/extract-bitmap.
On 05/20/2014 01:38 PM, Eric Blake wrote:
> On 05/20/2014 11:47 AM, Sanidhya Kashyap wrote:
>> This script extracts the bitmap only from a binary file. It takes only
>> a single input as file. This will be useful to users for exploring the
>> writable working set for the VM.
>>
>> Signed-off-by: Sa
Quoting Luiz Capitulino (2014-05-20 14:17:42)
> On Mon, 19 May 2014 15:26:03 +0800
> wrote:
>
> > From: Gonglei
> >
> > token should be closed in all conditions.
> > So move CloseHandle(token) to "out" branch.
>
> Looks good to me. Michael, are you going to pick this one?
Sure I'll queue it.
This series enables qemu-iotests to be run in a build tree outside of
the source tree. It also makes the tests use the command for invoking
the Python interpreter specified through configure instead of always
using "/usr/bin/env python".
v2:
- Patch 1:
- added error handling for obtaining the
As out-of-tree builds are preferred for qemu, running the qemu-iotests
in that out-of-tree build should be supported as well. To do so, a
symbolic link has to be created pointing to the check script in the
source directory. That script will check whether it has been run through
a symlink, and if so
iotest 083 filters out debug messages from nbd, which are prefixed (and
recognized) by __FILE__. However, the current filter (/^nbd\.c…/) is
valid for in-tree builds only, as out-of-tree builds will have a path
before that filename (e.g. "/tmp/qemu/nbd.c"). Fix this by adding .*
before "nbd\.c".
W
In order to allow out-of-tree iotests, create a symlink for the check
script in the build tree.
While doing so, also write configured options relevant to the iotests to
common.env in the build tree; currently, this is the command to invoke
Python 2.
Signed-off-by: Max Reitz
---
configure | 12 +
Instead of invoking Python scripts directly via ./, use $PYTHON to
obtain the correct Python interpreter command.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/031 | 8
tests/qemu-iotests/036 | 6 +++---
tests/qemu-iotests/039 | 18 +-
tests/qemu-iotests/054
Add a default common.env in case the one supposed to be emitted by
configure cannot be found.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/common.env.default | 6 ++
1 file changed, 6 insertions(+)
create mode 100644 tests/qemu-iotests/common.env.default
diff --git a/tests/qemu-iotests/
Source common.env in the iotests' check script. If the one supposed to
be created by configure cannot be found, use common.env.default from the
source tree.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/check | 16
1 file changed, 16 insertions(+)
diff --git a/tests/qemu-iote
Test 065 specified python2 to be used in its Shebang; this might not
work on systems without a python2 symlink and furthermore it is now
counter-productive, as the check script compares the Shebang to
"#!/usr/bin/env python" and only uses the Python interpreter selected by
configure on an exact mat
Currently, test 089 uses $QEMU_IMG info manually in order to obtain the
according output. However, the iotests should generally use _img_info as
this filters out more irrelevant information such as the host image size
or format specific information. Therefore, test 089 should use _img_info
as well.
Commit fd460606fd6f moved setting of eflags above calls to
cpu_x86_load_seg_cache() in seg_helper.c. Unfortunately, in
do_interrupt_protected() this moved the clearing of VM_MASK above a
test for it.
Fix this regression by storing the value of VM_MASK at the start of
do_interrupt_protected().
Si
Hi,
this series fixes cross-page TB linking bug in target-xtensa that managed
to survive for a major release period. With this bug fixed it is finally
possible to build linux kernel under xtensa linux running in system mode
QEMU (but it may take a couple of days to complete).
Max Filippov (3):
Signed-off-by: Max Filippov
---
tests/tcg/xtensa/test_mmu.S | 26 +++---
1 file changed, 19 insertions(+), 7 deletions(-)
diff --git a/tests/tcg/xtensa/test_mmu.S b/tests/tcg/xtensa/test_mmu.S
index 099031f..37174b9 100644
--- a/tests/tcg/xtensa/test_mmu.S
+++ b/tests/tcg/xte
Use tb->pc instead of dc->pc to check for cross-page jumps.
When TB translation stops at the page boundary dc->pc points to the next
page allowing chaining to TBs in it, which is wrong.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Max Filippov
---
target-xtensa/translate.c | 4 ++--
1 file changed,
Signed-off-by: Max Filippov
---
tests/tcg/xtensa/test_mmu.S | 220
1 file changed, 220 insertions(+)
diff --git a/tests/tcg/xtensa/test_mmu.S b/tests/tcg/xtensa/test_mmu.S
index 37174b9..58c5bca 100644
--- a/tests/tcg/xtensa/test_mmu.S
+++ b/tests/tcg
On Fri, May 16, 2014 at 09:59:25PM +0200, Paolo Bonzini wrote:
> CS.RPL is not equal to the CPL in the few instructions between
> setting CR0.PE and reloading CS. We get this right in the common
> case, because writes to CR0 do not modify the CPL, but it would
> not be enough if an SMI comes exact
Public bug reported:
I just ran static analyser cppcheck over today (20140520) qemu source
code.
It said many things, including
[qemu/block/qcow2.c:1942] -> [qemu/block/qcow2.c:1943]: (performance) Buffer
'pad_buf' is being writ
ten before its old content has been used.
S
> On 04/28/2014 09:25 AM, Tomoki Sekiyama wrote:
>> When an array of mount point paths is specified as 'mountpoints' argument
>> of guest-fsfreeze-freeze, qemu-ga with this patch will only freeze the file
>> systems mounted on specified paths in Linux.
>
> How does the management application learn
> On 04/28/2014 09:25 AM, Tomoki Sekiyama wrote:
>> When an array of mount point paths is specified as 'mountpoints' argument
>> of guest-fsfreeze-freeze, qemu-ga with this patch will only freeze the file
>> systems mounted on specified paths in Linux.
>
> How does the management application learn
On Tue, May 20, 2014 at 7:53 PM, Andreas Färber wrote:
> Am 20.05.2014 08:31, schrieb Peter Crosthwaite:
>> To get it out of the default GPIO list. This allows child devices to
>> use the un-named GPIO namespace without having to be SSI aware. That
>> is, there is no more need for machines to know
On Tue, May 20, 2014 at 7:49 PM, Andreas Färber wrote:
> Am 20.05.2014 08:30, schrieb Peter Crosthwaite:
>> This series implements Named GPIOs on the qdev level. Patch 1 is the
>> feature presentation.
>>
>> Second patch I give a useful example of the feature's use (an SSI
>> cleanup).
>>
>> This
On 20 May 2014 07:30, Peter Crosthwaite wrote:
> This series implements Named GPIOs on the qdev level. Patch 1 is the
> feature presentation.
I'm way behind on my review queue, but hopefully I can find time
to do the conversion of the GIC GPIOs -- I think that's the major
device with a really cum
On 05/20/2014 04:01 PM, Tomoki Sekiyama wrote:
> The patch below is for the command to get filesystems list.
>
> ===
> From: Tomoki Sekiyama
You'll want to resend it as a series of patches as a top-level thread;
not everyone notices a patch buried as a reply.
>
> qga: Add guest-get-fs-info com
On Wed, 7 May 2014, Tom Musta wrote:
On 5/6/2014 6:17 PM, BALATON Zoltan wrote:
On Tue, 6 May 2014, Tom Musta wrote:
On 5/6/2014 5:03 AM, BALATON Zoltan wrote:
I'd appreciate some insight and help.
[snip]
(1) Why is MorphOS using this invalid instruction form? Would it be easier to
fix the
This series of patches replaces some more occurrences of fprintf(stderr, ...)
with error_report() and removes the trailing "\n". Those for debugging are not
changed.
Le Tan (2):
arch_init: replace fprintf(stderr,...) with error_report()
block: replace fprintf(stderr,...) with error_report()
Replace fprintf(stderr,...) with error_report() in files block/*, block.c,
block-migration.c and blockdev.c. The trailing "\n"s of the @fmt argument
have been removed because @fmt of error_report() should not contain newline.
Signed-off-by: Le Tan
---
block-migration.c |5 +--
block.c
Replace fprintf(stderr,...) with error_report() in the file
arch_init.c. The trailing "\n"s of the @fmt argument have been removed
because @fmt of error_report() should not contain newline.
Signed-off-by: Le Tan
---
arch_init.c | 32 +++-
1 file changed, 15 insertio
>>> Signed-off-by: Sanidhya Kashyap
>>> ---
>>> scripts/extract-bitmap.py | 68
>>> +++
>>> 1 file changed, 68 insertions(+)
>>> create mode 100755 scripts/extract-bitmap.py
>
> Does this file need to be mentioned in any Makefile to ensure that it
> g
Hi, I am a student participating in GSoC 2014. My brief introduction
is given below. I am looking forward to studying QEMU and finishing
the GSoC project with the community. Thank you very much!
Name: Le Tan
IRC nick: #tamlok
Public git repo URL: https://github.com/tamlok/qemu.git
Project: Intel I
> -Original Message-
> From: Stefano Stabellini [mailto:stefano.stabell...@eu.citrix.com]
> Sent: Tuesday, May 20, 2014 6:51 PM
> To: Chen, Tiejun
> Cc: Stefano Stabellini; anthony.per...@citrix.com; m...@redhat.com;
> kelly.zyta...@amd.com; qemu-devel@nongnu.org;
> xen-de...@lists.xensourc
Quoting Marcel Apfelbaum (2014-05-20 10:07:59)
> Checks the output visitor behaviour for NULL values.
>
> Signed-off-by: Marcel Apfelbaum
> ---
> Notes:
> - I didn't add Michael's Sob because I tweaked the test a little.
Tweaked it so it didn't crash 100% of the time even after your fix? :)
A
On Tue, May 20, 2014 at 07:02:37PM +1000, Peter Crosthwaite wrote:
> On Mon, May 19, 2014 at 7:23 PM, Edgar E. Iglesias
> wrote:
> > From: "Edgar E. Iglesias"
> >
> > Signed-off-by: Edgar E. Iglesias
> > ---
> > target-arm/cpu.h| 2 +-
> > target-arm/helper.c | 20
> >
> -Original Message-
> From: Anthony PERARD [mailto:anthony.per...@citrix.com]
> Sent: Tuesday, May 20, 2014 10:45 PM
> To: Chen, Tiejun
> Cc: Gerd Hoffmann; stefano.stabell...@eu.citrix.com; m...@redhat.com;
> kelly.zyta...@amd.com; peter.mayd...@linaro.org;
> xen-de...@lists.xensource.com
On Tue, 05/20 07:43, Jeff Cody wrote:
> On Tue, May 20, 2014 at 02:04:29PM +0800, Fam Zheng wrote:
> > It makes no sense to check for "any" blocker on bs, we are here only
> > because of the mechanical conversion from in_use to op_blockers. Remove
> > it now, and let the callers check specific oper
On Tue, 05/20 13:13, Eric Blake wrote:
> On 05/20/2014 03:07 AM, Fam Zheng wrote:
> > Please first take a look at patch 7 to see what is supported by this series.
> >
> > Patch 1 ~ 3 allows some useful basic types in schema.
> >
> > Patch 4 ~ 6 implements the new syntax.
> >
> > Note: The introd
On Mon, May 12, 2014 at 08:57:30PM -0600, Eric Blake wrote:
> On 05/07/2014 07:14 PM, Amos Kong wrote:
> > The space before pointers is redundant.
> >
> > Signed-off-by: Amos Kong
> > ---
> > scripts/qapi-visit.py | 20 ++--
> > 1 file changed, 10 insertions(+), 10 deletions(-)
>
On Tue, 05/20 16:01, Paolo Bonzini wrote:
> Il 20/05/2014 15:16, Stefan Hajnoczi ha scritto:
> >On Tue, May 20, 2014 at 10:00:47AM +0800, Fam Zheng wrote:
> >>diff --git a/thread-pool.c b/thread-pool.c
> >>index fbdd3ff..d4984ba 100644
> >>--- a/thread-pool.c
> >>+++ b/thread-pool.c
> >>@@ -223,6 +
The current flow of canceling a thread from THREAD_ACTIVE state is:
1) Caller wants to cancel a request, so it calls thread_pool_cancel.
2) thread_pool_cancel waits on the conditional variable
elem->check_cancel.
3) The worker thread changes state to THREAD_DONE once the task is
notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1321464
Title:
qemu/block/qcow2.c:1942: possible performance problem ?
Status in QEMU:
New
Bug description:
I just ran static analyser cppcheck over today (20140520) qemu
Thanks for the quick patch.
Best Regards,
Sangho Park
-Original Message-
From: qemu-devel-bounces+sangho1206.park=samsung@nongnu.org
[mailto:qemu-devel-bounces+sangho1206.park=samsung@nongnu.org] On Behalf
Of Stefan Weil
Sent: Saturday, May 17, 2014 5:35 PM
To: qemu-devel@nongnu.or
101 - 200 of 222 matches
Mail list logo
