All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: Pekka Paalanen <ppaalanen@gmail.com>,
	Mario Kleiner <mario.kleiner.de@gmail.com>
Cc: Frederic Plourde <frederic.plourde@collabora.co.uk>,
	dri-devel@lists.freedesktop.org,
	wayland-devel@lists.freedesktop.org
Subject: Re: [PATCH weston 1/1] compositor: Abort on bad page flip timestamps
Date: Fri, 07 Nov 2014 18:56:30 +0900	[thread overview]
Message-ID: <545C974E.7020707@daenzer.net> (raw)
In-Reply-To: <20141107113630.388d4a4c@gmail.com>

On 07.11.2014 18:36, Pekka Paalanen wrote:
>
> If we still feel that exiting Weston on the first timestamp failure
> (zero or not increasing) is too harsh, we could simply log a warning
> and add again some heuristics on when things are too far wrong to
> continue.
>
> E.g. getting a single timestamp failure during the first 5 seconds of
> compositor uptime warrants an exit, but later probably not. We want to
> catch cases where the compositor cannot reliably work to begin with,
> but killing the user's session much later is pretty blunt if it already
> worked somewhat.
>
> Would that be good?

Yeah, that would address my main concern.


-- 
Earthling Michel Dänzer            |                  http://www.amd.com
Libre software enthusiast          |                Mesa and X developer
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2014-11-07  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1415210783-16839-1-git-send-email-frederic.plourde@collabora.co.uk>
     [not found] ` <545B1E88.5070702@daenzer.net>
2014-11-06 16:42   ` [PATCH weston 1/1] compositor: Abort on bad page flip timestamps Pekka Paalanen
     [not found]     ` <20141106184242.4e281eb9-DA5HUFbJnAM@public.gmane.org>
2014-11-07  6:04       ` Mario Kleiner
     [not found]         ` <545C60E0.8090405-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-11-07  9:36           ` Pekka Paalanen
2014-11-07  9:56             ` Michel Dänzer [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=545C974E.7020707@daenzer.net \
    --to=michel@daenzer.net \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=frederic.plourde@collabora.co.uk \
    --cc=mario.kleiner.de@gmail.com \
    --cc=ppaalanen@gmail.com \
    --cc=wayland-devel@lists.freedesktop.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 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.