qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jiahuan Zhang <jiahuanzhang90@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hight Processor time of Socket communciation
Date: Wed, 19 Apr 2017 15:34:36 +0200	[thread overview]
Message-ID: <CAJy91Cbo+CQbRMmS-1b32Hf=kgWb22N3htmiuyORW7y-of7Raw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA81o245N_zoSUtJ0SVupZyRE9cnfr15hmu+ReMuDj9iyQ@mail.gmail.com>

On 19 April 2017 at 12:09, Peter Maydell <peter.maydell@linaro.org> wrote:

> On 19 April 2017 at 11:04, Jiahuan Zhang <jiahuanzhang90@gmail.com> wrote:
> > Okay. Thank you for pointing this out.
> > I would like to make a new serial device based on pl011,
> > but containing a buffer for guest-to-host data transfer.
>
> As I've said, the PL011 is inherently byte at a time.
> If you want better than that, I recommend you use virtio-serial,
> because it already exists for this purpose.
>
> thanks
> -- PMM
>

Hi Peter,

But from the source code, I found the main characteristic of virtio-serial
is that,
virtio-serial can create multiple serial ports and each port has a pair of
control virt-queues and
a pair of guest input/output virt-queues.
Its "have_data" callback function enables multi-byte data transfer from
guest.
And it is not in a tranditional device emulation format.
I mean that no exact IO region is emulated for it.
Without Linux kernel driver, I don't know how to manipulate it.
For the time being, I enable the guest app to send data to
the pl011's data register directly via a pointer, as you see that in the
code above.

This is why I am thinking if adding a transmit buffer in pl011 for guest
writing
is a feasible alternative.

Any suggestion is welcome.
Regards,
Huan

  reply	other threads:[~2017-04-19 13:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 16:19 [Qemu-devel] Hight Processor time of Socket communciation Jiahuan Zhang
2017-04-18 16:26 ` 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 [this message]
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='CAJy91Cbo+CQbRMmS-1b32Hf=kgWb22N3htmiuyORW7y-of7Raw@mail.gmail.com' \
    --to=jiahuanzhang90@gmail.com \
    --cc=peter.maydell@linaro.org \
    --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).