mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: zaitcev@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: virt_to_page(pci_alloc_consistent())
Date: Thu, 03 Oct 2002 10:11:37 -0700 (PDT)	[thread overview]
Message-ID: <20021003.101137.56158798.davem@redhat.com> (raw)
In-Reply-To: <20021003122509.B8147@devserv.devel.redhat.com>

   From: Pete Zaitcev <zaitcev@redhat.com>
   Date: Thu, 3 Oct 2002 12:25:10 -0400

   > Date: Thu, 03 Oct 2002 01:03:44 -0700 (PDT)
   > From: "David S. Miller" <davem@redhat.com>
   
   > I think we MUST allow architectures to do what SPARC and ARM
   > do, there is simply no other way to change the page protections
   > easily for these kinds of systems.
   
   I can fix sparc, dunno about others. Do you have a problem
   on sparc64? Are you using a huge page to map the kernel?

ARM I believe does not have luxury you have.

See, some processors are like MIPS and something sort of
KSEG0 is used for PAGE_OFFSET mapping of physical pages.
So pages with page protections changes must live in some other
area of the kernel address space just like vmalloc() to get
the different protection bits.

I really would like sun4m to use big pages for the PAGE_OFFSET
mappings when possible Peter.  So I even don't think fixing Sparc
the way I know you are likely to is wise.


      reply	other threads:[~2002-10-03 17:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03  6:38 virt_to_page(pci_alloc_consistent()) Pete Zaitcev
2002-10-03  8:03 ` virt_to_page(pci_alloc_consistent()) David S. Miller
2002-10-03 16:25   ` virt_to_page(pci_alloc_consistent()) Pete Zaitcev
2002-10-03 17:11     ` David S. Miller [this message]

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=20021003.101137.56158798.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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

all inboxes | Powered by JetHome®