From: bill4carson@gmail.com (bill4carson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: arm L_PTE_XXX entry addition for Debugging purpose
Date: Tue, 31 Jul 2012 15:13:37 +0800 [thread overview]
Message-ID: <501785A1.6090806@gmail.com> (raw)
In-Reply-To: <CABFWu7b85yfwpTiJHTvz4OPHYLyzstnVU=_tgM6NmXb9vvChiw@mail.gmail.com>
On 2012?07?30? 17:39, Dhyan wrote:
> Dear All,
>
> From linux(2.6.35) arm page table architecture i can see we have one
> hardware page table and there is corresponding Linux page table Entry
> (L_PTE_*).The "Linux" PTE definitions are as like below from
> arch/arm/include/asm/pgtable.h.
>
> |#define L_PTE_PRESENT (1<< 0)
> #define L_PTE_FILE (1<< 1)
> #define L_PTE_YOUNG (1<< 1)
> #define L_PTE_BUFFERABLE(1<< 2)
> #define L_PTE_CACHEABLE (1<< 3)
> #define L_PTE_USER (1<< 4)
> #define L_PTE_WRITE (1<< 5)
> #define L_PTE_EXEC (1<< 6)
> #define L_PTE_DIRTY (1<< 7)
> #define L_PTE_COHERENT (1<< 9)
> #define L_PTE_SHARED (1<< 10)
> |
>
> So is it possible to add one more #|define L_PTE_DEBUG (1 << 11)| for my
> debugging purpose (basically to trap all the write to that page and set
> this bit when write happens and clear it off in another thread )? Or
> is there any limitation like we can use only L_PTE till 10th bit ?
>
No such limitation on bit 11, so you can use define L_PTE_DEBUG (1 << 11)
However I don't follow why you want to do so?
> So could you please help
>
> --
>
> Thanks & Regards
>
> Dhayn
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
--
Love each day!
--bill
next prev parent reply other threads:[~2012-07-31 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 9:39 arm L_PTE_XXX entry addition for Debugging purpose Dhyan
2012-07-31 7:13 ` bill4carson [this message]
2012-07-31 9:20 ` Dhyan
2012-08-01 2:08 ` bill4carson
2012-08-01 4:53 ` Dhyan
2012-08-01 5:57 ` Mulyadi Santosa
2012-08-01 6:17 ` Dhyan
2012-08-01 8:42 ` Mulyadi Santosa
2012-08-02 8:42 ` bill4carson
2012-08-02 9:03 ` Dhyan
2012-08-02 9:28 ` bill4carson
2012-08-02 9:33 ` Dhyan
-- strict thread matches above, loose matches on Subject: below --
2012-08-01 6:54 Vladimir Murzin
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=501785A1.6090806@gmail.com \
--to=bill4carson@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.