xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Oleksandr Tyshchenko <oleksandr.tyshchenko@globallogic.com>
Cc: Ian Campbell <ian.campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: ARM Generic Timer interrupt
Date: Tue, 27 May 2014 16:00:31 +0100	[thread overview]
Message-ID: <5384A88F.4090401@linaro.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1405271203470.4779@kaball.uk.xensource.com>

On 05/27/2014 01:11 PM, Stefano Stabellini wrote:
> Given that 1) didn't sound right to me, I tried 2) first but I had
> issues with the ARM emulator at the time.  And as an ulterior
> confirmation that deactivating it is not how ARM thought that the vtimer
> should be used, Linux and KVM do 1) too.

I suspect you had issue on the emulator because VCPU can EOI the timer
IRQ on another CPU.

If so, you will disable the vtimer interrupt forever on this CPU.

> But I don't like the idea of having to modify the vtimer handler in QNX,
> so I have hacked together this patch, that would do 2) on top of my
> maintenance interrupt series. Unfortunately it needs to ask for a
> maintenance interrupt for the vtimer interrupt, so I can't say I am
> completely convinced that it is the right thing to do.
> 
> What do people think about this?

The solution 2) seems very hackish. Hence, this IRQ will be fired very
often.

It may be better to let either QNX use physical timer (AFAIK it's
working out-of-box), or modifying to support virtual timer.

Regards,

-- 
Julien Grall

  reply	other threads:[~2014-05-27 15:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-26 15:26 ARM Generic Timer interrupt Oleksandr Tyshchenko
2014-05-27 12:11 ` Stefano Stabellini
2014-05-27 15:00   ` Julien Grall [this message]
2014-05-27 16:05     ` Stefano Stabellini
2014-05-27 16:12       ` Julien Grall
2014-05-27 16:53         ` Oleksandr Tyshchenko
2014-05-28 10:10   ` Ian Campbell
2014-05-28 11:32     ` Julien Grall
2014-05-28 11:34       ` Ian Campbell
2014-05-28 11:37         ` Julien Grall
2014-05-28 11:51         ` Stefano Stabellini
2014-05-28 11:54           ` Ian Campbell
2014-05-28 12:11             ` Stefano Stabellini
2014-05-28 12:20               ` Ian Campbell
2014-05-28 12:33                 ` Stefano Stabellini
2014-05-28 12:36                   ` Ian Campbell
2014-05-28 13:21                     ` Stefano Stabellini
2014-05-29  8:38                       ` Oleksandr Tyshchenko

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=5384A88F.4090401@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=oleksandr.tyshchenko@globallogic.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xen.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).