All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, "Hans J. Koch" <hjk@hansjkoch.de>,
	Kai Jiang <Kai.Jiang@freescale.com>,
	gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio: Support 36-bit physical addresses on 32-bit systems
Date: Wed, 12 Oct 2011 18:16:35 +0200	[thread overview]
Message-ID: <20111012161635.GD21852@local> (raw)
In-Reply-To: <AD39F4F8-E9C0-4090-9AEA-644F82DD328B@kernel.crashing.org>

On Wed, Oct 12, 2011 at 11:07:09AM -0500, Kumar Gala wrote:
> 
> On Oct 12, 2011, at 10:32 AM, Hans J. Koch wrote:
> 
> > On Wed, Oct 12, 2011 at 09:35:45AM -0500, Kumar Gala wrote:
> >> From: Kai Jiang <Kai.Jiang@freescale.com>
> >> 
> >> To support >32-bit physical addresses for UIO_MEM_PHYS type we need to
> >> extend the width of 'addr' in struct uio_mem.  Numerous platforms like
> >> embedded PPC, ARM, and X86 have support for systems with larger physical
> >> address than logical.
> >> 
> >> Since 'addr' may contain a physical, logical, or virtual address the
> >> easiest solution is to just change the type to 'unsigned long long'
> >> regardless of which type is utilized.
> > 
> > No. There's phys_addr_t for that purpose, defined in include/linux/types.h.
> > Please use that.
> 
> Do we believe phys_addr_t is always greater than or equal to size need for logical & virtual addresses?

Yes.

Hans

WARNING: multiple messages have this Message-ID (diff)
From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
	gregkh@suse.de, linuxppc-dev@ozlabs.org,
	linux-kernel@vger.kernel.org, Kai Jiang <Kai.Jiang@freescale.com>
Subject: Re: [PATCH] uio: Support 36-bit physical addresses on 32-bit systems
Date: Wed, 12 Oct 2011 18:16:35 +0200	[thread overview]
Message-ID: <20111012161635.GD21852@local> (raw)
In-Reply-To: <AD39F4F8-E9C0-4090-9AEA-644F82DD328B@kernel.crashing.org>

On Wed, Oct 12, 2011 at 11:07:09AM -0500, Kumar Gala wrote:
> 
> On Oct 12, 2011, at 10:32 AM, Hans J. Koch wrote:
> 
> > On Wed, Oct 12, 2011 at 09:35:45AM -0500, Kumar Gala wrote:
> >> From: Kai Jiang <Kai.Jiang@freescale.com>
> >> 
> >> To support >32-bit physical addresses for UIO_MEM_PHYS type we need to
> >> extend the width of 'addr' in struct uio_mem.  Numerous platforms like
> >> embedded PPC, ARM, and X86 have support for systems with larger physical
> >> address than logical.
> >> 
> >> Since 'addr' may contain a physical, logical, or virtual address the
> >> easiest solution is to just change the type to 'unsigned long long'
> >> regardless of which type is utilized.
> > 
> > No. There's phys_addr_t for that purpose, defined in include/linux/types.h.
> > Please use that.
> 
> Do we believe phys_addr_t is always greater than or equal to size need for logical & virtual addresses?

Yes.

Hans

  parent reply	other threads:[~2011-10-12 16:16 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 14:35 [PATCH] uio: Support 36-bit physical addresses on 32-bit systems Kumar Gala
2011-10-12 14:35 ` Kumar Gala
2011-10-12 15:32 ` Hans J. Koch
2011-10-12 15:32   ` Hans J. Koch
2011-10-12 16:07   ` Kumar Gala
2011-10-12 16:07     ` Kumar Gala
2011-10-12 16:15     ` Geert Uytterhoeven
2011-10-12 16:15       ` Geert Uytterhoeven
2011-10-13 14:10       ` Tabi Timur-B04825
2011-10-13 14:10         ` Tabi Timur-B04825
2011-10-13 14:25         ` Geert Uytterhoeven
2011-10-13 14:25           ` Geert Uytterhoeven
2011-10-13 14:35           ` Timur Tabi
2011-10-13 14:35             ` Timur Tabi
2011-10-12 16:16     ` Hans J. Koch [this message]
2011-10-12 16:16       ` Hans J. Koch
2011-10-12 16:19   ` Hans J. Koch
2011-10-12 16:19     ` Hans J. Koch
2011-10-12 18:40     ` Kumar Gala
2011-10-12 18:40       ` Kumar Gala
2011-10-12 20:23       ` Hans J. Koch
2011-10-12 20:23         ` Hans J. Koch
2011-10-12 20:58         ` Kumar Gala
2011-10-12 20:58           ` Kumar Gala
  -- strict thread matches above, loose matches on Subject: below --
2011-10-13 15:50 Kumar Gala
2011-10-13 15:50 ` Kumar Gala
2011-10-14 18:31 ` Hans J. Koch
2011-10-14 18:31   ` Hans J. Koch
2011-10-14 18:36   ` Greg KH
2011-10-14 18:36     ` Greg KH
2011-10-14 18:46     ` Hans J. Koch
2011-10-14 18:46       ` Hans J. Koch
2011-10-17 16:00   ` Kumar Gala
2011-10-17 16:00     ` Kumar Gala
2011-10-17 17:18     ` Hans J. Koch
2011-10-17 17:18       ` Hans J. Koch
2011-10-17 18:03       ` Hans J. Koch
2011-10-17 18:03         ` Hans J. Koch
2011-10-17 18:23         ` Greg KH
2011-10-17 18:23           ` Greg KH
2011-10-17 18:50           ` Hans J. Koch
2011-10-17 18:50             ` Hans J. Koch

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=20111012161635.GD21852@local \
    --to=hjk@hansjkoch.de \
    --cc=Kai.Jiang@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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 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.