The same definition for pte_page is duplicated for the MIPS32
PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
definition outside of preprocessor conditionals.
Signed-off-by: Paul Burton <paul.bur...@imgtec.com>
Reviewed-by: James Hogan <james.ho.
The same definition for pte_page is duplicated for the MIPS32
PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
definition outside of preprocessor conditionals.
Signed-off-by: Paul Burton
Reviewed-by: James Hogan
---
Changes in v3: None
Changes in v2: None
arch/
The same definition for pte_page is duplicated for the MIPS32
PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
definition outside of preprocessor conditionals.
Signed-off-by: Paul Burton <paul.bur...@imgtec.com>
Reviewed-by: James Hogan <james.ho.
The same definition for pte_page is duplicated for the MIPS32
PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
definition outside of preprocessor conditionals.
Signed-off-by: Paul Burton
Reviewed-by: James Hogan
---
Changes in v2: None
arch/mips/include/asm/pgtabl
On Fri, Apr 15, 2016 at 11:36:54AM +0100, Paul Burton wrote:
> The same definition for pte_page is duplicated for the MIPS32
> PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
> definition outside of preprocessor conditionals.
>
> Signed-off-by: Pa
On Fri, Apr 15, 2016 at 11:36:54AM +0100, Paul Burton wrote:
> The same definition for pte_page is duplicated for the MIPS32
> PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
> definition outside of preprocessor conditionals.
>
> Signed-off-by: Pau
The same definition for pte_page is duplicated for the MIPS32
PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
definition outside of preprocessor conditionals.
Signed-off-by: Paul Burton <paul.bur...@imgtec.com>
---
arch/mips/include/asm/pgtable-32.h | 6 +++-
The same definition for pte_page is duplicated for the MIPS32
PHYS_ADDR_T_64BIT case & the generic case. Unify them by moving a single
definition outside of preprocessor conditionals.
Signed-off-by: Paul Burton
---
arch/mips/include/asm/pgtable-32.h | 6 +++---
1 file changed, 3 insert
Daljeet Maini/India/IBM@IBMIN, |
| [EMAIL PROTECTED] |
| Subject: Re: pte_page|
>|
On Wed, 30 May 2001, Pete Wyckoff wrote:
> > __pa(page_address
, |
| [EMAIL PROTECTED] |
| Subject: Re: pte_page|
|
On Wed, 30 May 2001, Pete Wyckoff wrote:
__pa(page_address(pte_page(pte))) is the address you want. [or
pte_val(*pte
On Wed, 30 May 2001, Pete Wyckoff wrote:
> > __pa(page_address(pte_page(pte))) is the address you want. [or
> > pte_val(*pte) & (PAGE_SIZE-1) on x86 but this is platform-dependent.]
>
> Does this work on x86 non-kmapped highmem user pages too? (i.e. is
> page->virtu
[EMAIL PROTECTED] said:
> On Wed, 30 May 2001 [EMAIL PROTECTED] wrote:
> > I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page'
> > inside a module to get the physical address of a user space virtual
> > address. The physical address returned by 'pte_page' is
On Wed, 30 May 2001 [EMAIL PROTECTED] wrote:
> I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page'
> inside a module to get the physical address of a user space virtual
> address. The physical address returned by 'pte_page' is not page
> aligned whereas the vir
Brian Gerst wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
> > module to get the physical address of a user space virtual address. The
> > physical address returned by 'pte_page' is not page a
[EMAIL PROTECTED] wrote:
>
> I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
> module to get the physical address of a user space virtual address. The
> physical address returned by 'pte_page' is not page aligned whereas the
> virtual address was pa
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
module to get the physical address of a user space virtual address. The
physical address returned by 'pte_page' is not page aligned whereas the
virtual address was page aligned. Can somebody tell me the reason?
Also, can
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
module to get the physical address of a user space virtual address. The
physical address returned by 'pte_page' is not page aligned whereas the
virtual address was page aligned. Can somebody tell me the reason?
Also, can
[EMAIL PROTECTED] wrote:
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page' inside a
module to get the physical address of a user space virtual address. The
physical address returned by 'pte_page' is not page aligned whereas the
virtual address was page aligned. Can somebody
On Wed, 30 May 2001 [EMAIL PROTECTED] wrote:
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page'
inside a module to get the physical address of a user space virtual
address. The physical address returned by 'pte_page' is not page
aligned whereas the virtual address was page
[EMAIL PROTECTED] said:
On Wed, 30 May 2001 [EMAIL PROTECTED] wrote:
I use the 'pgt_offset', 'pmd_offset', 'pte_offset' and 'pte_page'
inside a module to get the physical address of a user space virtual
address. The physical address returned by 'pte_page' is not page
aligned whereas
On Wed, 30 May 2001, Pete Wyckoff wrote:
__pa(page_address(pte_page(pte))) is the address you want. [or
pte_val(*pte) (PAGE_SIZE-1) on x86 but this is platform-dependent.]
Does this work on x86 non-kmapped highmem user pages too? (i.e. is
page-virtual valid for every potential user
21 matches
Mail list logo
