All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Dongwon Kim <dongwon.kim@intel.com>
Cc: qemu-devel@nongnu.org,  berrange@redhat.com,  kraxel@redhat.com,
	pbonzini@redhat.com,  f4bug@amsat.org,
	 vivek.kasireddy@intel.com
Subject: Re: [PATCH v4 2/2] ui/gtk: a new array param monitor to specify the target displays
Date: Mon, 18 Jul 2022 11:06:35 +0200	[thread overview]
Message-ID: <87pmi2dc2s.fsf@pond.sub.org> (raw)
In-Reply-To: <20220713195947.GA53@dongwonk-MOBL.amr.corp.intel.com> (Dongwon Kim's message of "Wed, 13 Jul 2022 12:59:47 -0700")

Dongwon Kim <dongwon.kim@intel.com> writes:

> On Tue, Jul 12, 2022 at 08:11:08AM +0200, Markus Armbruster wrote:
>> Dongwon Kim <dongwon.kim@intel.com> writes:
>> 
>> > New integer array parameter, 'monitor' is for specifying the target
>> > monitors where individual GTK windows are placed upon launching.
>> >
>> > Monitor numbers in the array are associated with virtual consoles
>> > in the order of [VC0, VC1, VC2 ... VCn].
>> >
>> > Every GTK window containing each VC will be placed in the region
>> > of corresponding monitors.
>> >
>> > Usage: -display gtk,monitor.<id of VC>=<target monitor>,..
>> >        ex)-display gtk,monitor.0=1,monitor.1=0
>> >
>> > Cc: Daniel P. Berrangé <berrange@redhat.com>
>> > Cc: Markus Armbruster <armbru@redhat.com>
>> > Cc: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> > Cc: Paolo Bonzini <pbonzini@redhat.com>
>> > Cc: Gerd Hoffmann <kraxel@redhat.com>
>> > Cc: Vivek Kasireddy <vivek.kasireddy@intel.com>
>> > Signed-off-by: Dongwon Kim <dongwon.kim@intel.com>
>> > ---
>> >  qapi/ui.json    |  9 ++++++++-
>> >  qemu-options.hx |  3 ++-
>> >  ui/gtk.c        | 30 ++++++++++++++++++++++++++++--
>> >  3 files changed, 38 insertions(+), 4 deletions(-)
>> >
>> > diff --git a/qapi/ui.json b/qapi/ui.json
>> > index 413371d5e8..ee0f9244ef 100644
>> > --- a/qapi/ui.json
>> > +++ b/qapi/ui.json
>> > @@ -1195,12 +1195,19 @@
>> >  #               assuming the guest will resize the display to match
>> >  #               the window size then.  Otherwise it defaults to "off".
>> >  #               Since 3.1
>> > +# @monitor:     Array of numbers, each of which represents physical
>> > +#               monitor where GTK window containing a given VC will be
>> > +#               placed. Each monitor number in the array will be
>> > +#               associated with a virtual console starting from VC0.
>> > +#
>> > +#               since 7.1
>> 
>> I dislike repeating the type (here: array of numbers) in the
>> description.
>> 
>> Suggest something like
>> 
>>    # @monitor:     List of physical monitor numbers where the GTK windows
>>    #               containing the virtual consoles VC0, VC1, ... are to be
>>    #               placed.  (Since 7.1)
>> 
>> Missing: what happens when there are more VCs than list elements.  Can
>> you tell us?
>
>     # @monitor:     List of physical monitor numbers where the GTK windows
>     #               containing the virtual consoles VC0, VC1, ... are to be
>     #               placed. If a mapping exists for a VC, then it'd be
>     #               placed on that specific physical monitor; otherwise,
>     #               it'd default to the monitor from where it was launched
>     #               since 7.1
>
> How does this look?

Pretty good!

Nitpicks: replace "id'd" by "it will" or "it is to be", end your second
sentence with a period, and format "since" like we do elsewhere.
Together:

      # @monitor:     List of physical monitor numbers where the GTK windows
      #               containing the virtual consoles VC0, VC1, ... are to be
      #               placed. If a mapping exists for a VC, then it is to be
      #               placed on that specific physical monitor; otherwise,
      #               it defaults to the monitor from where it was launched.
      #               (Since 7.1)

>> 
>> >  #
>> >  # Since: 2.12
>> >  ##
>> >  { 'struct'  : 'DisplayGTK',
>> >    'data'    : { '*grab-on-hover' : 'bool',
>> > -                '*zoom-to-fit'   : 'bool'  } }
>> > +                '*zoom-to-fit'   : 'bool',
>> > +                '*monitor'       : ['uint16']  } }
>> >  
>> >  ##
>> >  # @DisplayEGLHeadless:
>> 
>> [...]
>> 



      reply	other threads:[~2022-07-18  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 23:39 [PATCH v4 0/2] handling guest multiple displays Dongwon Kim
2022-07-11 23:39 ` [PATCH v4 1/2] ui/gtk: detach VCs for additional guest displays Dongwon Kim
2022-07-11 23:39 ` [PATCH v4 2/2] ui/gtk: a new array param monitor to specify the target displays Dongwon Kim
2022-07-12  6:11   ` Markus Armbruster
2022-07-13 19:59     ` Dongwon Kim
2022-07-18  9:06       ` Markus Armbruster [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=87pmi2dc2s.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=dongwon.kim@intel.com \
    --cc=f4bug@amsat.org \
    --cc=kraxel@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vivek.kasireddy@intel.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 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.