On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
@@ -2234,13 +2234,24 @@ static void gen_st_asi(DisasContext *dc, TCGv src, TCGv
addr,
switch (da.type) {
case GET_ASI_EXCP:
break;
-case GET_ASI_DTWINX: /* Reserved for stda. */
-gen_exception(dc, TT_ILL_INSN);
-
On 11.10.2016 15:38, Peter Maydell wrote:
> On 11 October 2016 at 14:32, Thomas Huth wrote:
>> The pxe-test is run for three different targets now (x86_64, i386
>> and ppc64), and the bios-tables-test is run for two targets (x86_64
>> and i386). But each of the tests is using an invariant name for
First of all, a correction:
>> The exception is that there are places
>> where we don't have a BlockBackend and thus call
>> bdrv_drain/bdrv_co_drain instead of blk_drain/blk_co_drain
Nevermind---it's just that there is no blk_drained_begin/end yet.
On 11/10/2016 13:00, Kevin Wolf wrote:
> Actua
On Tue, Oct 04, 2016 at 09:43:31AM +0300, Emil Condrea wrote:
> Fixes:
> * WARNING: line over 80 characters
>
> Signed-off-by: Emil Condrea
> ---
> hw/block/xen_disk.c | 3 ++-
> hw/char/xen_console.c| 6 --
> hw/display/xenfb.c | 30
On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
+uint64_t size = 1024ULL * (8 << 3 * TTE_PGSIZE(tlb[i].tte));
Your previous expression, 8192 << 3 * TTE_PGSIZE is clearer. Perhaps this
itself should be extracted as a macro?
+if ((new_vaddr == vaddr) || ((new_
On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
+uint64_t mask = 1ULL + ~(8192ULL << 3 * TTE_PGSIZE(tlb->tte));
Not the first time it has appeared in this patch series, but I find the "1 + ~"
idiom to be strange. Surely plain old "-" is clearer.
r~
On Tue, Oct 11, 2016 at 03:08:34PM +0100, Dr. David Alan Gilbert wrote:
> * Daniel P. Berrange (berra...@redhat.com) wrote:
> > On Tue, Oct 11, 2016 at 12:26:37PM +0200, Samuel Ortiz wrote:
> > > Hi,
> > >
> > > On a qemu instance started with a qmp unix socket:
> > >
> > > -qmp unix:/tmp/ctrl.so
* Daniel P. Berrange (berra...@redhat.com) wrote:
> On Tue, Oct 11, 2016 at 12:26:37PM +0200, Samuel Ortiz wrote:
> > Hi,
> >
> > On a qemu instance started with a qmp unix socket:
> >
> > -qmp unix:/tmp/ctrl.sock,server,nowait
> >
> > I am trying to have multiple clients working on that socket
On Tue, Oct 11, 2016 at 01:58:35AM +0530, Kirti Wankhede wrote:
> Add file Documentation/vfio-mediated-device.txt that include details of
> mediated device framework.
>
> Signed-off-by: Kirti Wankhede
> Signed-off-by: Neo Jia
> Change-Id: I137dd646442936090d92008b115908b7b2c7bc5d
> ---
> Docume
On Tue, Oct 11, 2016 at 4:05 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> Signed-off-by: Artyom Tarasenko
>> ---
>> target-sparc/ldst_helper.c | 51
>> ++
>> 1 file changed, 15 insertions(+), 36 deletions(-)
>
>
Am 11.10.2016 um 15:46 hat Alberto Garcia geschrieben:
> On Mon 10 Oct 2016 06:03:41 PM CEST, Kevin Wolf wrote:
>
> >> Use block_job_add_bdrv() instead of blocking all operations in
> >> mirror_start_job() and unblocking them in mirror_exit().
> >>
> >> Signed-off-by: Alberto Garcia
> >
> > Comp
On Mon, Oct 10, 2016 at 11:14 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> if (is_exec) {
>> -helper_raise_exception(env, TT_CODE_ACCESS);
>> +if (env->lsu & (IMMU_E)) {
>> +helper_raise_exception(env, TT_CODE_ACCESS);
>> +
On 11.10.2016 15:55, Greg Kurz wrote:
> On Tue, 11 Oct 2016 15:32:02 +0200
> Thomas Huth wrote:
>
>> The pxe-test is run for three different targets now (x86_64, i386
>> and ppc64), and the bios-tables-test is run for two targets (x86_64
>> and i386). But each of the tests is using an invariant n
On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
Signed-off-by: Artyom Tarasenko
---
target-sparc/ldst_helper.c | 51 ++
1 file changed, 15 insertions(+), 36 deletions(-)
Perhaps this should be folded with patch 19.
+static uint64_t ultrasparc_tsb_
On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
Signed-off-by: Artyom Tarasenko
---
target-sparc/ldst_helper.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-sparc/ldst_helper.c b/target-sparc/ldst_helper.c
index 70febcb..250c23f 100644
--- a/target-sparc/ldst_helper
On Mon, Oct 10, 2016 at 02:56:25PM +0200, Cédric Le Goater wrote:
>
> >> @@ -227,11 +227,44 @@ static void ppc_powernv_init(MachineState *machine)
> >> snprintf(chip_name, sizeof(chip_name), "chip[%d]", CHIP_HWID(i));
> >> object_property_add_child(OBJECT(pnv), chip_name, chip,
On Mon, Oct 10, 2016 at 10:13 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> -//typedef struct SparcMMU
>> -union {
>> -uint64_t immuregs[16];
>> -struct {
>> -uint64_t tsb_tag_target;
>> -uint64_t unused_mmu_pri
On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
@@ -1295,10 +1295,9 @@ uint64_t helper_ld_asi(CPUSPARCState *env, target_ulong
addr,
asi &= 0xff;
-if ((asi < 0x80 && (env->pstate & PS_PRIV) == 0)
-|| (cpu_has_hypervisor(env)
-&& asi >= 0x30 && asi < 0x80
-
On Tue, Oct 04, 2016 at 09:43:30AM +0300, Emil Condrea wrote:
> Fixes the following errors:
> * ERROR: line over 90 characters
It's 80 ;), and there are a few more left in this patch.
> * ERROR: code indent should never use tabs
> * ERROR: space prohibited after that open square bracket '['
>
On Tue, Oct 11, 2016 at 7:50 AM, Richard Henderson wrote:
> On 10/10/2016 04:45 PM, Artyom Tarasenko wrote:
>>>
>>> Hmm. Would it make more sense to reorg these as
>>>
>>> TTE_US1_*
>>> TTE_UA2005_*
>>>
>>> with some duplication for the bits that are shared?
>>> As is, it's pretty hard to tel
On Tue, 11 Oct 2016 15:32:02 +0200
Thomas Huth wrote:
> The pxe-test is run for three different targets now (x86_64, i386
> and ppc64), and the bios-tables-test is run for two targets (x86_64
> and i386). But each of the tests is using an invariant name for the
> disk image with the boot sector c
On Mon, Oct 10, 2016 at 11:45 PM, Richard Henderson wrote:
> On 10/01/2016 05:05 AM, Artyom Tarasenko wrote:
>>
>> case 16: // UA2005 gl
>> CHECK_IU_FEATURE(dc, GL);
>> -tcg_gen_st32_tl(cpu_tmp0, cpu_env,
On Tue, 11 Oct 2016 10:24:38 -0300
Eduardo Habkost wrote:
> On Tue, Oct 11, 2016 at 03:21:05PM +0200, Igor Mammedov wrote:
> > On Tue, 11 Oct 2016 08:58:02 -0300
> > Eduardo Habkost wrote:
> >
> > > On Tue, Oct 11, 2016 at 01:45:21PM +0200, Igor Mammedov wrote:
> > > > On Mon, 10 Oct 2016 1
This option appears to be unused and undocumented, deprecate it.
Signed-off-by: Marc-André Lureau
---
vl.c | 5 +++--
include/monitor/monitor.h | 7 +++
qemu-options.hx | 8
3 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/vl.c b/vl.c
i
On 10/11/2016 01:47 AM, Alex Bennée wrote:
Richard Henderson writes:
Add all of cmpxchg, op_fetch, fetch_op, and xchg.
Handle both endian-ness, and sizes up to 8.
Handle expanding non-atomically, when emulating in serial.
Signed-off-by: Richard Henderson
This still seems to be suffering e
On Mon 10 Oct 2016 06:03:41 PM CEST, Kevin Wolf wrote:
>> Use block_job_add_bdrv() instead of blocking all operations in
>> mirror_start_job() and unblocking them in mirror_exit().
>>
>> Signed-off-by: Alberto Garcia
>
> Compared to the old code, this unblocks BLOCK_OP_TYPE_DATAPLANE, i.e.
> you
On 11 October 2016 at 14:32, Thomas Huth wrote:
> The pxe-test is run for three different targets now (x86_64, i386
> and ppc64), and the bios-tables-test is run for two targets (x86_64
> and i386). But each of the tests is using an invariant name for the
> disk image with the boot sector code - s
The pxe-test is run for three different targets now (x86_64, i386
and ppc64), and the bios-tables-test is run for two targets (x86_64
and i386). But each of the tests is using an invariant name for the
disk image with the boot sector code - so if the tests are running
in parallel, there is a race c
On Mon, Oct 10, 2016 at 02:28:52PM -0500, Eric Blake wrote:
> On 10/10/2016 01:36 PM, John Snow wrote:
[...]
> > I'll be honest that I don't know; this is related to Replication which I
> > know reasonably little about overall. It got added in the 2.8 timeframe,
> > so the behavior it currently e
On Mon, 2016-10-10 at 17:15 +0300, Marcel Apfelbaum wrote:
> > > > 2) can you really only plug a pcie-root-port (ioh3420)
> > > > into a pxb-pcie? Or will it accept anything that pcie.0
> > > > accepts?
> > >
> > > It supports only PCI Express Root Ports. It does not
> > > support Integrated Devic
Now that QAPI supports boxed types, we can have unions at the top level
of a command, so let's put our real options directly there for
blockdev-add instead of having a single "options" dict that contains the
real arguments.
blockdev-add is still experimental and we already made substantial
changes
On Tue, Oct 11, 2016 at 03:21:05PM +0200, Igor Mammedov wrote:
> On Tue, 11 Oct 2016 08:58:02 -0300
> Eduardo Habkost wrote:
>
> > On Tue, Oct 11, 2016 at 01:45:21PM +0200, Igor Mammedov wrote:
> > > On Mon, 10 Oct 2016 14:01:10 -0300
> > > Eduardo Habkost wrote:
> > > > On Mon, Oct 10, 2016 a
On Tue, 11 Oct 2016 08:58:02 -0300
Eduardo Habkost wrote:
> On Tue, Oct 11, 2016 at 01:45:21PM +0200, Igor Mammedov wrote:
> > On Mon, 10 Oct 2016 14:01:10 -0300
> > Eduardo Habkost wrote:
> > > On Mon, Oct 10, 2016 at 02:27:49PM +0200, Igor Mammedov wrote:
> > > > On Fri, 7 Oct 2016 17:29:
On 07.10.2016 20:54, Max Reitz wrote:
On 30.09.2016 12:53, Vladimir Sementsov-Ogievskiy wrote:
New field BdrvDirtyBitmap.persistent means, that bitmap should be saved
on bdrv_close, using format driver. Format driver should maintain bitmap
storing.
Signed-off-by: Vladimir Sementsov-Ogievskiy
-
Hi
Please, send any topic that you are interested in covering.
At the end of Monday I will send an email with the agenda or the
cancellation of the call, so hurry up.
After discussions on the QEMU Summit, we are going to have always open a
KVM call where you can add topics.
Call details:
By
On Tue, Oct 11, 2016 at 12:26:37PM +0200, Samuel Ortiz wrote:
> Hi,
>
> On a qemu instance started with a qmp unix socket:
>
> -qmp unix:/tmp/ctrl.sock,server,nowait
>
> I am trying to have multiple clients working on that socket but
> although the qmp server seems to accept the connections, onl
On Tue, Oct 11, 2016 at 08:51:01PM +0800, Fam Zheng wrote:
> On Tue, 10/04 09:42, Markus Armbruster wrote:
> > >> What's the advantage over simply using another QMP monitor? Naturally,
> > >> injecting arbitrary QMP commands behind libvirt's back isn't going to
> > >> end well, but "don't do that
Hi,
On a qemu instance started with a qmp unix socket:
-qmp unix:/tmp/ctrl.sock,server,nowait
I am trying to have multiple clients working on that socket but
although the qmp server seems to accept the connections, only the first
connected client gets his request processed. The next client reque
Hi,
Apologize for failing to make this email in short. Log is too long.
If the following statements failed to make me understood, you
are welcomed to ping me.
1. Problem description:
Recently, I find a strange thing with vIOMMU in QEMU. It looks like
g_hash_table_lookup() is not 100% give same re
On Tue, 10/04 09:42, Markus Armbruster wrote:
> >> What's the advantage over simply using another QMP monitor? Naturally,
> >> injecting arbitrary QMP commands behind libvirt's back isn't going to
> >> end well, but "don't do that then". Information queries and listening
> >> to events should be
Hi,
I'm using libvirt, but folks on libvirt mailing list said it makes more
sense to post here.
I have a Windows 7 SP1 Pro 64-bit VM which works fine on libvirt 2.3.0
and Qemu 2.7.0.
If I enable HyperV features
(https://libvirt.org/formatdomain.html#elementsFeatures) like "relaxed",
"spinl
On Tue, Oct 11, 2016 at 09:37:47AM -0300, Eduardo Habkost wrote:
> Use &error_abort so we don't ignore any errors on the property
> registration calls.
>
> Signed-off-by: Eduardo Habkost
> ---
> tests/check-qom-proplist.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
Reviewed-by
On Tue, Oct 11, 2016 at 09:37:46AM -0300, Eduardo Habkost wrote:
> The object_property_add_bool() call in dummy_init() was always
> failing because there was a "bv" class property already. Remove
> the class property so both object properties and class properties
> are covered by the test code.
>
Use &error_abort so we don't ignore any errors on the property
registration calls.
Signed-off-by: Eduardo Habkost
---
tests/check-qom-proplist.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/check-qom-proplist.c b/tests/check-qom-proplist.c
index 693dc4c..a92acc
A few fixes on check-qom-proplist that will ensure we test both
class properties and object properties, and catch errors when
registering properties in test code.
Eduardo Habkost (2):
tests: check-qom-proplist: Remove "bv" class property from class
tests: check-qom-proplist: Use &error_abort t
The object_property_add_bool() call in dummy_init() was always
failing because there was a "bv" class property already. Remove
the class property so both object properties and class properties
are covered by the test code.
Signed-off-by: Eduardo Habkost
---
tests/check-qom-proplist.c | 4
1
Le 08/10/2016 à 12:00, Laurent Vivier a écrit :
> Information about "qemu-trivial" ML can be found in the wiki:
>
> http://wiki.qemu.org/Contribute/TrivialPatches
>
> But the first place where a developer looks is the file MAINTAINERS.
>
> This also allows the get_maintainer.pl script to d
On Mon, 10 Oct 2016 21:57:55 +0800
Xiao Guangrong wrote:
> On 10/10/2016 08:59 PM, Igor Mammedov wrote:
> > On Sat, 8 Oct 2016 16:34:06 +0800
> > Xiao Guangrong wrote:
> >
> >> On 10/03/2016 09:48 PM, Igor Mammedov wrote:
> >>> On Fri, 12 Aug 2016 14:54:02 +0800
> >>> Xiao Guangrong wrote:
Hi,
I noticed that this patch kills the Qemu monitor for me. If I start a
text-mode guest with -nographic, then I can't switch to the monitor any
longer with Ctrl+a c . The guest works otherwise, e.g. I can login from
the console.
Tested on s390, but I think it's a more general issue, since the p
Hi
On Mon, Oct 10, 2016 at 5:29 PM Eric Blake wrote:
> [5 months later...]
> Going from qapi to QObject to JSON is wasteful compared to going
> straight from qapi to JSON. What's more, having QObject in the
> middle means that dict keys are shuffled according to hash ordering,
> while going str
On 01.10.2016 17:46, Max Reitz wrote:
On 30.09.2016 12:53, Vladimir Sementsov-Ogievskiy wrote:
Add dirty bitmap extension as specified in docs/specs/qcow2.txt.
For now, just mirror extension header into Qcow2 state and check
constraints.
For now, disable image resize if it has bitmaps. It will
Alex Bennée writes:
> Richard Henderson writes:
>
>> Add all of cmpxchg, op_fetch, fetch_op, and xchg.
>> Handle both endian-ness, and sizes up to 8.
>> Handle expanding non-atomically, when emulating in serial.
>>
>> Signed-off-by: Richard Henderson
>
> This still seems to be suffering expans
On Tue, Oct 11, 2016 at 01:45:21PM +0200, Igor Mammedov wrote:
> On Mon, 10 Oct 2016 14:01:10 -0300
> Eduardo Habkost wrote:
> > On Mon, Oct 10, 2016 at 02:27:49PM +0200, Igor Mammedov wrote:
> > > On Fri, 7 Oct 2016 17:29:02 -0300
> > > Eduardo Habkost wrote:
[...]
> > > > +static void x86_cpu_
Dear Thomas,
Thomas Huth writes:
> On 11.10.2016 10:27, Sascha Silbe wrote:
[pxe-test failing during "make check"]
>> There's a race condition in the tests. Both the "i386" and the "x86_64"
>> set of tests are creating and removing the same set of files:
>> tests/acpi-test-disk.raw (hard-coded i
On 01.10.2016 17:34, Max Reitz wrote:
On 30.09.2016 12:53, Vladimir Sementsov-Ogievskiy wrote:
Create block/qcow2-bitmap.c
Add data structures and constraints accordingly to docs/specs/qcow2.txt
Signed-off-by: Vladimir Sementsov-Ogievskiy
---
block/Makefile.objs | 2 +-
block/qcow2-bitmap
On Mon, 10 Oct 2016 21:09:30 +0800
Xiao Guangrong wrote:
> On 10/10/2016 08:51 PM, Igor Mammedov wrote:
> > On Sat, 8 Oct 2016 15:17:14 +0800
> > Xiao Guangrong wrote:
> >
> >> On 09/30/2016 09:14 PM, Igor Mammedov wrote:
> >>> On Fri, 12 Aug 2016 14:54:05 +0800
> >>> Xiao Guangrong wrote:
Tested-by: Claudio Imbrenda
On 10/10/16 17:46, Alex Bennée wrote:
> The changes to run_on_cpu and friends mean that all helpers are passed
> the CPUState of vCPU they are running on. The conversion missed the
> field in commit e0eeb4a21a3ca4b296220ce4449d8acef9de9049 which
> introduced bugs.
>
>
On Mon, 10 Oct 2016 14:01:10 -0300
Eduardo Habkost wrote:
> On Mon, Oct 10, 2016 at 02:27:49PM +0200, Igor Mammedov wrote:
> > On Fri, 7 Oct 2016 17:29:02 -0300
> > Eduardo Habkost wrote:
> >
> > > Fill the "unavailable-features" field on the x86 implementation
> > > of query-cpu-definitions
On Mon, 10 Oct 2016 13:58:25 -0300
Eduardo Habkost wrote:
> On Mon, Oct 10, 2016 at 02:25:32PM +0200, Igor Mammedov wrote:
> > On Fri, 7 Oct 2016 17:29:01 -0300
> > Eduardo Habkost wrote:
> >
> > > When probing for CPU model information, we need to reuse the code
> > > that initializes CPUID
On Mon, 10 Oct 2016 16:34:36 -0300
Eduardo Habkost wrote:
> TYPE_X86_CPU now call cpu_exec_init() on realize, so we don't
> need to set cannot_destroy_with_object_finalize_yet anymore.
>
> Signed-off-by: Eduardo Habkost
Reviewed-by: Igor Mammedov
> ---
> target-i386/cpu.c | 5 -
> 1 file
On Mon, Oct 10, 2016 at 5:44 PM Eric Blake wrote:
> Add pretty printing, where the format intentionally matches that of
> qobject_to_json() (a later patch will then rework qobject-json.c to
> work on top of the JSON visitor). The trickiest part is probably
> that the testsuite now has to honor p
On 11.10.2016 10:27, Sascha Silbe wrote:
> Dear Peter,
>
> Peter Maydell writes:
>
>> On 10 October 2016 at 15:13, Peter Maydell wrote:
>>> This failed 'make check' on aarch64 host (everything else was ok):
>>>
>>> TEST: tests/pxe-test... (pid=11699)
>>> /ppc64/pxe/virtio:
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Subject: [Qemu-devel] [PATCH 0/2] qemu-img: change img_open() and opening
method in dd
Message-id: 20161007153617.28704-1-ful
Hi
On Mon, Oct 10, 2016 at 5:25 PM Eric Blake wrote:
> Several spots in the code malloc a string, then wrap it in a
> QString, which has to duplicate the input. Adding a new
> constructor with transfer semantics makes this pattern more
> efficient, comparable to the just-added transfer semantic
Am 11.10.2016 um 11:54 hat Paolo Bonzini geschrieben:
> On 11/10/2016 11:39, Kevin Wolf wrote:
> > Am 10.10.2016 um 18:41 hat Paolo Bonzini geschrieben:
> >> On 10/10/2016 17:37, Kevin Wolf wrote:
> +while ((job = block_job_next(job))) {
> +AioContext *aio_context = blk_get_ai
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 1475760067-25756-1-git-send-email-peter.mayd...@linaro.org
Subject: [Qemu-devel] [PATCH 0/3] preliminaries for GIC
Am 10.10.2016 um 18:37 hat Paolo Bonzini geschrieben:
> On 10/10/2016 12:36, Kevin Wolf wrote:
> >
> > At the BlockBackend level (or really anywhere in the graph), we have two
> > different kinds of drain requests that we just fail to implement
> > differently today:
> >
> > 1. blk_drain(), i.e.
On 11/10/2016 12:35, Changlong Xie wrote:
> For nbd client, if request number is large than MAX_NBD_REQUESTS(16), we
> will queue the rest requests into free_sema->queue.
> When nbd client receives one reply, it will unlock free_sema, then pop
> the free_sema->queue head, so set free_sema->holde
Hi,
Your series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 1476089730-65776-1-git-send-email-arei.gong...@huawei.com
Subject: [Qemu-devel] [PATCH RESEND v6 00/12] virtio-cry
Only g_strdup(top_id) if 'top_id' is not NULL, although there
is no memory leak here
Signed-off-by: Changlong Xie
---
block/replication.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/replication.c b/block/replication.c
index 3bd1cf1..5b432d9 100644
--- a/block/re
V2:
1. fix typo
Changlong Xie (2):
block/replication: prefect the logic to acquire 'top_id'
block/replication: Clarify 'top-id' parameter usage
block/replication.c | 9 +++--
qapi/block-core.json | 3 ++-
2 files changed, 9 insertions(+), 3 deletions(-)
--
1.9.3
Replication driver only support 'top-id' parameter in secondary side,
and it must not be supplied in primary side
Signed-off-by: Changlong Xie
---
block/replication.c | 5 +
qapi/block-core.json | 3 ++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/block/replication.c b/blo
On 10/11/2016 02:30 PM, Fam Zheng wrote:
On Tue, 10/11 13:39, Changlong Xie wrote:
Replication driver only support 'top-id' parameter in secondary side,
and it must not be supplied in primary side
Signed-off-by: Changlong Xie
---
block/replication.c | 5 +
qapi/block-core.json | 3 ++-
Hi all
Recently during test COLO, i encounter some problems. Here is the backtrace
qemu-system-x86_64: util/qemu-coroutine-lock.c:148:
qemu_co_mutex_unlock: Assertion `mutex->holder == self' failed.
[New Thread 0x7fff0e7fc700 (LWP 20936)]
Program received signal SIGABRT, Aborted.
0x75
On Tue, Oct 11, 2016 at 09:55:54AM +0100, Peter Maydell wrote:
> On 11 October 2016 at 02:24, David Gibson wrote:
> > On Mon, Oct 10, 2016 at 03:10:33PM +0100, Peter Maydell wrote:
> >> On 10 October 2016 at 14:39, David Gibson
> >> wrote:
> >> > In the overwhelming majority of cases the endiann
On 10/11/16 10:22, Markus Armbruster wrote:
> Haozhong Zhang writes:
>
> > On 10/10/16 14:16, Eric Blake wrote:
> >> On 10/09/2016 07:34 PM, Haozhong Zhang wrote:
> >> > Xen uses this command to get the backend resource, guest SPA and size of
> >> > NVDIMM devices so as to map them to guest.
> >>
On Mon, 10/03 17:32, Alex Bennée wrote:
> This re-factors the docker makefile to include a docker-run target which
> can be controlled entirely from environment variables specified on the
> make command line. This allows us to run against any given docker image
> we may have in our repository, for
On Tue, 10/11 09:49, Alex Bennée wrote:
>
> Fam Zheng writes:
>
> > On Mon, 10/03 17:32, Alex Bennée wrote:
> >> Much like test-quick but only builds. This is useful for some of the
> >> build targets like ThreadSanitizer that don't yet pass "make check".
> >>
> >> Signed-off-by: Alex Bennée
>
On 11/10/2016 11:39, Kevin Wolf wrote:
> Am 10.10.2016 um 18:41 hat Paolo Bonzini geschrieben:
>> On 10/10/2016 17:37, Kevin Wolf wrote:
+while ((job = block_job_next(job))) {
+AioContext *aio_context = blk_get_aio_context(job->blk);
+
+aio_context_acquire(
v2 -> v3:
- Changed from safe_syscall4() to safe_syscall5() to rightly fit the
kernel implementation of preadv() and pwritev().
- Modified commit message.
v1 -> v2:
- Being that both of these system calls are interruptible, in QEMU
they should be implemented via the safe_sy
This system call performs the same task as the readv() system call,
with the exception of having the fourth argument, offset, which
specifes the file offset at which the input operation is to be performed.
Because of this, the preadv() implementation is based on the readv()
implementation in linux-
This system call performs the same task as the writev() system call,
with the exception of having the fourth argument, offset, which
specifes the file offset at which the input operation is to be performed.
Because of this, the pwritev() implementation is based on the writev()
implementation in lin
John Snow writes:
> On 10/05/2016 09:43 AM, Kevin Wolf wrote:
[...]
>> Here we have an additional caller in block/replication.c and qemu-img,
>> so the parameters must stay. For qemu-img, nothing changes. For
>> replication, the block job events are added as a side effect.
>>
>> Not sure if we wa
Am 10.10.2016 um 18:41 hat Paolo Bonzini geschrieben:
> On 10/10/2016 17:37, Kevin Wolf wrote:
> > > +while ((job = block_job_next(job))) {
> > > +AioContext *aio_context = blk_get_aio_context(job->blk);
> > > +
> > > +aio_context_acquire(aio_context);
> > > +block_job_p
Am 11.10.2016 um 00:51 hat John Snow geschrieben:
> >>Sadly for me, I realized this patch has a potential problem. When we
> >>were adding the bitmap operations, it became clear that the
> >>atomicity point was during .prepare, not .commit.
> >>
> >>e.g. the bitmap is cleared or created during prep
Just a trivial couple of patches addressing minor style issues.
Enforcing the correct order of operations (pop, unpop, push, rewind) with an
assert,
which was another potential change discussed previously, would add a non-trivial
amount of code and is not worth the effort in my opinion. A simple
The function undoes the effect of virtqueue_pop and doesn't do anything
destructive or irreversible so virtqueue_unpop is a more fitting name.
Signed-off-by: Ladi Prosek
---
hw/net/virtio-net.c| 2 +-
hw/virtio/virtio-balloon.c | 2 +-
hw/virtio/virtio.c | 6 +++---
include/hw/vi
The function does not fully initialize the returned VirtQueueElement and should
be used only internally from the virtio module.
Signed-off-by: Ladi Prosek
---
hw/virtio/virtio.c | 2 +-
include/hw/virtio/virtio.h | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/hw/vir
On 6 October 2016 at 14:21, Peter Maydell wrote:
> This set of three straightforward patches is a preliminary
> for adding virtualization support to the GICv3 emulation:
> * add a (nop implementation of) MDCCINT_EL1, since KVM
>will read/write it on worldswitch
> * fix some bugs in the GICv3
On 11 October 2016 at 09:27, Sascha Silbe wrote:
> There's a race condition in the tests. Both the "i386" and the "x86_64"
> set of tests are creating and removing the same set of files:
> tests/acpi-test-disk.raw (hard-coded in tests/bios-tables-test.c) and
> tests/pxe-test-disk.raw (hard-coded i
On 11/10/2016 00:51, John Snow wrote:
>> Clearing the bitmap is a bug because the caller could expect that the
>> bitmap is in its original state if the transaction fails. I doubt this
>> is a problem in practice, but we should fix it anyway.
>
> We make a backup to undo the process if it fails.
On 11 October 2016 at 02:24, David Gibson wrote:
> On Mon, Oct 10, 2016 at 03:10:33PM +0100, Peter Maydell wrote:
>> On 10 October 2016 at 14:39, David Gibson
>> wrote:
>> > In the overwhelming majority of cases the endianness of the device is
>> > known independent of the guest CPU and board.
>
On Mon, Oct 10, 2016 at 05:28:47PM +0200, Radim Krčmář wrote:
> Cluster x2APIC cannot work without KVM's x2apic API when the maximal
> APIC ID is greater than 8 and only KVM's LAPIC can support x2APIC, so we
> forbid other APICs and also the old KVM case with less than 9, to
> simplify the code.
>
Fam Zheng writes:
> On Mon, 10/03 17:32, Alex Bennée wrote:
>> Much like test-quick but only builds. This is useful for some of the
>> build targets like ThreadSanitizer that don't yet pass "make check".
>>
>> Signed-off-by: Alex Bennée
>> ---
>> tests/docker/test-build | 18 ++
On 11/10/2016 10:23, Daniel P. Berrange wrote:
> On Tue, Oct 11, 2016 at 09:36:29AM +0200, Paolo Bonzini wrote:
>>
>>
>> On 10/10/2016 19:46, Eduardo Habkost wrote:
>>> I don't think we have a plan, but I would support deprecating and
>>> removing very old machine-types. The question is: how old
On Mon, 10/03 17:32, Alex Bennée wrote:
> Much like test-quick but only builds. This is useful for some of the
> build targets like ThreadSanitizer that don't yet pass "make check".
>
> Signed-off-by: Alex Bennée
> ---
> tests/docker/test-build | 18 ++
> 1 file changed, 18 inser
Dear Peter,
Peter Maydell writes:
> On 10 October 2016 at 15:13, Peter Maydell wrote:
>> This failed 'make check' on aarch64 host (everything else was ok):
>>
>> TEST: tests/pxe-test... (pid=11699)
>> /ppc64/pxe/virtio: **
>> ERROR:/home/petma
On Tue, Oct 11, 2016 at 09:36:29AM +0200, Paolo Bonzini wrote:
>
>
> On 10/10/2016 19:46, Eduardo Habkost wrote:
> > I don't think we have a plan, but I would support deprecating and
> > removing very old machine-types. The question is: how old is too
> > old?
> >
> > For reference, the commits
Haozhong Zhang writes:
> On 10/10/16 14:16, Eric Blake wrote:
>> On 10/09/2016 07:34 PM, Haozhong Zhang wrote:
>> > Xen uses this command to get the backend resource, guest SPA and size of
>> > NVDIMM devices so as to map them to guest.
>> >
>> > Signed-off-by: Haozhong Zhang
>> > ---
>> > Cc:
On 10/10/2016 18:03, Kevin Wolf wrote:
>> > Use block_job_add_bdrv() instead of blocking all operations in
>> > mirror_start_job() and unblocking them in mirror_exit().
>> >
>> > Signed-off-by: Alberto Garcia
> Compared to the old code, this unblocks BLOCK_OP_TYPE_DATAPLANE, i.e.
> you can now
201 - 300 of 313 matches
Mail list logo
