On Wed, Feb 12, 2020 at 03:44:19PM -0600, Eric Blake wrote:
> On 2/11/20 5:54 AM, Roman Kagan wrote:
> > Devices (virtio-blk, scsi, etc.) and the block layer are happy to use
> > 32-bit for logical_block_size, physical_block_size, and min_io_size.
> > However, the properties in BlockConf are define
Patchew URL:
https://patchew.org/QEMU/20200213073630.2125-1-fangyi...@huawei.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ==
On 12.02.2020 18:43, Stefan Hajnoczi wrote:
On Tue, Feb 11, 2020 at 05:14:14PM +0300, Denis Plotnikov wrote:
The goal is to reduce the amount of requests issued by a guest on
1M reads/writes. This rises the performance up to 4% on that kind of
disk access pattern.
The maximum chunk size to b
On Thu, Feb 13, 2020 at 03:36:26PM +0800, Ying Fang wrote:
> On ARM64 platform, cpu frequency is retrieved via ACPI CPPC.
> A virtual cpufreq device based on ACPI CPPC is created to
> present cpu frequency info to the guest.
>
> The default frequency is set to host cpu nominal frequency,
> which i
On Wed, 12 Feb 2020 21:48:42 +0100
Philippe Mathieu-Daudé wrote:
> On 2/7/20 12:39 PM, Alex Bennée wrote:
> > From: Thomas Huth
> >
> > Since we can now use a s390x host on Travis, we can also build and
> > test the s390-ccw bios images there. For this we have to make sure
> > that roms/SLOF is
Patchew URL:
https://patchew.org/QEMU/1581580379-54109-1-git-send-email-robert...@linux.intel.com/
Hi,
This series failed the docker-quick@centos7 build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TES
On Mon, 3 Feb 2020 14:29:39 +1100
Alexey Kardashevskiy wrote:
> At the moment "pseries" starts in SLOF which only expects the FDT blob
> pointer in r3. As we are going to introduce a OpenFirmware support in
> QEMU, we will be booting OF clients directly and these expect a stack
> pointer in r1,
Supporting a build platform beyond its end of life makes no sense.
Spell that out just to be clear.
Signed-off-by: Markus Armbruster
---
qemu-doc.texi | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/qemu-doc.texi b/qemu-doc.texi
index a1ef6b6484..33b9597b1d 100644
--
Could HiSilicon respond to Dann & Rafael's comments #36 and #38?
Is there an upstream acceptable patch that addresses this issue?
** Changed in: kunpeng920
Status: Confirmed => Incomplete
** Changed in: qemu (Ubuntu Bionic)
Status: Confirmed => Incomplete
** Changed in: qemu (Ubunt
The only difference to hardware revision 4 is that the device doesn't
switch to VGA mode in case someone happens to touch a VGA register,
which should make things more robust in configurations with multiple
vga devices.
Swtiching back to VGA mode happens on reset, either full machine
reset or qxl
The following changes since commit e18e5501d8ac692d32657a3e1ef545b14e72b730:
Merge remote-tracking branch
'remotes/dgilbert-gitlab/tags/pull-virtiofs-20200210' into staging (2020-02-10
18:09:14 +)
are available in the Git repository at:
git://git.kraxel.org/qemu tags/vga-202
On Thu, Feb 13, 2020 at 11:08:35AM +0300, Denis Plotnikov wrote:
> On 12.02.2020 18:43, Stefan Hajnoczi wrote:
> > On Tue, Feb 11, 2020 at 05:14:14PM +0300, Denis Plotnikov wrote:
> > > The goal is to reduce the amount of requests issued by a guest on
> > > 1M reads/writes. This rises the performan
=》Could HiSilicon respond to Dann & Rafael's comments #36 and #38?
=》Is there an upstream acceptable patch that addresses this issue?
No upstream patchset， I Only provide a private solution and do not know
this root cause.
--
You received this bug notification because you are a member of qemu-
d
On 13.02.2020 12:08, Stefan Hajnoczi wrote:
On Thu, Feb 13, 2020 at 11:08:35AM +0300, Denis Plotnikov wrote:
On 12.02.2020 18:43, Stefan Hajnoczi wrote:
On Tue, Feb 11, 2020 at 05:14:14PM +0300, Denis Plotnikov wrote:
The goal is to reduce the amount of requests issued by a guest on
1M read
On Thu, Feb 13, 2020 at 09:43:34AM +0100, Markus Armbruster wrote:
> Supporting a build platform beyond its end of life makes no sense.
> Spell that out just to be clear.
Agreed, that matches my intention when first writing this doc.
>
> Signed-off-by: Markus Armbruster
> ---
> qemu-doc.texi |
Signed-off-by: Zhimin Feng
---
migration/rdma.c | 25 +
migration/rdma.h | 16
2 files changed, 21 insertions(+), 20 deletions(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index 2f1e69197f..23f7f525f4 100644
--- a/migration/rdma.c
+++ b/migration/r
Creation of the multifd send threads for RDMA migration,
nothing inside yet.
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 33 +---
migration/multifd.h | 2 +
migration/qemu-file.c | 5 +++
migration/qemu-file.h | 1 +
migration/rdma.c | 88
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 6 ++
migration/rdma.c| 17 +
2 files changed, 23 insertions(+)
diff --git a/migration/multifd.c b/migration/multifd.c
index 4ae25fc88f..c986d4c247 100644
--- a/migration/multifd.c
+++ b/migration/multifd.c
@@ -389,6 +
Signed-off-by: Zhimin Feng
---
migration/migration.c | 9 +
migration/migration.h | 1 +
2 files changed, 10 insertions(+)
diff --git a/migration/migration.c b/migration/migration.c
index 3a21a4686c..10a13e0c79 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -2208,6 +22
Signed-off-by: Zhimin Feng
---
migration/migration.c | 10 ++
migration/migration.h | 1 +
2 files changed, 11 insertions(+)
diff --git a/migration/migration.c b/migration/migration.c
index 10a13e0c79..819089a7ea 100644
--- a/migration/migration.c
+++ b/migration/migration.c
@@ -107,6 +
Add the 'qemu_rdma_registration' function,
multifd send threads call it to register memory.
Signed-off-by: Zhimin Feng
---
migration/rdma.c | 51
migration/rdma.h | 1 +
2 files changed, 52 insertions(+)
diff --git a/migration/rdma.c b/migration
We need to use the RDMAContext in migration/multifd.c
so it has to be exported.
Signed-off-by: Zhimin Feng
---
migration/rdma.c | 243 --
migration/rdma.h | 247 +++
2 files changed, 247 insertions(+), 243 de
Hi
This is a version against current code. It is based on the multifd work.
we can use the multifd parameters for rdma transport. All data is
transported by the multifd RDMA channels and the main channel is only
used to distribute its to the different multifd channels.
Zhimin Feng (14):
migrati
Hi Jason,
On Mon, Aug 19, 2019 at 1:40 PM Jason Wang wrote:
>
>
> On 2019/8/19 下午1:24, Bin Meng wrote:
> > On Sat, Aug 10, 2019 at 9:58 AM Alistair Francis
> > wrote:
> >> On Fri, Aug 9, 2019 at 12:26 AM Bin Meng wrote:
> >>> When CADENCE_GEM_ERR_DEBUG is turned on, there are several
> >>> com
register memory for multifd RDMA channels and transmit the destination
the keys to source to use including the virtual addresses.
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 34 +---
migration/rdma.c| 48 +
2 fi
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 15
migration/rdma.c| 58 +
migration/rdma.h| 2 ++
3 files changed, 70 insertions(+), 5 deletions(-)
diff --git a/migration/multifd.c b/migration/multifd.c
index c986d4c247..ba
On 2020/2/13 下午5:39, Bin Meng wrote:
Hi Jason,
On Mon, Aug 19, 2019 at 1:40 PM Jason Wang wrote:
On 2019/8/19 下午1:24, Bin Meng wrote:
On Sat, Aug 10, 2019 at 9:58 AM Alistair Francis wrote:
On Fri, Aug 9, 2019 at 12:26 AM Bin Meng wrote:
When CADENCE_GEM_ERR_DEBUG is turned on, there a
Signed-off-by: Zhimin Feng
---
migration/rdma.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index 873c17dc03..eb7c2edbe7 100644
--- a/migration/rdma.c
+++ b/migration/rdma.c
@@ -1749,7 +1749,7 @@ static int qemu_rdma_write_one(QEMUFi
Zhimin Feng wrote:
> If the migration is cancelled when it is in the completion phase,
> the migration state is set to MIGRATION_STATUS_CANCELLING.
> The VM maybe wait for the 'pause_sem' semaphore in migration_maybe_pause
> function, so that VM always is paused.
>
> Reported-by: Euler Robot
> Si
Transmit initial packet through the multifd RDMA channels,
so that we can identify the multifd channels.
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 33 +
migration/rdma.c| 2 ++
2 files changed, 23 insertions(+), 12 deletions(-)
diff --git a/migrat
In both sides. We still don't transmit anything through them,
and we only build the RDMA connections.
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 103 ---
migration/multifd.h | 10
migration/rdma.c| 115 --
All data is sent by multifd Channels, so we only register its for
multifd channels and main channel don't register its.
Signed-off-by: Zhimin Feng
---
migration/rdma.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/migration/rdma.c b/migration/rdma.c
index eb7c2edbe7..b7b56c0493 1006
Signed-off-by: Zhimin Feng
---
migration/multifd.c | 6 ++
migration/rdma.c| 5 ++---
migration/rdma.h| 1 +
3 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/migration/multifd.c b/migration/multifd.c
index ba5e0b11d0..886c8e1271 100644
--- a/migration/multifd.c
+++ b/mig
On 13/02/20 08:40, Alexey Kardashevskiy wrote:
>>>
>>> memory-region: system
>>> - (prio 0, i/o): system
>>> -01ff (prio 0, romd): omap_sx1.flash0-1
>>> -01ff (prio 0, rom): omap_sx1.flash0-0
>> Eh
wrote:
> From: Pan Nengyuan
>
> spotted by asan, 'check-qtest-aarch64' runs fail if sanitizers is enabled.
>
> Reported-by: Euler Robot
> Signed-off-by: Pan Nengyuan
Reviewed-by: Juan Quintela
On Wed, Feb 12, 2020 at 11:27:34PM +0100, Laszlo Ersek wrote:
> Michael,
>
> On 01/29/20 15:06, Igor Mammedov wrote:
> > Commit 3a61c8db9d25 introduced CPHP_GET_CPU_ID_CMD command but
> > did not sufficiently describe it. Fix it by adding missing command
> > documentation.
> >
> > Fixes: 3a61c8db
Zhimin Feng wrote:
> Signed-off-by: Zhimin Feng
Reviewed-by: Juan Quintela
Zhimin Feng wrote:
> Signed-off-by: Zhimin Feng
> ---
> migration/migration.c | 10 ++
> migration/migration.h | 1 +
> 2 files changed, 11 insertions(+)
>
> diff --git a/migration/migration.c b/migration/migration.c
> index 10a13e0c79..819089a7ea 100644
> --- a/migration/migration.c
>
On 2/13/20 3:56 AM, kuhn.chen...@huawei.com wrote:
From: Chen Qun
It's easy to reproduce as follow:
virsh qemu-monitor-command vm1 --pretty '{"execute": "device-list-properties",
"arguments":{"typename":"exynos4210.uart"}}'
ASAN shows memory leak stack:
#1 0xfffd896d71cb in g_malloc0 (/lib6
Zhimin Feng wrote:
> Creation of the multifd send threads for RDMA migration,
> nothing inside yet.
>
> Signed-off-by: Zhimin Feng
> ---
> migration/multifd.c | 33 +---
> migration/multifd.h | 2 +
> migration/qemu-file.c | 5 +++
> migration/qemu-file.h | 1 +
> migration/rd
Patchew URL:
https://patchew.org/QEMU/20200213093755.370-1-fengzhim...@huawei.com/
Hi,
This series failed the docker-mingw@fedora build test. Please find the testing
commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ==
On 11/02/2020 09:45, pannengy...@huawei.com wrote:
> From: Pan Nengyuan
>
> spotted by asan, 'check-qtest-aarch64' runs fail if sanitizers is enabled.
>
> Reported-by: Euler Robot
> Signed-off-by: Pan Nengyuan
> ---
> tests/qtest/migration-test.c | 14 --
> 1 file changed, 12 inse
On Thu, Feb 13, 2020 at 03:49:52PM +0800, Yubo Miao wrote:
> From: miaoyubo
>
> Since devices could not directly plugged into pxb-pcie,
Hmm is this different from the root port? intergrated devices
do exist for that actually.
> under arm,
how is arm special?
> one
> pcie-root port is plugged
* Wei Yang (richardw.y...@linux.intel.com) wrote:
> ram_discard_range() unmap page for specific range. To be specific, this
> clears related page table entries so that userfault would be triggered.
> But this step is not necessary at the very beginning.
>
> ram_postcopy_incoming_init() is called w
On 13/02/20 02:43, Alexey Kardashevskiy wrote:
>
> Ok. So, I have made a small firmware which does OF CI, loads GRUB and
> instantiates RTAS:
> https://github.com/aik/of1275
> Quite raw but gives the idea.
>
> It does not contain drivers and still relies on QEMU to hook an OF path
> to a backend.
On Thu, Feb 13, 2020 at 03:49:51PM +0800, Yubo Miao wrote:
> From: miaoyubo
>
> Currently virt machine is not supported by pxb-pcie,
> and only one main host bridge described in ACPI tables.
> Under this circumstance, different io numas for differnt devices
> is not possible, in order to present
On 13/02/20 08:52, Robert Hoo wrote:
> +
> +}
> +#pragma GCC pop_options
> +#endif
> +
> +
> /* Note that for test_buffer_is_zero_next_accel, the most preferred
> * ISA must have the least significant bit.
> */
> -#define CACHE_AVX21
> -#define CACHE_SSE42
> -#define CACHE_SSE24
>
On Thu, 13 Feb 2020 at 03:49, Gavin Shan wrote:
> On 2/12/20 10:34 PM, Peter Maydell wrote:
> > Yeah, this is on my list to look at; Richard Henderson also could
> > have a look at it. From a quick scan I suspect you may be missing
> > handling for AArch32.
> Yes, the functionality is only suppor
On 12/02/20 18:51, Peter Maydell wrote:
> On Wed, 12 Feb 2020 at 16:51, Philippe Mathieu-Daudé
> wrote:
>> We stopped testing in-tree builds 2 months ago:
>>
>> commit bc4486fb233573e77b6e9ad6d6379afb5e37ad8c
>> Author: Paolo Bonzini
>> Date: Wed Dec 11 15:33:49 2019 +0100
>>
>> ci: bui
* Daniel Cho (daniel...@qnap.com) wrote:
> Hi Hailiang,
>
> 1.
> OK, we will try the patch
> “0001-COLO-Optimize-memory-back-up-process.patch”,
> and thanks for your help.
>
> 2.
> We understand the reason to compare PVM and SVM's packet. However, the
> empty of SVM's packet queue might h
On 2/13/20 4:39 PM, Richard Henderson wrote:
On 2/12/20 7:49 PM, Gavin Shan wrote:
On 2/12/20 10:34 PM, Peter Maydell wrote:
Yeah, this is on my list to look at; Richard Henderson also could
have a look at it. From a quick scan I suspect you may be missing
handling for AArch32.
[Thanks for c
Le 13/02/2020 à 02:46, Aleksandar Markovic a écrit :
> From: Aleksandar Markovic
>
> Update mips syscall numbers based on Linux kernel tag v5.5.
>
> CC: Aurelien Jarno
> CC: Aleksandar Rikalo
> Signed-off-by: Aleksandar Markovic
> ---
> linux-user/mips/syscall_nr.h | 45 +++
On Wed, 5 Feb 2020 at 11:06, Gavin Shan wrote:
>
> This supports QMP/HMP "nmi" command by injecting SError interrupt to
> guest, which is expected to crash with that. Currently, It's supported
> on two CPU models: "host" and "max".
>
> Signed-off-by: Gavin Shan
> ---
> hw/arm/virt.c | 1
On Thu, Feb 13, 2020 at 12:28:25PM +0300, Denis Plotnikov wrote:
>
>
> On 13.02.2020 12:08, Stefan Hajnoczi wrote:
> > On Thu, Feb 13, 2020 at 11:08:35AM +0300, Denis Plotnikov wrote:
> > > On 12.02.2020 18:43, Stefan Hajnoczi wrote:
> > > > On Tue, Feb 11, 2020 at 05:14:14PM +0300, Denis Plotnik
On Thu, 13 Feb 2020 11:58:35 +1100
David Gibson wrote:
> Upcoming Secure VM support for pSeries machines introduces some
> complications for virtio, since the transfer buffers need to be
> explicitly shared so that the hypervisor can access them.
>
> While it's not strictly speaking dependent on
On Tue, Feb 11, 2020 at 03:34:48PM -0500, Alexander Bulekov wrote:
> 524b4c2c5c moves vl.c into softmmu/ , breaking the checkpatch
524b4c2c5c is a local git sha1. That commit will have a different sha1
when applied to qemu.git/master. Saying "The next patch" instead would
be fine.
However, this
On Thu, 2020-02-13 at 11:30 +0100, Paolo Bonzini wrote:
> On 13/02/20 08:52, Robert Hoo wrote:
> > +
> > +}
> > +#pragma GCC pop_options
> > +#endif
> > +
> > +
> > /* Note that for test_buffer_is_zero_next_accel, the most
> > preferred
> > * ISA must have the least significant bit.
> > */
> >
On Thu, 6 Feb 2020 at 18:34, Guenter Roeck wrote:
>
> Initialize EHCI controllers on AST2400 and AST2500 using the existing
> TYPE_PLATFORM_EHCI. After this change, booting ast2500-evb into Linux
> successfully instantiates a USB interface.
>
> ehci-platform 1e6a3000.usb: EHCI Host Controller
> eh
On Tue, Feb 11, 2020 at 03:34:49PM -0500, Alexander Bulekov wrote:
> Signed-off-by: Alexander Bulekov
> ---
> Makefile.objs | 2 --
> Makefile.target | 1 +
> softmmu/Makefile.objs | 2 ++
> vl.c => softmmu/vl.c | 0
> 4 files changed, 3 insertions(+), 2 deletions(-)
Please update
On Fri, 7 Feb 2020 at 17:45, Guenter Roeck wrote:
>
> Initialize EHCI controllers on AST2600 using the existing
> TYPE_PLATFORM_EHCI. After this change, booting ast2600-evb
> into Linux successfully instantiates a USB interface after
> the necessary changes are made to its devicetree files.
>
> eh
Valid signal numbers are between 1 (SIGHUP) and SIGRTMAX.
System includes define _NSIG to SIGRTMAX + 1, but
QEMU (like kernel) defines TARGET_NSIG to TARGET_SIGRTMAX.
Fix all the checks involving the signal range.
Signed-off-by: Laurent Vivier
Reviewed-by: Peter Maydell
Tested-by: Taylor Simps
The following changes since commit e18e5501d8ac692d32657a3e1ef545b14e72b730:
Merge remote-tracking branch
'remotes/dgilbert-gitlab/tags/pull-virtiofs-20200210' into staging (2020-02-10
18:09:14 +)
are available in the Git repository at:
git://github.com/vivier/qemu.git tags/linux-user-
This signal is defined for all other targets and we will need it later
Signed-off-by: Laurent Vivier
[pm: that this was actually an ABI change in the hppa kernel (at kernel
version 3.17, kernel commit 1f25df2eff5b25f52c139d). Before that
SIGRTMIN was 37...
All our other HPPA TARGET_SIG* values ar
"The purpose of this option is to allow an application to obtain the
security credentials of a Unix stream socket peer. It is analogous to
SO_PEERCRED (which provides authentication using standard Unix credentials
of pid, uid and gid), and extends this concept to other security
models." -- https:/
Some RT signals can be in use by glibc,
it's why SIGRTMIN (34) is generally greater than __SIGRTMIN (32).
So SIGRTMIN cannot be mapped to TARGET_SIGRTMIN.
Instead of swapping only SIGRTMIN and SIGRTMAX, map all the
range [TARGET_SIGRTMIN ... TARGET_SIGRTMAX - X] to
[__SIGRTMIN + X ... SIGRT
No functional changes. Prepare the field for future fixes.
Remove memset(.., 0, ...) that is useless on a static array
Signed-off-by: Laurent Vivier
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Peter Maydell
Tested-by: Taylor Simpson
Message-Id: <20200212125658.644558-3-laur...@vivier.eu>
> > + MIPS_SYS(sys_clock_gettime64, 2)
> > + MIPS_SYS(sys_clock_settime64, 4)
> > + MIPS_SYS(sys_clock_adjtime64, 2) /* 405 */
> > + MIPS_SYS(sys_clock_getres_time64, 4)
>
> According to
> https://github.com/strace/strace/blob/master/linux/syscallent-common-32.h:
>
> [BASE_NR + 406] = { 2, 0, SEN
From: Aleksandar Markovic
Update microblaze syscall numbers based on Linux kernel v5.5.
CC: Edgar E. Iglesias
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/microblaze/syscall_nr.h | 45 ++
1 file changed, 45 insertions(+)
d
From: Aleksandar Markovic
v2->v3:
- corrected number of arguments for two mips syscalls
v1->v2:
- corrected mips parts based on Laurent's review
This series is a spin-off of another larger linux-user series
that become too large to handle, hence these patches related to
syscall numbers ar
From: Aleksandar Markovic
Update alpha syscall numbers based on Linux kernel v5.5.
CC: Richard Henderson
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/alpha/syscall_nr.h | 35 +++
1 file changed, 35 insertions(+)
diff --git a/l
From: Aleksandar Markovic
Update m68k syscall numbers based on Linux kernel v5.5.
CC: Laurent Vivier
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/m68k/syscall_nr.h | 50 +++-
1 file changed, 49 insertions(+), 1 deletion
From: Aleksandar Markovic
Update sh4 syscall numbers based on Linux kernel v5.5.
CC: Aurelien Jarno
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/sh4/syscall_nr.h | 48 +
1 file changed, 48 insertions(+)
diff --git
From: Aleksandar Markovic
Update mips syscall numbers based on Linux kernel tag v5.5.
CC: Aurelien Jarno
CC: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/mips/syscall_nr.h | 45 +++
linux-user/mips64/syscall_nr.h | 50
From: Aleksandar Markovic
Update arm syscall numbers based on Linux kernel v5.5.
CC: Peter Maydell
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/arm/syscall_nr.h | 44
1 file changed, 44 insertions(+)
diff --git a/
From: Aleksandar Markovic
Currently, there is no usage of TARGET_NR_syscall_count for target
xtensa, and there is no obvious indication if there is some planned
usage in future.
CC: Max Filippov
Acked-by: Max Filippov
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-
From: Aleksandar Markovic
Update xtensa syscall numbers based on Linux kernel v5.5.
CC: Max Filippov
Acked-by: Max Filippov
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/xtensa/syscall_nr.h | 38 --
1 file changed, 36 inser
From: Aleksandar Markovic
Update x86_64 syscall numbers based on Linux kernel v5.5.
CC: Paolo Bonzini
CC: Richard Henderson
CC: Eduardo Habkost
Signed-off-by: Aleksandar Markovic
Reviewed-by: Laurent Vivier
---
linux-user/x86_64/syscall_nr.h | 24
1 file changed, 2
Hi Palmer,
On Thu, Feb 13, 2020 at 1:30 AM Palmer Dabbelt wrote:
>
> The following changes since commit 81a23caf47956778c5a5056ad656d1ef92bf9659:
>
> Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request'
> into staging (2020-02-10 17:08:51 +)
>
> are available in the Git
On 13.02.2020 14:45, Stefan Hajnoczi wrote:
On Thu, Feb 13, 2020 at 12:28:25PM +0300, Denis Plotnikov wrote:
On 13.02.2020 12:08, Stefan Hajnoczi wrote:
On Thu, Feb 13, 2020 at 11:08:35AM +0300, Denis Plotnikov wrote:
On 12.02.2020 18:43, Stefan Hajnoczi wrote:
On Tue, Feb 11, 2020 at 05:
On Wed, 12 Feb 2020 at 14:44, David Hildenbrand wrote:
>
> We want to actually resize ram blocks (make everything between
> used_length and max_length inaccessible) - however, not all ram block
> notifiers will support that. Let's teach the notifier that ram blocks
> are indeed resizable, but keep
Le 13/02/2020 à 13:29, Aleksandar Markovic a écrit :
> From: Aleksandar Markovic
>
> v2->v3:
>
> - corrected number of arguments for two mips syscalls
>
> v1->v2:
>
> - corrected mips parts based on Laurent's review
>
> This series is a spin-off of another larger linux-user series
> that
On 2/13/20 2:01 AM, Roman Kagan wrote:
On Wed, Feb 12, 2020 at 03:44:19PM -0600, Eric Blake wrote:
On 2/11/20 5:54 AM, Roman Kagan wrote:
Devices (virtio-blk, scsi, etc.) and the block layer are happy to use
32-bit for logical_block_size, physical_block_size, and min_io_size.
However, the prope
Public bug reported:
After upgrade qemu to v4.2.0, vhost-user multi-queues interrupt failed
with event idx interrupt mode when reconnection happens.
Test Environment:
DPDK version: DPDK v19.11
Other software versions: qemu 4.2.0.
OS: Linux 4.15.0-20-generic
Compiler: gcc (Ubuntu 7.3.0-16ubuntu3)
Gerd Hoffmann writes:
> Hi,
>
>> Thanks to the QMP coroutine support, the screendump handler can
>> trigger a graphic_hw_update(), yield and let the main loop run until
>> update is done. Then the handler is resumed, and the ppm_save() will
>> write the screen image to disk in the coroutine con
On Tue, 11 Feb 2020 at 19:42, Richard Henderson
wrote:
>
> For the purpose of rebuild_hflags_a64, we do not need to compute
> all of the va parameters, only tbi. Moreover, we can compute them
> in a form that is more useful to storing in hflags.
>
> This eliminates the need for aa64_va_parameter_
On Tue, 11 Feb 2020 at 19:42, Richard Henderson
wrote:
>
> Select should always be 0 for a regime with one range.
>
> Signed-off-by: Richard Henderson
This change makes sense, and matches what aa32_va_parameters() does,
but I think we need to update some of the callsites.
(1) In get_phys_addr_l
On Thu, 13 Feb 2020 at 13:12, Peter Maydell wrote:
>
> On Tue, 11 Feb 2020 at 19:42, Richard Henderson
> wrote:
> >
> > Select should always be 0 for a regime with one range.
> >
> > Signed-off-by: Richard Henderson
>
> This change makes sense, and matches what aa32_va_parameters() does,
> but I
On Thu, 13 Feb 2020 at 10:09, Philippe Mathieu-Daudé wrote:
>
> On 2/13/20 3:56 AM, kuhn.chen...@huawei.com wrote:
> > From: Chen Qun
> >
> > It's easy to reproduce as follow:
> > virsh qemu-monitor-command vm1 --pretty '{"execute":
> > "device-list-properties",
> > "arguments":{"typename":"exyn
From: "Dr. David Alan Gilbert"
rdma_accept_incoming_migration is called from an fd handler and
can't return an Error * anywhere.
Currently it's leaking Error's in errp/local_err - there's
no point putting them in there unless we can report them.
Turn most into fprintf's, and the last into an err
From: Keqian Zhu
qemu_savevm_nr_failover_devices() is originally designed to
get the number of failover devices, but it actually returns
the number of "unplug-pending" failover devices now. Moreover,
what drives migration state to wait-unplug should be the number
of "unplug-pending" failover devi
The following changes since commit e18e5501d8ac692d32657a3e1ef545b14e72b730:
Merge remote-tracking branch
'remotes/dgilbert-gitlab/tags/pull-virtiofs-20200210' into staging (2020-02-10
18:09:14 +)
are available in the Git repository at:
https://github.com/juanquintela/qemu.git tags/pul
From: "Dr. David Alan Gilbert"
There's an assert in autoconverge that checks that we quit the
iteration when we go below the expected threshold. Philippe
saw a case where this assert fired with the measured value
slightly over the threshold. (about 3k out of a few million).
I can think of two r
From: Pan Nengyuan
spotted by asan, 'check-qtest-aarch64' runs fail if sanitizers is enabled.
Reported-by: Euler Robot
Signed-off-by: Pan Nengyuan
Reviewed-by: Juan Quintela
Reviewed-by: Laurent Vivier
Signed-off-by: Juan Quintela
---
tests/qtest/migration-test.c | 14 --
1 fil
From: Zhimin Feng
If the migration is cancelled when it is in the completion phase,
the migration state is set to MIGRATION_STATUS_CANCELLING.
The VM maybe wait for the 'pause_sem' semaphore in migration_maybe_pause
function, so that VM always is paused.
Reported-by: Euler Robot
Signed-off-by:
If one is compiling more than one tree from the same source, it is
possible that they need different submodules. Change the check to see
that all modules that we are interested in are updated, discarding the
ones that we don't care about.
Signed-off-by: Juan Quintela
---
v1->v2:
patchw insists
On Thu, 2020-01-23 at 09:17 +0100, Johannes Berg wrote:
> Hi,
>
> Here's a repost of all the patches I sent back in August, with the
> in-band notifications rebased over the reset patch, so IDs have now
> changed a bit.
Ping?
The patches still apply on top of latest qemu.
I wanted to send some
On Thu, 13 Feb 2020 at 13:12, Peter Maydell wrote:
>
> On Tue, 11 Feb 2020 at 19:42, Richard Henderson
> wrote:
> >
> > Select should always be 0 for a regime with one range.
> >
> > Signed-off-by: Richard Henderson
>
> This change makes sense, and matches what aa32_va_parameters() does,
> but I
Daniel P. Berrangé writes:
> On Thu, Jan 30, 2020 at 09:03:00AM +0100, Markus Armbruster wrote:
>> Juan Quintela writes:
>>
>> > It will indicate which level use for compression.
>> >
>> > Signed-off-by: Juan Quintela
>>
>> This is slightly confusing (there is no zlib compression), unless you
On Thu, Feb 13, 2020 at 02:26:10PM +0100, Johannes Berg wrote:
> On Thu, 2020-01-23 at 09:17 +0100, Johannes Berg wrote:
> > Hi,
> >
> > Here's a repost of all the patches I sent back in August, with the
> > in-band notifications rebased over the reset patch, so IDs have now
> > changed a bit.
>
On 12.02.20 19:03, David Hildenbrand wrote:
> On 12.02.20 14:42, David Hildenbrand wrote:
>> We already allow resizable ram blocks for anonymous memory, however, they
>> are not actually resized. All memory is mmaped() R/W, including the memory
>> exceeding the used_length, up to the max_length.
>>
1 - 100 of 373 matches
Mail list logo
