Use enum ThrottleType instead in the throttle test codes.
Signed-off-by: zhenwei pi
---
tests/unit/test-throttle.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tests/unit/test-throttle.c b/tests/unit/test-throttle.c
index 7adb5e6652..a60b5fe22e 100644
--- a/tests
direction in throttle, this reduces memory, and uplayer
does not need a dummy callback any more.
Signed-off-by: zhenwei pi
---
util/throttle.c | 32 ++--
1 file changed, 22 insertions(+), 10 deletions(-)
diff --git a/util/throttle.c b/util/throttle.c
index 5642e61763
Use enum ThrottleType instead of number index.
Signed-off-by: zhenwei pi
---
include/qemu/throttle.h | 11 ---
util/throttle.c | 16 +---
2 files changed, 17 insertions(+), 10 deletions(-)
diff --git a/include/qemu/throttle.h b/include/qemu/throttle.h
index
other subsystems in this series, do this work in a followup series
after there patches apply.
v1:
- introduce enum ThrottleTimerType instead of timers[0], timer[1]...
- support read-only and write-only for throttle
- adapt related test codes
- cryptodev uses a write-only throttle timer
Signed-off-by: zhenwei pi
---
tests/unit/test-throttle.c | 66 ++
1 file changed, 66 insertions(+)
diff --git a/tests/unit/test-throttle.c b/tests/unit/test-throttle.c
index a60b5fe22e..5547837a58 100644
--- a/tests/unit/test-throttle.c
+++ b/tests/unit/test
Operations on a crytpodev are considered as *write* only, the callback
of read direction is never invoked. Use NULL instead of an unreachable
path(cryptodev_backend_throttle_timer_cb on read direction).
Signed-off-by: zhenwei pi
---
backends/cryptodev.c | 3 +--
1 file changed, 1 insertion
On 3/1/23 19:05, Daniel P. Berrangé wrote:
On Wed, Mar 01, 2023 at 06:58:44PM +0800, zhenwei pi wrote:
Account OPS/BPS for crypto device, this will be used for 'query-stats'
QEMU monitor command and QoS in the next step.
Note that a crypto device may support symmetric mode, asymm
Looks good to me. Thanks!
Reviewed-by: zhenwei pi
On 11/20/23 23:04, Philippe Mathieu-Daudé wrote:
Both cryptodev_backend_set_throttle() and CryptoDevBackendClass::init()
can set their Error** argument. Do not ignore them, return early on
failure. Use the ERRP_GUARD() macro as suggested in
-> dqbuf
... -> stream off
Signed-off-by: zhenwei pi
---
camera/meson.build | 4 +
camera/trace-events | 4 +
camera/v4l2.c | 637
qapi/camera.json| 21 +-
qemu-options.hx | 3 +
5 files changed, 667 insertions(+), 2 deletions(
mera +-+
++---+
|
+-+-+
| | |
+---+---+ +-+-++-+
|builtin| |v4l2(ready)||other drivers|
+---+ +---++-+
Signed-off-by: zhenwei pi
---
camera/builtin.c|
Define USB class code for video&mescellaneous.
Signed-off-by: zhenwei pi
---
include/hw/usb.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/hw/usb.h b/include/hw/usb.h
index 33668dd0a9..8e3d30b9f4 100644
--- a/include/hw/usb.h
+++ b/include/hw/usb.h
@@ -77,9 +77,11 @@
#de
ightness, hue ... control settings.
5, support control status interrupt.
Test guest Ubuntu-2004 desktop:
1, several applications: cheese, kamoso, guvcview, qcam(self-built
from libcamera source code), all work fine.
2, both builtin and v4l2 driver work fine.
Signed-off-by: zhenwei
A device of USB video class usually uses larger desc structure, so
use larger buffer to avoid failure.
Signed-off-by: zhenwei pi
---
hw/usb/desc.c | 15 ---
hw/usb/desc.h | 1 +
2 files changed, 9 insertions(+), 7 deletions(-)
diff --git a/hw/usb/desc.c b/hw/usb/desc.c
index
live migration
3, several actions defined in UVC SPEC
Zhenwei Pi (5):
camera: Introduce camera subsystem and builtin driver
camera: v4l2: Introduce v4l2 camera driver
usb: Introduce video&mescellaneous
usb: allow max 8192 bytes for desc
usb-video: Introduce USB video class
ca
","boundaries":[10,200,40]}}'
In fact this command does not work, but we still get success result.
qmp_x_block_latency_histogram_set is a batch setting API, report error ASAP.
Signed-off-by: zhenwei pi
---
blockdev.c | 19 ---
1 file changed, 16 insertions(
","boundaries":[10,200,40]}}'
In fact this command does not work, but we still get success result.
qmp_x_block_latency_histogram_set is a batch setting API, report error ASAP.
Signed-off-by: zhenwei pi
---
blockdev.c | 19 ---
1 file changed, 16 insertions(
"arguments":{"device":"drive-virtio-disk1","size":10485760}}'
The device file size actually grew, but the argument(10M) is less than the
effective size(12M). This command should fail, but QEMU still report success.
Signed-off-by: zhenwei pi
---
block/fil
replace tab with spaces and fix some comments
Signed-off-by: zhenwei pi
---
hw/display/cirrus_vga.c | 1662 +++
1 file changed, 831 insertions(+), 831 deletions(-)
diff --git a/hw/display/cirrus_vga.c b/hw/display/cirrus_vga.c
index 138ae96..6319889
currently qemu progress message only print into stdout, and other thread may
print some log into stdout at the same time.
add a new api qemu_progress_set_output to redirect progress message to
another file stream.
Signed-off-by: zhenwei pi
---
include/qemu-common.h | 1 +
util/qemu-progress.c
art_critical_warning by QMP.
v1:
- Add smart_critical_warning for nvme device which can be set by QEMU
command line to emulate hardware error.
Zhenwei Pi (4):
block/nvme: introduce bit 5 for critical warning
hw/block/nvme: fix overwritten bar.cap
hw/block/nvme: add smart_critical_warning
According to NVMe spec 1.4 section
, introduce bit 5
for "Persistent Memory Region has become read-only or unreliable".
Signed-off-by: zhenwei pi
---
include/block/nvme.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/block/nvme.h b/include/block/nvme.h
index 3e02d9ca98..
After PMR initialization, bar.cap should not be clear in function
nvme_init_ctrl. Otherwise the PMR cap would be always disabled.
Signed-off-by: zhenwei pi
---
hw/block/nvme.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/block/nvme.c b/hw/block/nvme.c
index 27d2c72716..f361103bb4
ATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- volatile memory backup device has failed
Signed-off-by: zhenwei pi
---
hw/block/nvme.c | 40
hw/block/nvme.h | 1 +
2 files changed, 41 insertions(+)
diff --git a/hw/block/nv
During smart critical warning injection by setting property from QMP
command, also try to trigger asynchronous event.
Signed-off-by: zhenwei pi
---
hw/block/nvme.c | 47 ---
1 file changed, 40 insertions(+), 7 deletions(-)
diff --git a/hw/block
According to NVMe spec 1.4 section
, introduce bit 5
for "Persistent Memory Region has become read-only or unreliable".
Signed-off-by: zhenwei pi
---
include/block/nvme.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/block/nvme.h b/include/block/nvme.h
index 9494246f1f..
ATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- volatile memory backup device has failed
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: zhenwei pi
---
hw/block/nvme.c | 45 +---
hw/block/nvme.h | 1 +
includ
ommand line to emulate hardware error.
Zhenwei Pi (3):
block/nvme: introduce bit 5 for critical warning
hw/block/nvme: add smart_critical_warning property
hw/blocl/nvme: trigger async event during injecting smart warning
hw/block/nvme.c | 91 +++-
hw/bl
During smart critical warning injection by setting property from QMP
command, also try to trigger asynchronous event.
Suggested by Keith, if a event has already been raised, there is no
need to enqueue the duplicate event any more.
Signed-off-by: zhenwei pi
---
hw/block/nvme.c | 48
On 1/18/21 5:34 PM, Klaus Jensen wrote:
On Jan 15 11:26, zhenwei pi wrote:
v3 -> v4:
- Drop "Fix overwritten bar.cap". (Already fixed)
- Avoid to enqueue the duplicate event.
- Several minor changes for coding style & function/variable name.
v2 -> v3:
- Introduce "
:
0 ~ 8k: 58% ~ 62%
8k ~ 32k: 10% ~ 12%
32k ~ 128k: 2% ~ 3%
128K ~ 512K: 24% ~ 26%
512K ~ : ...
And the histogram data help us to optimise backend distributed
storage.
zhenwei pi (3):
block/accounting: rename struct BlockLatencyHistogram
block/accounting
Introduce block size histogram statics for block devices.
For read/write/flush operation type, the block size region
[0, +inf) is divided into subregions by several points.
It works like block latency histogram.
Signed-off-by: zhenwei pi
---
block/accounting.c | 24
Set/Clear block size histograms through new command
x-block-size-histogram-set and show new statistics in
query-blockstats results.
Signed-off-by: zhenwei pi
---
block/qapi.c | 24
blockdev.c | 56 +++
qapi/block-core.json | 105
Rename struct BlockLatencyHistogram to BlockHistogram, and rename
related functions name.
make this struct and functions be common, they can be used widely.
Signed-off-by: zhenwei pi
---
block/accounting.c | 31 ++-
block/qapi.c | 2 +-
include
On 6/20/19 10:03 PM, Eric Blake wrote:
On 6/20/19 3:54 AM, zhenwei pi wrote:
Set/Clear block size histograms through new command
x-block-size-histogram-set and show new statistics in
query-blockstats results.
I'm guessing this is modeled after the existing
block-latency-histogram-set co
Rename struct BlockLatencyHistogram to BlockHistogram, and rename
related functions.
Make this struct and functions be common, they can be used widely.
Signed-off-by: zhenwei pi
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
block/accounting.c | 44
rtual machines write 25GB/s totally, the block size
histogram like following:
0 ~ 8k: 58% ~ 62%
8k ~ 32k: 10% ~ 12%
32k ~ 128k: 2% ~ 3%
128K ~ 512K: 24% ~ 26%
512K ~ : ...
And the histogram data help us to optimise backend distributed
storage.
zhenwei p
27;latency', it works as same
as the old command 'block-latency-histogram-set'. New enum 'size'
allows QEMU to fill histogram by block I/O size in byte.
Signed-off-by: zhenwei pi
Reviewed-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Eric Blake
---
block/qapi.c
Introduce block size histogram statics for block devices.
For read/write/flush operation type, the block size region
[0, +inf) is divided into subregions by several points.
It works like block latency histogram.
Signed-off-by: zhenwei pi
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
block
hink about this solution? Or do you have any other suggestions?
--
Thanks and Best Regards,
zhenwei pi
ASH_LOADED for guest crash loaded event. And suggested by KH Greg, I
moved
the bit definition to an uapi header file.
Then QEMU could include the header file from linux header and handle the new
event.
--
Thanks and Best Regards,
zhenwei pi
kexec, guest could wirte this bit to notify host side.
Host side handles crashloaded event, posts event to upper layer.
Then guest side continues to run kexec.
Test with libvirt, libvirt could recieve the new event. The patch of
libvirt will be sent soon.
Zhenwei Pi (2):
pvpanic: intr
Add bit 1 for pvpanic. This bit means that guest hits a panic, but
guest wants to handle error by itself. Typical case: Linux guest runs
kdump in panic. It will help us to separate the abnormal reboot from
normal operation.
Signed-off-by: zhenwei pi
---
docs/specs/pvpanic.txt | 8 ++--
1
Handle bit 1 write, then post event to monitor.
Suggested by Paolo, declear a new event, using GUEST_PANICKED could
cause upper layers to react by shutting down or rebooting the guest.
In advance for extention, add GuestPanicInformation in event message.
Signed-off-by: zhenwei pi
---
hw/misc
Handle bit 1 write, then post event to monitor.
Suggested by Paolo, declear a new event, using GUEST_PANICKED could
cause upper layers to react by shutting down or rebooting the guest.
In advance for extention, add GuestPanicInformation in event message.
Signed-off-by: zhenwei pi
---
hw/misc
kexec, guest could wirte this bit to notify host side.
Host side handles crashloaded event, posts event to upper layer.
Then guest side continues to run kexec.
Test with libvirt, libvirt could recieve the new event. The patch of
libvirt will be sent soon.
Zhenwei Pi (2):
pvpanic: intr
Add bit 1 for pvpanic. This bit means that guest hits a panic, but
guest wants to handle error by itself. Typical case: Linux guest runs
kdump in panic. It will help us to separate the abnormal reboot from
normal operation.
Signed-off-by: zhenwei pi
---
docs/specs/pvpanic.txt | 8 ++--
1
is patch:
1, append 'smart_critical_warning=16' for nvme parameters.
2, run smartctl in guest
#smartctl -H -l error /dev/nvme0n1
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- volatile memory backup device has failed
Signed-off-by: zhenwei pi
---
hw/bl
On 1/11/21 5:21 PM, Klaus Jensen wrote:
On Jan 11 10:14, Philippe Mathieu-Daudé wrote:
On 1/11/21 8:50 AM, zhenwei pi wrote:
There is a very low probability that hitting physical NVMe disk
hardware critical warning case, it's hard to write & test a monitor
agent service.
For
ATA SECTION ===
SMART overall-health self-assessment test result: FAILED!
- volatile memory backup device has failed
Signed-off-by: zhenwei pi
---
hw/block/nvme.c | 28
hw/block/nvme.h | 1 +
2 files changed, 29 insertions(+)
diff --git a/hw/block/nvme.c b/h
v1 -> v2:
Suggested by Philippe & Klaus, set/get smart_critical_warning by QMP.
v1:
Add smart_critical_warning for nvme device which can be set by QEMU
command line to emulate hardware error.
Zhenwei Pi (1):
hw/block/nvme: add smart_critical_warning property
hw/block/nvme
A AMD server typically has cpuid level 0x10(test on Rome/Milan), it
should not be changed to 0x1f in multi-dies case.
Fixes: a94e1428991 (target/i386: Add CPUID.1F generation support
for multi-dies PCMachine)
Signed-off-by: zhenwei pi
---
target/i386/cpu.c | 8 ++--
1 file changed, 6
On 7/2/21 4:35 AM, Michael Roth wrote:
Quoting Igor Mammedov (2021-07-01 03:43:13)
On Wed, 30 Jun 2021 14:18:09 -0500
Michael Roth wrote:
Quoting Dr. David Alan Gilbert (2021-06-29 09:06:02)
* zhenwei pi (pizhen...@bytedance.com) wrote:
A AMD server typically has cpuid level 0x10(test on
27;latency', it works as same
as the old command 'block-latency-histogram-set'. New enum 'size'
allows QEMU to fill histogram by block I/O size in byte.
Signed-off-by: zhenwei pi
Reviewed-by: Vladimir Sementsov-Ogievskiy
Reviewed-by: Eric Blake
---
block/qapi.c
Rename struct BlockLatencyHistogram to BlockHistogram, and rename
related functions.
Make this struct and functions be common, they can be used widely.
Signed-off-by: zhenwei pi
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
block/accounting.c | 44
- make 'block-latency-histogram-set' common.
- remove duplicated functions.
- fix uncommon indentation(reviewed by Vladimir Sementsov-Ogievskiy).
zhenwei pi (3):
block/accounting: rename struct BlockLatencyHistogram
block/accounting: introduce block size histogram
qapi: make b
Introduce block size histogram statics for block devices.
For read/write/flush operation type, the block size region
[0, +inf) is divided into subregions by several points.
It works like block latency histogram.
Signed-off-by: zhenwei pi
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
block
d
did. And further step we can do: if a host server hits a 'hypervisor-ignore'
or 'guest-mce', scheduler could migrate VM to another host; if hitting
'hypervisor-stop' or 'guest-triple-fault', scheduler could select other
healthy servers to launch VM.
zhenwei pi
Previously we can only get a simple string "Triple fault" in qemu
log. Add detailed message for the two reasons to describe why qemu
has to reset the guest.
Signed-off-by: zhenwei pi
---
target/i386/helper.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletion
Post memory failure event to uplayer to handle hardware memory
corrupted event. Rather than simple QEMU log, QEMU could report more
effective message to uplayer. For example, guest crashes by MCE,
selecting another host server is a better choice.
Signed-off-by: zhenwei pi
---
target/i386
Introduce 4 memory failure events for a guest. Then uplayer could
know when/why/what happened to a guest during hitting a hardware
memory failure.
Signed-off-by: zhenwei pi
---
qapi/run-state.json | 46 ++
1 file changed, 46 insertions(+)
diff --git
On 9/22/20 6:30 PM, Philippe Mathieu-Daudé wrote:
On 9/22/20 11:56 AM, zhenwei pi wrote:
Post memory failure event to uplayer to handle hardware memory
corrupted event. Rather than simple QEMU log, QEMU could report more
effective message to uplayer. For example, guest crashes by MCE
PING
On 9/22/20 5:56 PM, zhenwei pi wrote:
v1->v2:
Suggested by Peter Maydell, rename events to make them
architecture-neutral:
'PC-RAM' -> 'guest-memory'
'guest-triple-fault' -> 'guest-mce-fatal'
Suggested by Paolo, add more fields in event:
Hi,
A patchset about handling 'MCE' might have been ignored, can anyone tell
me whether the purpose is reasonable?
https://patchwork.kernel.org/cover/11773795/
On 9/14/20 9:43 PM, zhenwei pi wrote:
Although QEMU could catch signal BUS to handle hardware memory
corrupted event, s
On 9/21/20 8:48 PM, Peter Maydell wrote:
On Mon, 14 Sep 2020 at 14:53, zhenwei pi wrote:
Introduce 4 memory failure events for a guest. Then uplayer could
know when/why/what happened to a guest during hitting a hardware
memory failure.
Signed-off-by: zhenwei pi
On 9/21/20 8:09 PM, Paolo Bonzini wrote:
On 21/09/20 04:22, zhenwei pi wrote:
Hi,
A patchset about handling 'MCE' might have been ignored, can anyone tell
me whether the purpose is reasonable?
https://patchwork.kernel.org/cover/11773795/
Yes, it's very useful. Just one th
to another host; if hitting
'hypervisor-stop' or 'guest-triple-fault', scheduler could select other
healthy servers to launch VM.
Zhenwei Pi (3):
target-i386: seperate MCIP & MCE_MASK error reason
qapi/run-state.json: introduce memory failure event
target-i386: post me
Previously we can only get a simple string "Triple fault" in qemu
log. Add detailed message for the two reasons to describe why qemu
has to reset the guest.
Signed-off-by: zhenwei pi
---
target/i386/helper.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletion
sh a guest-mce is AR/AO.
Signed-off-by: zhenwei pi
---
qapi/run-state.json | 67 +
1 file changed, 67 insertions(+)
diff --git a/qapi/run-state.json b/qapi/run-state.json
index 7cc9f96a5b..f40111ac67 100644
--- a/qapi/run-state.json
+++ b/qapi
Post memory failure event to uplayer to handle hardware memory
corrupted event. Rather than simple QEMU log, QEMU could report more
effective message to uplayer. For example, guest crashes by MCE,
selecting another host server is a better choice.
Signed-off-by: zhenwei pi
---
target/i386
Previously we can only get a simple string "Triple fault" in qemu
log. Add detailed message for the two reasons to describe why qemu
has to reset the guest.
Signed-off-by: zhenwei pi
---
target/i386/helper.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletion
mce is AR/AO, previous mce is still processing in
guest or not.
Signed-off-by: zhenwei pi
---
qapi/run-state.json | 85 +
1 file changed, 85 insertions(+)
diff --git a/qapi/run-state.json b/qapi/run-state.json
index 7cc9f96a5b..d795dc21fc 10
event with 4 detailed
actions of QEMU, then uplayer could know what situaction QEMU hit and
did. And further step we can do: if a host server hits a 'hypervisor-ignore'
or 'guest-mce', scheduler could migrate VM to another host; if hitting
'hypervisor-stop' or 'guest
Post memory failure event to uplayer to handle hardware memory
corrupted event. Rather than simple QEMU log, QEMU could report more
effective message to uplayer. For example, guest crashes by MCE,
selecting another host server is a better choice.
Signed-off-by: zhenwei pi
---
target/i386
Hi, Paolo
This patch seems getting ignored. Because no maintainers found for
hw/misc/pvpanic.c, I also send this to you(hope it doesn't disturb you).
About this patch:
Looks good. And also test it, works fine.
Reviewed-by: zhenwei pi
On 11/3/20 3:50 AM, Alejandro Jimenez wrote:
Adve
Previously we can only get a simple string "Triple fault" in qemu
log. Add detailed message for the two reasons to describe why qemu
has to reset the guest.
Signed-off-by: zhenwei pi
---
target/i386/helper.c | 25 ++---
1 file changed, 18 insertions(+), 7 deletion
Acked-by: zhenwei pi
On 2/11/25 21:55, Stefano Garzarella wrote:
The function `vhost_dev_init()` expects the `struct vhost_dev`
(passed as a parameter) to be fully initialized. This is important
because some parts of the code check whether `vhost_dev->config_ops`
is NULL to determine if it
On 12/24/24 16:59, Philippe Mathieu-Daudé wrote:
Hi Gabriel,
On 24/12/24 00:46, Gabriel Barrantes wrote:
From c808fa797942b9bd32221594b7eef690a7558b14 Mon Sep 17 00:00:00 2001
From: Gabriel Barrantes
Date: Mon, 23 Dec 2024 14:58:12 -0600
Subject: [PATCH] backends/cryptodev-vhost-user: Fix
LGTM, thanks.
Reviewed-by: zhenwei pi
On 12/24/24 07:46, Gabriel Barrantes wrote:
From c808fa797942b9bd32221594b7eef690a7558b14 Mon Sep 17 00:00:00 2001
From: Gabriel Barrantes
Date: Mon, 23 Dec 2024 14:58:12 -0600
Subject: [PATCH] backends/cryptodev-vhost-user: Fix local_error leaks
Do
On 3/18/25 21:21, Markus Armbruster wrote:
zhenwei pi writes:
Hi Markus,
Current code style seems buggy, I think the main reason is that the Error *errp
is not generated at right place. keyctl_pkey_XXX fails without new error,
qcrypto_akcipher_XXX fails with new error, but they are in
;local_error);
}
if (ret < 0) {
-if (!local_error) {
-if (errno != EKEYREJECTED) {
-error_report("Failed do operation with keyctl: %d", errno);
-}
-} else {
-error_report_err(local_error);
-}
stat
LGTM, thanks!
Reviewed-by: zhenwei pi
On 3/12/25 18:11, Markus Armbruster wrote:
When cryptodev_lkcf_set_op_desc() fails, we report an error, but
continue anyway. This is wrong. We then pass a non-null @local_error
to various functions, which could easily fail error_setv()'s asserti
On 3/11/25 00:57, Thomas Huth wrote:
On 10/03/2025 17.51, Alex Bennée wrote:
David Milosevic writes:
Dear QEMU Developers,
I would like to propose the development of a video subsystem in QEMU,
with the initial
implementation focusing on UVC video device emulation and support for
multipl
On 3/12/25 18:11, Markus Armbruster wrote:
When cryptodev_lkcf_set_op_desc() fails, we report an error, but
continue anyway. This is wrong. We then pass a non-null @local_error
to various functions, which could easily fail error_setv()'s assertion
on failure.
Fail the function instead.
Whe
On 3/12/25 16:10, Markus Armbruster wrote:
scripts/coccinelle/error-use-after-free.cocci led me to this function:
static void cryptodev_lkcf_execute_task(CryptoDevLKCFTask *task)
{
CryptoDevBackendLKCFSession *session = task->sess;
CryptoDevBackendAsymOpInfo *asym_
I will leave ByteDance in the next days. Update email to stay reachable.
Signed-off-by: zhenwei pi
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7060cf49b9..2da7cf76b7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3278,7
301 - 385 of 385 matches
Mail list logo
