From: Marc-André Lureau
Once the middle mode is removed, the generated marshal functions will no
longer be exported.
Signed-off-by: Marc-André Lureau
---
monitor.c | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git a/monitor.c b/monitor.c
index 7e8ad0c..410c3a
From: Marc-André Lureau
Move the examples in the json file with the rest of the documentation to
avoid duplication.
Signed-off-by: Marc-André Lureau
---
docs/qmp/qmp-events.txt | 664
qapi/block-core.json| 59 -
qapi/block.json
From: Marc-André Lureau
The marshal functions are no longer exported, they are registered in the
dispatch table instead. The following patches will make use of
qmp_dispatch(). This patch temporarily breaks qmp/hmp commands.
Signed-off-by: Marc-André Lureau
---
Makefile | 2 +-
qmp-
From: Marc-André Lureau
It's static file now.
Signed-off-by: Marc-André Lureau
---
Makefile.target| 7 +-
qmp-commands-old.h | 683 +
qmp-commands.hx| 683 -
3 files changed, 685 i
From: Marc-André Lureau
Now that the register function is always generated, we can
remove the so-called "middle" mode to the generator script.
Signed-off-by: Marc-André Lureau
---
scripts/qapi-commands.py | 29 +
1 file changed, 5 insertions(+), 24 deletions(-)
dif
From: Marc-André Lureau
So we can get rid of the static qmp_cmds table.
Signed-off-by: Marc-André Lureau
---
monitor.c | 25 ++---
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/monitor.c b/monitor.c
index bfa0329..a2eb228 100644
--- a/monitor.c
+++ b/monit
From: Marc-André Lureau
Learn a new type of command, QmpCommandFuncAsync. They can return later
thanks to QmpReturn. This commit introduces the new types and register
functions.
Signed-off-by: Marc-André Lureau
---
include/qapi/qmp/dispatch.h | 5 +
qapi/qmp-dispatch.c | 3 +++
q
From: Marc-André Lureau
Replace the old "middle mode" dispatch code using the manually
maintained table by the one generated by qapi scripts.
Signed-off-by: Marc-André Lureau
---
monitor.c | 316 +++---
1 file changed, 34 insertions(+), 2
From: Marc-André Lureau
---
monitor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/monitor.c b/monitor.c
index 4deef29..25f9608 100644
--- a/monitor.c
+++ b/monitor.c
@@ -306,7 +306,7 @@ static void monitor_flush_locked(Monitor *mon)
return;
}
From: Marc-André Lureau
Let the caller know if the update is immediate or async.
Signed-off-by: Marc-André Lureau
---
hw/display/qxl-render.c | 5 +++--
hw/display/qxl.c| 8
hw/display/qxl.h| 2 +-
include/ui/console.h| 3 ++-
ui/console.c| 14 +
From: Marc-André Lureau
The table is no longer used.
Signed-off-by: Marc-André Lureau
---
monitor.c | 7 -
qmp-commands-old.h | 554 -
2 files changed, 561 deletions(-)
delete mode 100644 qmp-commands-old.h
diff --git a/monitor.c
From: Marc-André Lureau
Add a new QmpClient structure holding the dispatch return callback
and the list of pending QmpReturns.
When a client disconnects, call qmp_client_destroy(). This will remove
all pending returns from the client list, and prevent a reply from being
sent later to new clients
From: Marc-André Lureau
In order to prepare for the async support, give an optionnal qdict for
the dispatch call to be used for the reply. The qemu monitor will have
the request "id" pre-filled.
Signed-off-by: Marc-André Lureau
---
include/qapi/qmp/dispatch.h | 2 +-
monitor.c
From: Marc-André Lureau
Learn a new async command to make a correct screendump.
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=1230527
Signed-off-by: Marc-André Lureau
---
qapi-schema.json | 21 +++-
ui/console.c | 59 +++
From: Marc-André Lureau
The async support mandates that request have an 'id' (see documentation
in following patch).
Signed-off-by: Marc-André Lureau
---
qapi/qmp-dispatch.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/qapi/qmp-dispatch.c b/qapi/qmp-dispatch.c
index 83ecab5..73ba3a
From: Marc-André Lureau
Presumably 0.15 was the version it was first introduced, but
qmp keeps evolving. There is no point in having that version
has test prefix, qmp makes more sense.
Signed-off-by: Marc-André Lureau
---
tests/test-qmp-commands.c | 10 +-
1 file changed, 5 insertions(
Originally, timers were ticks based, and it made sense to
add ticks to current time to know when to trigger an alarm.
But since commit:
7447545 change all other clock references to use nanosecond resolution accessors
All timers use nanoseconds and we need to convert ticks to nanoseconds, by
doin
From: Marc-André Lureau
We could have arbitrary async command name, but it make sense to use a
specific name to avoid confusion.
Signed-off-by: Marc-André Lureau
---
scripts/qapi.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/scripts/qapi.py b/scripts/qapi.py
index 96901ab..d614673 100
From: Marc-André Lureau
Commands with the 'async' key will be registered as async type (see
previous commit), and will allow a synchronous (in command cb) or
asynchronous return (when ready, in idle etc).
Ex:
{ 'command': 'foo-async, 'data': {'arg': 'str'}, async: true }
Signed-off-by: Marc-And
From: Marc-André Lureau
Copy 'id' from request to reply dict. This can be done earlier, such as
done by the monitor (because the qemu monitor may reply directly without
qmp_dispatch), but is now done as well in qmp_dispatch() as convenience
for other users such as QGA and tests.
Signed-off-by: M
Originally, timers were ticks based, and it made sense to
add ticks to current time to know when to trigger an alarm.
But since commit:
7447545 change all other clock references to use nanosecond resolution accessors
All timers use nanoseconds and we need to convert ticks to nanoseconds, by
doin
muldiv64() is used to convert nanoseconds to microseconds.
x = muldiv64(qemu_clock_get_ns(..), 100, get_ticks_per_sec());
As get_ticks_per_sec() is 10^9, it can be replaced by:
x = qemu_clock_get_us(..);
Signed-off-by: Laurent Vivier
Reviewed-by: Stefan Hajnoczi
---
net/dump.c |
From: Marc-André Lureau
Check that async disaptch works.
Signed-off-by: Marc-André Lureau
---
tests/qapi-schema/qapi-schema-test.json | 2 ++
tests/qapi-schema/qapi-schema-test.out | 5 +++
tests/test-qmp-commands.c | 61 +
3 files changed, 68 i
From: Marc-André Lureau
Introduce QmpDispatchReturn, a callback called when a command reply is
ready to be sent. Future patches will extend the concept to allow async
replies.
QmpReturn and associated functions is used internally for sync
fonctions, but will be the basis of a async context (the
Originally, timers were ticks based, and it made sense to
add ticks to current time to know when to trigger an alarm.
But since commit:
7447545 change all other clock references to use nanosecond resolution accessors
All timers use nanoseconds and we need to convert ticks to nanoseconds.
As get
From: Marc-André Lureau
Add a function to be called when an async graphic update is done.
Signed-off-by: Marc-André Lureau
---
hw/display/qxl-render.c | 9 +++--
include/ui/console.h| 1 +
ui/console.c| 4
3 files changed, 12 insertions(+), 2 deletions(-)
diff --git a
From: Marc-André Lureau
Signed-off-by: Marc-André Lureau
---
docs/qmp/qmp-spec.txt | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/docs/qmp/qmp-spec.txt b/docs/qmp/qmp-spec.txt
index 4c28cd9..f1af7f7 100644
--- a/docs/qmp/qmp-spec.txt
+++ b/docs/qmp/qmp-sp
hpet defines a clock period in femtoseconds but
then converts it to nanoseconds to use the internal
timers.
We can define the period in nanoseconds and use it
directly, this allows to remove muldiv64().
We only need to convert the period to femtoseconds
to put it in internal hpet capability regis
From: Marc-André Lureau
Existing clients may not handle async replies very well. In order
to avoid the potential issues, let's introduce a capability that
the client must declare in order to make use of async commands.
Eventually, client should already handle unexpected events after a
command is
On Thu 17 Sep 2015 03:48:09 PM CEST, Kevin Wolf wrote:
> @@ -1929,6 +1925,11 @@ void bdrv_close(BlockDriverState *bs)
> bdrv_unref(backing_hd);
> }
>
> +if (bs->file != NULL) {
> +bdrv_unref(bs->file->bs);
> +bs->file = NULL;
> +}
>
Originally, timers were ticks based, and it made sense to
add ticks to current time to know when to trigger an alarm.
But since commit:
7447545 change all other clock references to use nanosecond resolution accessors
All timers use nanoseconds and we need to convert ticks to nanoseconds, by
doin
The following changes since commit 8a47d575dfac0f6675e2ac56c5921cc520d021a6:
Merge remote-tracking branch 'remotes/weil/tags/pull-wxx-20150924' into
staging (2015-09-24 22:09:41 +0100)
are available in the git repository at:
g...@github.com:vivier/qemu.git tags/pull-muldiv64-201
On Tue, Sep 01, 2015 at 12:03:08PM +0900, Hitoshi Mitake wrote:
> This patchset has two patches. The first one is a defensive purpose
> for rare cases. It is an improvement of the previous commit
> 96b14ff85acf. The second one is refining discard operation caused by
> fstrim command, etc. Current s
Jason Wang writes:
> On 09/24/2015 07:52 PM, Markus Armbruster wrote:
>> Yang Hongyang writes:
>>
>>> On 09/24/2015 04:41 PM, Markus Armbruster wrote:
Yang Hongyang writes:
[...]
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 2bada60..546500a 100644
> --- a/qapi-sch
On 09/25/2015 02:08 AM, Yang Hongyang wrote:
> This patchset addressed Markus comment on netfilter patch
> series, most of them are comment fixes.
>
> It is based on jason's net tree:
> https://github.com/jasowang/qemu/tree/net
If that tree is not yet merged mainline, wouldn't it be better to squ
Originally, timers were ticks based, and it made sense to
add ticks to current time to know when to trigger an alarm.
But since commit:
7447545 change all other clock references to use nanosecond resolution accessors
All timers use nanoseconds and we need to convert ticks to nanoseconds, by
doin
Thomas Huth writes:
> On 24/09/15 20:57, Markus Armbruster wrote:
>> Several devices don't survive object_unref(object_new(T)): they crash
>> or hang during cleanup, or they leave dangling pointers behind.
>>
>> This breaks at least device-list-properties, because
>> qmp_device_list_properties()
it's a simplier way suggested by Michael S. Tsirkin
to workaround virtio bug reported earlier:
http://lists.nongnu.org/archive/html/qemu-devel/2015-08/msg00522.html
where virtio can't handle buffer that crosses border
between 2 DIMM's (i.e. 2 MemoryRegions).
idea is to leave gaps between DIMMs, ma
Hi
On Fri, Sep 25, 2015 at 4:00 PM, Markus Armbruster wrote:
> VSERPORT_CHANGE is emitted when the guest opens or closes a
> virtio-serial port. The event's member "id" identifies the port.
>
> When several events arrive quickly, throttling drops all but the last
> of them. Because of that, a Q
On 09/25/2015 07:41 AM, Alberto Garcia wrote:
> Disabling I/O limits from a BDS also drains all pending throttled
> requests, so it should be done at the beginning of bdrv_close() with
> the rest of the bdrv_drain() calls before the BlockDriver is closed.
Can this be abused? If I have a guest runn
setting gap to non 0 value will make sparse DIMM
address auto allocation, leaving gaps between
a new DIMM address and preceeding existing DIMM.
Signed-off-by: Igor Mammedov
---
hw/i386/pc.c | 2 +-
hw/mem/pc-dimm.c | 13 +++--
hw/ppc/spapr.c | 2 +-
includ
On Fri 25 Sep 2015 04:22:26 PM CEST, Eric Blake wrote:
>> Disabling I/O limits from a BDS also drains all pending throttled
>> requests, so it should be done at the beginning of bdrv_close() with
>> the rest of the bdrv_drain() calls before the BlockDriver is closed.
>
> Can this be abused? If I h
This should help clarify the purpose of the function that returns
the host system's CPU cycle count.
Signed-off-by: Christopher Covington
---
bsd-user/main.c | 2 +-
cpus.c| 6 +++---
hw/intc/xics.c| 2 +-
hw/ppc/ppc.c | 4 ++--
include/
On 09/25/2015 06:39 AM, Andreas Färber wrote:
> All integers would get parsed by strtoll(), not handling the case of
> UINT64 properties with the most significient bit set.
>
> Implement a .type_uint64 visitor callback, reusing the existing
> parse_str() code through a new argument, using strtoull
On 09/25/2015 06:39 AM, Andreas Färber wrote:
> In addition to -42 also parse the maximum int64.
>
> Signed-off-by: Andreas Färber
> ---
> tests/test-string-input-visitor.c | 8
> 1 file changed, 8 insertions(+)
Shouldn't we also add tests of one-beyond-range, to have coverage of
expec
On 09/25/2015 06:39 AM, Andreas Färber wrote:
> Test parsing of decimal and hexadecimal uint64 numbers with most
> significient bit set.
s/significient/significant/
>
> Signed-off-by: Andreas Färber
> ---
> tests/test-string-input-visitor.c | 23 +++
> 1 file changed, 23 in
Signed-off-by: Markus Armbruster
---
docs/qmp/qmp-events.txt | 12
docs/qmp/qmp-spec.txt | 5 +
2 files changed, 17 insertions(+)
diff --git a/docs/qmp/qmp-events.txt b/docs/qmp/qmp-events.txt
index d92cc48..d2f1ce4 100644
--- a/docs/qmp/qmp-events.txt
+++ b/docs/qmp/qmp-even
On 09/25/2015 06:39 AM, Andreas Färber wrote:
> Add a test for parsing and setting a uint64 property.
>
> Signed-off-by: Andreas Färber
> ---
> MAINTAINERS | 1 +
> tests/Makefile | 3 ++
> tests/check-qom-props.c | 120
>
On 09/25/2015 06:39 AM, Andreas Färber wrote:
> Instead of using int64_t for qemu_strtoll() and uiint64_t for
s/uiint64/uint64/
> qemu_strtoull(), use long long and unsigned long long as their name
> implies.
>
> The only affected callers are our test cases.
>
> This prepares for following chec
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> This is mainly to please the doc generation that requires comment block
> before the declaration.
>
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json | 6 +-
> 1 file changed, 5 insertions(+)
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Signed-off-by: Marc-André Lureau
> ---
> qapi/block.json | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Adding qemu-trivial; this can be taken now through trivial tree without
waiting for pending
Andreas Färber writes:
> Am 25.09.2015 um 12:17 schrieb Thomas Huth:
>> On 24/09/15 20:57, Markus Armbruster wrote:
>>> The test doesn't check that the output makes any sense, only that QEMU
>>> survives. Useful since we've had an astounding number of crash bugs
>>> around there.
>>>
>>> In fact
Originally, timers were ticks based, and it made sense to
add ticks to current time to know when to trigger an alarm.
But since commit:
7447545 change all other clock references to use nanosecond resolution accessors
All timers use nanoseconds and we need to convert ticks to nanoseconds, by
doin
On Fri, Sep 25, 2015 at 02:39:45PM +0200, Andreas Färber wrote:
> Add a test for parsing and setting a uint64 property.
>
> Signed-off-by: Andreas Färber
> ---
> MAINTAINERS | 1 +
> tests/Makefile | 3 ++
> tests/check-qom-props.c | 120
> ++
muldiv64() is used to convert microseconds into CPU ticks.
But it is not clear and not commented. This patch uses macro
to clearly identify what is used: time, CPU frequency and ticks.
For an elapsed time and a given frequency, we compute how many ticks
we have.
Signed-off-by: Laurent Vivier
Re
Yang Hongyang writes:
> On 09/24/2015 05:12 PM, Markus Armbruster wrote:
>> Yang Hongyang writes:
>>
>>> This filter is to buffer/release packets, this feature can be used
>>> when using MicroCheckpointing, or other Remus like VM FT solutions, you
>>
>> What's "Remus"?
>
> Remus is an opensource
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> This was initially done to add qmp_capabilities documentation to the
> schema. Then I figured it would also help to get rid of the "middle
> mode" monitor dispatch code.
>
> Signed-off-by: Marc-André Lureau
Jason Wang writes:
> On 09/25/2015 03:18 PM, Yang Hongyang wrote:
>>
>>
>> On 09/24/2015 05:12 PM, Markus Armbruster wrote:
>>> Yang Hongyang writes:
[...]
+static ssize_t filter_buffer_receive_iov(NetFilterState *nf,
+ NetClientState *sender,
>>
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Moving the remaining bits of documentation to the schema files.
>
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json | 48 ++-
> qmp-commands.hx | 62
> --
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Add some missing double-#, the doc parser can't easily distinguish doc
> comments from comments to be ignored otherwise.
>
> Also add some more section headings.
>
> Signed-off-by: Marc-André Lureau
> ---
On 25/09/2015 13:35, David Gibson wrote:
> Hi Alex,
>
> Here are the parts of my recent series to allow VFIO devices on the
> spapr-pci-host-bridge device which affect the core VFIO code. They've
> been revised according to the comments from yourself and others.
>
> There's also one patch for
- Original Message -
> On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> > From: Marc-André Lureau
> >
> > Moving the remaining bits of documentation to the schema files.
> >
> > Signed-off-by: Marc-André Lureau
> > ---
> > qapi-schema.json | 48 +++
On Fri, 2015-09-18 at 16:30 +0800, Tiejun Chen wrote:
> Although we already have 'gfx_passthru' in b_info, this doesn't suffice
> after we want to handle IGD specifically. Now we define a new field of
> type, gfx_passthru_kind, to indicate we're trying to pass IGD. Actually
> this means we can bene
Programmingkid writes:
> On Sep 24, 2015, at 2:57 AM, Markus Armbruster wrote:
>
>> Programmingkid writes:
>>
>>> On Sep 23, 2015, at 4:35 PM, Peter Maydell wrote:
>>>
On 17 September 2015 at 21:17, Programmingkid
wrote:
> Add "Mount Image File..." and a "Eject Image File" menu
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Learn a few more markups used for API documentation.
>
> Signed-off-by: Marc-André Lureau
> ---
> scripts/texi2pod.pl | 44 +++-
> 1 file changed, 43 insertions(+),
Thomas Huth writes:
> On 25/09/15 10:03, Yang Hongyang wrote:
>>
>>
>> On 09/24/2015 05:12 PM, Markus Armbruster wrote:
>>> Yang Hongyang writes:
>> [...]
diff --git a/vl.c b/vl.c
index ec589e2..3cf89d5 100644
--- a/vl.c
+++ b/vl.c
@@ -2794,7 +2794,12 @@ static bool ob
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Learn to generate info/html/pdf/man documentation for QEMU and agent QMP
> APIs.
>
> This allows to provide missing agent documentation, and should help
"allows to" is not idiomatic English (it is missing a
From: Peter Lieven
st.st_blocks is always counted in 512 byte units. Do not
use st.st_blksize as multiplicator which may be larger.
Cc: qemu-sta...@nongnu.org
Signed-off-by: Peter Lieven
Reviewed-by: Max Reitz
Reviewed-by: Jeff Cody
Message-id: 1440067607-14547-1-git-send-email...@kamp.de
Sig
From: Wen Congyang
We will copy data in before_write_notifier to do backup.
It is a nested I/O request, so we cannot do copy-on-read.
The steps to reproduce it:
1. -drive copy-on-read=on,... // qemu option
2. drive_backup -f disk0 /path_to_backup.img // monitor command
Signed-off-by: Wen Congy
From: Hitoshi Mitake
In the commit 96b14ff85acf, requests for overlapping areas are
serialized. However, it cannot handle a case of non overlapping
requests. In such a case, min_dirty_data_idx and max_dirty_data_idx
can be overwritten by the requests and invalid inode update can
happen e.g. a cas
The following changes since commit eb9d0ea063fc7bdfab76b84085602a9e48d13ec7:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20150924'
into staging (2015-09-24 01:32:11 +0100)
are available in the git repository at:
g...@github.com:codyprime/qemu-kvm-jtc.git tags/block-
From: Wen Congyang
In some cases, we need to disable copy-on-read, and just
read the data.
Signed-off-by: Wen Congyang
Message-id: 1441682913-14320-2-git-send-email-we...@cn.fujitsu.com
Signed-off-by: Jeff Cody
---
block/io.c| 12 +++-
include/block/block.h | 9 ++---
From: Hitoshi Mitake
This patch refines discard support of the sheepdog driver. The
existing discard mechanism was implemented on SD_OP_DISCARD_OBJ, which
was introduced before fine grained reference counting on newer
sheepdog. It doesn't care about relations of snapshots and clones and
discards
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Since some commands are using 'gen': false, they are not registered
> automatically by the generator. Register manually instead.
>
> Signed-off-by: Marc-André Lureau
> ---
> monitor.c | 10 ++
> 1
On 09/25/2015 09:29 AM, Marc-André Lureau wrote:
>
>
> - Original Message -
>> On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
>>> From: Marc-André Lureau
>>>
>>> Moving the remaining bits of documentation to the schema files.
>>>
>>> Signed-off-by: Marc-André Lureau
>>> ---
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Clean-up qmp-commands.hx from examples.
>
> Signed-off-by: Marc-André Lureau
> ---
> qapi-schema.json | 1128 +++-
> qapi/block-core.json | 365 +
> qapi/block.json | 32 +
> qa
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> So we can get rid of the static qmp_cmds table.
>
> Signed-off-by: Marc-André Lureau
> ---
> monitor.c | 25 ++---
> 1 file changed, 14 insertions(+), 11 deletions(-)
Reviewed-by: Eric
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> The marshal functions are no longer exported, they are registered in the
> dispatch table instead. The following patches will make use of
> qmp_dispatch(). This patch temporarily breaks qmp/hmp commands.
Sho
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> The table is no longer used.
>
> Signed-off-by: Marc-André Lureau
> ---
> monitor.c | 7 -
> qmp-commands-old.h | 554
> -
> 2 files changed,
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> ---
> monitor.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Trivial, can be applied now without waiting for pending qapi patches.
Reviewed-by: Eric Blake
>
> diff --git a/monitor.c b/monitor
Yang Hongyang writes:
> This patchset addressed Markus comment on netfilter patch
> series, most of them are comment fixes.
>
> It is based on jason's net tree:
> https://github.com/jasowang/qemu/tree/net
>
> Signed-off-by: Yang Hongyang
I think we have enough issues to warrant a full respin.
On 23 September 2015 at 16:06, Programmingkid wrote:
> Removes the open dialog code that runs when no arguments
> are supplied with QEMU. Not everyone needs a hard drive
> or cdrom to boot their target. A user might only need to
> use their target's bios to do work. With that said,
> this patch re
From: Liu Yuan
With reopen supported, block-commit (and offline commit) is now supported for
image files whose base image uses the Sheepdog protocol driver.
Cc: qemu-devel@nongnu.org
Cc: Jeff Cody
Cc: Kevin Wolf
Cc: Stefan Hajnoczi
Signed-off-by: Liu Yuan
Message-id: 1440730438-24676-1-git-s
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Presumably 0.15 was the version it was first introduced, but
> qmp keeps evolving. There is no point in having that version
> has test prefix, qmp makes more sense.
s/has/be the/
>
> Signed-off-by: Marc-An
On 09/24/2015 02:34 AM, Markus Armbruster wrote:
> John Snow writes:
>
> [...]
>> Oh, I see: you're saying ...
>>
>> each action fetches the property, and if it's true, fail (for 2.5, at
>> least) with e.g. a message saying "This property is not [yet?] supported
>> for this action"
>
> Yes.
>
On Sep 25, 2015, at 12:09 PM, Peter Maydell wrote:
> On 23 September 2015 at 16:06, Programmingkid
> wrote:
>> Removes the open dialog code that runs when no arguments
>> are supplied with QEMU. Not everyone needs a hard drive
>> or cdrom to boot their target. A user might only need to
>> use t
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Now that the register function is always generated, we can
> remove the so-called "middle" mode to the generator script.
>
> Signed-off-by: Marc-André Lureau
> ---
> scripts/qapi-commands.py | 29 +
On 25.09.2015 17:42, Christopher Covington wrote:
> This should help clarify the purpose of the function that returns
> the host system's CPU cycle count.
+1
Best regards,
Sergey
On Sep 23, 2015, at 4:35 PM, Peter Maydell wrote:
> On 17 September 2015 at 21:17, Programmingkid
> wrote:
>> Add "Mount Image File..." and a "Eject Image File" menu items to
>> cocoa interface. This patch makes sharing files between the
>> host and the guest user-friendly.
>>
>> The "Mount Im
Hi
- Original Message -
> On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> > From: Marc-André Lureau
> >
> > Hi,
> >
> > I have grown a qapi branch during the past 2 months that was
> > post-poned for review until the introspection and other fixes got
> > merged or ready.
>
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Move the examples in the json file with the rest of the documentation to
> avoid duplication.
>
> Signed-off-by: Marc-André Lureau
> ---
> docs/qmp/qmp-events.txt | 664
> -
From: Peter Lieven
If the file is readonly its not expected to grow so
save the blocking call to nfs_fstat_async and use
the value saved at connection time. Also important
the monitor (and thus the main loop) will not hang
if block device info is queried and the NFS share
is unresponsive.
Signed
On 25 September 2015 at 09:12, Programmingkid wrote:
>
> On Sep 25, 2015, at 12:09 PM, Peter Maydell wrote:
>> (Also, isn't a simple test on gArgc going to cause us to put up
>> the dialog box even if qemu was started from the command line with
>> no arguments?)
>
> I suppose you are right. Will m
marcandre.lur...@redhat.com writes:
> From: Marc-André Lureau
>
> Hi,
>
> I have grown a qapi branch during the past 2 months that was
> post-poned for review until the introspection and other fixes got
> merged or ready.
>
> It could be splitted roughly in 3 parts, but since they depend on each
On 09/25/2015 08:03 AM, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> As the name suggests, the qapi2texi script converts JSON QAPI
> description into a standalone texi file suitable for different target
> formats.
>
> It parses the following kind of blocks with some little va
On 09/25/2015 08:00 AM, Markus Armbruster wrote:
> Make the variables holding the event QDict instead of QObject.
>
> Signed-off-by: Markus Armbruster
> ---
> monitor.c | 38 +++---
> 1 file changed, 19 insertions(+), 19 deletions(-)
>
> diff --git a/monitor.c b/
On 25/09/2015 16:42, Christopher Covington wrote:
> This should help clarify the purpose of the function that returns
> the host system's CPU cycle count.
>
> Signed-off-by: Christopher Covington
Acked-by: Paolo Bonzini
Good idea!
Paolo
> ---
> bsd-user/main.c | 2 +-
> cpus.c
On 23 September 2015 at 17:57, Programmingkid wrote:
> This patch prevents the user from accidentally quitting QEMU by pushing
> Command-Q or by pushing the close button on the main window. When
> the user does one of these two things, a dialog box appears verifying
> with the user if he or she wa
On 23 September 2015 at 18:21, Programmingkid wrote:
> When the user puts QEMU in the background while holding
> down a key, QEMU will not receive the keyup event when
> the user lets go of the key. When the user goes back to
> QEMU, QEMU will think the key is still down causing
> stuck key sympto
On 09/25/2015 08:00 AM, Markus Armbruster wrote:
> The event throttling state machine is hard to understand. I'm not
> sure it's entirely correct. Rewrite it in a more straightforward
> manner:
>
> State 1: No event sent recently (less than evconf->rate ns ago)
>
> Invariant: evstate->timer
1 - 100 of 285 matches
Mail list logo
