linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sakari.ailus@maxwell.research.nokia.com (Sakari Ailus)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] OMAP: IOMMU: add support to callback during fault handling
Date: Wed, 23 Feb 2011 22:09:05 +0200	[thread overview]
Message-ID: <4D656961.7080105@maxwell.research.nokia.com> (raw)
In-Reply-To: <AANLkTi=s-p3OQfzor27sf-qqqNxipSrOAEQtPQEGaO=L@mail.gmail.com>

Guzman Lugo, Fernando wrote:
> Hi,

Hi Fernando,

> In OMAP4 the cortex M3 is a double core processor and as each core is
> running they own version of the RTOS we threat them independently. So
> our driver which controls the remote processor sees two processor but
> both use the same iommu hw. When a iommu fault happens, at this
> moment, it is consider as a faltal error and it is no managed to
> recover and continue, instead a restart of the processor is needed, if
> the fault happens in core0 we need to reset core1 too and vice versa.
> if the iommu would support several user callbacks, we can register the
> callback which resets core0 and also the callback which resets core1
> and treat them as totally independent processors. Also we have an
> error event notifier driver, which is only in charge of notifying
> error events to userspace, so we would have multiple callbacks we
> could do this

The original purpose of the patch, as far as I understand, is to allow
getting useful information for debugging purposes should an iommu fault
happen.

Also, I'm not sure it's necessarily a good idea to just go and reset
the M3 cores in case an iommu fault happens --- this is very probably a
grave bug in the software running on those M3s. It should be fixed
instead of just hiding it. There will be consequences to host side as
well, won't there?

> iommu <---- register fault callback for error notify driver
> 
> instead of
> 
> iommu <--- register fault callback for remote processor driver
> <----register fault event for error notify driver.
> 
> with that, we remove one dependency of the errornotify driver.

I suppose this is not in mainline?

Regards,

-- 
Sakari Ailus
sakari.ailus at maxwell.research.nokia.com

  parent reply	other threads:[~2011-02-23 20:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-16 19:35 [PATCH v3 0/2] OMAP: IOMMU fault callback support David Cohen
2011-02-16 19:35 ` [PATCH v3 1/2] OMAP2+: IOMMU: don't print fault warning on specific layer David Cohen
2011-02-16 19:35 ` [PATCH v3 2/2] OMAP: IOMMU: add support to callback during fault handling David Cohen
2011-02-21  8:18   ` Hiroshi DOYU
2011-02-21  8:22     ` Felipe Balbi
2011-02-21  8:57       ` David Cohen
2011-02-21  9:20         ` Felipe Balbi
2011-02-21  9:07     ` David Cohen
2011-02-21  9:51       ` Hiroshi DOYU
2011-02-21 18:43   ` Ramirez Luna, Omar
2011-02-21 21:12     ` David Cohen
2011-02-21 23:25       ` Ramirez Luna, Omar
2011-02-21 23:48         ` David Cohen
2011-02-23  1:17   ` Guzman Lugo, Fernando
2011-02-23  9:45     ` David Cohen
2011-02-23 13:39       ` Guzman Lugo, Fernando
2011-02-23 19:54         ` David Cohen
2011-02-23 20:56           ` Sakari Ailus
2011-02-23 21:48             ` Guzman Lugo, Fernando
2011-02-24  6:39               ` David Cohen
2011-02-23 21:12           ` Guzman Lugo, Fernando
2011-02-23 20:09         ` Sakari Ailus [this message]
2011-02-23 20:21           ` David Cohen
2011-02-23 21:30           ` Guzman Lugo, Fernando
2011-02-24  8:35           ` Felipe Balbi
2011-02-24 11:26             ` David Cohen
2011-02-24 11:29               ` Felipe Balbi
2011-02-24 17:58                 ` Guzman Lugo, Fernando
2011-02-24 20:31                   ` Tony Lindgren
2011-02-24 22:21                     ` Tony Lindgren
2011-02-21  9:52 ` [PATCH v3 0/2] OMAP: IOMMU fault callback support Hiroshi DOYU

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=4D656961.7080105@maxwell.research.nokia.com \
    --to=sakari.ailus@maxwell.research.nokia.com \
    --cc=linux-arm-kernel@lists.infradead.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).