On Wed, Oct 26, 2022 at 02:54:25PM -0700, Isaku Yamahata wrote:
> On Tue, Oct 25, 2022 at 11:13:43PM +0800,
> Chao Peng wrote:
>
> > A memslot with KVM_MEM_PRIVATE being set can include both fd-based
> > private memory and hva-based shared memory. Architecture code (like TDX
> > code) can tell wh
On 10/25/2022 11:13 PM, Chao Peng wrote:
In memory encryption usage, guest memory may be encrypted with special
key and can be accessed only by the guest itself. We call such memory
private memory. It's valueless and sometimes can cause problem to allow
userspace to access guest private memory. T
On 27/10/2022 22.42, Christian Schoenebeck wrote:
On Thursday, October 27, 2022 7:37:07 PM CEST Stefan Hajnoczi wrote:
On Thu, 27 Oct 2022 at 12:38, Christian Schoenebeck
wrote:
On Thursday, October 27, 2022 5:53:47 PM CEST Thomas Huth wrote:
On 24/10/2022 12.54, Christian Schoenebeck wrote:
Am 27.10.22 um 14:17 schrieb Daniel P. Berrangé:
> On Thu, Oct 27, 2022 at 12:14:43PM +0200, Fiona Ebner wrote:
>> +warn_report("not removing PID file on exit: cannot resolve PID
>> file"
>> +" path: %s: %s", pid_file, strerror(errno));
>> +return;
>
Remove usage of aio_context_acquire by always submitting asynchronous
AIO to the current thread's LuringState.
In order to prevent mistakes from the caller side, avoid passing LuringState
in luring_io_{plug/unplug} and luring_co_submit.
Signed-off-by: Emanuele Giuseppe Esposito
---
block/file-p
Just remove some AioContext lock in LinuxAioState and ThreadPool.
Not related to anything specific, so I decided to send it as
a separate patch.
These patches are taken from Paolo's old draft series.
---
v2:
* assertion in thread_pool
* remove useless BlockDriverState * param in patch 1 and 2
* i
From: Paolo Bonzini
Remove usage of aio_context_acquire by always submitting asynchronous
AIO to the current thread's LinuxAioState.
In order to prevent mistakes from the caller side, avoid passing LinuxAioState
in laio_io_{plug/unplug} and laio_co_submit.
Signed-off-by: Paolo Bonzini
Signed-o
Use qemu_get_current_aio_context() where possible, since we always
submit work to the current thread anyways.
We want to also be sure that the thread submitting the work is
the same as the one processing the pool, to avoid adding
synchronization to the pool list.
Signed-off-by: Paolo Bonzini
Sig
When registering helpers via FFI for TCI, the inner loop that iterates
parameters of the helper reuses (and thus pollutes) the same variable
used by the outer loop that iterates all helpers, thus made some helpers
unregistered.
Fix this logic error by using a dedicated temporary variable for the
i
On Wed, Oct 26, 2022 at 10:31:45AM -0700, Isaku Yamahata wrote:
> On Tue, Oct 25, 2022 at 11:13:37PM +0800,
> Chao Peng wrote:
>
> > +int restrictedmem_get_page(struct file *file, pgoff_t offset,
> > + struct page **pagep, int *order)
> > +{
> > + struct restrictedmem_data
On 28/10/2022 09:11, Fiona Ebner wrote:
> Am 27.10.22 um 14:17 schrieb Daniel P. Berrangé:
>> On Thu, Oct 27, 2022 at 12:14:43PM +0200, Fiona Ebner wrote:
>>> +warn_report("not removing PID file on exit: cannot resolve PID
>>> file"
>>> +" path: %s: %s", pid_fil
Am 27. Oktober 2022 22:11:21 UTC schrieb "Philippe Mathieu-Daudé"
:
>Hi Daniel, Bernhard,
>
>On 27/10/22 11:47, Daniel Henrique Barboza wrote:
>> On 10/27/22 05:21, Bernhard Beschow wrote:
>>> Am 16. September 2022 14:36:05 UTC schrieb "Philippe Mathieu-Daudé"
>>> :
On 12/9/22 21:50, Bernhar
On 28/10/2022 06.57, Bin Meng wrote:
The usage of double/single quotes in test_q35_pci_unplug_json_request()
should be reversed to work on both win32 and non-win32 platforms:
- The value of -device parameter needs to be surrounded by "" as
Windows does not drop '' when passing it to QEMU whic
These patches introduced the support for configure interrupt
These codes are tested on x86_64 and aarch64 platforms.
the test scenario is based on vp-vdpa/vdpa_sim /virtio net device, with
the irqfd and without irqfd.
Tested in virtio-pci bus and virtio-mmio bus
Change in v2:
Add support for
Am 28.10.22 um 09:26 schrieb Thomas Lamprecht:
> On 28/10/2022 09:11, Fiona Ebner wrote:
>> Am 27.10.22 um 14:17 schrieb Daniel P. Berrangé:
>>> On Thu, Oct 27, 2022 at 12:14:43PM +0200, Fiona Ebner wrote:
+warn_report("not removing PID file on exit: cannot resolve
PID file"
To support configure interrupt for vhost-vdpa
Introduce VIRTIO_CONFIG_IRQ_IDX -1 as configure interrupt's queue index,
Then we can reuse the functions guest_notifier_mask and guest_notifier_pending.
Add the check of queue index in these drivers, if the driver does not support
configure interrupt, t
To reuse the interrupt process in configure interrupt
Need to decouple the single vector from the interrupt process.
We add new function kvm_virtio_pci_vector_use_one and _release_one.
These functions are used for the single vector, the whole process will
finish in the loop with vq number.
Signed-
To reuse the notifier process. We add the virtio_pci_get_notifier
to get the notifier and vector. The INPUT for this function is IDX,
The OUTPUT is the notifier and the vector
Signed-off-by: Cindy Lu
---
hw/virtio/virtio-pci.c | 88 +++---
1 file changed, 57 i
Add new call back function in vhost-vdpa, The function
vhost_set_config_call can set the event fd to kernel.
This function will be called in the vhost_dev_start
and vhost_dev_stop
Signed-off-by: Cindy Lu
---
hw/virtio/trace-events | 1 +
hw/virtio/vhost-vdpa.c | 8
2 files changed, 9 in
This patch introduces new VhostOps vhost_set_config_call.
This function allows the qemu to set the config
event fd to kernel driver.
Signed-off-by: Cindy Lu
---
include/hw/virtio/vhost-backend.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/include/hw/virtio/vhost-backend.h
b/include/h
Add the functions to support the configure interrupt in virtio
The function virtio_config_guest_notifier_read will notify the
guest if there is an configure interrupt.
The function virtio_config_set_guest_notifier_fd_handler is
to set the fd hander for the notifier
Signed-off-by: Cindy Lu
---
hw
Add functions to support configure interrupt in virtio_net
Add the functions to support vhost_net_config_pending
and vhost_net_config_mask.
Signed-off-by: Cindy Lu
---
hw/net/vhost_net.c | 9 +
hw/net/virtio-net.c | 4 ++--
include/net/vhost_net.h | 2 ++
3 files changed, 13 ins
Add configure interrupt support in virtio-mmio bus.
add function to set configure guest notifier.
Signed-off-by: Cindy Lu
---
hw/virtio/virtio-mmio.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/hw/virtio/virtio-mmio.c b/hw/virtio/virtio-mmio.c
index d240efef9
On 28/10/2022 06.57, Bin Meng wrote:
At present the virtio-9p related codes are built into libqos
unconditionally. Change to build them conditionally by testing
the 'virtfs' config option.
Signed-off-by: Bin Meng
Reviewed-by: Thomas Huth
Add process to handle the configure interrupt, The function's
logic is the same with vq interrupt.Add extra process to check
the configure interrupt
Signed-off-by: Cindy Lu
---
hw/virtio/virtio-pci.c | 110 -
include/hw/virtio/virtio-pci.h | 4 +-
2 file
Add functions to support configure interrupt.
The configure interrupt process will start in vhost_dev_start
and stop in vhost_dev_stop.
Also add the functions to support vhost_config_pending and
vhost_config_mask.
Signed-off-by: Cindy Lu
---
hw/virtio/vhost.c | 78 ++
On 28/10/2022 06.57, Bin Meng wrote:
When migration fails, QEMU exits with a status code EXIT_FAILURE.
Change qtests to use the well-defined macro instead of magic number.
Signed-off-by: Bin Meng
---
Changes in v6:
- new patch: "tests/qtest: Use EXIT_FAILURE instead of magic number"
tests/
On 28/10/2022 06.57, Bin Meng wrote:
Introduce an API for qtest to wait for the QEMU process to terminate.
Suggested-by: Marc-André Lureau
Signed-off-by: Bin Meng
---
Changes in v6:
- new patch: "tests/qtest: libqtest: Introduce qtest_wait_qemu()"
tests/qtest/libqtest.h | 9 ++
test
Hi
On Fri, Oct 28, 2022 at 8:58 AM Bin Meng wrote:
> In preparation to adding virtio-9p support on Windows, this series
> enables running qtest on Windows, so that we can run the virtio-9p
> tests on Windows to make sure it does not break accidently.
>
> Changes in v6:
> - drop patches that are
On 10/27/22 22:13, Richard Henderson wrote:
> On 10/27/22 22:22, Claudio Fontana wrote:
>> On 10/27/22 12:02, Richard Henderson wrote:
>>> +/* Per x86_restore_state_to_opc. */
>>> +if (TARGET_TB_PCREL) {
>>> +return (env->eip & TARGET_PAGE_MASK) | data[0];
>>> +} else {
>>> +
It's possible that a message contains both normal payload and ancillary
data in the same message, and even if no ancillary data is available
this information should be passed to the target, otherwise the target
cmsghdr will be left uninitialized and the target is going to access
uninitialized memor
Am 12.10.22 um 07:18 schrieb Ilya Leoshkevich:
Add ability to dump /tmp/perf-.map and jit-.dump.
The first one allows the perf tool to map samples to each individual
translation block. The second one adds the ability to resolve symbol
names, line numbers and inspect JITed code.
Example of use:
On 14/10/2022 16:25, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, BALATON Zoltan wrote:
On Fri, 14 Oct 2022, Mark Cave-Ayland wrote:
On 03/10/2022 21:13, BALATON Zoltan wrote:
By slight reorganisation we can avoid an else branch and some code
duplication which makes it easier to follow the cod
On 18/10/2022 12:37, BALATON Zoltan wrote:
On Tue, 11 Oct 2022, BALATON Zoltan wrote:
On Mon, 3 Oct 2022, BALATON Zoltan wrote:
This series includes some clean ups to mac_newworld and mac_oldworld
to make them a bit simpler and more readable, It also removes the
shared mac.h file that turns ou
On 25/10/2022 17:44, BALATON Zoltan wrote:
Since only one week is left until freeze starts I've included some
more patches in this version that I've intended to submit after the
clean ups but we're running out of time now. The last 3 patches could
be squashed together, I've just split these up b
On 28/10/2022 07.47, John Johnson wrote:
I pulled 7.1, and the megasas driver stopped being able to do reads
from a disk.
It looks to be related to this commit:
https://github.com/qemu/qemu/commit/fe9d8927e265fd723a6dc87cd6d220f4677dbe1f#diffe3f5f30efc54747e0624dca63e5f55f0012736c1875b
Icenowy Zheng writes:
> When registering helpers via FFI for TCI, the inner loop that iterates
> parameters of the helper reuses (and thus pollutes) the same variable
> used by the outer loop that iterates all helpers, thus made some helpers
> unregistered.
>
> Fix this logic error by using a d
在 2022-10-28星期五的 10:13 +0100，Alex Bennée写道：
>
> Icenowy Zheng writes:
>
> > When registering helpers via FFI for TCI, the inner loop that
> > iterates
> > parameters of the helper reuses (and thus pollutes) the same
> > variable
> > used by the outer loop that iterates all helpers, thus made som
On 28/10/22 09:21, Icenowy Zheng wrote:
When registering helpers via FFI for TCI, the inner loop that iterates
parameters of the helper reuses (and thus pollutes) the same variable
used by the outer loop that iterates all helpers, thus made some helpers
unregistered.
Oops, I didn't notice while
On 10/27/22 12:02, Richard Henderson wrote:
> Since we do not plan to exit, use cpu_unwind_state_data
> and extract exactly the data requested.
>
> Signed-off-by: Richard Henderson
> ---
> target/openrisc/sys_helper.c | 11 +--
> 1 file changed, 9 insertions(+), 2 deletions(-)
>
> diff
On Fri, Oct 28, 2022 at 4:09 PM Marc-André Lureau
wrote:
>
> Hi
>
> On Fri, Oct 28, 2022 at 8:58 AM Bin Meng wrote:
>>
>> In preparation to adding virtio-9p support on Windows, this series
>> enables running qtest on Windows, so that we can run the virtio-9p
>> tests on Windows to make sure it do
On 28/10/22 04:19, Duan, Zhenzhong wrote:
-Original Message-
From: David Hildenbrand
Sent: Friday, July 22, 2022 2:44 PM
To: Duan, Zhenzhong ; qemu-
de...@nongnu.org
Cc: pbonz...@redhat.com; pet...@redhat.com; f4...@amsat.org
Subject: Re: [PATCH] memory: Fix wrong end address dump
On
On Fri, Oct 28, 2022 at 3:59 AM Jason Wang wrote:
>
> On Thu, Oct 27, 2022 at 6:18 PM Eugenio Perez Martin
> wrote:
> >
> > On Thu, Oct 27, 2022 at 8:54 AM Jason Wang wrote:
> > >
> > > On Thu, Oct 27, 2022 at 2:47 PM Eugenio Perez Martin
> > > wrote:
> > > >
> > > > On Thu, Oct 27, 2022 at 6:3
On 10/27/22 22:20, Janis Schoetterl-Glausch wrote:
On Wed, 2022-10-26 at 10:34 +0200, Pierre Morel wrote:
On 10/25/22 21:58, Janis Schoetterl-Glausch wrote:
On Wed, 2022-10-12 at 18:20 +0200, Pierre Morel wrote:
In the S390x CPU topology the core_id specifies the CPU address
and the positi
On 25/10/2022 17:44, BALATON Zoltan wrote:
The mac99 machine emulates different machines depending on machine
properties or even if it is run as qemu-system-ppc64 or
qemu-system-ppc. This is very confusing for users and many hours were
lost trying to explain it or finding out why commands users
Hi
On Fri, Oct 28, 2022 at 1:21 PM Bin Meng wrote:
> On Fri, Oct 28, 2022 at 4:09 PM Marc-André Lureau
> wrote:
> >
> > Hi
> >
> > On Fri, Oct 28, 2022 at 8:58 AM Bin Meng wrote:
> >>
> >> In preparation to adding virtio-9p support on Windows, this series
> >> enables running qtest on Windows,
On 25/10/2022 17:44, BALATON Zoltan wrote:
Also update PowerMac family docs with some more recent info.
Signed-off-by: BALATON Zoltan
---
docs/about/deprecated.rst| 7 +++
docs/system/ppc/powermac.rst | 12
2 files changed, 15 insertions(+), 4 deletions(-)
diff --git
On Fri, Oct 28, 2022 at 5:41 PM Marc-André Lureau
wrote:
>
> Hi
>
> On Fri, Oct 28, 2022 at 1:21 PM Bin Meng wrote:
>>
>> On Fri, Oct 28, 2022 at 4:09 PM Marc-André Lureau
>> wrote:
>> >
>> > Hi
>> >
>> > On Fri, Oct 28, 2022 at 8:58 AM Bin Meng wrote:
>> >>
>> >> In preparation to adding virti
On 25/10/2022 22:31, BALATON Zoltan wrote:
OpenBIOS cannot run FCode ROMs yet but it can detect NDRV in VGA card
ROM and add it to the device tree for MacOS. Pass the NDRV this way
instead of via fw_cfg. This solves the problem with OpenBIOS also
adding the NDRV to ati-vga which it does not work
Usually, we let upper layers handle CPU pinning, because
pthread_setaffinity_np() (-> sched_setaffinity()) is blocked via
seccomp when starting QEMU with
-sandbox enable=on,resourcecontrol=deny
However, we want to configure and observe the CPU affinity of threads
from QEMU directly in some cas
From: Julia Suvorova
In the ACPI specification [1], the 'unarmed' bit is set when a device
cannot accept a persistent write. This means that when a memdev is
read-only, the 'unarmed' flag must be turned on. The logic is correct,
just changing the error message.
[1] ACPI NFIT NVDIMM Region Mappin
... and implement it under POSIX. When a ThreadContext is provided,
create new threads via the context such that these new threads obtain a
properly configured CPU affinity.
Reviewed-by: Michal Privoznik
Message-Id: <20221014134720.168738-6-da...@redhat.com>
Signed-off-by: David Hildenbrand
---
Let's allow for specifying a thread context via the "prealloc-context"
property. When set, preallcoation threads will be crated via the
thread context -- inheriting the same CPU affinity as the thread
context.
Pinning preallcoation threads to CPUs can heavily increase performance
in NUMA setups, b
The following changes since commit 0529245488865038344d64fff7ee05864d3d17f6:
Merge tag 'pull-target-arm-20221020' of
https://git.linaro.org/people/pmaydell/qemu-arm into staging (2022-10-20
14:36:12 -0400)
are available in the Git repository at:
https://github.com/davidhildenbrand/qemu.git
Hi Hesham,
On 2022/10/27 18:00, Hesham Almatary wrote:
> This patchset adds support for AArch64/HMAT including a test.
> It relies on other two patch sets from:
>
> Brice Goglin: to support -numa without initiators on q35/x86.
> https://lore.kernel.org/all/ed23accb-2c8b-90f4-a7a3-f81cc57bf...@i
Let's
* give the function a "qemu_*" style name
* make sure the parameters in the implementation match the prototype
* rename smp_cpus to max_threads, which makes the semantics of that
parameter clearer
... and add a function documentation.
Reviewed-by: Michal Privoznik
Message-Id: <2022101413
Setting the CPU affinity of QEMU threads is a bit problematic, because
QEMU doesn't always have permissions to set the CPU affinity itself,
for example, with seccomp after initialized by QEMU:
-sandbox enable=on,resourcecontrol=deny
General information about CPU affinities can be found in the
Let's make it easier to pin threads created via a ThreadContext to
all host CPUs currently belonging to a given set of host NUMA nodes --
which is the common case.
"node-affinity" is simply a shortcut for setting "cpu-affinity" manually
to the list of host CPUs belonging to the set of host nodes.
Currently, there is no way to configure a CPU affinity inside QEMU when
the sandbox option disables it for QEMU as a whole, for example, via:
-sandbox enable=on,resourcecontrol=deny
While ThreadContext objects can be created on the QEMU commandline and
the CPU affinity can be configured extern
From: Alex Bennée
We need an updated lcitool for this to deal with the weirdness
of a 32bit nsis tool for both 32 and 64 bit builds. As a result
there are some minor whitespace and re-order changes in a bunch
of the docker files.
Signed-off-by: Alex Bennée
Acked-by: Richard Henderson
Message-I
Hi Alex, in order to review carefully this patch:
https://lore.kernel.org/qemu-devel/20221027183637.2772968-2-alex.ben...@linaro.org/
I split it in 3 to convert in trivial patches to review.
(I kept your S-o-b tag).
Please consider as a replacement for your testing/next PR.
Regards,
Phil.
Alex
From: Alex Bennée
This helper is not Debian specific, rename it to cross_build().
Signed-off-by: Alex Bennée
Acked-by: Richard Henderson
Message-Id: <20220929114231.583801-10-alex.ben...@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé
---
tests/lcitool/refresh | 38 +++-
From: Alex Bennée
Convert another two dockerfiles to lcitool and update.
Signed-off-by: Alex Bennée
Acked-by: Richard Henderson
Message-Id: <20220929114231.583801-10-alex.ben...@linaro.org>
Signed-off-by: Philippe Mathieu-Daudé
---
.../dockerfiles/fedora-win32-cross.docker | 139
On 28/10/22 11:56, Philippe Mathieu-Daudé wrote:
Hi Alex, in order to review carefully this patch:
https://lore.kernel.org/qemu-devel/20221027183637.2772968-2-alex.ben...@linaro.org/
I split it in 3 to convert in trivial patches to review.
(I kept your S-o-b tag).
Please consider as a replacemen
On 10/27/22 22:42, Janis Schoetterl-Glausch wrote:
On Wed, 2022-10-12 at 18:21 +0200, Pierre Morel wrote:
The guest can use the STSI instruction to get a buffer filled
with the CPU topology description.
Let us implement the STSI instruction for the basis CPU topology
level, level 2.
Signed-
On 28/10/22 11:56, Philippe Mathieu-Daudé wrote:
From: Alex Bennée
We need an updated lcitool for this to deal with the weirdness
of a 32bit nsis tool for both 32 and 64 bit builds. As a result
s/nsis/NSIS/
there are some minor whitespace and re-order changes in a bunch
of the docker files.
Ammends commit b23046abe78f48498a423b802d6d86ba0172d57f 'pc: acpi-build:
simplify PCI bus tree generation'.
Signed-off-by: Bernhard Beschow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20221026133110.91828-2-shen...@gmail.com>
---
hw/i386/acpi-build.c | 7 ---
1 file changed, 7 deletion
The is_piix4 attribute is set once in one location and read once in
another. Doing both in one location allows for removing the attribute
altogether.
Signed-off-by: Bernhard Beschow
Reviewed-by: Philippe Mathieu-Daudé
Message-Id: <20221026133110.91828-3-shen...@gmail.com>
---
hw/i386/acpi-build
This series extends Igor's "x86: clean up ACPI PCI code part 2" series, doing
some further cleanup. It also simplifies experimentation with different south
bridges (PIIX4 and VT82xx) in the pc machine [1].
Testing done:
* `mache check`
* Start a live CD using "pc" and "q35" machine types
v2:
* Re
The code currently assumes Q35 iff ICH9 and i440fx iff PIIX. Now that more
AML generation has been moved into the south bridges and since the
machines define themselves primarily through their north bridges, let's
switch to resolving the north bridges for AML generation instead. This
also allows fo
Add the necessary code to parse the format changes for 'fixed-ram'
capability. One of the more notable changes in behavior is that in the
'fixed-ram' case ram pages are restored in one go rather than constantly
looping through the migration stream. Also due to idiosyncrasies of the
format I have ad
preadv is going to be needed when 'fixed-ram'-enabled stream are to be
restored. Add a minimal implementation of preadv for file channels and
expose it via the generic io_preadv interface.
Signed-off-by: Nikolay Borisov
---
io/channel-file.c | 27 +++
1 file changed, 27 i
On 17/10/22 08:24, Richard Henderson wrote:
Since 9b9c37c36439, we have only supported sparc64 cpus.
Debian and Gentoo now only support 64-bit sparc64 userland,
so it is time to drop the 32-bit sparc64 userland: sparc32plus.
Signed-off-by: Richard Henderson
---
tcg/sparc/tcg-target.h | 1
On 17/10/22 08:24, Richard Henderson wrote:
Emphasize that we only support full 64-bit code generation.
Signed-off-by: Richard Henderson
---
meson.build | 4 +---
tcg/{sparc => sparc64}/tcg-target-con-set.h | 0
tcg/{sparc => sparc64}/tcg-target-con-str.h | 0
In order to allow analyze-migration.py script to work with migration
streams that have the 'fixed-ram' capability set it's required to have
access to the stream's configuration object. This commit enables this
by making migration json writer part of MigrationState struct, allowing
the configuration
Introduce basic pwriteve/preadv support in the generic channel layer.
SPecific implementation will follow for the file channel as this is
required in order to support migration streams with fixed location of
each ram page.
Signed-off-by: Nikolay Borisov
---
include/io/channel.h | 49
Add
qemu_file_is_seekable/qemu_put_buffer_at/qemu_set_offset/qemu_get_offset
as those utility methods will be needed when implementing 'fixed-ram'
migration capability.
Signed-off-by: Nikolay Borisov
---
include/migration/qemu-file-types.h | 2 +
migration/qemu-file.c | 59 +++
Implement support for a "file:" uri so that a migration can be initiated
directly to a file from QEMU.
Unlike other migration protocol backends, the 'file' protocol cannot
honour non-blocking mode. POSIX file/block storage will always report
ready to read/write, regardless of how slow the underlyi
file-based migration requires the target to initiate its migration after
the source has finished writing out the data in the file. Currently
there's no easy way to initiate 'migrate-incoming', allow this by
introducing migrate_incoming_qmp helper, similarly to migrate_qmp.
Signed-off-by: Nikolay B
Restoring a 'fixed-ram' enabled migration stream would require reading
from specific offsets in the file so add a helper to QEMUFile that uses
the newly introduced qio_channel_file_preadv.
Signed-off-by: Nikolay Borisov
---
migration/qemu-file.c | 23 +++
migration/qemu-file.
The upcoming 'fixed-ram' feature would require qemu to write data at
specific offsets of the file. Add a minimal implementation of pwritev
and expose it via the io_pwritev interface.
Signed-off-by: Nikolay Borisov
---
io/channel-file.c | 25 +
1 file changed, 25 insertion
Add basic tests for file-based migration as well as for the 'fixed-ram'
feature.
Signed-off-by: Nikolay Borisov
---
tests/qtest/migration-test.c | 46
1 file changed, 46 insertions(+)
diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
i
To facilitate easier implementaiton of the 'fixed-ram' migration restore
factor out the code responsible for parsing the ramblocks headers. This
also makes ram_load_precopy easier to comprehend.
Signed-off-by: Nikolay Borisov
---
migration/ram.c | 142 +++-
This is a counterpart to the 'file:' uri support for source migration,
now a file can also serve as the source of an incoming migration.
Unlike other migration protocol backends, the 'file' protocol cannot
honour non-blocking mode. POSIX file/block storage will always report
ready to read/write, r
Implement 'fixed-ram' feature. The core of the feature is to ensure that
each ram page of the migration stream has a specific offset in the
resulting migration stream. The reason why we'd want such behavior are
two fold:
- When doing a 'fixed-ram' migration the resulting file will have a
bound
On Friday, October 28, 2022 9:07:17 AM CEST Thomas Huth wrote:
> On 27/10/2022 22.42, Christian Schoenebeck wrote:
> > On Thursday, October 27, 2022 7:37:07 PM CEST Stefan Hajnoczi wrote:
> >> On Thu, 27 Oct 2022 at 12:38, Christian Schoenebeck
> >> wrote:
> >>>
> >>> On Thursday, October 27, 2022
Here's the 3rd version of file-based migration support [0]. For background
check the cover letter of the initial. The main changes are :
- Updated commit message as per Daniel Berrange's suggestino for Patches 1-2
- Fixed tab in various pages
- Added comments better explaining how json_writer_st
Add a generic QIOChannel feature SEEKABLE which would be used by the
qemu_file* apis. For the time being this will be only implemented for
file channels.
Signed-off-by: Nikolay Borisov
---
include/io/channel.h | 1 +
io/channel-file.c| 9 +
2 files changed, 10 insertions(+)
diff --g
Passing `sizeof(cdb)` to `scsi_req_new()` looks like a correct fix to
me, but I'm not familiar enough with megasas / MegaRAID to be confident.
A possible slight alteration is to have `megasas_encode_lba()` return
the length of the CDB it synthesized, which IMO would make the
dependency more clear.
On Fri, Oct 28, 2022 at 4:05 PM Bernhard Beschow wrote:
>
> The code currently assumes Q35 iff ICH9 and i440fx iff PIIX. Now that more
> AML generation has been moved into the south bridges and since the
> machines define themselves primarily through their north bridges, let's
> switch to resolvin
Fixes the following build error:
fsdev/file-op-9p.h:156:56: error: declaration of 'struct statfs' will
not be visible outside of this function [-Werror,-Wvisibility]
int (*statfs)(FsContext *s, V9fsPath *path, struct statfs *stbuf);
^
On 28/10/2022 11.43, Bin Meng wrote:
On Fri, Oct 28, 2022 at 5:41 PM Marc-André Lureau
wrote:
Hi
On Fri, Oct 28, 2022 at 1:21 PM Bin Meng wrote:
On Fri, Oct 28, 2022 at 4:09 PM Marc-André Lureau
wrote:
Hi
On Fri, Oct 28, 2022 at 8:58 AM Bin Meng wrote:
In preparation to adding virti
On 10/28/22 09:16, Emanuele Giuseppe Esposito wrote:
From: Paolo Bonzini
Remove usage of aio_context_acquire by always submitting asynchronous
AIO to the current thread's LinuxAioState.
In order to prevent mistakes from the caller side, avoid passing LinuxAioState
in laio_io_{plug/unplug} and
On 10/28/22 09:16, Emanuele Giuseppe Esposito wrote:
Use qemu_get_current_aio_context() where possible, since we always
submit work to the current thread anyways.
We want to also be sure that the thread submitting the work is
the same as the one processing the pool, to avoid adding
synchronizati
Since only one week is left until freeze starts I've included some
more patches in this version that I've intended to submit after the
clean ups but we're running out of time now. The last 3 patches could
be squashed together, I've just split these up because I expect
resistence from Mark to any ch
The NVRAM_SIZE constant was defined but not used. Rename it to
MACIO_NVRAM_SIZE to match the device model and use it where appropriate.
Signed-off-by: BALATON Zoltan
Reviewed-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c| 2 +-
hw/ppc/mac_newworld.c| 4 ++--
include/hw/nvram/ma
Drop some more local variables additionally to commit b8df32555ce5 to
match clean ups done to mac_newwold in previous patch.
Signed-off-by: BALATON Zoltan
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Mark Cave-Ayland
---
hw/ppc/mac_oldworld.c | 43 +
This might allow the compiler to check values.
Signed-off-by: BALATON Zoltan
---
hw/ppc/mac_newworld.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/hw/ppc/mac_newworld.c b/hw/ppc/mac_newworld.c
index 37123daa6b..601ea518f8 100644
--- a/hw/ppc/mac_newworld.c
+++
The PROM_FILENAME and KERNEL_* defines are used by mac_oldworld and
mac_newworld but they don't have to be identical so these could be
moved to the individual boards.
Signed-off-by: BALATON Zoltan
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Mark Cave-Ayland
---
hw/ppc/mac.h | 4
Also update PowerMac family docs with some more recent info.
Signed-off-by: BALATON Zoltan
---
docs/about/deprecated.rst| 7 +++
docs/system/ppc/powermac.rst | 12
2 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/docs/about/deprecated.rst b/docs/about/depreca
1 - 100 of 341 matches
Mail list logo
