Il mer 16 ott 2024, 08:29 Junjie Mao ha scritto:
>
> The bindgen 0.59.1 installed from Ubuntu 22.04 apt source does not
> support the following args:
>
> '--formatter', 'rustfmt',
> '--merge-extern-blocks',
> '--allowlist-file', meson.project_source_root() + '/include/.*',
> '--al
Il mer 16 ott 2024, 08:10 Junjie Mao ha scritto:
> In my Ubuntu 22.04 environment (rustc 1.76.0 and bindgen 0.59.1 from
> apt) the feature `proc_macro_byte_character` is not yet stablized but
> used in proc-macro2. Downgrading proc-macro2 to 1.0.79 [1] and syn to
> 2.0.58 fixes that issue for me.
From: Hyman Huang
When VM is configured with huge memory, the current throttle logic
doesn't look like to scale, because migration_trigger_throttle()
is only called for each iteration, so it won't be invoked for a long
time if one iteration can take a long time.
The periodic dirty sync aims to f
From: Hyman Huang
v3:
1. drop the responsive throttle patchset
2. rename background sync to periodic ramblock dirty sync
3. move the cpu-throttle.* from system to migration
4. remove "rs" parameter in migration_bitmap_sync_precopy
5. implement periodic ramblock dirty sync in cpu-throttle.c
6. mov
From: Hyman Huang
Signed-off-by: Hyman Huang
---
tests/qtest/migration-test.c | 32
1 file changed, 32 insertions(+)
diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
index 95e45b5029..e6a2803e71 100644
--- a/tests/qtest/migration-test.c
From: Hyman Huang
The global static variable ram_state in fact is referred to by the
"rs" parameter in migration_bitmap_sync_precopy. For ease of calling
by the callees, use the global variable directly in
migration_bitmap_sync_precopy and remove "rs" parameter.
The migration_bitmap_sync_precopy
From: Hyman Huang
Move cpu-throttle.c from system to migration since it's
only used for migration; this makes us avoid exporting the
util functions and variables in misc.h but export them in
migration.h when implementing the background ramblock dirty
sync feature in the upcoming commits.
Additio
Hi
On Wed, Oct 16, 2024 at 2:29 PM Roman Penyaev wrote:
> This patch implements multiplexing capability of several backend
> devices, which opens up an opportunity to use a single frontend
> device on the guest, which can be manipulated from several
> backend devices.
>
> The idea of the change
Hi
On Fri, Oct 11, 2024 at 9:19 PM Paolo Bonzini wrote:
> The following changes since commit
> b5ab62b3c0050612c7f9b0b4baeb44ebab42775a:
>
> Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into
> staging (2024-10-04 19:28:37 +0100)
>
> are available in the Git repository at:
>
>
在 2024/10/16 下午4:13, maobibo 写道:
ping.
@Song
Could you give some comments since it is LoongArch specific?
Regards
Bibo Mao
On 2024/9/29 下午3:22, Bibo Mao wrote:
KVM LBT supports on LoongArch requires the linux-header kvm_para.h,
also unistd_64.h is required by unistd.h on LoongArch since 6.11
Hi Daniel,
On 2024/10/4 下午 11:57, Daniel Henrique Barboza wrote:
From: Tomasz Jeznach
The RISC-V IOMMU spec predicts that the IOMMU can use translation caches
to hold entries from the DDT. This includes implementation for all cache
commands that are marked as 'not implemented'.
There are some
u.git tags/pull-loongarch-20241016
for you to fetch changes up to e376c2d87cbbad3483adcd5e827bdd144edb7d2c:
hw/loongarch/fw_cfg: Build in common_ss[] (2024-10-16 16:06:07 +0800)
pull-loongarc
From: Philippe Mathieu-Daudé
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Song Gao
Reviewed-by: Thomas Huth
Message-Id: <20240927213254.17552-2-phi...@linaro.org>
Signed-off-by: Song Gao
---
include/hw/loongarch/virt.h | 1 -
1 file changed, 1 deletion(-)
diff --git a/include/hw/loong
From: Philippe Mathieu-Daudé
Nothing in LoongArch fw_cfg.c requires target specific definitions.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Song Gao
Reviewed-by: Thomas Huth
Message-Id: <20240927213254.17552-3-phi...@linaro.org>
Signed-off-by: Song Gao
---
hw/loongarch/meson.build |
From: Bibo Mao
ACPI ged is used for power management on LoongArch virt platform, in
general it is parsed from acpi table. However if system boot directly from
elf kernel, no UEFI bios is provided and acpi table cannot be used also.
Here acpi ged pm register is exposed with FDT table, it is compa
From: Bibo Mao
Macro definition is added for acpi sleep control register, ged emulation
driver can use the macro , also it can be used in FDT table if ged is
exposed with FDT table.
Signed-off-by: Bibo Mao
Reviewed-by: Igor Mammedov
Message-Id: <20240918014206.2165821-2-maob...@loongson.cn>
Si
From: Bibo Mao
Variable env->cf[i] is defined as bool type, it is treated as int type
with shift operation. However the max possible width is 56 for the shift
operation, exceeding the width of int type. And there is existing api
read_fcc() which is converted to u64 type with bitwise shift, it can
Hi
On Wed, Oct 16, 2024 at 3:13 PM Marc-André Lureau <
marcandre.lur...@gmail.com> wrote:
> Hi
>
> On Wed, Oct 16, 2024 at 2:29 PM Roman Penyaev wrote:
>
>> This patch implements multiplexing capability of several backend
>> devices, which opens up an opportunity to use a single frontend
>> devi
Hi
On Wed, Oct 16, 2024 at 2:28 PM Roman Penyaev wrote:
>
> This adds a few lines describing `mux-be` multiplexer configuration
> for multiplexing several backend devices with a single frontend
> device.
>
> Signed-off-by: Roman Penyaev
> Cc: "Marc-André Lureau"
> Cc: qemu-devel@nongnu.org
> --
On 15/10/2024 23.13, Michael Kowal wrote:
From: Glenn Miles
Added new test for pool interrupts.
Signed-off-by: Glenn Miles
Signed-off-by: Michael Kowal
---
tests/qtest/pnv-xive2-test.c | 77
1 file changed, 77 insertions(+)
diff --git a/tests/qtest/pn
Paolo Bonzini writes:
> Il mer 16 ott 2024, 08:10 Junjie Mao ha scritto:
>
> In my Ubuntu 22.04 environment (rustc 1.76.0 and bindgen 0.59.1 from
> apt) the feature `proc_macro_byte_character` is not yet stablized but
> used in proc-macro2. Downgrading proc-macro2 to 1.0.79 [1] and syn to
>
The @result parameter passed to hash/hmac APIs may either contain
a pre-allocated buffer, or a buffer can be allocated on the fly.
Clarify these two different usage models in the API docs.
Signed-off-by: Daniel P. Berrangé
---
include/crypto/hash.h | 30 +++---
include/cr
Daniel P. Berrangé (3):
crypto/hash: avoid overwriting user supplied result pointer
tests: correctly validate result buffer in hash/hmac tests
include/crypto: clarify @result/@result_len for hash/hmac APIs
crypto/hash-gcrypt.c | 15 ---
crypto/hash-glib.c
Validate that the pre-allocated buffer pointer was not overwritten
by the hash/hmac APIs.
Signed-off-by: Daniel P. Berrangé
---
tests/unit/test-crypto-hash.c | 7 ---
tests/unit/test-crypto-hmac.c | 6 --
2 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/tests/unit/test-cryp
If the user provides a pre-allocated buffer for the hash result,
we must use that rather than re-allocating a new buffer.
Reported-by: Dorjoy Chowdhury
Signed-off-by: Daniel P. Berrangé
---
crypto/hash-gcrypt.c | 15 ---
crypto/hash-glib.c | 11 +--
crypto/hash-gnutls.c |
The test is trivial: several backends, 1 `mux-be`, 1 frontend
do the buffer write and read. Pipe is used for EAGAIN verification.
Signed-off-by: Roman Penyaev
Cc: "Marc-André Lureau"
Cc: qemu-devel@nongnu.org
---
tests/unit/test-char.c | 306 -
1 file cha
In the following patches backend multiplexer will be
introduced. This patch renames the structure and a
few mux macros to reflect that this mux is responsible
only for multiplexing of frontend devices.
This patch does the following:
s/MuxChardev/MuxFeChardev/g
s/CHARDEV_IS_MUX/CHARDEV_IS_MUX_
Mux is a character backend (host side) device, which multiplexes
multiple frontends with one backend device. The following is a
few lines from the QEMU manpage [1]:
A multiplexer is a "1:N" device, and here the "1" end is your
specified chardev backend, and the "N" end is the various parts
o
Patch introduces `mux-be-id=ID` option for all chardev devices.
This is necessary to attach chardev to `mux-be` for backend
multiplexing. Actual implementation wimplementation will follow.
Signed-off-by: Roman Penyaev
Cc: "Marc-André Lureau"
Cc: qemu-devel@nongnu.org
---
chardev/char.c | 3 +++
In the following patches backend multiplexer will be
introduced and the implementation will be named as
follows: `char-mux-be.c`. This patch renames the
frontend multiplexer from `char-mux.c` to
`char-mux-fe.c`.
Signed-off-by: Roman Penyaev
Cc: "Marc-André Lureau"
Cc: qemu-devel@nongnu.org
---
This patch implements multiplexing capability of several backend
devices, which opens up an opportunity to use a single frontend
device on the guest, which can be manipulated from several
backend devices.
The idea of the change is trivial: keep list of backend devices
(up to 4), init them on deman
This adds a few lines describing `mux-be` multiplexer configuration
for multiplexing several backend devices with a single frontend
device.
Signed-off-by: Roman Penyaev
Cc: "Marc-André Lureau"
Cc: qemu-devel@nongnu.org
---
qemu-options.hx | 78 -
This patch renames calls in the frontend mux implementation
to reflect its frontend nature. Patch does the following:
s/mux_chr/mux_fe_chr/g
No functional changes are made.
Signed-off-by: Roman Penyaev
Cc: "Marc-André Lureau"
Cc: qemu-devel@nongnu.org
---
chardev/char-fe.c | 6 ++-
The suspend/resume open multiplexer calls are generic
and will be used for frontend (current mux) and backend
(will follow) implementations. Move them away from the
`char-mux-fe.c` to more generic `char.c` file. Also
for the sake of clarity these renames were made:
s/suspend_mux_open/mux_suspend
Sorry about the email style, I'm not familiar with it yet
> It's probably worth including this in the commit message.
Agree, I'll do it.
> It would be good to reference the sail implementation and the
justification for the change there
Sail implementation is probably here:
https://github.com/ris
On Wed, Oct 16, 2024 at 11:07:41AM +0200, Cédric Le Goater wrote:
> This is a simple conversion of the tests with some cleanups and
> adjustments to match the new test framework. Replace the zephyr image
> MD5 hashes with SHA256 hashes while at it.
>
> The SDK tests depend on a ssh class from avoc
On 2024/10/14 19:22, Clément Léger wrote:
Add ext_ssdbltrp in RISCVCPUConfig and implement MSTATUS.SDT,
{H|M}ENVCFG.DTE and modify the availability of MTVAL2 based on the
presence of the Ssdbltrp ISA extension.
Signed-off-by: Clément Léger
Reviewed-by: Alistair Francis
---
target/riscv/cpu
ping.
@Song
Could you give some comments since it is LoongArch specific?
Regards
Bibo Mao
On 2024/9/29 下午3:22, Bibo Mao wrote:
KVM LBT supports on LoongArch requires the linux-header kvm_para.h,
also unistd_64.h is required by unistd.h on LoongArch since 6.11
Signed-off-by: Bibo Mao
---
s
VHOST_USER_BACKEND_SHARED_OBJECT_ADD and
VHOST_USER_BACKEND_SHARED_OBJECT_REMOVE state
in the spec that they return 0 for successful
operations, non-zero otherwise. However,
implementation relies on the return types
of the virtio-dmabuf library, with opposite
semantics (true if everything is correc
This is a simple conversion of the tests with some cleanups and
adjustments to match the new test framework. Replace the zephyr image
MD5 hashes with SHA256 hashes while at it.
The SDK tests depend on a ssh class from avocado.utils which is
difficult to replace. To be addressed separately.
Signed
Error responses from swtpm are typically only 4 bytes long with the
exception of a few commands that return more bytes. Therefore, read the
entire response in 2 passes and stop if the first few bytes indicate an
error response with no subsequent bytes readable. Read the rest in a 2nd
pass, if neede
Use the new ptm_cap_n structure for getting the PTM_GET_CAPABILITY response
from swtpm. Previously only 17 bits could possibly have been set in ptm_cap
(=uint64_t) in big endian order and those bits are now found in the 2nd
32bit word in the response in the caps field.
This data structure makes it
In case swtpm was to return a control channel message with an error code it
would often return less bytes than the full response. In some cases the
current reading of the returned bytes would get stuck since more bytes are
expected. Therefore, pass a separate parameter indicating how many bytes to
On Wed, Oct 16, 2024 at 10:57:07AM -0400, Stefan Berger wrote:
> Use the new ptm_cap_n structure for getting the PTM_GET_CAPABILITY response
> from swtpm. Previously only 17 bits could possibly have been set in ptm_cap
> (=uint64_t) in big endian order and those bits are now found in the 2nd
> 32bi
On 10/16/2024 3:33 AM, Thomas Huth wrote:
On 15/10/2024 23.13, Michael Kowal wrote:
From: Glenn Miles
Added new test for pool interrupts.
Signed-off-by: Glenn Miles
Signed-off-by: Michael Kowal
---
tests/qtest/pnv-xive2-test.c | 77
1 file changed, 77
On Wed, Oct 16, 2024 at 03:56:42PM +0800, yong.hu...@smartx.com wrote:
> From: Hyman Huang
>
> Move cpu-throttle.c from system to migration since it's
> only used for migration; this makes us avoid exporting the
> util functions and variables in misc.h but export them in
> migration.h when implem
On Wed, Oct 16, 2024 at 03:56:43PM +0800, yong.hu...@smartx.com wrote:
> From: Hyman Huang
>
> The global static variable ram_state in fact is referred to by the
> "rs" parameter in migration_bitmap_sync_precopy. For ease of calling
> by the callees, use the global variable directly in
> migratio
On Wed, Oct 16, 2024 at 10:57:08AM -0400, Stefan Berger wrote:
> Error responses from swtpm are typically only 4 bytes long with the
> exception of a few commands that return more bytes. Therefore, read the
> entire response in 2 passes and stop if the first few bytes indicate an
> error response w
Rather than waiting for the completion of migration on the source side,
wait for it on the destination QEMU side to avoid accessing the TPM TIS
memory mapped registers before QEMU could restore their state. This
error condition could be triggered on busy systems where the destination
QEMU did not h
On Wed, Oct 16, 2024 at 11:21:59AM -0400, Stefan Berger wrote:
> Rather than waiting for the completion of migration on the source side,
> wait for it on the destination QEMU side to avoid accessing the TPM TIS
> memory mapped registers before QEMU could restore their state. This
> error condition
On Wed, Oct 16, 2024 at 06:07:12PM +0200, Thomas Huth wrote:
> The linker on OpenBSD complains:
>
> ld: warning: dirtyrate.c:447 (../src/migration/dirtyrate.c:447)(...):
> warning: strcpy() is almost always misused, please use strlcpy()
Is that the only place it complains ? We use 'strcpy' in
(I) Summary
===
This patch is the beginning of the support of the Security Protocol and
Data Model (SPDM). There are some known issues (see II), but it's
usable and not many users are going to use this functionality for now,
Signed-off-by: htafr
---
.gitmodules | 3 ++
Kconfig.host | 3 ++
meson.build | 84 +++
meson_options.txt | 8
scripts/make-config-poison.sh | 19
scripts/meson-buildoptions.sh | 9 +
Hi,
On 15/10/24 11:16, Paolo Bonzini wrote:
The gen_cmpxchg8b and gen_cmpxchg16b functions even have the correct
prototype already; the only thing that needs to be done is removing the
gen_lea_modrm() call.
This moves the last LOCK-enabled instructions to the new decoder. It is
now possible to
On Wed, 22 May 2024 17:34:52 +0200
Anthony Harivel wrote:
> Starting with the "Sandy Bridge" generation, Intel CPUs provide a RAPL
> interface (Running Average Power Limit) for advertising the accumulated
> energy consumption of various power domains (e.g. CPU packages, DRAM,
> etc.).
>
> The co
On Wed, 22 May 2024 17:34:49 +0200
Anthony Harivel wrote:
> Dear maintainers,
>
> First of all, thank you very much for your review of my patch
> [1].
I've tried to play with this feature and have a few questions about it
1. trying to start with non accessible or not existent socket
On 16/10/24 06:30, Daniel P. Berrangé wrote:
On Wed, Oct 16, 2024 at 11:07:41AM +0200, Cédric Le Goater wrote:
This is a simple conversion of the tests with some cleanups and
adjustments to match the new test framework. Replace the zephyr image
MD5 hashes with SHA256 hashes while at it.
The SDK
On Wed, Oct 16, 2024 at 05:01:38PM +0100, Jonathan Cameron wrote:
> On Tue, 8 Oct 2024 20:01:07 -0700
> Davidlohr Bueso wrote:
>
> > On Tue, 08 Oct 2024, nifan@gmail.com wrote:\n
> > >From: Fan Ni
> > >
> > >In the function cmd_firmware_update_get_info for handling Get FW info
> > >command (
Hi Igor,
Igor Mammedov, Oct 16, 2024 at 13:52:
> On Wed, 22 May 2024 17:34:49 +0200
> Anthony Harivel wrote:
>
>> Dear maintainers,
>>
>> First of all, thank you very much for your review of my patch
>> [1].
>
> I've tried to play with this feature and have a few questions about it
>
Thanks f
On Tue, 8 Oct 2024 20:01:07 -0700
Davidlohr Bueso wrote:
> On Tue, 08 Oct 2024, nifan@gmail.com wrote:\n
> >From: Fan Ni
> >
> >In the function cmd_firmware_update_get_info for handling Get FW info
> >command (0x0200h), the vmem, pmem and DC capacity size check were
> >incorrect. The size sh
The linker on OpenBSD complains:
ld: warning: dirtyrate.c:447 (../src/migration/dirtyrate.c:447)(...):
warning: strcpy() is almost always misused, please use strlcpy()
It's currently not a real problem in this case since both arrays
have the same size (256 bytes). But just in case somebody chan
On 10/16/24 9:34 AM, Stefan Berger wrote:
In case swtpm was to return a control channel message with an error code it
would only return 4 bytes. However, some of the commands expect a response
with more bytes and QEMU would get stuck in qemu_chr_fe_read_all() waiting
for bytes following the er
Stefan Berger writes:
> On 10/15/24 6:02 PM, Fabiano Rosas wrote:
>> Stefan Berger writes:
>>
>>> On 10/15/24 3:57 PM, Fabiano Rosas wrote:
Stefan Berger writes:
>>>
>
> So this here is failing for you every time?
>
> QTEST_QEMU_BINARY=build/qemu-system-aarch64
>
Hi Salil,
> On 15 Oct 2024, at 09:59, Salil Mehta wrote:
>
> PROLOGUE
>
>
> To assist in review and set the right expectations from this RFC, please first
> read the sections *APPENDED AT THE END* of this cover letter:
>
> 1. Important *DISCLAIMER* [Section (X)]
> 2. Work presented at
Use the new ptm_cap_n structure for getting the PTM_GET_CAPABILITY response
from swtpm. Previously only 17 bits could possibly have been set in ptm_cap
(=uint64_t) in big endian order and those bits are now found in the 2nd
32bit word in the response in the caps field.
This data structure makes it
In case swtpm was to return a control channel message with an error code it
would only return 4 bytes. However, some of the commands expect a response
with more bytes and QEMU would get stuck in qemu_chr_fe_read_all() waiting
for bytes following the error code. Therefore, read the response in 2
pas
On Wed, Oct 16, 2024 at 4:20 PM Daniel P. Berrangé wrote:
>
>
>
> Daniel P. Berrangé (3):
> crypto/hash: avoid overwriting user supplied result pointer
> tests: correctly validate result buffer in hash/hmac tests
> include/crypto: clarify @result/@result_len for hash/hmac APIs
>
> crypto/ha
Error responses from swtpm are always only 4 bytes long with the exception
of CMD_GET_STATEBLOB that returns more bytes. Therefore, read the entire
response in 2 passes and stop if the first 4 bytes indicate an error
response with no subsequent bytes readable. Read the rest in a 2nd pass, if
needed
Hi,
On Wed, Oct 16, 2024 at 1:14 PM Marc-André Lureau
wrote:
>
> Hi
>
> On Wed, Oct 16, 2024 at 2:29 PM Roman Penyaev wrote:
>>
>> This patch implements multiplexing capability of several backend
>> devices, which opens up an opportunity to use a single frontend
>> device on the guest, which can
Hi
On Wed, Oct 16, 2024 at 2:28 PM Roman Penyaev wrote:
>
> The test is trivial: several backends, 1 `mux-be`, 1 frontend
> do the buffer write and read. Pipe is used for EAGAIN verification.
>
> Signed-off-by: Roman Penyaev
> Cc: "Marc-André Lureau"
> Cc: qemu-devel@nongnu.org
> ---
> tests/u
Hi Igor,
I will let Paolo or Daniel answering those architecture questions, they
are more qualified than me.
Thanks
Anthony
Igor Mammedov, Oct 16, 2024 at 14:17:
> On Wed, 22 May 2024 17:34:52 +0200
> Anthony Harivel wrote:
>
>> Starting with the "Sandy Bridge" generation, Intel CPUs provide
Ping
This patch series has been reviewed by Alex. I am not sure if it needs
more review. If not, maybe this can be picked up for merging. Thanks!
Regards,
Dorjoy
Hello Philippe,
The Google-Bug-Id is an internal ID and should have been removed. The
information in the bug was mostly transcribed in the cover letter of
this patch series.
Thanks
Roque
On Mon, Oct 7, 2024 at 1:06 PM Philippe Mathieu-Daudé wrote:
>
> Hi Roque,
>
> On 6/9/24 19:54, Roque Arcud
On 10/16/24 11:03 AM, Daniel P. Berrangé wrote:
On Wed, Oct 16, 2024 at 10:57:07AM -0400, Stefan Berger wrote:
Use the new ptm_cap_n structure for getting the PTM_GET_CAPABILITY response
from swtpm. Previously only 17 bits could possibly have been set in ptm_cap
(=uint64_t) in big endian orde
Paolo Bonzini writes:
> offset_of! was stabilized in Rust 1.77.0. Use an alternative implemenation
> that was found on the Rust forums, and whose author agreed to license as
> MIT for use in QEMU.
>
> The alternative allows only one level of field access, but apart
> from this can be used just
Philippe Mathieu-Daudé writes:
> On 10/10/24 12:01, Markus Armbruster wrote:
>> The error message doesn't matter much, as the "openpic" device isn't
>> user-creatable. But it's the last use of
>> QERR_PROPERTY_VALUE_OUT_OF_RANGE, which has to go. Change the message
>> just like the previous com
Hi Michael:
On Wed, Oct 16, 2024 at 1:58 AM Michael Tokarev wrote:
>
> On 15.09.2024 04:06, Akihiko Odaki wrote:
> > Most of this series are fixes for software RSS and hash reporting, which
> > should have no production user.
> >
> > However there is one exception; patch "virtio-net: Fix size che
On 10/17/24 08:47, Markus Armbruster wrote:
Fux build broken by semantic conflict with commit
8f525028bc6 (qapi/crypto: Rename QCryptoAFAlg to QCryptoAFAlgo).
Fixes: 90c3dc60735a (crypto/hash-afalg: Implement new hash API)
Signed-off-by: Markus Armbruster
My bad :/ Obviously, I didn't catch t
On 16/10/2024 18.22, Daniel P. Berrangé wrote:
On Wed, Oct 16, 2024 at 06:07:12PM +0200, Thomas Huth wrote:
The linker on OpenBSD complains:
ld: warning: dirtyrate.c:447 (../src/migration/dirtyrate.c:447)(...):
warning: strcpy() is almost always misused, please use strlcpy()
Is that the o
On 2024/10/17 11:52, Richard Henderson wrote:
On 10/16/24 19:57, LIU Zhiwei wrote:
Hi Richard,
On 2024/10/17 02:38, Richard Henderson wrote:
2595: if (dec->cfg->ext_zcmop) {
2690: if (dec->cfg->ext_zcmp && ((inst >> 12) & 0b01)) {
2716: if (!dec->cfg->ex
Fux build broken by semantic conflict with commit
8f525028bc6 (qapi/crypto: Rename QCryptoAFAlg to QCryptoAFAlgo).
Fixes: 90c3dc60735a (crypto/hash-afalg: Implement new hash API)
Signed-off-by: Markus Armbruster
---
crypto/hash-afalg.c | 10 +-
1 file changed, 5 insertions(+), 5 deletion
On 16/10/2024 22.38, Cédric Le Goater wrote:
This is a simple conversion of the tests with some cleanups and
adjustments to match the new test framework. Replace the zephyr image
MD5 hashes with SHA256 hashes while at it.
The SDK tests depend on a ssh class from avocado.utils which is
difficult
Hi Daniel,
Thanks for the review, I will send a V2 addressing the comments.
Regards,
Sai Pavan
>-Original Message-
>From: Daniel Henrique Barboza
>Sent: Wednesday, October 16, 2024 1:28 AM
>To: Boddu, Sai Pavan ; qemu-devel@nongnu.org;
>qemu-ri...@nongnu.org
>Cc: Paolo Bonzini ; Palmer
From: Hyman Huang
Move cpu-throttle.c from system to migration since it's
only used for migration; this makes us avoid exporting the
util functions and variables in misc.h but export them in
migration.h when implementing the periodic ramblock dirty
sync feature in the upcoming commits.
Since CPU
From: Hyman Huang
Since CPU throttling only occurs when auto-converge
is on, stop it conditionally.
Signed-off-by: Hyman Huang
---
migration/migration.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/migration/migration.c b/migration/migration.c
index 021faee2f3..37a200
From: Hyman Huang
When VM is configured with huge memory, the current throttle logic
doesn't look like to scale, because migration_trigger_throttle()
is only called for each iteration, so it won't be invoked for a long
time if one iteration can take a long time.
The periodic dirty sync aims to f
From: Hyman Huang
Signed-off-by: Hyman Huang
---
accel/tcg/icount-common.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/accel/tcg/icount-common.c b/accel/tcg/icount-common.c
index 8d3d3a7e9d..30bf8500dc 100644
--- a/accel/tcg/icount-common.c
+++ b/accel/tcg/icount-common.c
@@ -36,7 +36,6
From: Hyman Huang
The global static variable ram_state in fact is referred to by the
"rs" parameter in migration_bitmap_sync_precopy. For ease of calling
by the callees, use the global variable directly in
migration_bitmap_sync_precopy and remove "rs" parameter.
The migration_bitmap_sync_precopy
From: Hyman Huang
v4:
1. split the [PATCH v3 1/6] into smaller patches.
2. refine some comment and commit message
3. fix race issue for the throttle_dirty_sync_timer
4. refine the util function cpu_throttle_dirty_sync_timer
Thanks Peter for the suggestions.
Please review.
Yong
v3:
1. drop the
From: Hyman Huang
Signed-off-by: Hyman Huang
Reviewed-by: Peter Xu
---
tests/qtest/migration-test.c | 32
1 file changed, 32 insertions(+)
diff --git a/tests/qtest/migration-test.c b/tests/qtest/migration-test.c
index 95e45b5029..e6a2803e71 100644
--- a/tests/
Daniel P. Berrangé writes:
> From: Alejandro Zeise
>
> Updates the afalg hash driver to support the new accumulative
> hashing changes as part of the patch series.
>
> Implements opening/closing of contexts, updating hash data
> and finalizing the hash digest.
>
> In order to support the update
On Wed, Oct 16, 2024 at 11:50 PM Peter Xu wrote:
> On Wed, Oct 16, 2024 at 03:56:42PM +0800, yong.hu...@smartx.com wrote:
> > From: Hyman Huang
> >
> > Move cpu-throttle.c from system to migration since it's
> > only used for migration; this makes us avoid exporting the
> > util functions and va
On 10/16/24 19:57, LIU Zhiwei wrote:
Hi Richard,
On 2024/10/17 02:38, Richard Henderson wrote:
2595: if (dec->cfg->ext_zcmop) {
2690: if (dec->cfg->ext_zcmp && ((inst >> 12) & 0b01)) {
2716: if (!dec->cfg->ext_zcmt) {
2726: if (!dec->
On Thu, Oct 17, 2024 at 2:49 AM Peter Xu wrote:
> On Wed, Oct 16, 2024 at 03:56:44PM +0800, yong.hu...@smartx.com wrote:
> > From: Hyman Huang
> >
> > When VM is configured with huge memory, the current throttle logic
> > doesn't look like to scale, because migration_trigger_throttle()
> > is on
Signed-off-by: Huang Shiyuan
Co-authored-by: TANG Tiancheng
Signed-off-by: TANG Tiancheng
Reviewed-by: Liu Zhiwei
Reviewed-by: Richard Henderson
Signed-off-by: Swung0x48
Hi,
We should remove the tag "Signed-off-by: swung0x48swung0...@outlook.com" since the
author's real name, Huang Shiyuan, is
On Wed, Oct 16, 2024 at 8:32 PM Trd thg wrote:
>
> Sorry about the email style, I'm not familiar with it yet
No worries! It takes some getting used to. Mostly just plain text
emails and reply inline :)
Alistair
>
> > It's probably worth including this in the commit message.
> Agree, I'll do it.
On Thu, Oct 17, 2024 at 2:35 AM htafr wrote:
>
> (I) Summary
> ===
>
> This patch is the beginning of the support of the Security Protocol and
> Data Model (SPDM). There are some known issues (see II), but it's
> usable and no
On Mon, Oct 14, 2024 at 5:43 PM Clément Léger wrote:
>
>
>
> On 11/10/2024 05:22, Alistair Francis wrote:
> > On Wed, Sep 25, 2024 at 9:59 PM Clément Léger wrote:
> >>
> >> When the Ssdbltrp ISA extension is enabled, if a trap happens in S-mode
> >> while SSTATUS.SDT isn't cleared, generate a dou
On Sat, Oct 12, 2024 at 4:52 AM Ved Shanbhogue wrote:
>
> Alistair Francis wrote:
> >> When the Ssdbltrp extension is enabled, SSTATUS.SDT field is cleared
> >> when executing sret. When executing mret/mnret, SSTATUS.SDT is cleared
> >> when returning to U, VS or VU and VSSTATUS.SDT is cleared whe
Error responses from swtpm are typically only 4 bytes long with the
exception of a few commands that return more bytes. Therefore, read the
entire response in 2 steps and stop if the first few bytes indicate an
error response with no subsequent bytes readable. Read the rest in a 2nd
step, if needed
1 - 100 of 195 matches
Mail list logo
