qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] add pci-serial device.
Date: Fri, 28 Sep 2012 12:07:40 +0200	[thread overview]
Message-ID: <20120928100739.GB7522@redhat.com> (raw)
In-Reply-To: <87wqzhuedo.fsf@codemonkey.ws>

On Wed, Sep 26, 2012 at 08:01:39AM -0500, Anthony Liguori wrote:
> Gerd Hoffmann <kraxel@redhat.com> writes:
> 
> > On 09/26/12 01:43, Anthony Liguori wrote:
> >> Gerd Hoffmann <kraxel@redhat.com> writes:
> >> 
> >>>   Hi,
> >>>
> >>> Two patches, first split up serial.c a bit,
> >>> then actually add the pci-based serial device.
> >> 
> >> The series looks good to me.  A couple requests:
> >> 
> >> 1) Could you add a spec describing this new PCI device?  Doesn't need to
> >>    be more than a couple paragraphs since the device is super simple.
> >
> > Well, it is pretty strait forward:  A single IO bar, 8 bytes in size,
> > where the 16550 uart is mapped to:
> >
> > [kraxel@fedora ~]$ lspci -vse
> > 00:0e.0 Serial controller: Red Hat, Inc. Device 0002 (rev 01) (prog-if
> > 00 [8250])
> > 	Subsystem: Red Hat, Inc Device 1100
> > 	Physical Slot: 14
> > 	Flags: fast devsel, IRQ 11
> > 	I/O ports at c130 [size=8]
> > 	Kernel driver in use: serial
> >
> > But I can surely add a comment about it.
> 
> Understood, but I'd really prefer a file in docs/.  We should be
> rigorous about having formal specs for all of our paravirtual devices.
> The code shouldn't be the spec.
> 
> >
> >> 2) Could you make the inf file an separate patch and either include
> >>    documentation in the commit message on how to use it with Windows or
> >>    just add a comment to the inf file?
> >
> > I think a comment is better, easier to find than a commit message.
> > Will do.
> 
> So do I.  Thanks.
> 
> >> This is a new PCI space for QEMU too.  
> >
> > It isn't new, I just followed what the pci bridge is doing (which has
> > 1b36:0001).
> 
> Ah, Michael, could you add a quick spec to docs for the pci_bridge
> device?

What exactly would you like to see in this spec?

> >
> >> Is this a driver that is "owned"
> >> by QEMU and Red Hat is donating the PCI id or is this a driver that RH
> >> controls that we're implementing?
> >
> > I consider it being owned by qemu.
> 
> Great.
> 
> Regards,
> 
> Anthony Liguori
> 
> >
> > cheers,
> >   Gerd

      parent reply	other threads:[~2012-09-28 10:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-24 11:28 [Qemu-devel] [PATCH 0/2] add pci-serial device Gerd Hoffmann
2012-09-24 11:28 ` [Qemu-devel] [PATCH 1/2] serial: split serial.c Gerd Hoffmann
2012-09-24 11:28 ` [Qemu-devel] [PATCH 2/2] serial: add pci variant Gerd Hoffmann
2012-09-25 23:43 ` [Qemu-devel] [PATCH 0/2] add pci-serial device Anthony Liguori
2012-09-26  0:18   ` Jan Kiszka
2012-09-26  6:54     ` Gerd Hoffmann
2012-09-26  6:44   ` Gerd Hoffmann
2012-09-26 13:01     ` Anthony Liguori
2012-09-27  5:53       ` Gerd Hoffmann
2012-09-28 10:06         ` Michael S. Tsirkin
2012-09-28 11:45           ` Gerd Hoffmann
2012-09-28 10:07       ` Michael S. Tsirkin [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=20120928100739.GB7522@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=kraxel@redhat.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).