All of lore.kernel.org
 help / color / mirror / Atom feed
From: ahmedsoliman0x666@gmail.com (Ahmed Soliman)
To: kernelnewbies@lists.kernelnewbies.org
Subject: How to change page permission from inside the kernel?
Date: Sat, 7 Jul 2018 13:05:51 +0200	[thread overview]
Message-ID: <CAAGnT3bs6MkJoaLuLgsVYJN-OatiZqZZyQNJDs_Xa8xy9+iAsw@mail.gmail.com> (raw)
In-Reply-To: <1530929582.5350.28.camel@surriel.com>

> It sounds like the only permission you care about is
> the permission of the _guest_ writing to that memory,
> not the permission of the qemu-kvm userspace program
> writing to that memory.
Yes that is perhaps what I meant.
>
> You may be looking at the wrong page mapping to
> manipulate.

I think that it is still the same mapping because hva created by
qemu-kvm is the one used by the guest (after another layer of paging
?).
I will check TLB specs and verify valdis worries about problems with
interfering data moving to TLB.
But I think I moved away from the original question. So I will re-ask
it again, How can i change set R/O protection to a page from inside a
kernel module ? That was the current problem I was facing.

> --
> All Rights Reversed.

  reply	other threads:[~2018-07-07 11:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06 18:06 How to change page permission from inside the kernel? Ahmed Soliman
2018-07-06 18:42 ` valdis.kletnieks at vt.edu
2018-07-06 19:29   ` Ahmed Soliman
2018-07-06 21:10     ` valdis.kletnieks at vt.edu
     [not found]       ` <CAAGnT3Ymh6EcdaLo=rGR4-oH0nYub8v9VCZaCtppyxxJAmh5Ag@mail.gmail.com>
2018-07-06 21:59         ` Fwd: " Ahmed Soliman
2018-07-06 22:32           ` valdis.kletnieks at vt.edu
2018-07-06 23:31             ` Ahmed Soliman
2018-07-07  2:06               ` valdis.kletnieks at vt.edu
2018-07-07  2:13     ` Rik van Riel
2018-07-07 11:05       ` Ahmed Soliman [this message]
2018-07-06 18:49 ` Ruben Safir

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=CAAGnT3bs6MkJoaLuLgsVYJN-OatiZqZZyQNJDs_Xa8xy9+iAsw@mail.gmail.com \
    --to=ahmedsoliman0x666@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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.