qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	qemu list <qemu-devel@nongnu.org>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH 2/3] virtio-serial: Add description fields for qdev properties
Date: Fri, 28 May 2010 18:28:37 +0530	[thread overview]
Message-ID: <20100528125836.GB9122@amit-laptop.redhat.com> (raw)
In-Reply-To: <m3ocg0fawm.fsf@blackfin.pond.sub.org>

On (Fri) May 28 2010 [14:50:17], Markus Armbruster wrote:
> Amit Shah <amit.shah@redhat.com> writes:
> 
> > Signed-off-by: Amit Shah <amit.shah@redhat.com>
> > ---
> >  hw/virtio-console.c |   17 ++++++++++-------
> >  hw/virtio-serial.h  |   12 ++++++++++++
> >  2 files changed, 22 insertions(+), 7 deletions(-)
> >
> > diff --git a/hw/virtio-console.c b/hw/virtio-console.c
> > index ccd277a..8a99a99 100644
> > --- a/hw/virtio-console.c
> > +++ b/hw/virtio-console.c
> > @@ -95,11 +95,13 @@ static VirtIOSerialPortInfo virtconsole_info = {
> >      .init          = virtconsole_initfn,
> >      .exit          = virtconsole_exitfn,
> >      .qdev.props = (Property[]) {
> > -        DEFINE_PROP_UINT8("is_console", VirtConsole, port.is_console, 1, ""),
> > +        DEFINE_PROP_UINT8("is_console", VirtConsole, port.is_console, 1,
> > +                          PROP_VIRTSERIAL_IS_CONSOLE_DESC),
> >          DEFINE_PROP_UINT32("nr", VirtConsole, port.id, VIRTIO_CONSOLE_BAD_ID,
> > -                           ""),
> > -        DEFINE_PROP_CHR("chardev", VirtConsole, chr, ""),
> > -        DEFINE_PROP_STRING("name", VirtConsole, port.name, ""),
> > +                           PROP_VIRTSERIAL_NR_DESC),
> > +        DEFINE_PROP_CHR("chardev", VirtConsole, chr, PROP_VIRTSERIAL_CHR_DESC),
> > +        DEFINE_PROP_STRING("name", VirtConsole, port.name,
> > +                           PROP_VIRTSERIAL_NAME_DESC),
> >          DEFINE_PROP_END_OF_LIST(),
> >      },
> >  };
> > @@ -133,9 +135,10 @@ static VirtIOSerialPortInfo virtserialport_info = {
> >      .exit          = virtconsole_exitfn,
> >      .qdev.props = (Property[]) {
> >          DEFINE_PROP_UINT32("nr", VirtConsole, port.id, VIRTIO_CONSOLE_BAD_ID,
> > -                           ""),
> > -        DEFINE_PROP_CHR("chardev", VirtConsole, chr, ""),
> > -        DEFINE_PROP_STRING("name", VirtConsole, port.name, ""),
> > +                           PROP_VIRTSERIAL_NR_DESC),
> > +        DEFINE_PROP_CHR("chardev", VirtConsole, chr, PROP_VIRTSERIAL_CHR_DESC),
> > +        DEFINE_PROP_STRING("name", VirtConsole, port.name,
> > +                           PROP_VIRTSERIAL_NAME_DESC),
> >          DEFINE_PROP_END_OF_LIST(),
> >      },
> >  };
> > diff --git a/hw/virtio-serial.h b/hw/virtio-serial.h
> > index a93b545..2a13432 100644
> > --- a/hw/virtio-serial.h
> > +++ b/hw/virtio-serial.h
> > @@ -58,6 +58,18 @@ struct virtio_console_control {
> >  
> >  /* == In-qemu interface == */
> >  
> > +#define PROP_VIRTSERIAL_IS_CONSOLE_DESC                                 \
> > +    "An hvc console will be spawned in the guest since this is a console port"
> > +
> > +#define PROP_VIRTSERIAL_NR_DESC                                         \
> > +    "The 'number' for the port for predictable port numbers for better migration support"
> > +
> > +#define PROP_VIRTSERIAL_CHR_DESC                \
> > +    "The chardev to associate this port with"
> > +
> > +#define PROP_VIRTSERIAL_NAME_DESC                \
> > +    "Name for the port that's exposed to the guest for port discovery"
> > +
> >  typedef struct VirtIOSerial VirtIOSerial;
> >  typedef struct VirtIOSerialBus VirtIOSerialBus;
> >  typedef struct VirtIOSerialPort VirtIOSerialPort;
> 
> Why put the description macros in the header, away from their only uses?

That's because the virtserial infrastructure will be used in places
other than just the virtio-console.c file (spice, clipboard, etc.).

		Amit

  reply	other threads:[~2010-05-28 12:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  9:57 [Qemu-devel] [RFC PATCH 1/3] qdev: Add a description field for qdev properties for documentation Amit Shah
2010-05-28  9:57 ` [Qemu-devel] [RFC PATCH 2/3] virtio-serial: Add description fields for qdev properties Amit Shah
2010-05-28 12:50   ` Markus Armbruster
2010-05-28 12:58     ` Amit Shah [this message]
2010-05-28  9:57 ` [Qemu-devel] [RFC PATCH 3/3] net.h: Add description fields for qdev properites Amit Shah
2010-05-28 12:50   ` Markus Armbruster
2010-05-28 12:59     ` Amit Shah
2010-05-28 13:45       ` Markus Armbruster
2010-05-28 12:49 ` [Qemu-devel] [RFC PATCH 1/3] qdev: Add a description field for qdev properties for documentation Markus Armbruster
2010-05-28 12:57   ` 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=20100528125836.GB9122@amit-laptop.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).