qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-serial: PCI device for simple host <-> guest communication
Date: Thu, 11 Jun 2009 21:51:30 +0530	[thread overview]
Message-ID: <20090611162129.GA19119@amit-x200.pnq.redhat.com> (raw)
In-Reply-To: <f43fc5580906110907h341a4237pafefdfcac4e4b9ee@mail.gmail.com>

On (Thu) Jun 11 2009 [19:07:26], Blue Swirl wrote:
> On 6/11/09, Amit Shah <amit.shah@redhat.com> wrote:
> > On (Tue) Jun 09 2009 [13:56:57], Anthony Liguori wrote:
> >  > Richard W.M. Jones wrote:
> >  >> On Tue, Jun 09, 2009 at 10:12:48PM +0530, Amit Shah wrote:
> >  >> [...]
> >  >>
> >  >> Are you going to post the virtio driver for the Linux kernel later?
> >  >>
> >  >
> >  > Yeah, I'd like to see the Linux driver before drawing conclusions.
> >
> >  Pasting here a slightly older version of the patch. I'm actively working
> >  on it; a few things might have changed but the basic idea remains the
> >  same.
> 
> >  + * along with this program; if not, write to the Free Software
> >  + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
> 
> Old FSF address, the new one is on Franklin St.

OK, will update.

> >  +struct virtio_serial_port {
> 
> >  +       unsigned int read_len;
> 
> This limits the maximum transfer length to 4G, which is way too short
> on 64 bit hosts. ;-)

This is only valid for a single packet that's transmitted via the queue
at a time and I doubt anyone's going to use bigger packets :-)

(That size is also limited by the kernel -- and the current code only
alloctes one PAGE_SIZE buffer for the transfer.)

> >  +struct virtio_serial_config {
> >  +       __u8 nr_ports;
> >  +       __u16 status;
> >  +} __attribute__((packed));
> 
> The structure should be redesigned to work without packed attribute.
> status field is unaligned.

I'll see how to untangle it.

		Amit

  reply	other threads:[~2009-06-11 16:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 16:42 [Qemu-devel] [RFC] virtio-serial device Amit Shah
2009-06-09 16:42 ` [Qemu-devel] [PATCH] pci: add define for communication class devices Amit Shah
2009-06-09 16:42   ` [Qemu-devel] [PATCH] qdev: add virtserial char drv init hacks Amit Shah
2009-06-09 16:42     ` [Qemu-devel] [PATCH] virtio-serial: PCI device for simple host <-> guest communication Amit Shah
2009-06-09 17:15       ` [Qemu-devel] " Jan Kiszka
2009-06-09 18:15         ` Richard W.M. Jones
2009-06-09 19:19           ` Jan Kiszka
2009-06-09 18:17       ` [Qemu-devel] " Richard W.M. Jones
2009-06-09 18:47         ` Stuart Brady
2009-06-09 18:56         ` Anthony Liguori
2009-06-09 23:40           ` Paul Brook
2009-06-10 10:31           ` Amit Shah
2009-06-10 18:00             ` Jamie Lokier
2009-06-11  4:31               ` Amit Shah
2009-06-12  1:56                 ` Jamie Lokier
2009-06-11 13:51           ` Amit Shah
2009-06-11 16:07             ` Blue Swirl
2009-06-11 16:21               ` Amit Shah [this message]
2009-06-10 10:28         ` 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=20090611162129.GA19119@amit-x200.pnq.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    /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).