From: Balbir Singh <bsingharora@gmail.com>
To: linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: aneesh.kumar@linux.vnet.ibm.com, Balbir Singh <bsingharora@gmail.com>
Subject: [powerpc v5 0/3] Enable IAMR storage keys for radix
Date: Mon, 14 Nov 2016 23:16:15 +1100 [thread overview]
Message-ID: <1479125778-18496-1-git-send-email-bsingharora@gmail.com> (raw)
The first patch sets up AMOR in hypervisor mode. AMOR
needs to be setup before IAMR (details of AMOR/IAMR in
each patch). The second patch enables detection of exceptions
generated due to instruction fetch violations caused
and OOPSs' the task. The third patch enables IAMR for
both hypervisor and guest kernels.
I've tested with patch series with a sample hack and
payload.
Chris Smart helped with the series, reviewing and
providing valuable feedback
Changelog
Remove __init annotation for iamr and amor init
Balbir Singh (3):
Setup AMOR in HV mode
Detect instruction fetch denied and report
Enable storage keys for radix - user mode execution
arch/powerpc/mm/fault.c | 4 ++++
arch/powerpc/mm/pgtable-radix.c | 41 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 45 insertions(+)
--
2.5.5
next reply other threads:[~2016-11-14 12:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 12:16 Balbir Singh [this message]
2016-11-14 12:16 ` [powerpc v5 1/3] Setup AMOR in HV mode Balbir Singh
2016-11-14 12:16 ` [powerpc v5 2/3] Detect instruction fetch denied and report Balbir Singh
2016-11-15 2:39 ` Michael Ellerman
2016-11-14 12:16 ` [powerpc v5 3/3] Enable storage keys for radix - user mode execution Balbir Singh
2016-11-15 2:40 ` [powerpc v5 0/3] Enable IAMR storage keys for radix Michael Ellerman
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=1479125778-18496-1-git-send-email-bsingharora@gmail.com \
--to=bsingharora@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).