On Fri, Jul 26, 2019 at 04:44:44PM +0200, Greg Kurz wrote:
> When the machine is reset, the MSI bitmap is cleared but the allocated
> MSIs are not freed. Some operating systems, such as AIX, can detect the
> previous configuration and assert.
>
> Empty the MSI cache, this performs the needed clean
On Fri, Jul 26, 2019 at 04:44:49PM +0200, Greg Kurz wrote:
> PHBs already take care of clearing the MSIs from the bitmap during reset
> or unplug. No need to do this globally from the machine code. Rather add
> an assert to ensure that PHBs have acted as expected.
>
> Signed-off-by: Greg Kurz
Ap
On Thu, Jul 18, 2019 at 01:54:12PM +0200, Cédric Le Goater wrote:
> This is to perform lookups in the NVT table when a vCPU is dispatched
> and possibily resend interrupts.
>
> Future XIVE chip will use a different class for the model of the
> interrupt controller and we might need to change the t
On 28/07/2019 09:46, David Gibson wrote:
> On Thu, Jul 18, 2019 at 01:54:12PM +0200, Cédric Le Goater wrote:
>> This is to perform lookups in the NVT table when a vCPU is dispatched
>> and possibily resend interrupts.
>>
>> Future XIVE chip will use a different class for the model of the
>> interru
sainath grandhi writes:
> Hello
> I am working with qemu tracing support and combined with tcg.
> I read that if tcg property is used for trace-event, it generates a
> trace-event once during translation and another trace-event after the
> execution.
>
> I made the following change in target/i3
Hi Stefan,
On 2019/7/26 17:11, Stefan Hajnoczi wrote:
> Most lo_do_lookup() have already checked that the parent inode exists.
> lo_lookup() hasn't and can therefore hit a NULL pointer dereference when
> lo_inode(req, parent) returns NULL.
>
> Signed-off-by: Stefan Hajnoczi
> ---
> contrib/virt
When there is no hint, the first un-overlapped range is the proper one.
Just break the loop instead of iterate the whole list.
Signed-off-by: Wei Yang
---
hw/mem/memory-device.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
index df3261b32a
We are already at the last condition check.
Signed-off-by: Wei Yang
---
hw/mem/memory-device.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
index 5f2c408036..df3261b32a 100644
--- a/hw/mem/memory-device.c
+++ b/hw/mem/memory-device.c
@@ -186,
When we iterate the memory-device list to get the available range, it is not
necessary to iterate the whole list.
1) the first non-overlap range is the proper one if no hint is provided
2) no more overlap for hinted range if tmp exceed it
Wei Yang (3):
memory-device: not necessary to use goto f
The memory-device list built by memory_device_build_list is ordered by
its address, this means if the tmp range exceed the hinted range, all
the following range will not overlap with it.
Signed-off-by: Wei Yang
---
hw/mem/memory-device.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
On 2019-07-22 16:21, Markus Armbruster wrote:
"Zoltán Kővágó" writes:
On 2019-07-16 08:23, Markus Armbruster wrote:
"Kővágó, Zoltán" writes:
Signed-off-by: Kővágó, Zoltán
---
ui/vnc.h| 2 ++
monitor/misc.c | 12 +++-
ui/vnc.c| 15 ++-
hmp-com
On 2019-07-28 15:42, Zoltán Kővágó wrote:
On 2019-07-22 16:21, Markus Armbruster wrote:
"Zoltán Kővágó" writes:
On 2019-07-16 08:23, Markus Armbruster wrote:
"Kővágó, Zoltán" writes:
Signed-off-by: Kővágó, Zoltán
---
ui/vnc.h | 2 ++
monitor/misc.c | 12 +++-
ui/v
On Fri, Jul 26, 2019 at 06:52:01PM -0400, John Snow wrote:
> We can turn logging on/off globally instead of per-function.
>
> Remove use_log from run_job, and use python logging to turn on
> diffable output when we run through a script entry point.
>
> (No, I have no idea why output on 245 change
On Fri, Jul 26, 2019 at 06:52:00PM -0400, John Snow wrote:
> Like script_main, but doesn't require a single point of entry.
> Replace all existing initialization sections with this drop-in replacement.
>
> This brings debug support to all existing script-style iotests.
>
> Note: supported_oses=['
Currently multifd migration has not been limited and it will consume
the whole bandwidth of Nic. These two patches add speed limitation to
it.
Ivan Ren (2):
migration: add qemu_file_update_rate_transfer interface
migration: add speed limit for multifd migration
migration/qemu-file.c | 5 +++
Add qemu_file_update_rate_transfer for just update bytes_xfer for
speed limitation. This will be used for further migration feature
such as multifd migration.
Signed-off-by: Ivan Ren
---
migration/qemu-file.c | 5 +
migration/qemu-file.h | 1 +
2 files changed, 6 insertions(+)
diff --git a/
Limit the speed of multifd migration through common speed limitation
qemu file.
Signed-off-by: Ivan Ren
---
migration/ram.c | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/migration/ram.c b/migration/ram.c
index 889148dd84..e3fde16776 100644
--- a/mig
On 28/07/2019 16:09, David Gibson wrote:
> On Sat, Jul 20, 2019 at 11:28:50AM +1000, Alexey Kardashevskiy wrote:
>> QEMU already implements H_CAS called by SLOF. The existing handler
>> prepares a diff FDT and SLOF applies it on top of its current tree.
>> In SLOF-less setup when the user explic
On Fri, Jul 26, 2019 at 01:49:00PM +0200, Greg Kurz wrote:
> On Fri, 26 Jul 2019 12:48:09 +0530
> sathn...@linux.vnet.ibm.com wrote:
>
> > From: Satheesh Rajendran
> >
> > Current acceptance test will not run in powerpc Little endian
> > environment due the arch name does not match the qemu bina
On Sun, Jul 28, 2019 at 11:06:27AM +0200, Cédric Le Goater wrote:
> On 28/07/2019 09:46, David Gibson wrote:
> > On Thu, Jul 18, 2019 at 01:54:12PM +0200, Cédric Le Goater wrote:
> >> This is to perform lookups in the NVT table when a vCPU is dispatched
> >> and possibily resend interrupts.
> >>
>
"Zoltán Kővágó" writes:
> On 2019-07-28 15:42, Zoltán Kővágó wrote:
>> On 2019-07-22 16:21, Markus Armbruster wrote:
>>> "Zoltán Kővágó" writes:
>>>
On 2019-07-16 08:23, Markus Armbruster wrote:
[...]
>> diff --git a/hmp-commands.hx b/hmp-commands.hx
>> index bfa5681dd2..fa7f009268
The set of patches include the block-related updates
of the record/replay icount feature:
- application of 'snapshot' option on the file layer instead of
the top one: command line and documentation fix
- implementation of bdrv_snapshot_goto for blkreplay driver
- start/stop fix in replay mode
From: Pavel Dovgalyuk
This patch disables setting '-snapshot' option on by default
in record/replay mode. This is needed for creating vmstates in record
and replay modes.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Kevin Wolf
---
vl.c | 10 --
1 file changed, 8 insertions(+), 2 deletio
From: Pavel Dovgalyuk
This patch enables making snapshots with blkreplay used in
block devices.
This function is required to make bdrv_snapshot_goto without
calling .bdrv_open which is not implemented.
Signed-off-by: Pavel Dovgalyuk
Acked-by: Kevin Wolf
---
block/blkreplay.c |8
From: Pavel Dovgalyuk
This patch updates the description of the command lines for using
record/replay with attached block devices.
Signed-off-by: Pavel Dovgalyuk
---
docs/replay.txt | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/docs/replay.txt b/docs/replay
From: Pavel Dovgalyuk
After recent updates block devices cannot be closed on qemu exit.
This happens due to the block request polling when replay is not finished.
Therefore now we stop execution recording before closing the block devices.
Signed-off-by: Pavel Dovgalyuk
---
replay/replay.c |
This series of patches will build Heterogeneous Memory Attribute Table (HMAT)
according to the command line. The ACPI HMAT describes the memory attributes,
such as memory side cache attributes and bandwidth and latency details,
related to the Memory Proximity Domain.
The software is expected to use
From: Liu Jingqi
Add -numa hmat-lb option to provide System Locality Latency and
Bandwidth Information. These memory attributes help to build
System Locality Latency and Bandwidth Information Structure(s)
in ACPI Heterogeneous Memory Attribute Table (HMAT).
Signed-off-by: Liu Jingqi
Signed-off-
From: Pavel Dovgalyuk
In record/replay mode bdrv queue is controlled by replay mechanism.
It does not allow saving or loading the snapshots
when bdrv queue is not empty. Stopping the VM is not blocked by nonempty
queue, but flushing the queue is still impossible there,
because it may cause deadlo
From: Pavel Dovgalyuk
Replay is capable of recording normal BH events, but sometimes
there are single use callbacks scheduled with aio_bh_schedule_oneshot
function. This patch enables recording and replaying such callbacks.
Block layer uses these events for calling the completion function.
Replay
Add struct NumaState in MachineState and move existing numa global
nb_numa_nodes(renamed as "num_nodes") into NumaState. And add variable
numa_support into MachineClass to decide which submachines support NUMA.
Suggested-by: Igor Mammedov
Suggested-by: Eduardo Habkost
Signed-off-by: Tao Xu
---
In ACPI 6.3 chapter 5.2.27 Heterogeneous Memory Attribute Table (HMAT),
The initiator represents processor which access to memory. And in 5.2.27.3
Memory Proximity Domain Attributes Structure, the attached initiator is
defined as where the memory controller responsible for a memory proximity
domain
From: Liu Jingqi
This structure describes the memory access latency and bandwidth
information from various memory access initiator proximity domains.
The latency and bandwidth numbers represented in this structure
correspond to rated latency and bandwidth for the platform.
The software could use
Public bug reported:
Hi all,
Version: QEMU emulator version 3.1.0 (Debian 1:3.1+dfsg-7+build1)
I'm running some DHCP traffic to a *custom* DHCP server with user-mode
networking in QEMU. I'm using port 30067 for the server, so this does
not conflict with the built-in DHCP server.
DHCP broadcasts
ACPI table HMAT has been introduced, QEMU now builds HMAT tables for
Heterogeneous Memory with boot option '-numa node'.
Add test cases on PC and Q35 machines with 2 numa nodes.
Because HMAT is generated when system enable numa, the
following tables need to be added for this test:
tests/acpi-tes
Move existing numa global have_numa_distance into NumaState.
Reviewed-by: Igor Mammedov
Reviewed-by: Liu Jingqi
Suggested-by: Igor Mammedov
Suggested-by: Eduardo Habkost
Signed-off-by: Tao Xu
---
No changes in v8.
---
hw/arm/sbsa-ref.c| 2 +-
hw/arm/virt-acpi-build.c | 2 +-
hw/arm/
In struct arm_boot_info, kernel_filename, initrd_filename and
kernel_cmdline are copied from from MachineState. This patch add
MachineState as a parameter into arm_load_dtb() and move the copy chunk
of kernel_filename, initrd_filename and kernel_cmdline into
arm_load_kernel().
Reviewed-by: Igor Ma
From: Liu Jingqi
Add -numa hmat-cache option to provide Memory Side Cache Information.
These memory attributes help to build Memory Side Cache Information
Structure(s) in ACPI Heterogeneous Memory Attribute Table (HMAT).
Signed-off-by: Liu Jingqi
Signed-off-by: Tao Xu
---
No changes in v8.
--
Move existing numa global numa_info (renamed as "nodes") into NumaState.
Reviewed-by: Igor Mammedov
Suggested-by: Igor Mammedov
Suggested-by: Eduardo Habkost
Signed-off-by: Tao Xu
Signed-off-by: Tao Xu
---
No changes in v8.
---
exec.c | 2 +-
hw/acpi/aml-build.c | 6
From: Liu Jingqi
This structure describes memory side cache information for memory
proximity domains if the memory side cache is present and the
physical device forms the memory side cache.
The software could use this information to effectively place
the data in memory to maximize the performance
On Mon, Jul 29, 2019 at 10:32:52AM +0800, Ivan Ren wrote:
>Add qemu_file_update_rate_transfer for just update bytes_xfer for
>speed limitation. This will be used for further migration feature
>such as multifd migration.
>
>Signed-off-by: Ivan Ren
>---
> migration/qemu-file.c | 5 +
> migration/
From: Liu Jingqi
HMAT is defined in ACPI 6.3: 5.2.27 Heterogeneous Memory Attribute Table
(HMAT). The specification references below link:
http://www.uefi.org/sites/default/files/resources/ACPI_6_3_final_Jan30.pdf
It describes the memory attributes, such as memory side cache
attributes and bandw
On Mon, Jul 29, 2019 at 10:32:53AM +0800, Ivan Ren wrote:
>Limit the speed of multifd migration through common speed limitation
>qemu file.
>
>Signed-off-by: Ivan Ren
>---
> migration/ram.c | 22 --
> 1 file changed, 12 insertions(+), 10 deletions(-)
>
>diff --git a/migration/ra
Patchew URL:
https://patchew.org/QEMU/156438176555.22071.10523120047318890136.stgit@pasha-Precision-3630-Tower/
Hi,
This series failed build test on s390x host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
#
On Sun, 28 Jul 2019 21:13:02 +0800
Wei Yang wrote:
> We are already at the last condition check.
>
> Signed-off-by: Wei Yang
Reviewed-by: Igor Mammedov
> ---
> hw/mem/memory-device.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/hw/mem/memory-device.c b/hw/mem/memory-device.c
> i
>> if (multifd_send_state->pages->used) {
>>-if (multifd_send_pages() < 0) {
>>+if (multifd_send_pages(rs) < 0) {
>> error_report("%s: multifd_send_pages fail", __func__);
>> return;
>> }
>>@@ -1083,6 +1084,7 @@ static void multifd_send_sync_main(
On 7/26/2019 10:17 PM, Eduardo Habkost wrote:
On Fri, Jul 26, 2019 at 03:43:43PM +0200, Igor Mammedov wrote:
On Wed, 24 Jul 2019 15:15:28 -0300
Eduardo Habkost wrote:
On Wed, Jul 24, 2019 at 05:48:11PM +0200, Igor Mammedov wrote:
On Wed, 24 Jul 2019 12:02:41 -0300
Eduardo Habkost wrote:
47 matches
Mail list logo
