From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Maarten Lankhorst <m.b.lankhorst@gmail.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
nouveau@lists.freedesktop.org
Subject: Re: [Nouveau] [PATCH] drm/nouveau: Ack interrupts for some fuc engines
Date: Tue, 26 Mar 2013 07:29:24 +0100 [thread overview]
Message-ID: <51514044.1040709@canonical.com> (raw)
In-Reply-To: <20130325181456.GA8026@joi.lan>
Op 25-03-13 19:14, Marcin Slusarz schreef:
> On Mon, Mar 25, 2013 at 10:22:37AM +0100, Maarten Lankhorst wrote:
>> Fixes 100% cpu usage when the exit interrupt never got acked.
>>
>> Signed-off-by: Maarten Lankhorst <m.b.lankhorst@gmail.com>
>> ---
>> diff --git a/drivers/gpu/drm/nouveau/core/core/falcon.c b/drivers/gpu/drm/nouveau/core/core/falcon.c
>> index e05c157..b11c5f3 100644
>> --- a/drivers/gpu/drm/nouveau/core/core/falcon.c
>> +++ b/drivers/gpu/drm/nouveau/core/core/falcon.c
>> @@ -229,6 +229,24 @@ _nouveau_falcon_fini(struct nouveau_object *object, bool suspend)
>> return nouveau_engine_fini(&falcon->base, suspend);
>> }
>>
>> +void
>> +nouveau_falcon_intr(struct nouveau_subdev *subdev)
>> +{
>> + struct nouveau_falcon *falcon = (void*)subdev;
>> + u32 intr = nv_ro32(falcon, 0x008);
>> +
>> + nv_wo32(falcon, 0x004, intr);
>> +
>> + if (intr & 0x10) {
>> + intr &= ~0x10;
>> +
>> + nv_info(falcon, "Exit interrupt called\n");
> Do you really want to print it at "info" level? How frequent it is?
It shouldn't be often, I want it to run at the error level since that usually means the firmware exited prematurely/crashed and things go bad, but it happens with the secret scrubber finishing on initialization too. That one is harmless though.
>> + }
>> +
>> + if (intr)
>> + nv_error(falcon, "Unhandled interrupt %08x\n", intr);
>> +}
>> +
>> int
>> nouveau_falcon_create_(struct nouveau_object *parent,
>> struct nouveau_object *engine,
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
>
next prev parent reply other threads:[~2013-03-26 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 9:22 [PATCH] drm/nouveau: Ack interrupts for some fuc engines Maarten Lankhorst
2013-03-25 18:14 ` [Nouveau] " Marcin Slusarz
2013-03-26 6:29 ` Maarten Lankhorst [this message]
2013-03-26 20:29 ` Marcin Slusarz
[not found] ` <20130326202952.GA11307-OI9uyE9O0yo@public.gmane.org>
2013-03-27 6:21 ` Maarten Lankhorst
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=51514044.1040709@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=m.b.lankhorst@gmail.com \
--cc=marcin.slusarz@gmail.com \
--cc=nouveau@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox