Rename the argument to fix:
tests/unit/test-aio.c:130:44: error: declaration shadows a variable in the
global scope [-Werror,-Wshadow]
static void set_event_notifier(AioContext *ctx, EventNotifier *notifier,
^
tests/unit/test-aio.c:22:20: note: p
Rename the global variable to avoid:
tests/unit/test-coroutine.c:430:11: error: declaration shadows a variable in
the global scope [-Werror,-Wshadow]
bool *done = opaque;
^
tests/unit/test-coroutine.c:438:10: error: declaration shadows a variable in
the global scope [-Werro
Rename the variable to fix:
tests/qtest/rtl8139-test.c:28:33: error: declaration shadows a variable in
the global scope [-Werror,-Wshadow]
static void save_fn(QPCIDevice *dev, int devfn, void *data)
^
tests/qtest/rtl8139-test.c:37:17: error: declaration sha
Rename the variable to fix:
tests/qtest/hd-geo-test.c:610:11: error: declaration shadows a variable in
the global scope [-Werror,-Wshadow]
char *img_file_name;
^
tests/qtest/hd-geo-test.c:80:14: note: previous declaration is here
static char *img_file_name[backend_last];
Clean up global variables shadowing in tests/
in order to be able to use -Wshadow with Clang.
Philippe Mathieu-Daudé (10):
system/qtest: Clean up global variable shadowing in
qtest_server_init()
tests/throttle: Clean up global variable shadowing
tests/virtio-scsi: Clean up global variabl
Rename the global 'adc' variable in order to avoid:
tests/qtest/npcm7xx_adc-test.c:98:58: error: declaration shadows a variable
in the global scope [-Werror,-Wshadow]
static uint32_t adc_read_con(QTestState *qts, const ADC *adc)
^
t
Rename the (unused) 'allow' argument, following the pattern
used by the other tests in this file. This fixes:
tests/qtest/virtio-scsi-test.c:159:61: error: declaration shadows a variable
in the global scope [-Werror,-Wshadow]
static void hotplug(void *obj, void *data, QGuestAllocator *alloc)
Rename the variable to fix:
tests/qtest/cdrom-test.c:40:50: error: declaration shadows a variable in the
global scope [-Werror,-Wshadow]
static int prepare_image(const char *arch, char *isoimage)
^
tests/qtest/cdrom-test.c:18:13: note: prev
On 9/10/23 12:02, Philippe Mathieu-Daudé wrote:
Rename the variable to fix:
tests/qtest/hd-geo-test.c:610:11: error: declaration shadows a variable in
the global scope [-Werror,-Wshadow]
char *img_file_name;
^
tests/qtest/hd-geo-test.c:80:14: note: previous declaration
On Mon 09 Oct 2023 12:02:43 PM +02, Philippe Mathieu-Daudé wrote:
> Follow all other tests pattern from this file, use the
> global 'cfg' variable to fix:
>
> tests/unit/test-throttle.c:621:20: error: declaration shadows a variable in
> the global scope [-Werror,-Wshadow]
> ThrottleConfig
On 09/10/2023 09.44, Thomas Huth wrote:
On 05/10/2023 19.38, Daniel P. Berrangé wrote:
When variables are used without being initialized, there is potential
to take advantage of data that was pre-existing on the stack from an
earlier call, to drive an exploit.
It is good practice to always init
On 10/9/23 08:32, marcandre.lur...@redhat.com wrote:
> From: Marc-André Lureau
>
> Add a "VFIODisplay" subsection whenever "x-ramfb-migrate" is turned on.
>
> Turn it off by default on machines <= 8.1 for compatibility reasons.
>
> Signed-off-by: Marc-André Lureau
> Reviewed-by: Laszlo Ersek
Hi Richard,
On 8/10/23 23:50, Richard W.M. Jones wrote:
RISCV_CPU(cs) uses a checked cast. When QOM cast debugging is enabled
this adds about 5% total overhead when emulating RV64 on x86-64 host.
Using a RISC-V guest with 16 vCPUs, 16 GB of guest RAM, virtio-blk
disk. The guest has a copy of
Hi Eric,
thanks for the quick answer.
On 10/9/23 11:29, Eric Auger wrote:
Hi Markus,
On 10/9/23 09:06, Markus Frank wrote:
Hello,
I have already sent this email to qemu-discuss but I did not get a reply.
https://lists.nongnu.org/archive/html/qemu-discuss/2023-09/msg00034.html
Maybe someone h
Philippe Mathieu-Daudé writes:
> Commit d11bf9bf0f ("vl: Factor configure_blockdev() out of main()")
> passed &bdo_queue as argument, but this isn't really necessary since
> there is only one call, so we still use the global variable.
>
> Dropping the &bdo_queue argument allows to silence this gl
On Sat, Oct 7, 2023 at 4:23 AM Yajun Wu wrote:
>
>
> On 10/6/2023 6:34 PM, Michael S. Tsirkin wrote:
> > External email: Use caution opening links or attachments
> >
> >
> > On Fri, Oct 06, 2023 at 11:47:55AM +0200, Hanna Czenczek wrote:
> >> On 06.10.23 11:26, Michael S. Tsirkin wrote:
> >>> On F
Coverity scan reports multiple false-positive "defects" for the
following series of actions in virtio.c:
MemoryRegionCache indirect_desc_cache;
address_space_cache_init_empty(&indirect_desc_cache);
address_space_cache_destroy(&indirect_desc_cache);
For some reason it's unable to recognize t
On Thu, Oct 5, 2023 at 5:01 PM Paolo Bonzini wrote:
>
> Currently, AUD_register_card picks the audio backend from either:
>
> - the first audiodev that was created
>
> - the audio_prio_list[] array, which can be customized at
> configure time
>
> This series instead extends -audio to define a de
On 09-10-23, 10:59, Alex Bennée wrote:
> Now the new base class supports config handling we can take advantage
> and make vhost-user-gpio a much simpler boilerplate wrapper. Also as
> this doesn't require any target specific hacks we only need to build
> the stubs once.
>
> Message-Id: <2023041816
On 09-10-23, 10:59, Alex Bennée wrote:
> Now we can take advantage of the new base class and make
> vhost-user-i2c a much simpler boilerplate wrapper. Also as this
> doesn't require any target specific hacks we only need to build the
> stubs once.
>
> Message-Id: <20230418162140.373219-13-alex.ben
When CPUArchState* is available (here CPUXtensaState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
XtensaCPU*). The QOM cast XTENSA_CPU() macro will be slower
when building with --enable-qom-cast-debug.
Signed-off-by: Philippe Mathieu-Daudé
---
target/xtensa/op_helper.c | 4 ++
When CPUArchState* is available (here CPUS390XState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
S390CPU*). The QOM cast S390_CPU() macro will be slower when
building with --enable-qom-cast-debug.
Signed-off-by: Philippe Mathieu-Daudé
---
target/s390x/diag.c | 2 +-
1 file ch
When we have a CPUArchState* pointer we can directly get the
corresponding ArchCPU* pointer with env_archcpu(). No need to
use QOM cast which is slower due when building with
--enable-qom-cast-debug.
This series replace ARCH_CPU(env_cpu(env)) by env_archcpu(env)
when possible.
Philippe Mathieu-Da
When CPUArchState* is available (here CPUX86State*), we can
use the fast env_archcpu() macro to get ArchCPU* (here X86CPU*).
The QOM cast X86_CPU() macro will be slower when building with
--enable-qom-cast-debug.
Pass CPUX86State* as argument to simulate_rdmsr / simulate_wrmsr
instead of a CPUStat
When CPUArchState* is available (here CPURISCVState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
RISCVCPU*). The QOM cast RISCV_CPU() macro will be slower
when building with --enable-qom-cast-debug.
Inspired-by: Richard W.M. Jones
Signed-off-by: Philippe Mathieu-Daudé
---
ta
We already have 'x86_cpu = X86_CPU(cpu)'. Use the variable
instead of doing another QOM cast with X86_CPU().
Signed-off-by: Philippe Mathieu-Daudé
---
target/i386/hvf/x86_emu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target/i386/hvf/x86_emu.c b/target/i386/hvf/x86
Commit 57df0dff1a1 (qapi: Extend -compat to set policy for unstable
interfaces) neglected to update the "Limitation" paragraph to mention
feature 'unstable' in addition to feature 'deprecated'. Do that now.
Signed-off-by: Markus Armbruster
---
qapi/compat.json | 4 ++--
1 file changed, 2 insert
When CPUArchState* is available (here CPUPPCState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
PowerPCCPU*). The QOM cast POWERPC_CPU() macro will be
slower when building with --enable-qom-cast-debug.
Signed-off-by: Philippe Mathieu-Daudé
---
target/ppc/excp_helper.c | 2 +-
On Mon, Oct 09, 2023 at 12:15:17PM +0200, Thomas Huth wrote:
> On 09/10/2023 09.44, Thomas Huth wrote:
> > On 05/10/2023 19.38, Daniel P. Berrangé wrote:
> > > When variables are used without being initialized, there is potential
> > > to take advantage of data that was pre-existing on the stack fr
At this moment there are eleven CPU extension properties that starts
with capital 'Z': Zifencei, Zicsr, Zihintntl, Zihintpause, Zawrs, Zfa,
Zfh, Zfhmin, Zve32f, Zve64f and Zve64d. All other extensions are named
with lower-case letters.
We want all properties to be named with lower-case letters sin
Hi,
This second version of the patch fixes a 'with with' typo in the
deprecated.rst document. No other changes made.
Patch already acked.
Changes from v1:
- remove 'with with' from docs/about/deprecated.rst
- v1 link:
https://lore.kernel.org/qemu-riscv/20231007171427.1210117-1-dbarb...@ventanam
Virtual CPU hotplug support is being added across various architectures[1][3].
This series adds various code bits common across all architectures:
1. vCPU creation and Parking code refactor [Patch 1]
2. Update ACPI GED framework to support vCPU Hotplug [Patch 4,6,7]
3. ACPI CPUs AML code change [P
KVM vCPU creation is done once during the initialization of the VM when Qemu
thread is spawned. This is common to all the architectures.
Hot-unplug of vCPU results in destruction of the vCPU object in QOM but the
corresponding KVM vCPU object in the Host KVM is not destroyed and its
representative
ACPI CPU hotplug related initialization should only happen if ACPI_CPU_HOTPLUG
support has been enabled for particular architecture. Add cpu_hotplug_hw_init()
stub to avoid compilation break.
Signed-off-by: Salil Mehta
Reviewed-by: Jonathan Cameron
Reviewed-by: Gavin Shan
---
hw/acpi/acpi-cpu-
OSPM evaluates _EVT method to map the event. The CPU hotplug event eventually
results in start of the CPU scan. Scan figures out the CPU and the kind of
event(plug/unplug) and notifies it back to the guest. Update the GED AML _EVT
method with the call to \\_SB.CPUS.CSCN
Also, macro CPU_SCAN_METHOD
CPUs Control device(\\_SB.PCI0) register interface for the x86 arch is based on
PCI and is IO port based and hence existing CPUs AML code assumes _CRS objects
would evaluate to a system resource which describes IO Port address. But on ARM
arch CPUs control device(\\_SB.PRES) register interface is m
CPU ctrl-dev MMIO region length could be used in ACPI GED and various other
architecture specific places. Move ACPI_CPU_HOTPLUG_REG_LEN macro to more
appropriate common header file.
Signed-off-by: Salil Mehta
Reviewed-by: Alex Bennée
Reviewed-by: Jonathan Cameron
Reviewed-by: Gavin Shan
---
h
On 10/8/23 22:39, Alistair Francis wrote:
On Sun, Oct 8, 2023 at 3:15 AM Daniel Henrique Barboza
wrote:
At this moment there are eleven CPU extension properties that starts
with capital 'Z': Zifencei, Zicsr, Zihintntl, Zihintpause, Zawrs, Zfa,
Zfh, Zfhmin, Zve32f, Zve64f and Zve64d. All othe
Virtual CPU Hot-unplug leads to unrealization of a CPU object. This also
involves destruction of the CPU AddressSpace. Add common function to help
destroy the CPU AddressSpace.
Signed-off-by: Salil Mehta
---
include/exec/cpu-common.h | 8
include/hw/core/cpu.h | 1 +
softmmu/physm
On 9/10/23 13:04, Markus Armbruster wrote:
Commit 57df0dff1a1 (qapi: Extend -compat to set policy for unstable
interfaces) neglected to update the "Limitation" paragraph to mention
With retrospective, 'experimental' seems more meaningful. Anyway,
too late.
feature 'unstable' in addition to f
ACPI GED(as described in the ACPI 6.2 spec) can be used to generate ACPI events
when OSPM/guest receives an interrupt listed in the _CRS object of GED. OSPM
then maps or demultiplexes the event by evaluating _EVT method.
This change adds the support of cpu hotplug event initialization in the
exist
Add common function to help unregister the GDB Register Space. This shall be
done in context to the CPU unrealization.
Signed-off-by: Salil Mehta
---
gdbstub/gdbstub.c | 15 +++
include/exec/gdbstub.h | 5 +
2 files changed, 20 insertions(+)
diff --git a/gdbstub/gdbstub.c
ACPI GED shall be used to convey to the guest kernel about any CPU hot-(un)plug
events. Therefore, existing ACPI GED framework inside QEMU needs to be enhanced
to support CPU hotplug state and events.
Co-developed-by: Keqian Zhu
Signed-off-by: Keqian Zhu
Signed-off-by: Salil Mehta
Reviewed-by:
From: Jean-Philippe Brucker
When a KVM vCPU is reset following a PSCI CPU_ON call, its power state
is not synchronized with KVM at the moment. Because the vCPU is not
marked dirty, we miss the call to kvm_arch_put_registers() that writes
to KVM's MP_STATE. Force mp_state synchronization.
Signed-
Thomas Huth writes:
> On 29/09/2023 17.06, Bernhard Beschow wrote:
>> Am 21. September 2023 23:44:42 UTC schrieb Gurchetan Singh
>> :
>>> On Tue, Sep 19, 2023 at 3:07 PM Akihiko Odaki
>>> wrote:
>>>
On 2023/09/20 3:36, Bernhard Beschow wrote:
>
>
> Am 15. September 2023 02:38:0
On Mon, 9 Oct 2023, Bernhard Beschow wrote:
Am 8. Oktober 2023 11:08:58 UTC schrieb BALATON Zoltan :
On Sun, 8 Oct 2023, Mark Cave-Ayland wrote:
On 05/10/2023 23:13, BALATON Zoltan wrote:
The initial value for BARs were set in reset method for emulating
legacy mode at start but this does not
On 10/9/23 08:02, Philippe Mathieu-Daudé wrote:
When CPUArchState* is available (here CPURISCVState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
RISCVCPU*). The QOM cast RISCV_CPU() macro will be slower
when building with --enable-qom-cast-debug.
Inspired-by: Richard W.M.
On Mon, Oct 09, 2023 at 10:37:25AM +0200, Thomas Huth wrote:
> Rename some variables to avoid compiler warnings when compiling
> with -Wshadow=local.
>
> Signed-off-by: Thomas Huth
> ---
> v2: Renamed the variable to something more unique
>
> contrib/vhost-user-gpu/vugpu.h | 8 ---
Philippe Mathieu-Daudé writes:
> On 9/10/23 13:04, Markus Armbruster wrote:
>> Commit 57df0dff1a1 (qapi: Extend -compat to set policy for unstable
>> interfaces) neglected to update the "Limitation" paragraph to mention
>
> With retrospective, 'experimental' seems more meaningful. Anyway,
> too
On 10/9/23 08:02, Philippe Mathieu-Daudé wrote:
When CPUArchState* is available (here CPUPPCState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
PowerPCCPU*). The QOM cast POWERPC_CPU() macro will be
slower when building with --enable-qom-cast-debug.
Signed-off-by: Philippe
On 9/10/23 12:26, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
Commit d11bf9bf0f ("vl: Factor configure_blockdev() out of main()")
passed &bdo_queue as argument, but this isn't really necessary since
there is only one call, so we still use the global variable.
Dropping the &bdo_que
On Mon, 9 Oct 2023, Philippe Mathieu-Daudé wrote:
Hi Zoltan,
On 6/10/23 00:13, BALATON Zoltan wrote:
The AmigaOne is a rebranded MAI Teron board that uses U-Boot firmware
with patches to support AmigaOS and is very similar to pegasos2 so can
be easily emulated sharing most code with pegasos2. T
Hi,
On 10/9/23 12:25, Markus Frank wrote:
> Hi Eric,
>
> thanks for the quick answer.
>
> On 10/9/23 11:29, Eric Auger wrote:
>> Hi Markus,
>>
>> On 10/9/23 09:06, Markus Frank wrote:
>>> Hello,
>>>
>>> I have already sent this email to qemu-discuss but I did not get a
>>> reply.
>>> https://list
> On 09-Oct-2023, at 3:17 PM, Philippe Mathieu-Daudé wrote:
>
> Fix:
>
> hw/acpi/pcihp.c:499:36: error: declaration shadows a variable in the global
> scope [-Werror,-Wshadow]
> MemoryRegion *address_space_io,
> ^
> include/exec/add
On 09/10/2023 13.45, Michael S. Tsirkin wrote:
On Mon, Oct 09, 2023 at 10:37:25AM +0200, Thomas Huth wrote:
Rename some variables to avoid compiler warnings when compiling
with -Wshadow=local.
Signed-off-by: Thomas Huth
---
v2: Renamed the variable to something more unique
contrib/vhost-u
On 09.10.23 12:43, Ilya Maximets wrote:
Coverity scan reports multiple false-positive "defects" for the
following series of actions in virtio.c:
MemoryRegionCache indirect_desc_cache;
address_space_cache_init_empty(&indirect_desc_cache);
address_space_cache_destroy(&indirect_desc_cache)
Am 8. Oktober 2023 11:08:58 UTC schrieb BALATON Zoltan :
>On Sun, 8 Oct 2023, Mark Cave-Ayland wrote:
>> On 05/10/2023 23:13, BALATON Zoltan wrote:
>>
>>> The initial value for BARs were set in reset method for emulating
>>> legacy mode at start but this does not work because PCI code resets
>>
On 09.10.23 13:28, Salil Mehta wrote:
KVM vCPU creation is done once during the initialization of the VM when Qemu
thread is spawned. This is common to all the architectures.
Hot-unplug of vCPU results in destruction of the vCPU object in QOM but the
corresponding KVM vCPU object in the Host KVM
On 09.10.23 13:28, Salil Mehta wrote:
CPU ctrl-dev MMIO region length could be used in ACPI GED and various other
architecture specific places. Move ACPI_CPU_HOTPLUG_REG_LEN macro to more
appropriate common header file.
Signed-off-by: Salil Mehta
Reviewed-by: Alex Bennée
Reviewed-by: Jonathan
On 09.10.23 13:28, Salil Mehta wrote:
ACPI CPU hotplug related initialization should only happen if ACPI_CPU_HOTPLUG
support has been enabled for particular architecture. Add cpu_hotplug_hw_init()
stub to avoid compilation break.
Signed-off-by: Salil Mehta
Reviewed-by: Jonathan Cameron
Reviewe
> On 09-Oct-2023, at 3:17 PM, Philippe Mathieu-Daudé wrote:
>
> Fix:
>
> hw/core/loader.c:1073:27: error: declaration shadows a variable in the
> global scope [-Werror,-Wshadow]
> bool option_rom, MemoryRegion *mr,
>^
> include/sysemu/sysem
I apologize for the late reply.
Peter Xu writes:
> On Tue, Sep 26, 2023 at 10:40:27PM +0200, Markus Armbruster wrote:
>> Peter Xu writes:
>>
>> > Quotting from Markus in his replies:
>>
>> Quoting
>>
>> Suggest something like "Markus recently wrote:"
>
> Will do.
>
>>
>> > migrate-set-par
On 09.10.23 13:28, Salil Mehta wrote:
ACPI GED(as described in the ACPI 6.2 spec) can be used to generate ACPI events
when OSPM/guest receives an interrupt listed in the _CRS object of GED. OSPM
then maps or demultiplexes the event by evaluating _EVT method.
This change adds the support of cpu h
On Sun, 8 Oct 2023 01:47:38 +0530
wrote:
> From: Ankit Agrawal
>
> The CPU cache coherent device memory can be added as NUMA nodes
> distinct from the system memory nodes. These nodes are associated
> with the device and Qemu needs a way to maintain this link.
Hi Ankit,
I'm not sure I'm convi
On Sun, 8 Oct 2023 01:47:40 +0530
wrote:
> From: Ankit Agrawal
>
> NVIDIA GPU's support MIG (Mult-Instance GPUs) feature [1], which allows
> partitioning of the GPU device resources (including device memory) into
> several (upto 8) isolated instances. Each of the partitioned memory needs
> a de
On 2023/10/9 5:50, Richard W.M. Jones wrote:
RISCV_CPU(cs) uses a checked cast. When QOM cast debugging is enabled
this adds about 5% total overhead when emulating RV64 on x86-64 host.
Using a RISC-V guest with 16 vCPUs, 16 GB of guest RAM, virtio-blk
disk. The guest has a copy of the qemu s
Thomas Huth writes:
> On 09/10/2023 13.45, Michael S. Tsirkin wrote:
>> On Mon, Oct 09, 2023 at 10:37:25AM +0200, Thomas Huth wrote:
>>> Rename some variables to avoid compiler warnings when compiling
>>> with -Wshadow=local.
>>>
>>> Signed-off-by: Thomas Huth
>>> ---
>>> v2: Renamed the varia
Philippe Mathieu-Daudé writes:
> On 9/10/23 12:26, Markus Armbruster wrote:
>> Philippe Mathieu-Daudé writes:
>>
>>> Commit d11bf9bf0f ("vl: Factor configure_blockdev() out of main()")
>>> passed &bdo_queue as argument, but this isn't really necessary since
>>> there is only one call, so we sti
On 2023/10/9 19:02, Philippe Mathieu-Daudé wrote:
When CPUArchState* is available (here CPURISCVState*), we
can use the fast env_archcpu() macro to get ArchCPU* (here
RISCVCPU*). The QOM cast RISCV_CPU() macro will be slower
when building with --enable-qom-cast-debug.
Inspired-by: Richard W.M.
On Mon, 9 Oct 2023, Philippe Mathieu-Daudé wrote:
Since commit 93198b6cad ("i2c: Split smbus into parts") the SDRAM
types are enumerated as sdram_type in "hw/i2c/smbus_eeprom.h".
Using the enum removes this global shadow warning:
hw/mips/malta.c:209:12: error: declaration shadows a variable in
In v3:
- Use env_archcpu
- Rerun the benchmark to get new "after" figures
Rich.
RISCV_CPU(cs) uses a checked cast. When QOM cast debugging is enabled
this adds about 5% total overhead when emulating RV64 on x86-64 host.
Using a RISC-V guest with 16 vCPUs, 16 GB of guest RAM, virtio-blk
disk. The guest has a copy of the qemu source tree. The test
involves compiling the qemu
On Mon, Oct 09, 2023 at 08:36:28PM +0800, LIU Zhiwei wrote:
>
> On 2023/10/9 5:50, Richard W.M. Jones wrote:
> >RISCV_CPU(cs) uses a checked cast. When QOM cast debugging is enabled
> >this adds about 5% total overhead when emulating RV64 on x86-64 host.
> >
> >Using a RISC-V guest with 16 vCPUs,
On Mon, Oct 09, 2023 at 01:02:35PM +0200, Philippe Mathieu-Daudé wrote:
> When CPUArchState* is available (here CPURISCVState*), we
> can use the fast env_archcpu() macro to get ArchCPU* (here
> RISCVCPU*). The QOM cast RISCV_CPU() macro will be slower
> when building with --enable-qom-cast-debug.
On 09.10.23 14:30, Jonathan Cameron wrote:
On Sun, 8 Oct 2023 01:47:40 +0530
wrote:
From: Ankit Agrawal
NVIDIA GPU's support MIG (Mult-Instance GPUs) feature [1], which allows
partitioning of the GPU device resources (including device memory) into
several (upto 8) isolated instances. Each of
On 10/9/23 11:09, Eric Auger wrote:
Hi All,
This is the v5 respin of the IOMMUFD prerequisite series.
This applies on top of vfio-next:
https://github.com/legoater/qemu/, branch vfio-next.
Per Cédric's suggestion, the IOMMUFD patchset v1[1] is now split
into two series, this prerequisite series
On 2023/10/9 20:53, Richard W.M. Jones wrote:
On Mon, Oct 09, 2023 at 08:36:28PM +0800, LIU Zhiwei wrote:
On 2023/10/9 5:50, Richard W.M. Jones wrote:
RISCV_CPU(cs) uses a checked cast. When QOM cast debugging is enabled
this adds about 5% total overhead when emulating RV64 on x86-64 host.
From: Andrei Gudkov via
This patch allows to measure dirty page rate for
sub-second intervals of time. An optional argument is
introduced -- calc-time-unit. For example:
{"execute": "calc-dirty-rate", "arguments":
{"calc-time": 500, "calc-time-unit": "millisecond"} }
Millisecond granularity al
dirtylimit-dirtyrate-pull-request-20231009
for you to fetch changes up to 84719f6d0b75448400068adb78d85000e884f0cd:
migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time (2023-10-08
15:06:12 +0800)
Dirtylimit and dirtyrat
From: Andrei Gudkov via
Currently query-dirty-rate uses QEMU_CLOCK_REALTIME as
the source for start-time field. This translates to
clock_gettime(CLOCK_MONOTONIC), i.e. number of seconds
since host boot. This is not very useful. The only
reasonable use case of start-time I can imagine is to
check
On 10/9/23 04:20, Zhenzhong Duan wrote:
Hi,
This trivial patchset fixes a incremental memory leak in rare case,
and some cleanup on ap/ccw.
This patchset is based on vfio-next.
Applied on vfio-next.
Thanks,
C.
On 10/6/23 19:59, Joao Martins wrote:
On 06/10/2023 18:09, Cédric Le Goater wrote:
Getting acks from everyone will be difficultsince some PHBs are orphans.
[...] This is what gets me a bit hesitant
orphans shouldn't be an issue, nor the PPC emulated machines. We will see
what other maintaine
On Mon, 9 Oct 2023, Bernhard Beschow wrote:
Am 8. Oktober 2023 11:08:58 UTC schrieb BALATON Zoltan :
On Sun, 8 Oct 2023, Mark Cave-Ayland wrote:
On 05/10/2023 23:13, BALATON Zoltan wrote:
The initial value for BARs were set in reset method for emulating
legacy mode at start but this does not
On Mon, 09 Oct 2023 12:59, Alex Bennée wrote:
diff --git a/hw/virtio/meson.build b/hw/virtio/meson.build
index 51c3f97c2d..d0b963199c 100644
--- a/hw/virtio/meson.build
+++ b/hw/virtio/meson.build
@@ -18,8 +18,15 @@ if have_vhost
# fixme - this really should be generic
specific_virtio_ss
On 10/4/2023 8:55 PM, Fabiano Rosas wrote:
Het Gala writes:
modify multifd tcp common test to incorporate the new QAPI
syntax defined.
Suggested-by: Aravind Retnakaran
Signed-off-by: Het Gala
Reviewed-by: Daniel P. Berrangé
---
tests/qtest/migration-test.c | 7 ++-
1 file changed, 6 i
On 10/4/2023 9:02 PM, Fabiano Rosas wrote:
Fabiano Rosas writes:
Het Gala writes:
On 04/10/23 7:03 pm, Fabiano Rosas wrote:
Het Gala writes:
This is v11 patchset of modified 'migrate' and 'migrate-incoming' QAPI design
for upstream review.
Update: Daniel has reviewed all patches and i
On 10/9/23 14:58, Cédric Le Goater wrote:
> On 10/9/23 11:09, Eric Auger wrote:
>> Hi All,
>>
>> This is the v5 respin of the IOMMUFD prerequisite series.
>> This applies on top of vfio-next:
>> https://github.com/legoater/qemu/, branch vfio-next.
>>
>> Per Cédric's suggestion, the IOMMUFD patch
Hi David,
Thanks for the review.
> From: David Hildenbrand
> Sent: Monday, October 9, 2023 1:21 PM
> To: Salil Mehta ; qemu-devel@nongnu.org;
> qemu-...@nongnu.org
> Cc: m...@kernel.org; jean-phili...@linaro.org; Jonathan Cameron
> ; lpieral...@kernel.org;
> peter.mayd...@linaro.org; richard.hen
> From: David Hildenbrand
> Sent: Monday, October 9, 2023 1:22 PM
> To: Salil Mehta ; qemu-devel@nongnu.org; qemu-
> a...@nongnu.org
> Cc: m...@kernel.org; jean-phili...@linaro.org; Jonathan Cameron
> ; lpieral...@kernel.org;
> peter.mayd...@linaro.org; richard.hender...@linaro.org;
> imamm...@red
On Mon, 09 Oct 2023 12:59, Alex Bennée wrote:
diff --git a/docs/system/devices/vhost-user.rst
b/docs/system/devices/vhost-user.rst
index a80e95a48a..0f9eec3f00 100644
--- a/docs/system/devices/vhost-user.rst
+++ b/docs/system/devices/vhost-user.rst
@@ -15,6 +15,47 @@ to the guest. The code is m
ository at:
https://github.com/newfriday/qemu.git
tags/dirtylimit-dirtyrate-pull-request-20231009
for you to fetch changes up to 84719f6d0b75448400068adb78d85000e884f0cd:
migration/dirtyrate: use QEMU_CLOCK_HOST to report start-time (2023-10-08
15:0
On 9/10/23 14:48, Richard W.M. Jones wrote:
RISCV_CPU(cs) uses a checked cast. When QOM cast debugging is enabled
this adds about 5% total overhead when emulating RV64 on x86-64 host.
Using a RISC-V guest with 16 vCPUs, 16 GB of guest RAM, virtio-blk
disk. The guest has a copy of the qemu sour
> From: David Hildenbrand
> Sent: Monday, October 9, 2023 1:23 PM
> To: Salil Mehta ; qemu-devel@nongnu.org; qemu-
> a...@nongnu.org
> Cc: m...@kernel.org; jean-phili...@linaro.org; Jonathan Cameron
> ; lpieral...@kernel.org;
> peter.mayd...@linaro.org; richard.hender...@linaro.org;
> imamm...@red
Manos Pitsidianakis writes:
> On Mon, 09 Oct 2023 12:59, Alex Bennée wrote:
>>diff --git a/hw/virtio/meson.build b/hw/virtio/meson.build
>>index 51c3f97c2d..d0b963199c 100644
>>--- a/hw/virtio/meson.build
>>+++ b/hw/virtio/meson.build
>>@@ -18,8 +18,15 @@ if have_vhost
>> # fixme - this re
On 10/9/23 15:38, Eric Auger wrote:
On 10/9/23 14:58, Cédric Le Goater wrote:
On 10/9/23 11:09, Eric Auger wrote:
Hi All,
This is the v5 respin of the IOMMUFD prerequisite series.
This applies on top of vfio-next:
https://github.com/legoater/qemu/, branch vfio-next.
Per Cédric's suggestion,
Marcin Juszkiewicz writes:
> Update prebuilt firmware images:
> - Neoverse V1/N2 cpu support
> - non-secure EL2 virtual timer
> - XHCI controller in DSDT
>
> With those changes we can now run OpenBSD as part of sbsa-ref tests.
>
> Signed-off-by: Marcin Juszkiewicz
Queued to maintainer/october
On 09.10.23 15:49, Salil Mehta wrote:
From: David Hildenbrand
Sent: Monday, October 9, 2023 1:23 PM
To: Salil Mehta ; qemu-devel@nongnu.org; qemu-
a...@nongnu.org
Cc: m...@kernel.org; jean-phili...@linaro.org; Jonathan Cameron
; lpieral...@kernel.org;
peter.mayd...@linaro.org; richard.hender...@
On 09.10.23 15:42, Salil Mehta wrote:
Hi David,
Thanks for the review.
From: David Hildenbrand
Sent: Monday, October 9, 2023 1:21 PM
To: Salil Mehta ; qemu-devel@nongnu.org;
qemu-...@nongnu.org
Cc: m...@kernel.org; jean-phili...@linaro.org; Jonathan Cameron
; lpieral...@kernel.org;
peter.mayd
> On 09-Oct-2023, at 3:17 PM, Philippe Mathieu-Daudé wrote:
>
> Fix:
>
> hw/display/vga.c:2307:29: error: declaration shadows a variable in the
> global scope [-Werror,-Wshadow]
>MemoryRegion *address_space_io, bool init_vga_ports)
>^
> include/e
> From: David Hildenbrand
> Sent: Monday, October 9, 2023 1:27 PM
> To: Salil Mehta ; qemu-devel@nongnu.org; qemu-
> a...@nongnu.org
> Cc: m...@kernel.org; jean-phili...@linaro.org; Jonathan Cameron
> ; lpieral...@kernel.org;
> peter.mayd...@linaro.org; richard.hender...@linaro.org;
> imamm...@red
101 - 200 of 366 matches
Mail list logo
