-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qemu-armv7a Ivshmem config and document update #15818
base: master
Are you sure you want to change the base?
Conversation
@anchao @acassis @xiaoxiang781216 @GUIDINGLI Could you help review this PR? |
please discard roles changes: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please move the driver chanegs to a separate PR
please rename commit
rpmsgblk_server: fix the syslog format warning title to
drivers/rpmsgblk_server: fix the syslog format warning
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@CV-Bowen please include a Documentation/ to rpproxy_ivshmem and rpserver_ivshmem board profiles explaining what it does and how to test/validate it.
misc/rpmsgblk_server.c:135:16: warning: format '%d' expects argument of type 'int', but argument 3 has type 'int32_t' {aka 'long int'} [-Wformat=] 135 | ferr("block device open failed, ret=%d\n", msg->header.result); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~ | | | int32_t {aka long int} misc/rpmsgblk_server.c:135:48: note: format string is defined here 135 | ferr("block device open failed, ret=%d\n", msg->header.result); | ~^ | | | int | %ld misc/rpmsgblk_server.c: In function 'rpmsgblk_close_handler': misc/rpmsgblk_server.c:170:16: warning: format '%d' expects argument of type 'int', but argument 3 has type 'int32_t' {aka 'long int'} [-Wformat=] 170 | ferr("block device close failed, ret=%d\n", msg->header.result); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~ | | | int32_t {aka long int} misc/rpmsgblk_server.c:170:49: note: format string is defined here 170 | ferr("block device close failed, ret=%d\n", msg->header.result); | ~^ | | | int | %ld Signed-off-by: Bowen Wang <[email protected]>
add discard-data=on in proxy launch command, so the proxy side will clean the share memory to make sure that the shared memory is clean every time server and proxy are started. Signed-off-by: Bowen Wang <[email protected]>
eef3f56
to
cb0efe6
Compare
@CV-Bowen I cannot find it: https://nuttx.apache.org/docs/latest/search.html?q=rpserver_ivshmem&check_keywords=yes&area=default https://nuttx.apache.org/docs/latest/search.html?q=rpproxy_ivshmem&check_keywords=yes&area=default# All new board profiles need to be documented to let users know what they are suppose to do |
I added the missing qemu-armv8a/ivshmem chapter |
Documentation/platforms/arm/qemu/boards/qemu-armv7a/index.rst |
I think that the driver commit should be in a separate PR since the fix is independent from the other commit |
@jerpelea I enable the CONFIG_BLK_RPMSG_SERVER in rpproxy_server and found this compile warning, so I think this fix is related with other commit in this PR? |
These two commits are actually interdependent
|
Summary
commit bfd8f01
Author: Bowen Wang [email protected]
Date: Wed Feb 12 15:46:59 2025 +0800
commit 7cd275b
Author: Bowen Wang [email protected]
Date: Wed Feb 12 15:46:15 2025 +0800
Impact
ivshmem configs
Testing
testing with qemu-armv7a:rpserver_ivshmem qemu-armv7a:rpproxy_ivshmem with rpmsg ping
qemu-armv7a test result