From: David Gibson <david@gibson.dropbear.id.au>
To: alarson@ddci.com
Cc: agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] Subject: [PATCH] target-ppc: Add global timer group A to open-pic.
Date: Wed, 26 Apr 2017 12:51:34 +1000 [thread overview]
Message-ID: <20170426025134.GM16882@umbus.fritz.box> (raw)
In-Reply-To: <OF7D33B8CD.4B2CD628-ON8625810C.00022270-8625810C.000378AB@ddci.com>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
On Sun, Apr 23, 2017 at 07:37:55PM -0500, alarson@ddci.com wrote:
> David Gibson <david@gibson.dropbear.id.au> wrote on 04/23/2017 06:17:22
> PM:
>
> > From: David Gibson <david@gibson.dropbear.id.au>
> > To: Aaron Larson <alarson@ddci.com>
> > Cc: agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
> > Date: 04/23/2017 06:54 PM
> > Subject: Re: Subject: [PATCH] target-ppc: Add global timer group A to
> open-pic.
> >
> > On Fri, Apr 21, 2017 at 02:58:23PM -0700, Aaron Larson wrote:
> > > Add global timer group A to open-pic. This patch is still somewhat
> > > dubious because I'm not sure how to determine what QEMU wants for the
> > > timer frequency. Suggestions solicited.
> >
> > This commit message really needs some more context. What's a "global
> > time group A" a and why do we want it?
>
> The open-pic spec includes two sets/groups of timers, groups A and B,
> 4 timers in each group. Previously in QEMU the timer group A
> registers were implemented but they did not "count" or generate any
> interrupts. The patch makes the timers to do both (count and generate
> interrupts).
Ok, sounds good, but this is exactly the sort of thing that needs to
go in the commit message.
> About a year ago I mentioned that we had implemented this and offered
> to submit a patch, which seemed to be acceptable. Sadly, when I
> reviewed the implementation it had several egregious errors that I
> didn't know how to fix until recently.
Ok. Now that you mention that, it rings a vague bell.
> Quite frankly I didn't expect the patch to be accepted in its current
> form for the reason mentioned in the above commit log and was hoping
> for some guidance. If this is no longer a desirable patch, I can
> certainly continue to maintain it locally for our use.
That's fine - but I need context of what the patch is attempting to
do, and why that's desirable in order to properly review it.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-04-26 3:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 21:58 [Qemu-devel] Subject: [PATCH] target-ppc: Add global timer group A to open-pic Aaron Larson
2017-04-23 23:17 ` David Gibson
2017-04-24 0:37 ` alarson
2017-04-26 2:51 ` David Gibson [this message]
2017-04-26 4:34 ` David Gibson
2017-05-03 1:37 ` alarson
2017-05-03 5:14 ` David Gibson
-- strict thread matches above, loose matches on Subject: below --
2017-04-21 21:48 Aaron Larson
2017-04-21 21:52 ` no-reply
2017-04-21 22:12 ` alarson
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=20170426025134.GM16882@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=alarson@ddci.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 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).