The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Rik van Riel <riel@redhat.com>,
	Jesse Barnes <jbarnes@engr.sgi.com>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	linux-kernel@vger.kernel.org, akpm@osdl.org, kurt@garloff.de,
	Ian.Pratt@cl.cam.ac.uk, Christian.Limpach@cl.cam.ac.uk
Subject: Re: [PATCH] Xen/i386 cleanups - AGP bus/phys cleanups
Date: Wed, 16 Mar 2005 17:05:38 -0800	[thread overview]
Message-ID: <4238D7E2.2060002@tupshin.com> (raw)
In-Reply-To: <16952.53719.150647.638710@cargo.ozlabs.ibm.com>

Paul Mackerras wrote:

>Rik van Riel writes:
>
>  
>
>>Thing is, the rest of the kernel uses virt_to_phys for
>>two different things.  Only one of them has to do with
>>the real physical address, the other is about getting
>>the page frame number.
>>    
>>
>
>So fix the places that are using virt_to_phys to get the page frame
>number to use virt_to_pfn instead. :)
>
>  
>
>>On native x86, x86-64 and others, the page frame number
>>and physical address are directly related to each other.
>>Under Xen, however, the two are different - and the
>>AGPGART really needs to have the physical address ;)
>>    
>>
>
>If Xen is letting the kernel program the GART, you just lost any
>memory isolation between partitions you might have been trying to
>enforce. :)
>  
>
Since xen only lets the  dom0 (privileged domain) program the GART, all 
of the domU's  (non-privileged domains) are still isolated from each other.

-Tupshin

  reply	other threads:[~2005-03-17  1:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-16 11:48 [PATCH] Xen/i386 cleanups - AGP bus/phys cleanups Keir Fraser
2005-03-16 14:31 ` Christoph Hellwig
2005-03-16 14:58   ` Keir Fraser
2005-03-16 15:01   ` Rik van Riel
2005-03-16 18:10     ` Christoph Hellwig
2005-03-16 18:35       ` Keir Fraser
2005-03-16 18:42         ` Jesse Barnes
2005-03-16 19:08           ` Keir Fraser
2005-03-16 19:06         ` Christoph Hellwig
2005-03-16 19:11           ` Keir Fraser
2005-03-16 17:40   ` Alan Cox
2005-03-16 17:54 ` Jesse Barnes
2005-03-16 21:24 ` Paul Mackerras
2005-03-16 22:06   ` Jesse Barnes
2005-03-16 23:55     ` Rik van Riel
2005-03-17  0:39       ` Paul Mackerras
2005-03-17  1:05         ` Tupshin Harper [this message]
2005-03-17  3:44         ` Rik van Riel
2005-03-17  4:42       ` Christoph Hellwig
2005-03-17  4:58         ` Rik van Riel
2005-03-17  9:16     ` Keir Fraser
2005-03-17  9:34       ` Paul Mackerras
2005-03-17 10:56         ` Keir Fraser
2005-03-19 10:07           ` Eric W. Biederman
2005-03-19 10:56             ` Christian Limpach
2005-03-19 13:01               ` Keir Fraser
2005-03-17 13:53         ` Alan Cox
2005-03-18  0:16           ` Paul Mackerras
2005-03-18  4:23             ` Rik van Riel
2005-03-18  9:05             ` Keir Fraser

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=4238D7E2.2060002@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=Ian.Pratt@cl.cam.ac.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=jbarnes@engr.sgi.com \
    --cc=kurt@garloff.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=riel@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