linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Andi Kleen" <ak@suse.de>
To: virtualization@lists.osdl.org, linux-kernel@vger.kernel.org,
	bunk@stusta.de
Date: Fri, 18 Nov 2005 17:05:07 +0100	[thread overview]
raw)

Sender: ak@brahms.suse.de
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [2.6 patch] mark virt_to_bus/bus_to_virt as __deprecated on i386
References: <20051118014055.GK11494@stusta.de>
From: Andi Kleen <ak@suse.de>
Date: 18 Nov 2005 17:05:07 +0100
In-Reply-To: <20051118014055.GK11494@stusta.de>
Message-ID: <p73lkzmhrgs.fsf@brahms.suse.de>
Lines: 17
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Adrian Bunk <bunk@stusta.de> writes:

> virt_to_bus/bus_to_virt are long deprecated, mark them as __deprecated 
> on i386.

I don't think you can do that. We still need these functions in low 
level architecture code at least.

Using __pa/__va doesn't cut it because it won't work on Xen guests
which have different views on bus vs physical addresses. The Xen
code is (hopefully) in the process of being merged, so intentionally
breaking them isn't a good idea.

So if anything there would need to be replacement functions for it
first that do the same thing. But why not just keep the old ones?

-Andi

             reply	other threads:[~2005-11-20 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18 16:05 Andi Kleen [this message]
2005-11-21 10:06 ` (no subject) Keir Fraser
2005-11-21 10:11   ` Russell King
2005-11-21 17:27   ` Andi Kleen

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=437DFBB3.mailLJC11TKEB@suse.de \
    --to=ak@suse.de \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    /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).