All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] hw/char/cmsdk-apb-timer: Correctly identify and set one-shot mode
Date: Mon, 2 Jul 2018 10:57:40 -0700	[thread overview]
Message-ID: <20180702175740.GA14904@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA97xX72WabGwn7GAQJxMcpzYzyV9yDBg1qF0zLuSDZwSA@mail.gmail.com>

On Mon, Jul 02, 2018 at 06:10:36PM +0100, Peter Maydell wrote:
> On 2 July 2018 at 18:05, Guenter Roeck <linux@roeck-us.net> wrote:
> > I don't think I'll have more time available to spend on this
> > anytime soon. If it works for you, just drop the patch. I can
> > keep it local in my branch. My version of qemu is different anyway,
> > after all.
> 
> I'd kind of like to fix the bug, though. I'd just like you
> to provide the image you're testing with...
> 

Ah, but that won't help. We are dealing with a heisenbug, and me using
a different host than you (or even a different gcc version) may be
sufficient to make the problem disappear on your system.

The mps2 images use high resolution timers, which is likely what is
triggering here. My working assumption is that those timers trigger at
the wrong time because the timer is set up in periodic instead of one-time
mode. With that, behavior is more or less random. On some systems it will
work, on some systems it won't. Since we can not agree that setting the
timer in periodic mode instead of one-shot mode is a problem, I don't
really see how we can proceed. I would somehow have to prove to you that
there is an observable problem in the first place, well beyond of what
I already did. That might take a lot of time - much more than I would
be able to spend on it.

Guenter

  reply	other threads:[~2018-07-02 17:58 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-19  2:08 [Qemu-devel] [PATCH] hw/char/cmsdk-apb-timer: Correctly identify and set one-shot mode Guenter Roeck
2018-06-26 17:17 ` [Qemu-arm] " Peter Maydell
2018-06-26 17:17   ` [Qemu-devel] " Peter Maydell
2018-06-26 17:59   ` [Qemu-arm] " Guenter Roeck
2018-06-26 17:59     ` [Qemu-devel] " Guenter Roeck
2018-06-26 18:10     ` [Qemu-arm] " Peter Maydell
2018-06-26 18:10       ` [Qemu-devel] " Peter Maydell
2018-06-26 18:43       ` [Qemu-arm] " Guenter Roeck
2018-06-26 18:43         ` [Qemu-devel] " Guenter Roeck
2018-06-26 20:00       ` [Qemu-arm] " Guenter Roeck
2018-06-26 20:00         ` [Qemu-devel] " Guenter Roeck
2018-07-02 15:05         ` Peter Maydell
2018-07-02 15:29           ` [Qemu-arm] " Peter Maydell
2018-07-02 15:29             ` [Qemu-devel] " Peter Maydell
2018-07-02 16:27           ` [Qemu-arm] " Guenter Roeck
2018-07-02 16:27             ` [Qemu-devel] " Guenter Roeck
2018-07-02 16:46             ` [Qemu-arm] " Peter Maydell
2018-07-02 16:46               ` [Qemu-devel] " Peter Maydell
2018-07-02 17:05               ` [Qemu-arm] " Guenter Roeck
2018-07-02 17:05                 ` [Qemu-devel] " Guenter Roeck
2018-07-02 17:10                 ` [Qemu-arm] " Peter Maydell
2018-07-02 17:10                   ` [Qemu-devel] " Peter Maydell
2018-07-02 17:57                   ` Guenter Roeck [this message]
2018-07-02 18:06                     ` [Qemu-arm] " Peter Maydell
2018-07-02 18:06                       ` [Qemu-devel] " Peter Maydell
2018-07-02 18:37                       ` [Qemu-arm] " Guenter Roeck
2018-07-02 18:37                         ` [Qemu-devel] " Guenter Roeck
2018-07-03 17:06                         ` Peter Maydell
2018-07-03 18:49                           ` [Qemu-arm] " Guenter Roeck
2018-07-03 18:49                             ` [Qemu-devel] " Guenter Roeck
2018-07-03 20:08                             ` [Qemu-arm] " Peter Maydell
2018-07-03 20:08                               ` [Qemu-devel] " Peter Maydell

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=20180702175740.GA14904@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --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 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.