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-arm] [PATCH] hw/char/cmsdk-apb-timer: Correctly identify and set one-shot mode
Date: Mon, 2 Jul 2018 10:05:22 -0700 [thread overview]
Message-ID: <20180702170522.GA9885@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA8+ZxcRLBgonZaqpAfumKFvhk7yDhX=Fe0KjoeTxWsczg@mail.gmail.com>
On Mon, Jul 02, 2018 at 05:46:39PM +0100, Peter Maydell wrote:
> On 2 July 2018 at 17:27, Guenter Roeck <linux@roeck-us.net> wrote:
> > Again, in my observation the boot sometimes stalls without my
> > patch. Maybe there is a better fix, but the code as-is doesn't
> > work for me. All I can say is that the current code does not set
> > one-shot mode when it should, and that seems wrong.
> >
> > You could of course take out the zero delta warning. Personally
> > I would caution against that - whenever I have seen that warning,
> > it suggested that something is wrong with the emulation, and it
> > helped me track down the problem. Your call, of course. Also,
> > I don't think taking out the warning would fix my stall problem.
>
> Can you provide me with something I can reproduce with, then,
> please? My kernel + buildroot don't repro the problem: it always
> seems to boot fine. I had a look at your testbuild git repo
> but couldn't manage to figure out how to build a binary
> from it. I'm ok with building a QEMU from your branch for
> testing this, but I'd rather not try to figure out how to
> reproduce your kernel and root filesystem setup.
>
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.
Thanks,
Guenter
WARNING: multiple messages have this Message-ID (diff)
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:05:22 -0700 [thread overview]
Message-ID: <20180702170522.GA9885@roeck-us.net> (raw)
In-Reply-To: <CAFEAcA8+ZxcRLBgonZaqpAfumKFvhk7yDhX=Fe0KjoeTxWsczg@mail.gmail.com>
On Mon, Jul 02, 2018 at 05:46:39PM +0100, Peter Maydell wrote:
> On 2 July 2018 at 17:27, Guenter Roeck <linux@roeck-us.net> wrote:
> > Again, in my observation the boot sometimes stalls without my
> > patch. Maybe there is a better fix, but the code as-is doesn't
> > work for me. All I can say is that the current code does not set
> > one-shot mode when it should, and that seems wrong.
> >
> > You could of course take out the zero delta warning. Personally
> > I would caution against that - whenever I have seen that warning,
> > it suggested that something is wrong with the emulation, and it
> > helped me track down the problem. Your call, of course. Also,
> > I don't think taking out the warning would fix my stall problem.
>
> Can you provide me with something I can reproduce with, then,
> please? My kernel + buildroot don't repro the problem: it always
> seems to boot fine. I had a look at your testbuild git repo
> but couldn't manage to figure out how to build a binary
> from it. I'm ok with building a QEMU from your branch for
> testing this, but I'd rather not try to figure out how to
> reproduce your kernel and root filesystem setup.
>
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.
Thanks,
Guenter
next prev parent reply other threads:[~2018-07-02 17:07 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 ` Guenter Roeck [this message]
2018-07-02 17:05 ` 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
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=20180702170522.GA9885@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.