linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: torvalds@transmeta.com, andrea@suse.de, alan@lxorguk.ukuu.org.uk,
	sct@redhat.com, Gerhard.Wichert@pdb.siemens.de,
	Winfried.Gerhard@pdb.siemens.de, linux-kernel@vger.rutgers.edu,
	linux-mm@kvack.org
Subject: Re: [bigmem-patch] 4GB with Linux on IA32
Date: Tue, 17 Aug 1999 12:46:35 +0100 (BST)	[thread overview]
Message-ID: <E11GhhN-0004Rx-00@the-village.bc.nu> (raw)
In-Reply-To: <199908170650.XAA95856@google.engr.sgi.com> from "Kanoj Sarcar" at Aug 16, 99 11:50:42 pm

> I will give you one example of the type of cases that I am talking about.
> In drivers/char/bttv.c, VIDIOCSFBUF ioctl seems to be setting the "vidadr"
> to a kernel virtual address from the physical address present in the 
> user's pte. This will not work for bigmem pages.

Oh now I understand Linus rather bizarre message

VIDIOCSFBUF takes a physical base address. The &1 stuff thats i nthere is 
a debug hook that never got taken out. You can ignore the &1 case in that
ioctl or just remove it.

Alan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

  parent reply	other threads:[~1999-08-17 11:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-16 16:29 Andrea Arcangeli
1999-08-16 16:48 ` Matthew Wilcox
1999-08-16 17:19   ` Andrea Arcangeli
1999-08-16 18:43 ` Kanoj Sarcar
1999-08-16 19:43   ` Alan Cox
1999-08-16 20:54     ` Andrea Arcangeli
1999-08-16 22:47       ` Andrea Arcangeli
1999-08-16 23:26         ` Andrea Arcangeli
1999-08-16 23:39           ` Kanoj Sarcar
1999-08-17  0:10             ` Andrea Arcangeli
1999-08-17  6:37               ` Kanoj Sarcar
1999-08-17  6:41                 ` Linus Torvalds
1999-08-17  6:50                   ` Kanoj Sarcar
1999-08-17  7:03                     ` Linus Torvalds
1999-08-17  7:23                       ` Linus Torvalds
1999-08-17 11:39                         ` Alan Cox
1999-08-26 16:27                           ` Andrea Arcangeli
1999-08-17 11:46                     ` Alan Cox [this message]
1999-08-17 14:26             ` Andrea Arcangeli
1999-08-17  6:39           ` Linus Torvalds
1999-08-17 12:40             ` Andrea Arcangeli
1999-08-17  6:29         ` Linus Torvalds
1999-08-17 12:37           ` Andrea Arcangeli
1999-08-17 14:04             ` Andrea Arcangeli
1999-08-17  8:52         ` Jakub Jelinek
1999-08-17  9:13         ` Pavel Machek
1999-08-18 14:08           ` Andrea Arcangeli
1999-08-19 12:20             ` Andrea Arcangeli
1999-08-16 23:28       ` Kanoj Sarcar
1999-08-16 23:49         ` Andrea Arcangeli
1999-08-17  6:29         ` David S. Miller
1999-08-17 12:38           ` Andrea Arcangeli
1999-08-17  0:17       ` Andrea Arcangeli
1999-08-19 13:33         ` Thierry Vignaud
1999-08-19 16:49           ` Stephen C. Tweedie
1999-08-20  7:35             ` Thierry Vignaud
1999-08-20  9:55               ` Alan Cox
1999-08-20 18:25               ` Linus Torvalds
1999-08-16 20:34   ` Andrea Arcangeli

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=E11GhhN-0004Rx-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=Gerhard.Wichert@pdb.siemens.de \
    --cc=Winfried.Gerhard@pdb.siemens.de \
    --cc=andrea@suse.de \
    --cc=kanoj@google.engr.sgi.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=sct@redhat.com \
    --cc=torvalds@transmeta.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