public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@petalogix.com>
To: steve@digidescorp.com
Cc: monstr@monstr.eu, microblaze-uclinux@itee.uq.edu.au,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH, RESEND] microblaze: Fix level interrupt ACKing
Date: Tue, 24 Nov 2009 13:45:22 +0100	[thread overview]
Message-ID: <4B0BD562.4010602@petalogix.com> (raw)
In-Reply-To: <1258742956.2881.3.camel@iscandar.digidescorp.com>

Steven J. Magnani wrote:
> On Fri, 2009-11-20 at 12:07 +0100, Michal Simek wrote:
>> Hi Steve,
>>
>> steve@digidescorp.com wrote:
>>> Level interrupts need to be ack'd in the unmask handler, as in powerpc. 
>>> Among other issues, this bug causes the system clock to appear to run at 
>>> double-speed.
>> Can you send me any step-by-step manual how to demonstrate me this 
>> fault? If system clock runs at double-speed, then I should be able able 
>> to see that time is two times faster. Or do you mean different behavior?
> 
> Unless there's a way to read jiffies_64 in userspace, the easiest way I
> know of is to use the debugger. Stop the kernel soon after you boot it,
> and read jiffies_64. Continue execution for some known amount of
> wall-clock time, then stop the kernel again and recheck jiffies_64.
> Without the patch, the number of elapsed jiffies is twice what you'd
> expect based on HZ.

yes, I saw that behavior. Just thinking what caused that jiffies was two 
times faster.

But anyway. I added this patch to next branch.

Thanks,
Michal

> 
>> Thanks,
>> Michal
> 
> Regards,
> ------------------------------------------------------------------------
>  Steven J. Magnani               "I claim this network for MARS!
>  www.digidescorp.com              Earthling, return my space modulator!"
> 
>  #include <standard.disclaimer>
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663

      reply	other threads:[~2009-11-24 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-17 14:43 [PATCH, RESEND] microblaze: Fix level interrupt ACKing steve
2009-11-20 11:07 ` Michal Simek
2009-11-20 18:49   ` Steven J. Magnani
2009-11-24 12:45     ` Michal Simek [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=4B0BD562.4010602@petalogix.com \
    --to=michal.simek@petalogix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=microblaze-uclinux@itee.uq.edu.au \
    --cc=monstr@monstr.eu \
    --cc=steve@digidescorp.com \
    /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