From: Jiahuan Zhang <jiahuanzhang90@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Hight Processor time of Socket communciation
Date: Tue, 18 Apr 2017 18:19:05 +0200 [thread overview]
Message-ID: <CAJy91CZpAiZ6adPmbAESrYqDgtK37CEgw4SAk97jCNduADy6Tw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
Dear QEMU developers,
I am measuring the processor time for guest-host communication via socket.
The guest app is to write a 5M image to a serial device.
The serial deivce is redirected to the socket in the command line.
The host app is to receive the data via socket until the peer closes the
connection.
Please find in the attachment the Processor time graph generated by Windows
Performance Monitor.
The graph shows the processor time is almost 100% while communicating.
Surprising me! My expectation is 1%.
I wonder if this is the right performance for QEMU socket communciation? Or
this high processor time is caused by the serial device? If so, any
optimization I can do?
Here is the QEMU command-line i used.
$ qemu/build/arm-softmmu/qemu-system-arm.exe -M vexpress-a9 -kernel
zImage_vexpress_4-10 -dtb vexpress-v2p-ca9.dtb -initrd rootfs.img.gz
-append "console=ttyAMA0 root=/dev/ram rdinit=linuxrc" -chardev
socket,host=localhost,port=27015,server,nowait,id=char1 -serial
telnet:localhost:5555,server,nowait -serial stdio -serial stdio -serial
chardev:char1 -monitor telnet:localhost:4444,server,nowait -sd test.img
-nographic
Please correct me if something is wrong.
Best rergards,
Huan
[-- Attachment #2: socket_guest.png --]
[-- Type: image/png, Size: 74842 bytes --]
next reply other threads:[~2017-04-18 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-18 16:19 Jiahuan Zhang [this message]
2017-04-18 16:26 ` [Qemu-devel] Hight Processor time of Socket communciation Peter Maydell
2017-04-19 8:56 ` Jiahuan Zhang
2017-04-19 9:15 ` Peter Maydell
2017-04-19 9:25 ` Jiahuan Zhang
2017-04-19 9:55 ` Peter Maydell
2017-04-19 10:04 ` Jiahuan Zhang
2017-04-19 10:09 ` Peter Maydell
2017-04-19 13:34 ` Jiahuan Zhang
2017-04-19 20:03 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJy91CZpAiZ6adPmbAESrYqDgtK37CEgw4SAk97jCNduADy6Tw@mail.gmail.com \
--to=jiahuanzhang90@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).