Richard Henderson writes:
> On 07/23/2016 12:58 AM, Nikunj A Dadhania wrote:
>> Richard Henderson writes:
>>
>>> On 07/18/2016 10:35 PM, Nikunj A Dadhania wrote:
+tcg_gen_andi_tl(src1, cpu_gpr[rA(ctx->opcode)], 0xFF);
+for (i = 0; i < 64; i += 8) {
+tcg_gen_shri_tl
On 07/20/2016 09:27 PM, Dave Hansen wrote:
QEMU 2.6 added support for the XSAVE family of instructions, which
includes the XSETBV instruction which allows setting the 'XCR0'
register.
But, when booting Linux kernels with XSAVE support enabled, I was
getting very early crashes where the instructi
On 07/23/2016 12:58 AM, Nikunj A Dadhania wrote:
Richard Henderson writes:
On 07/18/2016 10:35 PM, Nikunj A Dadhania wrote:
+tcg_gen_andi_tl(src1, cpu_gpr[rA(ctx->opcode)], 0xFF);
+for (i = 0; i < 64; i += 8) {
+tcg_gen_shri_tl(t0, arg1, i);
+tcg_gen_andi_tl(t0, t0, 0x
On 18.07.2016 19:04, Halil Pasic wrote:
>
>
> On 07/18/2016 05:57 PM, Max Reitz wrote:
>> On 18.07.2016 17:48, Halil Pasic wrote:
>>>
>>>
>>> On 07/18/2016 04:41 PM, Max Reitz wrote:
On 18.07.2016 14:30, Halil Pasic wrote:
> Make raw_open for POSIX more consistent in handling errors by s
On 07/22/2016 05:57 PM, Max Reitz wrote:
> On 18.07.2016 22:57, John Snow wrote:
>> From: Fam Zheng
>>
>> The added group of operations enables tracking of the changed bits in
>> the dirty bitmap.
>>
>> Signed-off-by: Fam Zheng
>> Reviewed-by: Max Reitz
>> Signed-off-by: John Snow
>> ---
>>
On 18.07.2016 22:57, John Snow wrote:
> From: Fam Zheng
>
> Signed-off-by: Fam Zheng
> [Fixed minor constant issue. --js]
> Signed-off-by: John Snow
>
> Signed-off-by: John Snow
> ---
> tests/test-hbitmap.c | 139
> +++
> 1 file changed, 139 i
On 18.07.2016 22:57, John Snow wrote:
> From: Fam Zheng
>
> The added group of operations enables tracking of the changed bits in
> the dirty bitmap.
>
> Signed-off-by: Fam Zheng
> Reviewed-by: Max Reitz
> Signed-off-by: John Snow
> ---
> block/dirty-bitmap.c | 52
>
On Fri, Jul 22, 2016 at 11:32:48AM +1000, David Gibson wrote:
> On Thu, Jul 21, 2016 at 05:54:33PM +0200, Igor Mammedov wrote:
> > Instead use QTAIL's tqe_prev field to detect if cpu's been
> > placed in list by cpu_exec_init() which is always set if
> > QTAIL element is in list.
> >
> > Fixes SIG
On 22.07.2016 14:53, Daniel P. Berrange wrote:
> This is a followup to:
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg01723.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg03642.html
> v3: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg03885.h
Changes from v2:
Set the timers to NULL when unrealizing them, as the data structure
is still intact.
Split out the removal of the mutex from ipmi_bmc_sim to its own patch.
I did figure out a way to test these. You can set the realize bool
in the qapi for the device to cause it to be realized/
From: Corey Minyard
Add an unrealize function to free the timer allocated in the
realize function, unregister the vmstate, and free any
pending messages.
Signed-off-by: Corey Minyard
Reviewed-by: Marc-André Lureau
---
hw/ipmi/ipmi_bmc_sim.c | 16
1 file changed, 16 insertions
From: Corey Minyard
Add an exit function to free the timer allocated in the
realize function.
Signed-off-by: Corey Minyard
Cc: Richard W.M. Jones
Reviewed-by: Marc-André Lureau
Reviewed-by: Richard W.M. Jones
---
hw/watchdog/wdt_i6300esb.c | 10 ++
1 file changed, 10 insertions(+)
From: Corey Minyard
Get rid of the unnecessary mutex, it was a vestige
of something else that was not done. That way we don't
have to free it.
Signed-off-by: Corey Minyard
Reviewed-by: Marc-André Lureau
---
hw/ipmi/ipmi_bmc_sim.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/hw/ip
From: Corey Minyard
Add an unrealize function to free the timer allocated in the
realize function and to delete the port memory added there,
too.
Signed-off-by: Corey Minyard
Cc: Richard W.M. Jones
Cc: Marc-André Lureau
Reviewed-by: Richard W.M. Jones
---
hw/watchdog/wdt_ib700.c | 12 ++
Richard Henderson writes:
> On 07/18/2016 10:35 PM, Nikunj A Dadhania wrote:
>> +tcg_gen_andi_tl(src1, cpu_gpr[rA(ctx->opcode)], 0xFF);
>> +for (i = 0; i < 64; i += 8) {
>> +tcg_gen_shri_tl(t0, arg1, i);
>> +tcg_gen_andi_tl(t0, t0, 0xFF);
>> +tcg_gen_brcond_tl(TCG_
Hello,
On behalf of the QEMU Team, I'd like to announce the availability of the
first release candidate for the QEMU 2.7 release. This release is meant
for testing purposes and should not be used in a production environment.
http://wiki.qemu.org/download/qemu-2.7.0-rc0.tar.bz2
You can help impr
On Fri, Jul 22, 2016 at 08:04:08PM +0530, Prasanna Kumar Kalever wrote:
> 1. qapi @BlockdevOptionsGluster schema member name s/debug_level/debug-level/
> 2. rearrange the versioning
> 3. s/server description/servers description/
>
> Signed-off-by: Prasanna Kumar Kalever
> v2: address review comme
On 22.07.2016 18:40, Paolo Bonzini wrote:
>
>
> On 22/07/2016 18:27, Max Reitz wrote:
>>
>> So I can't see a strong argument for not modularizing the format block
>> drivers, but in turn I don't have a strong argument for doing so either.
>>
>> Therefore: Why not? :-)
>
> The usual argument is t
According to the e500mc and e5500 core reference manual they have support
for the mftb instruction.
Signed-off-by: Michael Walle
---
changes v2:
- add the flag to e500mc, too
target-ppc/translate_init.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-ppc/translat
On Fri, Jul 22, 2016 at 08:04:08PM +0530, Prasanna Kumar Kalever wrote:
> 1. qapi @BlockdevOptionsGluster schema member name s/debug_level/debug-level/
> 2. rearrange the versioning
> 3. s/server description/servers description/
>
> Signed-off-by: Prasanna Kumar Kalever
> v2: address review comme
On 14.07.2016 19:19, Vladimir Sementsov-Ogievskiy wrote:
> Mirror can do up to 16 in-flight requests, but actually on full copy
> (the whole source disk is non-zero) in-flight is always 1. This happens
> as the request is not limited in size: the data occupies maximum available
> capacity of s->buf
On 22/07/2016 18:27, Max Reitz wrote:
>
> So I can't see a strong argument for not modularizing the format block
> drivers, but in turn I don't have a strong argument for doing so either.
>
> Therefore: Why not? :-)
The usual argument is that there is an additional cost in
maintainability. Th
So far, QHT functions assume that the passed qht has previously been
initialized--otherwise they segfault.
This patch makes an exception for qht_statistics_init, with the goal
of simplifying calling code. For instance, qht_statistics_init is
called from the 'info jit' dump, and given that under KV
> Am 22.07.2016 um 18:29 schrieb Michael Walle :
>
> According to the e5500 core reference manual it has support for the mftb
> instruction.
>
> Signed-off-by: Michael Walle
I'm surprised this didn't hit anyone before. Could you please check the other
e500 cpu types too and endure consistenc
According to the e5500 core reference manual it has support for the mftb
instruction.
Signed-off-by: Michael Walle
---
target-ppc/translate_init.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target-ppc/translate_init.c b/target-ppc/translate_init.c
index 5ecafc7..f1261af
On 19.07.2016 12:54, Paolo Bonzini wrote:
>
>
> On 14/07/2016 21:02, Colin Lord wrote:
>> Here's v4 of the modularization series. Things that have changed since
>> v3 include:
>>
>> - Fix indentation of the generated header file module_block.h
>> - Drivers and probe functions are now all located
Igor Mammedov writes:
> On Thu, 21 Jul 2016 10:36:40 +0200
> Markus Armbruster wrote:
>
>> Igor Mammedov writes:
[...]
>> > @@ -352,15 +352,14 @@ void os_mem_prealloc(int fd, char *area, size_t
>> > memory)
>> > for (i = 0; i < numpages; i++) {
>> > memset(area + (hpagesi
Hello Stefan,
On Tue, Jul 19, 2016 at 10:40 AM, Stefan Hajnoczi
wrote:
> On Tue, Jul 19, 2016 at 09:47:13AM +0200, Christian Pinto wrote:
> > > > +During the initialization phase the device connects also to the
> > > communication
> > > > +channel. It has to be noted that the behavior of the dev
I've taken all the suggestions apart from the bellow (comment inline):
Sergey Fedorov writes:
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -99,6 +99,26 @@ STEXI
>> Select CPU model (@code{-cpu help} for list and additional feature
>> selection)
>> ETEXI
>>
>> +DEF("accel", HAS_AR
On 07/22/2016 05:18 PM, Michael Walle wrote:
64 bit user mode doesn't work for the e5500 core because the MSR_CM bit is
not set which enables the 64 bit mode for this MMU model. Memory addresses
are truncated to 32 bit, which results in "Invalid data memory access"
error messages. Fix it by setti
On Fri, Jul 22, 2016 at 04:11:58PM +0100, Daniel P. Berrange wrote:
> On Fri, Jul 22, 2016 at 04:55:16PM +0200, Pavel Hrdina wrote:
> > Hi,
> >
> > So there was made a decision that default ROM bars for network devices
> > shouldn't
> > be packaged for ARM architecture. Based on this thorough ex
64 bit user mode doesn't work for the e5500 core because the MSR_CM bit is
not set which enables the 64 bit mode for this MMU model. Memory addresses
are truncated to 32 bit, which results in "Invalid data memory access"
error messages. Fix it by setting the MSR_CM bit for this MMU model.
Signed-o
On Fri, Jul 22, 2016 at 04:55:16PM +0200, Pavel Hrdina wrote:
> Hi,
>
> So there was made a decision that default ROM bars for network devices
> shouldn't
> be packaged for ARM architecture. Based on this thorough explanation [1] it
What do you mean by 'shouldn't be packaged for ARM architectur
On 22 July 2016 at 03:30, Icenowy Zheng wrote:
> According to comments in /usr/include/linux/eventpoll.h, x86_64 have
> the same memory layout of struct target_epoll_event as i386. So on a
> aligned host, if x86_64 should be packed, i386 will also need.
>
> This has been tested with a i386 guest o
On 07/18/2016 11:05 PM, Paolo Bonzini wrote:
Because atomic_read/atomic_set does not work on platforms that only
support 32-bit atomic writes, we need volatile_read/volatile_set.
This patch fixes up Sergey's series to use volatile_read/volatile_set
instead of atomic_read/atomic_set. Because vol
On Fri, Jul 22, 2016 at 7:37 PM, Eric Blake wrote:
> On 07/22/2016 06:01 AM, Prasanna Kumar Kalever wrote:
>> currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded
>> in a call to glfs logging api, in case if debug level is chosen to
>> DEBUG/TRACE
>
> s/api, in case if/ap
currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded
in a call to glfs logging api. When the debug level is chosen to DEBUG/TRACE,
gfapi logs will be huge and fill/overflow the console view.
This patch provides a commandline option to mention log file path which helps
in l
Hi,
So there was made a decision that default ROM bars for network devices shouldn't
be packaged for ARM architecture. Based on this thorough explanation [1] it
makes sense that it's useless. However it leads to a small issue with starting
a guest on ARM hosts with PCI network device, if there a
On Fri, Jul 22, 2016 at 8:16 PM, Eric Blake wrote:
> On 07/22/2016 08:34 AM, Prasanna Kumar Kalever wrote:
>> 1. qapi @BlockdevOptionsGluster schema member name s/debug_level/debug-level/
>> 2. rearrange the versioning
>> 3. s/server description/servers description/
>>
>> Signed-off-by: Prasanna K
On 07/22/2016 08:34 AM, Prasanna Kumar Kalever wrote:
> 1. qapi @BlockdevOptionsGluster schema member name s/debug_level/debug-level/
> 2. rearrange the versioning
> 3. s/server description/servers description/
>
> Signed-off-by: Prasanna Kumar Kalever
This part is fine.
> v2: address review co
On Fri, Jul 22, 2016 at 09:16:57AM +0200, Greg Kurz wrote:
> On Fri, 22 Jul 2016 11:28:48 +1000
> David Gibson wrote:
>
> > On Fri, Jul 22, 2016 at 01:01:26AM +0200, Greg Kurz wrote:
> > > This patch ensures QEMU won't terminate while hotplugging a device if the
> > > global property cannot be se
Public bug reported:
I am trying to read the first 16 bytes of the System Process on a
Windows XP x64 SP2 using the memsave monitor command.
I cloned the latest release of QEMU, v2.6.0, configured it with
./configure --target-list=i386-softmmu,x86_64-softmmu --enable-sdl
and compiled it.
I firs
FIY
Forwarding messages
From: "lisiheng"
Date: 2016-07-22 14:56:36
To: qemu-disc...@nongnu.org
Subject: qemu driver_mirror error "Operation not permitted"
Hi All,
I use libvirtd to call qemu drive_mirror return error message "Operation not
permitted", Butdirectlyrunqemu
Hello -
I'm using ssh with the -X switch to get onto a server where I have kvm
installed. I've made a virtual disk and I'm issuing the following command:
kvm -name livecd-debian -monitor vc -no-quit -m 1024 -usb -drive
media=disk,if=ide,index=0,file=mastodonhdd1.qcow2,snapshot=off -drive
media
Public bug reported:
I use libvirtd to call qemu drive_mirror return error message "Operation not
permitted", But directly run qemu and call drive_mirror is OK;
when drive_mirror target is logic device return error message "Operation not
permitted",But the file is OK;
Operating Environment：
OS:
On Fri, Jul 22, 2016 at 7:39 PM, Eric Blake wrote:
>
> On 07/22/2016 04:05 AM, Prasanna Kumar Kalever wrote:
> > 1. s/@debug-level/@debug_level/
>
> Wrong. I asked for the opposite, s/debug_level/debug-level/
oops!
>
> > 2. rearrange the versioning
> > 3. s/server description/servers descriptio
1. qapi @BlockdevOptionsGluster schema member name s/debug_level/debug-level/
2. rearrange the versioning
3. s/server description/servers description/
Signed-off-by: Prasanna Kumar Kalever
v2: address review comments given by Eric Blake
v1: Initial patch
---
qapi/block-core.json | 6 +++---
1 fi
Sure, I will continue to send revisions until it is approved upstream.
On Jul 22, 2016 5:24 PM, "Quan Xu" wrote:
> Anthony, thanks for your explaination.
> IMO, patch 1 and patch 2 need your detailed review.. IMO the reset
> patches are good in general..
> Emil, if patch 1 / patch 2 are reviewed
Anthony, thanks for your explaination.IMO, patch 1 and patch 2 need your
detailed review.. IMO the reset patches are good in general..Emil, if patch 1 /
patch 2 are reviewed from anthony, could you send out v10? :) i know it's not
an easy task, thanks in advence!!
Quan
On Mon, 18 Jul 2016 15:5
On 07/22/2016 06:01 AM, Prasanna Kumar Kalever wrote:
> currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded
> in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE
s/api, in case if/api. When the/
s/TRACE/TRACE,/
> gfapi logs will be huge and fil
On 07/22/2016 04:05 AM, Prasanna Kumar Kalever wrote:
> 1. s/@debug-level/@debug_level/
Wrong. I asked for the opposite, s/debug_level/debug-level/
> 2. rearrange the versioning
> 3. s/server description/servers description/
>
> Signed-off-by: Prasanna Kumar Kalever
> ---
> qapi/block-core.js
On 07/22/2016 03:46 PM, Michael Walle wrote:
Am 2016-07-22 15:07, schrieb Alexander Graf:
On 22 Jul 2016, at 15:00, Michael Walle wrote:
64 bit user mode doesn't work for the e5500 core because the MSR_CM
bit is
not set which enables the 64 bit mode for this MMU model. Memory
addresses
are
sorry for the bad format from web email, and later review (neo training in
new company).. patch 6 -- patch 12, rename * patch, are good to me.
Quan
--From:Emil
Condrea Time:2016 Jul 19 (Tue) 00:54To:Eric Blake
Cc:qemu-d
From: Greg Kurz
Without presuming if we got there because of a user mistake or some
more subtle bug in the tooling, it really does not make sense to
implement a non-functional device.
Signed-off-by: Greg Kurz
Reviewed-by: Marcel Apfelbaum
Reviewed-by: Cornelia Huck
Signed-off-by: Greg Kurz
-
On Fri, 22 Jul 2016 15:42:48 +0200
Cornelia Huck wrote:
> [...]
> > > > > On Thu, 21 Jul 2016 23:21:16 +0200
> > > > > Greg Kurz wrote:
> > > > >
> > > > > > From: Greg Kurz
> > > > > >
> > > > > > Without presuming if we got there because of a user mistake or some
> > > > > > more subtle
On Fri, Jul 22, 2016 at 11:28:48AM +1000, David Gibson wrote:
> On Fri, Jul 22, 2016 at 01:01:26AM +0200, Greg Kurz wrote:
> > This patch ensures QEMU won't terminate while hotplugging a device if the
> > global property cannot be set and errp points to error_fatal or error_abort.
> >
> > While he
On 07/22/2016 06:53 AM, Daniel P. Berrange wrote:
> This is a followup to:
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg01723.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg03642.html
> v3: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg0388
On 2016-06-18 22:48, Hervé Poussineau wrote:
> Hi Aurélien,
>
> Le 20/05/2016 à 21:56, Aurelien Jarno a écrit :
> > On 2016-05-20 15:05, Hervé Poussineau wrote:
> > > Incidentally, this fixes YAMON on big endian guest.
> > >
> > > Signed-off-by: Hervé Poussineau
> > > ---
> > > hw/mips/gt64xxx_
On Fri, 22 Jul 2016 15:23:19 +0200
Greg Kurz wrote:
> On Fri, 22 Jul 2016 12:32:24 +0200
> Cornelia Huck wrote:
>
> > On Fri, 22 Jul 2016 12:11:11 +0200
> > Greg Kurz wrote:
> >
> > > On Fri, 22 Jul 2016 10:04:35 +0200
> > > Cornelia Huck wrote:
> > >
> > > > On Thu, 21 Jul 2016 23:21:16
Am 2016-07-22 15:07, schrieb Alexander Graf:
On 22 Jul 2016, at 15:00, Michael Walle wrote:
64 bit user mode doesn't work for the e5500 core because the MSR_CM
bit is
not set which enables the 64 bit mode for this MMU model. Memory
addresses
are truncated to 32 bit, which results in "Invalid
On 2016-07-19 09:09, Richard Henderson wrote:
> On 06/24/2016 09:18 AM, Richard Henderson wrote:
> > I was unhappy about the complexity of the second try.
> >
> > Better to convert to normal temps, allowing in rare
> > occasions, spilling the "globals" to the stack in order
> > to satisfy register
On Fri, 22 Jul 2016 12:32:24 +0200
Cornelia Huck wrote:
> On Fri, 22 Jul 2016 12:11:11 +0200
> Greg Kurz wrote:
>
> > On Fri, 22 Jul 2016 10:04:35 +0200
> > Cornelia Huck wrote:
> >
> > > On Thu, 21 Jul 2016 23:21:16 +0200
> > > Greg Kurz wrote:
> > >
> > > > From: Greg Kurz
> > > >
>
On Fri, 22 Jul 2016 12:11:11 +0200
Greg Kurz wrote:
> On Fri, 22 Jul 2016 10:04:35 +0200
> Cornelia Huck wrote:
>
> > On Thu, 21 Jul 2016 23:21:16 +0200
> > Greg Kurz wrote:
> >
> > > From: Greg Kurz
> > >
> > > Without presuming if we got there because of a user mistake or some
> > > more
> On 22 Jul 2016, at 15:00, Michael Walle wrote:
>
> 64 bit user mode doesn't work for the e5500 core because the MSR_CM bit is
> not set which enables the 64 bit mode for this MMU model. Memory addresses
> are truncated to 32 bit, which results in "Invalid data memory access"
> error messages.
On 2016-07-22 10:55, Paul Burton wrote:
> The print routine provided as part of the in-built bootloader had a bug
> in that it attempted to use a jump instruction as part of a loop, but
> the target has its upper bits zeroed leading to control flow
> transferring to 0xb814 rather than the inten
64 bit user mode doesn't work for the e5500 core because the MSR_CM bit is
not set which enables the 64 bit mode for this MMU model. Memory addresses
are truncated to 32 bit, which results in "Invalid data memory access"
error messages. Fix it by setting the MSR_CM bit for this MMU model.
Signed-o
This is a followup to:
v1: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg01723.html
v2: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg03642.html
v3: https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg03885.html
The 'qemu-img info' tool has ability to print format
The qemu-img info command has the ability to expose format
specific metadata about volumes. Wire up this facility for
the LUKS driver to report on cipher configuration and key
slot usage.
$ qemu-img info ~/VirtualMachines/demo.luks
image: /home/berrange/VirtualMachines/demo.luks
file f
When creating new block encryption volumes, we accept a list of
parameters to control the formatting process. It is useful to
be able to query what those parameters were for existing block
devices. Add a qcrypto_block_get_info() method which returns a
QCryptoBlockInfo instance to report this data.
In do_brk(), we were inadvertently truncating the size
of a requested brk() from the guest by putting it into an
'int' variable. This meant that we would incorrectly report
success back to the guest rather than a failed allocation,
typically resulting in the guest then segfaulting. Use
abi_ulong in
On 21.07.2016 21:14, Peter Maydell wrote:
> On 20 July 2016 at 22:16, Eric Blake wrote:
>> On 07/20/2016 10:05 AM, Peter Maydell wrote:
>>> On 19 July 2016 at 23:47, Max Reitz wrote:
The following changes since commit
5d3217340adcb6c4f0e4af5d2b865331eb2ff63d:
disas: Fix ATT
On 07/22/2016 04:22 AM, Marc-André Lureau wrote:
Hi
- Original Message -
From: Corey Minyard
Add an unrealize function to free the timer allocated in the
realize function, unregsiter the vmstate, and free any
pending messages.
I don't know how to test this either, the device seems to
On 07/22/2016 05:12 AM, Richard W.M. Jones wrote:
On Fri, Jul 22, 2016 at 05:26:27AM -0400, Marc-André Lureau wrote:
btw, I do not how to test this yet either.
I have a little test framework for the watchdog device which cuts
through a lot of the BS with running the full watchdog daemon, and
al
currently all the libgfapi logs defaults to '/dev/stderr' as it was hardcoded
in a call to glfs logging api, in case if debug level is chosen to DEBUG/TRACE
gfapi logs will be huge and fill/overflow the console view.
this patch provides a commandline option to mention log file path which helps
in
The goal of this patch is to have a stable core-id which does not depend
on any DT related semantics, which involve non-obvious computations on
modern PowerPC server cpus.
With this patch, the DT core id is computed on-demand as:
(core-id / smp_threads) * smt
where smt is the number of th
On 21 July 2016 at 17:28, Aurelien Jarno wrote:
> On 2016-07-21 13:44, Peter Maydell wrote:
>> Ping?
>>
>> thanks
>> -- PMM
>>
>> On 12 July 2016 at 13:50, Peter Maydell wrote:
>> > Coverity spots that helper_movcal() calls malloc() but doesn't
>> > check for failure. Fix this by switching to the
On 07/22/2016 06:38 PM, Daniel P. Berrange wrote:
On Fri, Jul 22, 2016 at 06:43:51PM +0800, Cao jin wrote:
On 07/22/2016 06:30 PM, Daniel P. Berrange wrote:
On Fri, Jul 22, 2016 at 06:34:11PM +0800, Cao jin wrote:
Hi Daniel
On 07/21/2016 11:39 PM, Daniel P. Berrange wrote:
On Thu, Jul 21
> > > i.e. the use of fiemap to duplicate the exact layout of a file
> > > from userspace is only posisble if you can /guarantee/ the source
> > > file has not changed in any way during the copy operation at the
> > > pointin time you finalise the destination data copy.
> >
> > We don't do exactly
On Fri, Jul 22, 2016 at 06:43:51PM +0800, Cao jin wrote:
>
>
> On 07/22/2016 06:30 PM, Daniel P. Berrange wrote:
> > On Fri, Jul 22, 2016 at 06:34:11PM +0800, Cao jin wrote:
> > > Hi Daniel
> > >
> > > On 07/21/2016 11:39 PM, Daniel P. Berrange wrote:
> > > > On Thu, Jul 21, 2016 at 08:42:25AM -
On 07/22/2016 06:30 PM, Daniel P. Berrange wrote:
On Fri, Jul 22, 2016 at 06:34:11PM +0800, Cao jin wrote:
Hi Daniel
On 07/21/2016 11:39 PM, Daniel P. Berrange wrote:
On Thu, Jul 21, 2016 at 08:42:25AM -0600, Eric Blake wrote:
On 07/21/2016 04:33 AM, Cao jin wrote:
It is never used, and no
On Fri, Jul 22, 2016 at 06:34:11PM +0800, Cao jin wrote:
> Hi Daniel
>
> On 07/21/2016 11:39 PM, Daniel P. Berrange wrote:
> > On Thu, Jul 21, 2016 at 08:42:25AM -0600, Eric Blake wrote:
> > > On 07/21/2016 04:33 AM, Cao jin wrote:
> > > > It is never used, and now all connect is nonblocking via
>
On 22 July 2016 at 09:00, Amit Shah wrote:
> The following changes since commit 206d0c24361a083fbdcb2cc86fb75dc8b7f251a2:
>
> Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging
> (2016-07-21 20:12:37 +0100)
>
> are available in the git repository at:
>
> http://git.kern
From: Wen Congyang
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Signed-off-by: Changlong Xie
Reviewed-by: Eric Blake
Signed-off-by: Wang WeiWei
---
qapi/block-core.json | 19 +--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git
Block replication is a very important feature which is used for
continuous checkpoints(for example: COLO).
You can get the detailed information about block replication from here:
http://wiki.qemu.org/Features/BlockReplication
Usage:
Please refer to docs/block-replication.txt
You can get the patc
Hi Daniel
On 07/21/2016 11:39 PM, Daniel P. Berrange wrote:
On Thu, Jul 21, 2016 at 08:42:25AM -0600, Eric Blake wrote:
On 07/21/2016 04:33 AM, Cao jin wrote:
It is never used, and now all connect is nonblocking via
inet_connect_addr().
Could be squashed with 1/2. In fact, if you squash it
From: Changlong Xie
Normal backup(sync='none') workflow:
step 1. NBD peformance I/O write from client to server
qcow2_co_writev
bdrv_co_writev
...
bdrv_aligned_pwritev
notifier_with_return_list_notify -> backup_do_cow
bdrv_driver_pwritev // write new contents
From: Changlong Xie
This commit introduces six replication interfaces(for block, network etc).
Firstly we can use replication_(new/remove) to create/destroy replication
instances, then in migration we can use replication_(start/stop/do_checkpoint
/get_error)_all to handle all replication operatio
From: Wen Congyang
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Signed-off-by: Changlong Xie
Signed-off-by: Wang WeiWei
---
block/Makefile.objs | 1 +
block/replication.c | 658
2 files changed, 659 in
From: Wen Congyang
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Signed-off-by: Changlong Xie
Signed-off-by: Wang WeiWei
---
block/backup.c | 18 ++
include/block/block_backup.h | 3 +++
2 files changed, 21 insertions(+)
crea
From: Changlong Xie
Signed-off-by: Wen Congyang
Signed-off-by: Changlong Xie
Signed-off-by: Wang WeiWei
---
tests/.gitignore | 1 +
tests/Makefile.include | 4 +
tests/test-replication.c | 575 +++
3 files changed, 580 insertions(+)
c
From: Wen Congyang
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Signed-off-by: Changlong Xie
Signed-off-by: Wang WeiWei
---
docs/block-replication.txt | 239 +
1 file changed, 239 insertions(+)
create mode 10064
From: Wen Congyang
Signed-off-by: Wen Congyang
Signed-off-by: Changlong Xie
Signed-off-by: Wang WeiWei
---
block.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/block.c b/block.c
index 30d64e6..194a060 100644
--- a/block.c
+++ b/block.c
@@ -1311,6 +1311,23 @@ void bdr
From: Wen Congyang
Auto complete mirror job in background to prevent from
blocking synchronously
Signed-off-by: Wen Congyang
Signed-off-by: Changlong Xie
Signed-off-by: Wang WeiWei
---
block/mirror.c| 13 +
blockdev.c| 2 +-
include/block/block_int.h
From: Wen Congyang
Some programs that add a dependency on it will use
the block layer directly.
Signed-off-by: Wen Congyang
Signed-off-by: zhanghailiang
Signed-off-by: Gonglei
Signed-off-by: Changlong Xie
Reviewed-by: Stefan Hajnoczi
Reviewed-by: Jeff Cody
Signed-off-by: Wang WeiWei
---
On Fri, Jul 22, 2016 at 05:26:27AM -0400, Marc-André Lureau wrote:
> btw, I do not how to test this yet either.
I have a little test framework for the watchdog device which cuts
through a lot of the BS with running the full watchdog daemon, and
also has some simple instructions to follow:
http:
On Fri, 22 Jul 2016 10:04:35 +0200
Cornelia Huck wrote:
> On Thu, 21 Jul 2016 23:21:16 +0200
> Greg Kurz wrote:
>
> > From: Greg Kurz
> >
> > Without presuming if we got there because of a user mistake or some
> > more subtle bug in the tooling, it really does not make sense to
> > implement
1. s/@debug-level/@debug_level/
2. rearrange the versioning
3. s/server description/servers description/
Signed-off-by: Prasanna Kumar Kalever
---
qapi/block-core.json | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/qapi/block-core.json b/qapi/block-core.json
index f46
On Fri, 22 Jul 2016 14:35:05 +1000
David Gibson wrote:
> On Fri, Jul 22, 2016 at 12:56:26AM +0300, Michael S. Tsirkin wrote:
> > On Thu, Jul 21, 2016 at 05:54:31PM +0200, Igor Mammedov wrote:
> > > Series fixes migration issues caused by unstable cpu_index which depended
> > > on order cpus wer
Bharata B Rao writes:
> On Mon, Jul 18, 2016 at 10:35 PM, Nikunj A Dadhania
> wrote:
>> ISA 3.0 has introduced EO - Expanded Opcode. Introduce third level
>> indirect opcode table and corresponding parsing routines.
>>
>> EO (11:12) Expanded opcode field
>> Formats: XX1
>>
>> EO (11:15) Expanded
The print routine provided as part of the in-built bootloader had a bug
in that it attempted to use a jump instruction as part of a loop, but
the target has its upper bits zeroed leading to control flow
transferring to 0xb814 rather than the intended 0xbfc00814. Fix this
by using a branch instr
1 - 100 of 154 matches
Mail list logo
