From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [Ksummit-2013-discuss] [ARM ATTEND] Trustzone-based security solution for ARM Linux
Date: Thu, 15 Aug 2013 11:44:26 -0700 [thread overview]
Message-ID: <20130815184426.GA23581@kroah.com> (raw)
In-Reply-To: <20130815183319.GE23006@n2100.arm.linux.org.uk>
On Thu, Aug 15, 2013 at 07:33:19PM +0100, Russell King - ARM Linux wrote:
> On Thu, Aug 15, 2013 at 11:26:00AM -0700, Greg KH wrote:
> > That's their decision, which is fine. Getting the Linux CAN stack
> > "certified" might be a good goal for a manufacturer who wants to ship
> > Linux for this type of system, although we all know how much those
> > things really matter when it comes to technical issues :)
>
> If response times matter, and you're relying on software to produce
> those response times, then you really need to look at threaded IRQs.
> The standard Linux interrupt model sucks, especially if you have USB
> enabled.
Using USB withing a "trusted OS" situation isn't very wise for a number
of reasons :)
There is work happening on making USB host controllers use threaded
interrups, the first round of changes just went into the usb-next branch
in linux-next, and will show up in 3.12. It reduces the overhead of USB
on ARM systems by a measurable ammount. There are more patches coming
for this as well to fix up other related issues, and USB host
controllers.
> I'm still seeing upwards of 2.6ms servicing times for USB keyboards
> and nice, which given that they are just a set of keys and a position
> sensor is totally crazy.
USB is not exactly a low-latency protocol. A lot happens for just those
"key press" packets to make it to the machine.
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-15 18:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 3:44 [ARM ATTEND] Trustzone-based security solution for ARM Linux Barry Song
2013-08-15 4:28 ` [Ksummit-2013-discuss] " Greg KH
2013-08-15 5:14 ` Jassi Brar
2013-08-15 7:45 ` Barry Song
2013-08-15 8:05 ` Greg KH
2013-08-15 8:22 ` Barry Song
2013-08-15 16:01 ` Greg KH
2013-08-16 2:08 ` Barry Song
2013-08-15 8:24 ` Ard Biesheuvel
2013-08-15 15:56 ` Greg KH
2013-08-15 17:41 ` Ard Biesheuvel
2013-08-15 18:26 ` Greg KH
2013-08-15 18:33 ` Russell King - ARM Linux
2013-08-15 18:44 ` Greg KH [this message]
2013-08-15 8:17 ` Jassi Brar
2013-08-15 8:36 ` Barry Song
2013-08-15 7:36 ` Barry Song
2013-08-15 16:03 ` Stephen Warren
2013-08-15 17:43 ` Dave Martin
2013-08-16 2:39 ` Barry Song
2013-08-16 11:14 ` Dave Martin
2013-08-16 11:17 ` Jassi Brar
2013-08-19 23:31 ` Barry Song
2013-08-15 9:05 ` Barry Song
2013-08-15 7:57 ` Ben Dooks
2013-08-15 8:06 ` Barry Song
2013-08-15 14:08 ` Dave Martin
2013-08-16 2:49 ` Barry Song
[not found] <20130816110446.GA2909@localhost.localdomain>
2013-08-19 23:13 ` [Ksummit-2013-discuss] " Barry Song
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=20130815184426.GA23581@kroah.com \
--to=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.