From: Rusty Russell <rusty@rustcorp.com.au>
To: Amit Shah <amit.shah@redhat.com>, Anthony Liguori <aliguori@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
virtualization@linux-foundation.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v10 1/1] virtio_console: Add support for multiple ports for generic guest and host communication
Date: Fri, 6 Nov 2009 17:40:02 +1030 [thread overview]
Message-ID: <200911061740.03734.rusty@rustcorp.com.au> (raw)
In-Reply-To: <1257266319-24300-2-git-send-email-amit.shah@redhat.com>
On Wed, 4 Nov 2009 03:08:39 am Amit Shah wrote:
> Expose multiple char devices ("ports") for simple communication
> between the host userspace and guest.
OK, I've taken the chance to audit this patch. I started adding patches
until I got overwhelmed. It's a complete mess and needs a total rewrite :(
This shows the problem with feeding me a complete driver rewrite in one
big hit. You've combined lots of changes and techniques in here at once:
1) Moved work out of interrupt handlers and into work_struct.
2) Encapsulated the buffer information in a structure.
3) Added an optional header to the buffer(s).
4) Added control messages.
5) Encapsulated the per-port information into a structure.
6) Allocated a static buffer pool of over 4MB (!)
7) Added an ad-hoc throttling mechanism.
8) Added debugfs support.
Less important nitpicks:
1) Don't call a struct list_head 'next', it confused the crap out of me.
Call it list or some other non-name.
2) Don't call control messages "internal". Use ONE good name, ie. control.
3) Don't use list_for_each_safe() to get the head entry of a list. Your
use is buggy anyway: buf will never be NULL afterwards.
In summary: this is the one we're going to throw away.
Now I'm going to start again, one patch at a time, and see how that works.
Sorry,
Rusty.
next prev parent reply other threads:[~2009-11-06 7:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 16:38 [PATCH v10 0/1] virtio-console: Support for generic ports and multiple consoles Amit Shah
2009-11-03 16:38 ` [PATCH v10 1/1] virtio_console: Add support for multiple ports for generic guest and host communication Amit Shah
2009-11-06 7:10 ` Rusty Russell [this message]
2009-11-06 8:00 ` Christian Borntraeger
2009-11-06 13:00 ` Anthony Liguori
2009-11-06 14:12 ` Christian Borntraeger
2009-11-06 14:32 ` Anthony Liguori
2009-11-06 14:32 ` Anthony Liguori
2009-11-06 14:12 ` Christian Borntraeger
2009-11-06 13:00 ` Anthony Liguori
2009-11-06 8:00 ` Christian Borntraeger
2009-11-09 12:08 ` Amit Shah
2009-11-09 12:08 ` Amit Shah
2009-11-10 2:19 ` Rusty Russell
2009-11-10 2:19 ` Rusty Russell
2009-11-06 7:10 ` Rusty Russell
2009-11-06 7:43 ` Christian Borntraeger
2009-11-09 12:09 ` Amit Shah
2009-11-09 12:09 ` Amit Shah
2009-11-06 7:43 ` Christian Borntraeger
2009-11-03 16:38 ` Amit Shah
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=200911061740.03734.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=aliguori@us.ibm.com \
--cc=amit.shah@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.