Fix CPU hotplug IRQ migration
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 4 patches 0 repliesNew
1 of 4 patches is in this archive. The cover letter announces 4.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 3/4 | ARM: CPU hotplug: pass in proper affinity mask on IRQ migration | +0 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/4] Fix CPU hotplug IRQ migration
Quoted 1 line · Russell King - ARM Linux
On Fri, Jul 22, 2011 at 11:05:01AM +0530, Santosh Shilimkar wrote:
[...]
Quoted 8 lines
Secure code is called on CPU1 too, so I don't think your statement is accurate. Eg:
omap_modify_auxcoreboot0(0x0, 0x200) omap_read_auxcoreboot0()both result in calling secure code on CPU1.
These are monitor mode secure API's and they can be executed on any CPU.
I am talking about the services like secure encryption/decryption, secure copy, saving secure RAM etc.
These services can't be executed on CPU1 and hence the concern. There is entire secure middle-ware which runs in parallel with Linux and all it's services are bound to CPU0 only.
Regards
Santosh