From: Akihiko Odaki <akihiko.odaki@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu Developers <qemu-devel@nongnu.org>,
xen-devel@lists.xenproject.org,
"Michael S . Tsirkin" <mst@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>
Subject: Re: [PATCH v3 2/3] ui: Deliver refresh rate via QemuUIInfo
Date: Thu, 9 Jun 2022 21:12:59 +0900 [thread overview]
Message-ID: <c0c610b8-df0c-7e2a-385f-bcf70c987182@gmail.com> (raw)
In-Reply-To: <20220609120214.bay3cl24oays6x6d@sirius.home.kraxel.org>
On 2022/06/09 21:02, Gerd Hoffmann wrote:
> On Thu, Jun 09, 2022 at 08:45:41PM +0900, Akihiko Odaki wrote:
>> On 2022/06/09 19:28, Gerd Hoffmann wrote:
>>>> --- a/include/ui/console.h
>>>> +++ b/include/ui/console.h
>>>> @@ -139,6 +139,7 @@ typedef struct QemuUIInfo {
>>>> int yoff;
>>>> uint32_t width;
>>>> uint32_t height;
>>>> + uint32_t refresh_rate;
>>>> } QemuUIInfo;
>>>> /* cursor data format is 32bit RGBA */
>>>> @@ -426,7 +427,6 @@ typedef struct GraphicHwOps {
>>>> void (*gfx_update)(void *opaque);
>>>> bool gfx_update_async; /* if true, calls graphic_hw_update_done() */
>>>> void (*text_update)(void *opaque, console_ch_t *text);
>>>> - void (*update_interval)(void *opaque, uint64_t interval);
>>>> void (*ui_info)(void *opaque, uint32_t head, QemuUIInfo *info);
>>>> void (*gl_block)(void *opaque, bool block);
>>>> } GraphicHwOps;
>>>
>>> So you are dropping update_interval, which isn't mentioned in the commit
>>> message at all. Also this patch is rather big. I'd suggest:
>>>
>>> (1) add refresh_rate
>>> (2) update users one by one
>>> (3) finally drop update_interval when no user is left.
>>>
>>> thanks,
>>> Gerd
>>>
>>
>> I think 1 and 3 should have to be done once since refresh_rate and
>> update_interval would interfere with each other otherwise.
>
> Well, between 1 and 3 both old and new API are active. Shouldn't be
> much of a problem because the GraphicHwOps implementations are using
> only the one or the other.
>
> take care,
> Gerd
>
The only GraphicHwOps implementation updated with this change is xenfb.
xenfb can be switched to use refresh_rate in step 1 or 3.
Switching to use refresh_rate in step 1 would break the refresh rate
propagation until all host displays are updated to set refresh_rate
instead of calling update_interval.
Switching to use refresh_rate in step 3 would break the refresh rate
propagation when a host display is updated to set refresh_rate instead
of calling update_interval but xenfb does not use refresh_rate.
Regards,
Akihiko Odaki
next prev parent reply other threads:[~2022-06-09 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 11:55 [PATCH v3 0/3] virtio-gpu: Respect UI refresh rate for EDID Akihiko Odaki
2022-02-26 11:55 ` [PATCH v3 1/3] ui/console: Do not return a value with ui_info Akihiko Odaki
2022-02-26 11:55 ` [PATCH v3 2/3] ui: Deliver refresh rate via QemuUIInfo Akihiko Odaki
2022-06-09 10:28 ` Gerd Hoffmann
2022-06-09 11:45 ` Akihiko Odaki
2022-06-09 12:02 ` Gerd Hoffmann
2022-06-09 12:12 ` Akihiko Odaki [this message]
2022-06-09 13:34 ` Gerd Hoffmann
2022-02-26 11:55 ` [PATCH v3 3/3] virtio-gpu: Respect UI refresh rate for EDID Akihiko Odaki
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=c0c610b8-df0c-7e2a-385f-bcf70c987182@gmail.com \
--to=akihiko.odaki@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).