All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Alex Nixon <alex.nixon@citrix.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/3] Globally defining phys_addr_t
Date: Thu, 11 Sep 2008 01:31:39 -0700	[thread overview]
Message-ID: <48C8D76B.10901@goop.org> (raw)

Hi Ingo,

This is a repost of a little 3-patch series which Andrew has been
carrying in -mm.  It cleans up the definition of phys_addr_t to make it
kernel-wide rather than x86-specific, and fixes up PFN_PHYS() to use it
to avoid address truncation.

We currently have a few workarounds for this problem in the tree, but
Alex found another bug caused by PFN_PHYS(), so it's probably better if
you bring these patches into tip.git for now.

PowerPC also defines a phys_addr_t with the same meaning as x86; the
powerpc arch maintainers are happy with these patches.

The third patch in the series is not necessary to fix any bug, but it
removes the separate definition of resource_size_t to define it in terms
of phys_addr_t.  I include it for competeness.

Thanks,
    J

             reply	other threads:[~2008-09-11  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-11  8:31 Jeremy Fitzhardinge [this message]
2008-09-11  9:53 ` [PATCH 0/3] Globally defining phys_addr_t Ingo Molnar
2008-09-11 10:20   ` Andrew Morton
2008-09-11 11:56     ` Ingo Molnar
2008-09-11 16:08     ` Jeremy Fitzhardinge
2008-09-11 10:03 ` Geert Uytterhoeven
2008-09-11 11:50   ` Ralf Baechle
2008-09-11 11:50     ` [uml-devel] " Ralf Baechle
2008-09-11 16:06   ` Jeremy Fitzhardinge
2008-09-11 16:17     ` Maciej W. Rozycki

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=48C8D76B.10901@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex.nixon@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.