qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: [Qemu-devel] Re: Multiple Port Support for virtio-console
Date: Thu, 10 Sep 2009 17:27:12 +0530	[thread overview]
Message-ID: <20090910115712.GA27014@amit-x200.redhat.com> (raw)
In-Reply-To: <1252483925-26336-1-git-send-email-amit.shah@redhat.com>

On (Wed) Sep 09 2009 [13:41:59], Amit Shah wrote:
> 
> Hello all,
> 
> Here is a new iteration of the patch series that implements a
> transport for guest and host communications.
> 
> I've tested for compatibility (old qemu & new kernel, new qemu & old
> kernel, new qemu & new kernel) and it all works fine*. Migration works
> with the patch Juan just posted.
> 
> There are a few items on my todo list but this works well.
> 
> New since last send:
> - migrate per-port buffers that are queued up
> - in-qemu api for open/close/read/write of ports.
>   - the read() is a callback that's invoked when complete data
>     corresponding to one write() request on the guest is available.
> - removed comments from virtio_console.c that are no longer relevant.
> - address review comments by Juan
> 
> TODO:
> - Convert all config writes to little endian in qemu / convert from
>   little endian to host endian in guest
> - Address a few FIXMEs spread in the code
> - Introduce a watermark to stop a rogue host process flooding guest
>   with data
> 
> Conditions:
> * Heavy IO on an hvc port and a non-hvc port causes memory corruption
>   each time, same place. It could be realted to locking but I doubt
>   that. This still has to be sorted out

I can't reproduce this badness anymore with the linux-next kernel in the
guest.

So I request the maintainers to please review this patchset for and
consider for inclusion.

Thanks,
		Amit

      parent reply	other threads:[~2009-09-10 11:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09  8:11 [Qemu-devel] Multiple Port Support for virtio-console Amit Shah
2009-09-09  8:12 ` [Qemu-devel] [PATCH] virtio_console: Add support for multiple ports for generic guest and host communication Amit Shah
2009-09-09  8:12   ` [Qemu-devel] [PATCH 1/5] char: Emit 'OPENED' events on char device open Amit Shah
2009-09-09  8:12     ` [Qemu-devel] [PATCH 2/5] virtio-console: Add support for multiple ports for generic guest-host communication Amit Shah
2009-09-09  8:12       ` [Qemu-devel] [PATCH 3/5] virtio-console: in-qemu api for open/read/write/close ports Amit Shah
2009-09-09  8:12         ` [Qemu-devel] [PATCH 4/5] vnc: add a is_vnc_active() helper Amit Shah
2009-09-09  8:12           ` [Qemu-devel] [PATCH 5/5] vnc: Send / receive guest clipboard if virtio-console connected to clipboard port Amit Shah
2009-09-10 11:57 ` Amit Shah [this message]

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=20090910115712.GA27014@amit-x200.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=virtualization@lists.linux-foundation.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).