From: Christoph Hellwig <hch@lst.de>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 2/5] [POWERPC] 8xx: generic 8xx code arch/powerpc port
Date: Wed, 15 Nov 2006 19:23:16 +0100 [thread overview]
Message-ID: <20061115182316.GA20719@lst.de> (raw)
In-Reply-To: <20061114012816.17455.12059.stgit@localhost.localdomain>
On Tue, Nov 14, 2006 at 04:28:16AM +0300, Vitaly Bordug wrote:
> --- /dev/null
> +++ b/arch/powerpc/kernel/dma-mapping.c
Can we please give this a more descriptive name? MIPS names the
equivalent dma-noncoherent.c which makes a lot of sense to me.
> +#include <linux/module.h>
> +#include <linux/signal.h>
> +#include <linux/sched.h>
> +#include <linux/kernel.h>
> +#include <linux/errno.h>
> +#include <linux/string.h>
> +#include <linux/types.h>
> +#include <linux/ptrace.h>
> +#include <linux/mman.h>
> +#include <linux/mm.h>
> +#include <linux/swap.h>
> +#include <linux/stddef.h>
> +#include <linux/vmalloc.h>
> +#include <linux/init.h>
> +#include <linux/delay.h>
> +#include <linux/bootmem.h>
> +#include <linux/highmem.h>
> +#include <linux/dma-mapping.h>
> +#include <linux/hardirq.h>
> +
> +#include <asm/pgalloc.h>
> +#include <asm/prom.h>
> +#include <asm/io.h>
> +#include <asm/mmu_context.h>
> +#include <asm/pgtable.h>
> +#include <asm/mmu.h>
> +#include <asm/uaccess.h>
> +#include <asm/smp.h>
> +#include <asm/machdep.h>
Do you really need all these headers?
> +int map_page(unsigned long va, phys_addr_t pa, int flags);
this one doesn't seem to be used ever. And even if it was a non-static
forward-declaration in a .c is not something we'd want.
> +/*
> + * VM region handling support.
> + *
> + * This should become something generic, handling VM region allocations for
> + * vmalloc and similar (ioremap, module space, etc).
> + *
> + * I envisage vmalloc()'s supporting vm_struct becoming:
> + *
> + * struct vm_struct {
> + * struct vm_region region;
> + * unsigned long flags;
> + * struct page **pages;
> + * unsigned int nr_pages;
> + * unsigned long phys_addr;
> + * };
> + *
> + * get_vm_area() would then call vm_region_alloc with an appropriate
> + * struct vm_region head (eg):
> + *
> + * struct vm_region vmalloc_head = {
> + * .vm_list = LIST_HEAD_INIT(vmalloc_head.vm_list),
> + * .vm_start = VMALLOC_START,
> + * .vm_end = VMALLOC_END,
> + * };
> + *
> + * However, vmalloc_head.vm_start is variable (typically, it is dependent on
> + * the amount of RAM found at boot time.) I would imagine that get_vm_area()
> + * would have to initialise this each time prior to calling vm_region_alloc(
Yeah, I suspect you should do that instead of adding another copy of
a copy of core VM code..
Btw, is there anything ppc-specific in the noncoherent dma code?
It might be a good idea to put it into lib/ otherwise, I'll contribute
a dma-coherent.c for simple architectures for there aswell..
> --- a/arch/powerpc/mm/fault.c
> +++ b/arch/powerpc/mm/fault.c
> @@ -447,3 +447,102 @@ void bad_page_fault(struct pt_regs *regs
>
> die("Kernel access of bad area", regs, sig);
> }
> +
> +#ifdef CONFIG_8xx
> +
Can we put this functions into a separate file instea of an
ifdefed section
> +/* The pgtable.h claims some functions generically exist, but I
> + * can't find them......
> + */
> +pte_t *va_to_pte(unsigned long address)
> +{
> + pgd_t *dir;
> + pmd_t *pmd;
> + pte_t *pte;
> +
> + if (address < TASK_SIZE)
> + return NULL;
> +
> + dir = pgd_offset(&init_mm, address);
> + if (dir) {
> + pmd = pmd_offset(dir, address & PAGE_MASK);
> + if (pmd && pmd_present(*pmd)) {
> + pte = pte_offset_kernel(pmd, address & PAGE_MASK);
> + if (pte && pte_present(*pte))
> + return(pte);
> + }
> + }
> + return NULL;
> +}
But wha do you need this for anyway? It's not used anywhere currently,
and it's not 8xx-specific at all?
> +unsigned long va_to_phys(unsigned long address)
> +{
> + pte_t *pte;
> +
> + pte = va_to_pte(address);
> + if (pte)
> + return(((unsigned long)(pte_val(*pte)) & PAGE_MASK) | (address & ~(PAGE_MASK)));
> + return (0);
> +}
Shouldn't you use virt_to_phys instead?
Also for the last two I'd prefer if you'd find a way to avoid adding
them.
next prev parent reply other threads:[~2006-11-15 18:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061114012504.17455.13833.stgit@localhost.localdomain>
2006-11-14 1:28 ` [PATCH 1/5] [POWERPC] 8xx: platform-specific mmu updates Vitaly Bordug
2006-11-14 1:28 ` [PATCH 2/5] [POWERPC] 8xx: generic 8xx code arch/powerpc port Vitaly Bordug
2006-11-15 18:23 ` Christoph Hellwig [this message]
2006-11-15 23:36 ` Vitaly Bordug
2006-11-16 22:48 ` Benjamin Herrenschmidt
2006-11-17 6:49 ` Christoph Hellwig
2006-11-17 8:00 ` Christoph Hellwig
2006-11-18 1:24 ` Dan Malek
2006-11-20 10:24 ` Christoph Hellwig
2006-11-21 0:26 ` Dan Malek
2006-11-14 1:28 ` [PATCH 3/5] [POWERPC] 8xx: platform-related changes to the fsl_soc.c Vitaly Bordug
2006-11-14 2:21 ` Benjamin Herrenschmidt
2006-11-14 12:48 ` Vitaly Bordug
2006-11-14 1:28 ` [PATCH 4/5] [POWERPC] 8xx: powerpc port of core CPM, CPM PIC, etc Vitaly Bordug
2006-11-14 2:44 ` Benjamin Herrenschmidt
2006-11-14 1:28 ` [PATCH 5/5] [POWERPC] 8xx: Add mpc885ads support and common mpc8xx Vitaly Bordug
2006-11-14 2:47 ` Benjamin Herrenschmidt
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=20061115182316.GA20719@lst.de \
--to=hch@lst.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=vbordug@ru.mvista.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).