Implement a simple first-fit memory allocator that
attempts to keep track of leased blocks of memory
in order to be able to re-use blocks.
Additionally, allow the user to specify when
initializing the device that upon cleanup,
we would like to assert that there are no
blocks in use. This may be us
Use the new call to pc_alloc_uninit
as a test for the new pathways.
The leak checking / assert pathways are
not enabled in this patch, leaving this
as an option to future test writers.
Signed-off-by: John Snow
---
tests/ide-test.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/ide-
From: Marc Marí
Signed-off-by: Marc Marí
Signed-off-by: John Snow
---
tests/libqos/malloc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/libqos/malloc.h b/tests/libqos/malloc.h
index 46f6000..5565381 100644
--- a/tests/libqos/malloc.h
+++ b/tests/libqos/malloc.h
@@
* Pavel Dovgalyuk (pavel.dovga...@ispras.ru) wrote:
> VMState added by this patch preserves correct
> loading of the FDC device state.
This is a pretty big series, but I suspect most people don't need
most of these devices, especially for replay/reverse execution stuff.
Why don't you boil this dow
On 26 July 2014 08:26, Stefan Weil wrote:
> Static code analyzers complain about a dubious & operation used for a
> boolean value. The code does not test the PSTATE_SP bit as it should.
>
> Cc: Peter Maydell
> Signed-off-by: Stefan Weil
> ---
>
> Hello Peter,
>
> I'm not sure whether the "!" is
On 08/01/2014 12:41 AM, Markus Armbruster wrote:
> +if (data == NULL) {
Wouldn't it be even more idiomatic as:
if (!data) {
Probably applies throughout your series.
>>> OK, will do. Thanks!
>>
>> Not so quick! You are free to use that in your patches,
The following changes since commit 541bbb07eb197a870661ed702ae1f15c7d46aea6:
Update version for v2.1.0 release (2014-08-01 13:31:29 +0100)
are available in the git repository at:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git xen-20140801
for you to fetch changes up to
Il 01/08/2014 16:34, Stefan Hajnoczi ha scritto:
> On Wed, Jul 09, 2014 at 11:53:01AM +0200, Paolo Bonzini wrote:
>> diff --git a/async.c b/async.c
>> index 34af0b2..ac40eab 100644
>> --- a/async.c
>> +++ b/async.c
>> @@ -152,39 +152,43 @@ void qemu_bh_delete(QEMUBH *bh)
>> bh->deleted = 1;
>>
On 08/01/2014 01:46 AM, arei.gong...@huawei.com wrote:
> From: Gonglei
>
> Yoda conditions lack readability, and QEMU has a
> strict compiler configuration for checking a common
> mistake like "if (dev = NULL)". Make it a written rule.
>
> Signed-off-by: Gonglei
> ---
> CODING_STYLE | 14 +
From: Roger Pau Monne
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 value in errno instead of the value
returned by the function.
Signe
* Yang Hongyang (yan...@cn.fujitsu.com) wrote:
> Virtual machine (VM) replication is a well known technique for
> providing application-agnostic software-implemented hardware fault
> tolerance "non-stop service". COLO is a high availability solution.
> Both primary VM (PVM) and secondary VM (SVM) r
From: Roger Pau Monne
The current behaviour of tap_open for BSD systems differ greatly from
it's Linux counterpart. Since FreeBSD supports interface renaming and
tap device cloning by opening /dev/tap, implement a FreeBSD specific
version of tap_open that behaves like it's Linux counterpart.
Thi
On Fri, Aug 01, 2014 at 10:52:55PM +0800, Ming Lei wrote:
> On Fri, Aug 1, 2014 at 9:48 PM, Ming Lei wrote:
> > On Fri, Aug 1, 2014 at 9:13 PM, Stefan Hajnoczi wrote:
> >> On Fri, Aug 01, 2014 at 10:54:02AM +0800, Ming Lei wrote:
> >>> On Fri, Aug 1, 2014 at 12:30 AM, Paolo Bonzini
> >>> wrote:
Hi Stefan,
As v3 posted earlier today but with a format string fix which didn't
show up in the ust build I tested it on
Alex Bennée (2):
trace: teach lttng backend to use format strings
trace: add some tcg tracing support
cpu-exec.c | 6 ++
scripts/tra
This makes the UST backend pay attention to the format string arguments
that are defined when defining payload data. With this you can now
ensure integers are reported in hex mode if you want.
Signed-off-by: Alex Bennée
---
v2
- remove silly debug statements
v3
- fix spelling
- rebase to
This adds a couple of tcg specific trace-events which are useful for
tracing execution though tcg generated blocks. It's been tested with
lttng user space tracing but is generic enough for all systems. The tcg
events are:
* translate_block - when a subject block is translated
* exec_tb - when
From: Chunyan Liu
qemu side patch to support xen HVM direct kernel boot:
if -kernel exists, calls xen_load_linux(), which will read kernel/initrd
and add a linuxboot.bin or multiboot.bin option rom. The
linuxboot.bin/multiboot.bin will load kernel/initrd and jump to execute
kernel directly. It's
On 30 July 2014 16:20, Alex Bennée wrote:
> Hi,
>
> Not too much has changed:
>
> * added a review tag
> * fixed up review comments
> * added some notes about benchmark results
> * added a patch to disable ARMv5 in AArch64 build
>
> The most important thing is I've measured a 25-30% improv
On Fri, 2014-08-01 at 09:25 -0600, Alex Williamson wrote:
> On Fri, 2014-08-01 at 09:35 +0800, Le Tan wrote:
> > Hi Alex,
> >
> > 2014-07-30 22:46 GMT+08:00 Alex Williamson :
> > > On Wed, 2014-07-30 at 22:16 +0800, Le Tan wrote:
> > >> Hi Michael,
> > >>
> > >> 2014-07-30 21:16 GMT+08:00 Michael
On 2014-08-01 18:35, Alex Williamson wrote:
> On Fri, 2014-08-01 at 09:25 -0600, Alex Williamson wrote:
>> On Fri, 2014-08-01 at 09:35 +0800, Le Tan wrote:
>>> Hi Alex,
>>>
>>> 2014-07-30 22:46 GMT+08:00 Alex Williamson :
On Wed, 2014-07-30 at 22:16 +0800, Le Tan wrote:
> Hi Michael,
>
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of
the QEMU 2.1.0 release. This release contains 2200+ commits from 180
authors.
http://wiki.qemu.org/download/qemu-2.1.0.tar.bz2
The full list of changes are available at:
http://wiki.qemu.org/ChangeLog/2.1
Highlight
On 07/30/2014 11:20 AM, Alex Bennée wrote:
> If you attempt to run a system image which uses 1k pages in the
> qemu-system-aarch64 build it will fail thanks to the change to 12 bit
> pages. The boards are still available for the qemu-system-arm build.
I fail to understand the correlation between A
On Fri, 2014-08-01 at 18:39 +0200, Jan Kiszka wrote:
> On 2014-08-01 18:35, Alex Williamson wrote:
> > On Fri, 2014-08-01 at 09:25 -0600, Alex Williamson wrote:
> >> On Fri, 2014-08-01 at 09:35 +0800, Le Tan wrote:
> >>> Hi Alex,
> >>>
> >>> 2014-07-30 22:46 GMT+08:00 Alex Williamson :
> On We
On 1 August 2014 17:45, Christopher Covington wrote:
> On 07/30/2014 11:20 AM, Alex Bennée wrote:
>> If you attempt to run a system image which uses 1k pages in the
>> qemu-system-aarch64 build it will fail thanks to the change to 12 bit
>> pages. The boards are still available for the qemu-system
As another test (still running qemu-git-2.1.0-rc2-git-20140721), I
disabled NTP on the two servers (and rebooted them), but left it running
on the guest.
When doing the migration, server a (where the guest was running) had an
NTP offset of -3.037619 s, and server b was at -3.337718 s. The guest
wa
On 08/01/2014 09:19 AM, Paolo Bonzini wrote:
> Il 01/08/2014 16:02, Joel Schopp ha scritto:
I think the patch is right but, besides these considerations, does this
bug still manifest itself after Andrew fixed the start address of the
device at 0x9001 (IIRC it was the pl031)?
>>
The test in configure checks for struct mmsghdr in sys/socket.h,
but actual source (net/l2tpv3.c) includes a linux-specific header,
linux/ip.h. This fails on at least kFreeBSD (Debian with FreeBSD
header and glibc), because glibc declares mmsghdr but does not
provide linux/ip.h.
Probably the conf
This patch series adds inbound migrate capability from qemu-kvm version
1.0. The main ideas are those set out in Cole Robinson's patch here:
http://pkgs.fedoraproject.org/cgit/qemu.git/tree/0001-Fix-migration-from-qemu-kvm.patch?h=f20
however, rather than patching statically (and breaking inbound
m
Add a machine type pc-1.0-qemu-kvm for live migrate compatibility
with qemu-kvm version 1.0.
Signed-off-by: Alex Bligh
---
hw/acpi/piix4.c | 49 --
hw/i386/pc_piix.c| 31 +
hw/timer/i8254_common.c | 4
Add a configure option --enable-pc-1-0-qemu-kvm and the
corresponding --disable-pc-1-0-qemu-kvm, defaulting
to disabled.
Rename machine type pc-1.0 to pc-1.0-qemu-git.
Make pc-1.0 machine type an alias of either pc-1.0-qemu-kvm
or pc-1.0-qemu-git depending on the value of the config
option.
Sign
Some non-linux systems, for example a system with
FreeBSD kernel and glibc, may declare struct mmsghdr
(in glibc) but may not have linux-specific header
file linux/ip.h. The actual implementation in qemu
includes this linux-specific header file unconditionally,
so compilation fails if it is not pr
Il 30/07/2014 17:20, Alex Bennée ha scritto:
> Hi,
>
> Not too much has changed:
>
> * added a review tag
> * fixed up review comments
> * added some notes about benchmark results
> * added a patch to disable ARMv5 in AArch64 build
>
> The most important thing is I've measured a 25-30% i
On 31.07.2014 09:51, Benoît Canet wrote:
The Saturday 26 Jul 2014 à 21:22:05 (+0200), Max Reitz wrote :
Depending on the changed options and the image format,
bdrv_amend_options() may take a significant amount of time. In these
cases, a way to be informed about the operation's status is desirab
On 31.07.2014 09:56, Benoît Canet wrote:
The Saturday 26 Jul 2014 à 21:22:06 (+0200), Max Reitz wrote :
Now that bdrv_amend_options() supports a status callback, use it to
display a progress report.
Signed-off-by: Max Reitz
---
qemu-img.c | 26 +++---
1 file changed, 23
On 06/12/2014 05:03 AM, Markus Armbruster wrote:
Michael Tokarev writes:
10.06.2014 10:34, Paolo Bonzini wrote:
Il 10/06/2014 08:30, Michael Tokarev ha scritto:
Hello.
The question is: are the drive shortcuts - -cdrom, -hda, -hdb etc -
supposed to work in -machine q35 too? Or are they mer
02.08.2014 00:10, John Snow wrote:
[]
> For at least the immediate future, the AHCI device doesn't support the
> mixed-mode SATA/PATA access models, though I suppose we could, it seems like
> a more obvious and simple solution to just allow the shorthand syntactic
> sugar commands to use the nat
On 31.07.2014 10:06, Benoît Canet wrote:
The Saturday 26 Jul 2014 à 21:22:08 (+0200), Max Reitz wrote :
The only really time-consuming operation potentially performed by
qcow2_amend_options() is zero cluster expansion when downgrading qcow2
images from compat=1.1 to compat=0.10, so report status
On 31.07.2014 10:30, Benoît Canet wrote:
The Saturday 26 Jul 2014 à 21:22:11 (+0200), Max Reitz wrote :
Add some tests for progress output to 061.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/061 | 27 +++
tests/qemu-iotests/061.out | 32 ++
On 08/01/2014 02:18 PM, Max Reitz wrote:
>>> +if (status_cb) {
>>> +status_cb(bs, *visited_l1_entries << (s->l2_bits +
>>> s->cluster_bits),
>>> + l1_entries << (s->l2_bits + s->cluster_bits));
>> Shifting is a multiplication so it keep proportionality inta
On Fri, Aug 01, 2014 at 11:15:29AM +0800, Gareth wrote:
> Hi all
>
> What does '-enable-kvm' option mean? I have heard two versions of answers:
It's a shortcut for:
$qemu -machine accel=kvm
> a) guest OS would have /dev/kvm device and which could help vm in guest OS
> (nested vm)
That's nest
On 01.08.2014 22:38, Eric Blake wrote:
On 08/01/2014 02:18 PM, Max Reitz wrote:
+if (status_cb) {
+status_cb(bs, *visited_l1_entries << (s->l2_bits +
s->cluster_bits),
+ l1_entries << (s->l2_bits + s->cluster_bits));
Shifting is a multiplication so it k
On 31.07.2014 10:24, Benoît Canet wrote:
The Saturday 26 Jul 2014 à 21:22:10 (+0200), Max Reitz wrote :
Currently, we have a bitmap for keeping track of which clusters have
been created during the zero cluster expansion process. This was
necessary because we need to properly increase the refcou
On 1 August 2014 17:06, Peter Maydell wrote:
> I'm taking the first two of these into target-arm.next because
> they're obvious standalone bugfixes. I need to think about the
> last three a bit more: I dislike just dropping the ARMv5 CPUs
> from qemu-system-aarch64, it's kind of arbitrary.
So:
*
On 1 August 2014 17:41, Michael Roth wrote:
> On behalf of the QEMU Team, I'd like to announce the availability of
> the QEMU 2.1.0 release. This release contains 2200+ commits from 180
> authors.
> Thank you to everyone involved!
Yep, thanks to everybody who helped get this one out of the door;
2014-08-01 23:25 GMT+08:00 Alex Williamson :
> On Fri, 2014-08-01 at 09:35 +0800, Le Tan wrote:
>> Hi Alex,
>>
>> 2014-07-30 22:46 GMT+08:00 Alex Williamson :
>> > On Wed, 2014-07-30 at 22:16 +0800, Le Tan wrote:
>> >> Hi Michael,
>> >>
>> >> 2014-07-30 21:16 GMT+08:00 Michael S. Tsirkin :
>> >> >
On Sat, Aug 2, 2014 at 1:35 AM, Peter Maydell wrote:
> On 26 June 2014 06:02, Alistair Francis wrote:
>> Call the new pmccntr_sync() function when there is a possibility
>> of swapping ELs (I.E. when there is an exception)
>>
>> Signed-off-by: Alistair Francis
>> ---
>>
>> target-arm/helper-a64
On 07/31/2014 10:01 AM, Stefan Hajnoczi wrote:
On Mon, Jul 07, 2014 at 02:18:07PM -0400, John Snow wrote:
+/*** IO macros for the AHCI memory registers. ***/
+#define void_incr(vptr, OFST) ((void *)((char *)(vptr) + (OFST)))
I'm pretty sure QEMU takes advantage of GCC's void pointer arithmetic
Depending on the changed options and the image format,
bdrv_amend_options() may take a significant amount of time. In these
cases, a way to be informed about the operation's status is desirable.
Since the operation is rather complex and may fundamentally change the
image, implementing it as AIO or
As soon as options is set in img_amend(), it needs to be freed before
the function returns. This leak is rather insignificant, as qemu-img
will exit subsequently anyway, but there's no point in not fixing it.
Signed-off-by: Max Reitz
Reviewed-by: Eric Blake
Reviewed-by: Benoit Canet
---
qemu-i
The main purpose of this series is to add a progress report to
qemu-img amend. This is achieved by adding a callback function to
bdrv_amend_options() - the reasons for this choice are explained in
patch 1.
While adapting qcow2's expand_zero_clusters_in_l1() accordingly, I
noticed a way to simplify
Now that bdrv_amend_options() supports a status callback, use it to
display a progress report.
Signed-off-by: Max Reitz
---
qemu-img-cmds.hx | 4 ++--
qemu-img.c | 25 ++---
qemu-img.texi| 2 +-
3 files changed, 25 insertions(+), 6 deletions(-)
diff --git a/qemu-
The only really time-consuming operation potentially performed by
qcow2_amend_options() is zero cluster expansion when downgrading qcow2
images from compat=1.1 to compat=0.10, so report status of that
operation and that operation only through the status CB.
For this, approximate the progress as th
Reading the refcount of a cluster is an operation which can be useful in
all of the qcow2 code, so make that function globally available.
While touching this function, amend the comment describing the "addend"
parameter: It is (no longer, if it ever was) necessary to have it set to
-1 or 1; any va
Currently, we have a bitmap for keeping track of which clusters have
been created during the zero cluster expansion process. This was
necessary because we need to properly increase the refcount for shared
L2 tables.
However, now we can simply take the L2 refcount and use it for the
cluster allocat
Add some tests for progress output to 061.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/061 | 25 +
tests/qemu-iotests/061.out | 30 ++
tests/qemu-iotests/group | 2 +-
3 files changed, 56 insertions(+), 1 deletion(-)
diff --git a/te
On Sat, Aug 2, 2014 at 12:03 AM, Stefan Hajnoczi wrote:
> On Fri, Aug 01, 2014 at 10:52:55PM +0800, Ming Lei wrote:
>> On Fri, Aug 1, 2014 at 9:48 PM, Ming Lei wrote:
>> > On Fri, Aug 1, 2014 at 9:13 PM, Stefan Hajnoczi
>> > wrote:
>> >> On Fri, Aug 01, 2014 at 10:54:02AM +0800, Ming Lei wrote:
ARMv7M has it's own bootloader (separate from the regular ARM
bootloader) that is elf aware. It is able to load elfs but it does
not set the program counter to the elf entry point. Make it more
consistent with the regular ARM bootloader by setting the program
counter to the given elf entry point.
On 2014-08-01 19:16, Alex Williamson wrote:
>> Also, it may let some of our device
>> models deviate from their real versions (I suppose, e.g., none of the
>> e1000 devices we currently emulate exposed FLR).
>
> Of course, but what are the chances that the driver will care?
No drivers of GPOSes,
101 - 158 of 158 matches
Mail list logo
