Hi Jason,
I have briefly tested yesterday on a P4080 board and did not see any
issues. I do not have much expertise on KASLR, but I will take a look
over the code.
Regards,
Diana
On 7/25/2019 10:16 AM, Jason Yan wrote:
> Hi all, any comments?
>
>
> On 2019/7/17 16:06, Jason Yan wrote:
>> This se
On 2019/7/26 3:58, Kees Cook wrote:
On Thu, Jul 25, 2019 at 03:16:28PM +0800, Jason Yan wrote:
Hi all, any comments?
I'm a fan of it, but I don't know ppc internals well enough to sanely
review the code. :) Some comments below on design...
Hi Kees, Thanks for your comments.
On 2019/7
On 2019/7/26 15:04, Diana Madalina Craciun wrote:
Hi Jason,
I have briefly tested yesterday on a P4080 board and did not see any
issues. I do not have much expertise on KASLR, but I will take a look
over the code.
Hi Diana, thanks. Looking forward to your suggestions.
Regards,
Diana
On
On Tue, Jul 23, 2019 at 09:43:55PM +0530, Vaibhav Jain wrote:
> Update the hvcalls.h to include op-codes for new hcalls introduce to
> manage SCM memory. Also update existing hcall definitions to reflect
> current papr specification for SCM.
>
> The removed hcall op-codes H_SCM_MEM_QUERY, H_SCM_BL
This series converts the text files under Documentation with doesn't end
neither .txt or .rst and are not part of ABI or features.
This series is at:
https://git.linuxtv.org/mchehab/experimental.git/log/?h=rst_for_5_4_v3
And it is based on yesterday's upstream tree.
After this series, we
Convert docs to ReST and add them to the arch-specific
book.
The conversion here was trivial, as almost every file there
was already using an elegant format close to ReST standard.
The changes were mostly to mark literal blocks and add a few
missing section title identifiers.
One note with regar
Em Fri, 26 Jul 2019 09:51:10 -0300
Mauro Carvalho Chehab escreveu:
> This series converts the text files under Documentation with doesn't end
> neither .txt or .rst and are not part of ABI or features.
>
> This series is at:
> https://git.linuxtv.org/mchehab/experimental.git/log/?h=rst_for
On Fri, Jul 26, 2019 at 03:20:26PM +0800, Jason Yan wrote:
> The boot code only maps one 64M zone at early start. If the kernel crosses
> two 64M zones, we need to map two 64M zones. Keep the kernel in one 64M
> saves a lot of complex codes.
Ah-ha. Gotcha. Thanks for the clarification.
> Yes, if
