From: Michael Ellerman <mpe@ellerman.id.au>
To: Balbir Singh <bsingharora@gmail.com>, linuxppc-dev@ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com, Balbir Singh <bsingharora@gmail.com>
Subject: Re: [powerpc v5 0/3] Enable IAMR storage keys for radix
Date: Tue, 15 Nov 2016 13:40:12 +1100 [thread overview]
Message-ID: <87bmxhzcs3.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <1479125778-18496-1-git-send-email-bsingharora@gmail.com>
Balbir Singh <bsingharora@gmail.com> writes:
> 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
> Enable storage keys for radix - user mode execution
These should be "powerpc/mm/radix: ...".
> Detect instruction fetch denied and report
And that should be "powerpc/mm: ..."
cheers
prev parent reply other threads:[~2016-11-15 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 12:16 [powerpc v5 0/3] Enable IAMR storage keys for radix Balbir Singh
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 ` Michael Ellerman [this message]
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=87bmxhzcs3.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=linuxppc-dev@ozlabs.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.