From: Balbir Singh <bsingharora@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Cc: "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>,
Michael Ellerman <mpe@ellerman.id.au>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Subject: Re: [PATCH v1 1/3] arch/powerpc/set_memory: Implement set_memory_xx routines
Date: Fri, 4 Aug 2017 13:53:31 +1000 [thread overview]
Message-ID: <CAKTCnzkUt_LQmhE8hOi12LUtmiZCE0NEFweGb6pMbAzkB2arsQ@mail.gmail.com> (raw)
In-Reply-To: <87zibgngs2.fsf@linux.vnet.ibm.com>
On Fri, Aug 4, 2017 at 1:38 PM, Aneesh Kumar K.V
<aneesh.kumar@linux.vnet.ibm.com> wrote:
> Balbir Singh <bsingharora@gmail.com> writes:
>
>> On Wed, Aug 2, 2017 at 8:09 PM, Aneesh Kumar K.V
>> <aneesh.kumar@linux.vnet.ibm.com> wrote:
>>> Balbir Singh <bsingharora@gmail.com> writes:
>>>
>>>> Add support for set_memory_xx routines. With the STRICT_KERNEL_RWX
>>>> feature support we got support for changing the page permissions
>>>> for pte ranges. This patch adds support for both radix and hash
>>>> so that we can change their permissions via set/clear masks.
>>>>
>>>> A new helper is required for hash (hash__change_memory_range()
>>>> is changed to hash__change_boot_memory_range() as it deals with
>>>> bolted PTE's).
>>>>
>>>> hash__change_memory_range() works with vmalloc'ed PAGE_SIZE requests
>>>> for permission changes. hash__change_memory_range() does not invoke
>>>> updatepp, instead it changes the software PTE and invalidates the PTE.
>>>>
>>>> For radix, radix__change_memory_range() is setup to do the right
>>>> thing for vmalloc'd addresses. It takes a new parameter to decide
>>>> what attributes to set.
>>>>
>>> ....
>>>
>>>> +int hash__change_memory_range(unsigned long start, unsigned long end,
>>>> + unsigned long set, unsigned long clear)
>>>> +{
>>>> + unsigned long idx;
>>>> + pgd_t *pgdp;
>>>> + pud_t *pudp;
>>>> + pmd_t *pmdp;
>>>> + pte_t *ptep;
>>>> +
>>>> + start = ALIGN_DOWN(start, PAGE_SIZE);
>>>> + end = PAGE_ALIGN(end); // aligns up
>>>> +
>>>> + /*
>>>> + * Update the software PTE and flush the entry.
>>>> + * This should cause a new fault with the right
>>>> + * things setup in the hash page table
>>>> + */
>>>> + pr_debug("Changing flags on range %lx-%lx setting 0x%lx removing 0x%lx\n",
>>>> + start, end, set, clear);
>>>> +
>>>> + for (idx = start; idx < end; idx += PAGE_SIZE) {
>>>
>>>
>>>> + pgdp = pgd_offset_k(idx);
>>>> + pudp = pud_alloc(&init_mm, pgdp, idx);
>>>> + if (!pudp)
>>>> + return -1;
>>>> + pmdp = pmd_alloc(&init_mm, pudp, idx);
>>>> + if (!pmdp)
>>>> + return -1;
>>>> + ptep = pte_alloc_kernel(pmdp, idx);
>>>> + if (!ptep)
>>>> + return -1;
>>>> + hash__pte_update(&init_mm, idx, ptep, clear, set, 0);
>>
>> I think this does the needful, if H_PAGE_HASHPTE is set, the flush
>> will happen
>>
>>>> + hash__flush_tlb_kernel_range(idx, idx + PAGE_SIZE);
>>>> + }
>>>
>>> You can use find_linux_pte_or_hugepte. with my recent patch series
>>> find_init_mm_pte() ?
>>>
>>
>> for pte_mkwrite and pte_wrprotect?
>
> For walking page table. I am not sure you really want to allocate page
> table in that function. If you do, then what will be the initial value
> of PTE ? We are requesting to set an clear from and existing PTE entry
> right ? If you find a none page table entry you should handle it via a
> fault ?
>
Fair enough, I've been lazy with that check, I'll fix it in v2
Balbir Singh.
next prev parent reply other threads:[~2017-08-04 3:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 11:25 [PATCH v1 0/3] Implement set_memory_xx for ppc64 book3s Balbir Singh
2017-08-01 11:25 ` [PATCH v1 1/3] arch/powerpc/set_memory: Implement set_memory_xx routines Balbir Singh
2017-08-01 19:08 ` christophe leroy
2017-08-02 3:07 ` Balbir Singh
2017-08-02 10:09 ` Aneesh Kumar K.V
2017-08-02 10:33 ` Balbir Singh
2017-08-04 3:38 ` Aneesh Kumar K.V
2017-08-04 3:53 ` Balbir Singh [this message]
2017-08-01 11:25 ` [PATCH v1 2/3] Enable ARCH_HAS_SET_MEMORY Balbir Singh
2017-08-01 11:25 ` [PATCH v1 3/3] arch/powerpc/net/bpf: Basic EBPF support Balbir Singh
2017-08-02 14:22 ` Naveen N. Rao
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=CAKTCnzkUt_LQmhE8hOi12LUtmiZCE0NEFweGb6pMbAzkB2arsQ@mail.gmail.com \
--to=bsingharora@gmail.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
/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).