Ping --- would you like me to resubmit the patch using CONFIG_BSD?
Cheers,
~Andrew
On Wed, Aug 1, 2018 at 10:39 AM Andrew Oates wrote:
>
>
>
> On Wed, Aug 1, 2018 at 6:10 AM Peter Maydell
> wrote:
>
>> On 1 August 2018 at 00:25, Andrew Oates wrote:
>> > Both CONFIG_BSD and not-CONFIG_LINUX w
Currently call gates are always treated as 32-bit gates. In IA-32e mode
(either compatibility or 64-bit submode), system segment descriptors are
always 64-bit. Treating them as 32-bit has the expected unfortunate
effect: only the lower 32 bits of the offset are loaded, the stack
pointer is trunca
Le 12/06/2018 à 02:51, Richard Henderson a écrit :
> This includes clone, getgroups, gettid, setfsgid, setfsuid,
> setgroups, setsid, setuid, fork, getegid, getegid32, geteuid,
> geteuid32, getgid, getgid32, getgroups32, getpgrp, getpid,
> getppid, getresgid, getresgid32, getresuid, getresuid32,
>
Le 12/06/2018 à 02:51, Richard Henderson a écrit :
> Transform outermost "break" to "return ret". If the immediately
> preceeding statement was an assignment to ret, return the value
> directly.
>
> Reviewed-by: Laurent Vivier
> Signed-off-by: Richard Henderson
> ---
> linux-user/syscall.c | 9
From: zhanghailiang
COLO thread may sleep at qemu_sem_wait(&s->colo_checkpoint_sem),
while failover works begin, It's better to wakeup it to quick
the process.
Signed-off-by: zhanghailiang
Reviewed-by: Dr. David Alan Gilbert
---
migration/colo.c | 8
1 file changed, 8 insertions(+)
From: Zhang Chen
This diagram make user better understand COLO.
Suggested by Markus Armbruster.
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
---
docs/COLO-FT.txt | 34 ++
1 file changed, 34 insertions(+)
diff --git a/docs/COLO-FT.txt b/docs/COLO-FT.txt
From: zhanghailiang
Notify all net filters about the checkpoint and failover event.
Signed-off-by: zhanghailiang
Reviewed-by: Dr. David Alan Gilbert
---
migration/colo.c | 15 +++
1 file changed, 15 insertions(+)
diff --git a/migration/colo.c b/migration/colo.c
index 688d6f40b2..
Filter needs to process the event of checkpoint/failover or
other event passed by COLO frame.
Signed-off-by: zhanghailiang
---
include/net/filter.h | 5 +
net/filter.c | 17 +
net/net.c| 28
3 files changed, 50 insertions(+)
After one round of checkpoint, the states between PVM and SVM
become consistent, so it is unnecessary to adjust the sequence
of net packets for old connections, besides, while failover
happens, filter-rewriter will into failover mode that needn't
handle the new TCP connection.
Signed-off-by: zhang
Libvirt or other high level software can use this command query colo status.
You can test this command like that:
{'execute':'query-colo-status'}
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
---
migration/colo.c| 21 +
qapi/migration.json | 32
From: zhanghailiang
Don't need to flush all VM's ram from cache, only
flush the dirty pages since last checkpoint
Signed-off-by: Li Zhijian
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
Signed-off-by: zhanghailiang
Reviewed-by: Dr. David Alan Gilbert
---
migration/ram.c | 9 +
Signed-off-by: Emilio G. Cota
---
linux-user/qemu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/linux-user/qemu.h b/linux-user/qemu.h
index b4959e41c6..e6a8bc5867 100644
--- a/linux-user/qemu.h
+++ b/linux-user/qemu.h
@@ -143,7 +143,7 @@ typedef struct TaskState {
/*
We record the address of the dirty pages that received,
it will help flushing pages that cached into SVM.
Here, it is a trick, we record dirty pages by re-using migration
dirty bitmap. In the later patch, we will start the dirty log
for SVM, just like migration, in this way, we can record both
the
From: Zhang Chen
We add is_colo_support_client_type() to check the net client type for
COLO-compare. Currently we just support TAP.
Suggested by Jason.
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
---
include/net/net.h | 1 +
net/colo-compare.c | 5 +
net/net.c | 14 +++
From: Zhang Chen
Suggested by Markus Armbruster rename COLO unknown mode to none mode.
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
Reviewed-by: Eric Blake
Reviewed-by: Markus Armbruster
---
migration/colo-failover.c | 2 +-
migration/colo.c | 2 +-
qapi/migration.json
We should not load PVM's state directly into SVM, because there maybe some
errors happen when SVM is receving data, which will break SVM.
We need to ensure receving all data before load the state into SVM. We use
an extra memory to cache these data (PVM's ram). The ram cache in secondary side
is i
There are several stages during loadvm/savevm process. In different stage,
migration incoming processes different types of sections.
We want to control these stages more accuracy, it will benefit COLO
performance, we don't have to save type of QEMU_VM_SECTION_START
sections everytime while do check
From: zhanghailiang
If some errors happen during VM's COLO FT stage, it's important to
notify the users of this event. Together with 'x-colo-lost-heartbeat',
Users can intervene in COLO's failover work immediately.
If users don't want to get involved in COLO's failover verdict,
it is still necess
During the time of VM's running, PVM may dirty some pages, we will transfer
PVM's dirty pages to SVM and store them into SVM's RAM cache at next checkpoint
time. So, the content of SVM's RAM cache will always be same with PVM's memory
after checkpoint.
Instead of flushing all content of PVM's RAM
We add almost full TCP state machine in filter-rewriter, except
TCPS_LISTEN and some simplify in VM active close FIN states.
After a net connection is closed, we didn't clear its releated resources
in connection_track_table, which will lead to memory leak.
Let't track the state of net connection,
We need to know if migration is going into COLO state for
incoming side before start normal migration.
Instead by using the VMStateDescription to send colo_state
from source side to destination side, we use MIG_CMD_ENABLE_COLO
to indicate whether COLO is enabled or not.
Signed-off-by: zhanghailia
For COLO FT, both the PVM and SVM run at the same time,
only sync the state while it needs.
So here, let SVM runs while not doing checkpoint, change
DEFAULT_MIGRATE_X_CHECKPOINT_DELAY to 200*100.
Besides, we forgot to release colo_checkpoint_semd and
colo_delay_timer, fix them here.
Signed-off-b
Make sure master start block replication after slave's block
replication started.
Besides, we need to activate VM's blocks before goes into
COLO state.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
---
migration/colo.c | 43 ++
While do checkpoint, we need to flush all the unhandled packets,
By using the filter notifier mechanism, we can easily to notify
every compare object to do this process, which runs inside
of compare threads as a coroutine.
Signed-off-by: zhanghailiang
Signed-off-by: Zhang Chen
Signed-off-by: Zha
It's a good idea to use notifier to notify COLO frame of
inconsistent packets comparing.
Signed-off-by: Zhang Chen
Signed-off-by: Zhang Chen
Signed-off-by: zhanghailiang
---
net/colo-compare.c | 37 ++---
net/colo-compare.h | 2 ++
2 files changed, 28 insertion
Hi~ All~
COLO Frame, block replication and COLO proxy(colo-compare,filter-mirror,
filter-redirector,filter-rewriter) have been exist in qemu
for long time, it's time to integrate these three parts to make COLO really
works.
In this series, we have some optimizations for COLO frame, including sep
On Wed, Aug 8, 2018 at 2:44 AM Dr. David Alan Gilbert
wrote:
> * Zhang Chen (zhangc...@gmail.com) wrote:
> > On Sat, Jul 28, 2018 at 2:51 AM, Dr. David Alan Gilbert <
> dgilb...@redhat.com
> > > wrote:
> >
> > > * Zhang Chen (zhangc...@gmail.com) wrote:
> > > > We record the address of the dirty
On Tue, Aug 7, 2018 at 10:30 PM Dr. David Alan Gilbert
wrote:
> * Zhang Chen (zhangc...@gmail.com) wrote:
> > Make sure master start block replication after slave's block
> > replication started.
> >
> > Besides, we need to activate VM's blocks before goes into
> > COLO state.
> >
> > Signed-off-
On 8/10/18 5:39 PM, Alberto Garcia wrote:
On Fri 10 Aug 2018 08:26:43 AM CEST, Leonid Bloch wrote:
Previously, the L2 cache was allocated without considering the image
size, and an option existed to manually determine its size.
This is not quite correct: the L2 cache was set to the maximum nee
On 08/07/2018 05:09 PM, Dr. David Alan Gilbert wrote:
* Peter Maydell (peter.mayd...@linaro.org) wrote:
On 7 August 2018 at 15:57, Dr. David Alan Gilbert wrote:
* Gerd Hoffmann (kra...@redhat.com) wrote:
On Fri, Jul 20, 2018 at 10:19:48AM +0200, remy.n...@blade-group.com wrote:
From: "Remy
On 8/10/18 4:14 PM, Alberto Garcia wrote:
On Fri 10 Aug 2018 08:26:42 AM CEST, Leonid Bloch wrote:
The refcount cache size does not need to be set to its minimum value in
read_cache_sizes(), as it is set to at least its minimum value in
qcow2_update_options_prepare().
Signed-off-by: Leonid Bloc
On 8/10/18 2:50 PM, Alberto Garcia wrote:
On Fri 10 Aug 2018 08:26:39 AM CEST, Leonid Bloch wrote:
Signed-off-by: Leonid Bloch
---
docs/qcow2-cache.txt | 16 +++-
qemu-options.hx | 9 ++---
2 files changed, 17 insertions(+), 8 deletions(-)
diff --git a/docs/qcow2-cach
Hi.
On 11.08.2018 14:23, Ming Lei wrote:
Please test for-4.19/block:
https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=for-4.19/block
This slow boot issue should have been fixed by the following commits:
1311326cf475 blk-mq: avoid to synchronize rcu inside
blk_clea
On Fri, Aug 10, 2018 at 9:31 PM, Richard Henderson
wrote:
> These insns require u=1; failed to include that in the switch
> cases. This probably happened during one of the rebases just
> before final commit.
>
> Fixes: d17b7cdcf4e
> Signed-off-by: Richard Henderson
Reviewed-by: Laurent Desnogue
No need to include linux/types.h, is empty anyway.
Suggested-by: Thomas Huth
Signed-off-by: Marcel Apfelbaum
---
hw/rdma/vmw/pvrdma_cmd.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/rdma/vmw/pvrdma_cmd.c b/hw/rdma/vmw/pvrdma_cmd.c
index 14255d609f..3f697c8db7 100644
--- a/hw/rdma/vmw/
Hi,
On 08/07/2018 03:19 PM, Laszlo Ersek wrote:
On 08/07/18 09:04, Jing Liu wrote:
Add hint to firmware (e.g. SeaBIOS) to reserve addtional
IO/MEM/PREF spaces for legacy pci-pci bridge, to enable
some pci devices hotplugging whose IO/MEM/PREF spaces
requests are larger than the ones in pci-pci
Hi,
On 08/06/2018 11:51 AM, Thomas Huth wrote:
On 07/28/2018 05:50 AM, Rebecca Cran wrote:
On 7/25/18 5:14 AM, Thomas Huth wrote:
Note that the error has been reported to happen on FreeBSD - so I doubt
that this header should be here.
Anyway, our include/standard-headers/linux/types.h is al
On Fri, Aug 10, 2018 at 9:31 PM, Richard Henderson
wrote:
> For 0x1.3p+0 + 0x1.ffep+14 = 0x1.0001fffp+15
> we dropped the sticky bit and so failed to raise inexact.
>
> Reported-by: Laurent Desnogues
> Signed-off-by: Richard Henderson
Tested-by: Laurent Desnogues
Reviewed-by: L
On Fri, Aug 10, 2018 at 9:31 PM, Richard Henderson
wrote:
> We were using the wrong flush-to-zero bit for the non-half input.
>
> Fixes: 46d33d1e3c9
> Cc: qemu-sta...@nongnu.org (3.0.1)
> Reported-by: Laurent Desnogues
> Signed-off-by: Richard Henderson
Tested-by: Laurent Desnogues
Reviewed-by
On Fri, Aug 10, 2018 at 9:31 PM, Richard Henderson
wrote:
> This makes float16_muladd correctly use FZ16 not FZ.
>
> Fixes: 6ceabaad110
> Cc: qemu-sta...@nongnu.org (3.0.1)
> Reported-by: Laurent Desnogues
> Signed-off-by: Richard Henderson
Tested-by: Laurent Desnogues
Reviewed-by: Laurent Des
On Fri, Aug 10, 2018 at 9:31 PM, Richard Henderson
wrote:
> When FZ is set, input_denormal exceptions are recognized, but this does
> not happen with FZ16. The softfloat code has no way to distinguish
> these bits and will raise such exceptions into fp_status_f16.flags,
> so ignore them when comp
On Fri, Aug 10, 2018 at 9:31 PM, Richard Henderson
wrote:
> When support for FZ16 was added, we failed to include the bit
> within FPCR_MASK, which means that it could never be set.
> Continue to zero FZ16 when ARMv8.2-FP16 is not enabled.
>
> Fixes: d81ce0ef2c4
> Cc: qemu-sta...@nongnu.org (3.0.1
On 08/11/2018 01:23 AM, Laurent Vivier wrote:
> This fixes java in a linux-user chroot:
> $ java --version
> qemu-sh4: .../accel/tcg/cpu-exec.c:634: cpu_loop_exec_tb: Assertion
> `use_icount' failed.
> qemu: uncaught target signal 6 (Aborted) - core dumped
> Aborted (core dumped)
>
> In g
On 08/11/2018 10:23 AM, Laurent Vivier wrote:
> This fixes java in a linux-user chroot:
> $ java --version
> qemu-sh4: .../accel/tcg/cpu-exec.c:634: cpu_loop_exec_tb: Assertion
> `use_icount' failed.
> qemu: uncaught target signal 6 (Aborted) - core dumped
> Aborted (core dumped)
>
> In g
> On Aug 11, 2018, at 1:40 AM, qemu-devel-requ...@nongnu.org wrote:
>
>
> Hello,
>
> Le 10/08/2018 ? 18:17, Programmingkid a ?crit?:
>>
>> Can a real 40p machine boot Windows NT 4.0 PowerPC?
>>
>>
>
> Yes.
>
> A real 40p machine is able to run (at least):
> - Windows NT (up to 4.0 SP1)
>
On 2018-08-10 08:28, Markus Armbruster wrote:
> Marc-André Lureau writes:
>
>> Spotted by ASAN:
>>
>> =
>> ==5378==ERROR: LeakSanitizer: detected memory leaks
>>
>> Direct leak of 65536 byte(s) in 1 object(s) allocated from:
>> #
On Sat, Aug 11, 2018 at 5:47 PM, Oleksandr Natalenko
wrote:
> Hi.
>
> I'd like to resurrect previous discussion [1] regarding slow kernel boot
> inside QEMU with virtio-scsi disks attached and blk_mq enabled.
>
> Symptom:
>
> [2.830857] ata1: SATA max UDMA/133 abar m4096@0x98002000 port 0x9800
Hi.
I'd like to resurrect previous discussion [1] regarding slow kernel boot
inside QEMU with virtio-scsi disks attached and blk_mq enabled.
Symptom:
[2.830857] ata1: SATA max UDMA/133 abar m4096@0x98002000 port
0x98002100 irq 36
[2.834559] ata2: SATA max UDMA/133 abar m4096@0x980020
Instantiate the LED matrix and set board-level
pull-up default values to buttons A and B.
This is necessary to calm down the microsoft pxt
javascript runtime available for the micro:bit.
Signed-off-by: Steffen Görtz
---
hw/arm/microbit.c | 52 ++-
incl
Instantiate NVMs, NVMC, UART, RNG, GPIO and TIMERs.
Signed-off-by: Steffen Görtz
---
hw/arm/nrf51_soc.c | 153 +++--
include/hw/arm/nrf51_soc.h | 16 +++-
2 files changed, 161 insertions(+), 8 deletions(-)
diff --git a/hw/arm/nrf51_soc.c b/hw/arm/nrf51_s
Nordic Semiconductor nRF51 SOCs are available
in different "variants" which differ in available memory.
This patchs adds a "variant" attribute to the SOC
so that the user can choose between different variants and
thus memory sizes.
See product specification
http://infocenter.nordicsemi.com/pdf/nR
The base address determines a peripherals id, which identifies its
interrupt line, see NRF51 reference manual section 10 peripheral
interface. This little gem calculates the peripheral id based
on its base address.
Signed-off-by: Steffen Görtz
---
hw/arm/nrf51_soc.c | 3 +++
1 file changed, 3 in
This patch series extends the stub of the nRF51 SOC and
bbc:microbit machine with the devices provided in the
previous patch series.
Based-on: 20180806100114.21410-1-cont...@steffen-goertz.de
Steffen Görtz (7):
hw/arm/nrf51_soc: nRF51 Calculate peripheral id from base address
arm: Move nRF51
This patch takes care that errors that occur during
instantiation of the cortex-m0 cpu are properly propagated.
Signed-off-by: Steffen Görtz
---
hw/arm/nrf51_soc.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/hw/arm/nrf51_soc.c b/hw/arm/nrf51_soc.c
index 226
This patch adds a link to the product specification
which contain additional information about the
Nordic Semiconductor nRF51 SOC series.
Furthermore it adds a copyright line to all
files that get changed significantly.
Signed-off-by: Steffen Görtz
---
hw/arm/microbit.c | 1 +
hw/arm/n
The machine state will be used to host the SOC
and board level devices like the LED matrix and
devices to handle to pushbuttons A and B.
Signed-off-by: Steffen Görtz
---
hw/arm/microbit.c | 38 --
include/hw/arm/microbit.h | 29
This fixes java in a linux-user chroot:
$ java --version
qemu-sh4: .../accel/tcg/cpu-exec.c:634: cpu_loop_exec_tb: Assertion
`use_icount' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
Aborted (core dumped)
In gen_conditional_jump() in the GUSA_EXCLUSIVE part, we must rese
57 matches
Mail list logo
