All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>
Cc: xen-devel@lists.xensource.com, sos22@cam.ac.uk,
	xen-ia64-devel@lists.xensource.com
Subject: RE: [Xen-ia64-devel] cset 8690 blk driver regression
Date: Tue, 31 Jan 2006 16:08:46 -0700	[thread overview]
Message-ID: <1138748926.13596.132.camel@localhost> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD5980932@cacexc12.americas.cpqcorp.net>

On Tue, 2006-01-31 at 14:48 -0800, Magenheimer, Dan (HP Labs Fort
Collins) wrote:
> These were two separate bugs.  Backing out
> (or otherwise rewriting) that patch is still
> necessary for domU to boot on ia64.
> 
> A gnttab_shared_gpfn macro sounds good to me!
> (assuming defined to the pre-patch lines for
> ia64 and the post-patch lines for x86?)

   The easiest thing would be making __mfn_to_gpfn() be a pass through
like below.  It works for now, but I don't know what I'm breaking by
doing this.  Thanks,

	Alex

diff -r 9ef5f0ec9df8 xen/include/asm-ia64/mm.h
--- a/xen/include/asm-ia64/mm.h Tue Jan 31 17:39:35 2006
+++ b/xen/include/asm-ia64/mm.h Tue Jan 31 10:07:45 2006
@@ -422,8 +422,7 @@
 * here. However if it's allocated by HV, we should access it directly
 */
 
-#define __mfn_to_gpfn(_d, mfn)                 \
-    machine_to_phys_mapping[(mfn)]
+#define __mfn_to_gpfn(_d, mfn)  (mfn)
 
 #define __gpfn_to_mfn(_d, gpfn)                        \
     __gpfn_to_mfn_foreign((_d), (gpfn))


-- 
Alex Williamson                             HP Linux & Open Source Lab

  reply	other threads:[~2006-01-31 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31 22:48 [Xen-ia64-devel] cset 8690 blk driver regression Magenheimer, Dan (HP Labs Fort Collins)
2006-01-31 23:08 ` Alex Williamson [this message]
2006-01-31 23:39   ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2006-01-31 20:11 Magenheimer, Dan (HP Labs Fort Collins)

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=1138748926.13596.132.camel@localhost \
    --to=alex.williamson@hp.com \
    --cc=dan.magenheimer@hp.com \
    --cc=sos22@cam.ac.uk \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.