From: Kumar Gala <galak@kernel.crashing.org>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: "hjk@hansjkoch.de" <hjk@hansjkoch.de>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"gregkh@suse.de" <gregkh@suse.de>,
Jiang Kai-B18973 <B18973@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][v2] uio: Support 36-bit physical addresses on 32-bit systems
Date: Thu, 13 Oct 2011 10:32:51 -0500 [thread overview]
Message-ID: <9BD33578-CD8E-4784-AC6A-ADE4614E0FC1@kernel.crashing.org> (raw)
In-Reply-To: <CAOZdJXWd_u_EWXNhh3-t258+Y8mx=JuJhU93CeZfaocPZvhOFA@mail.gmail.com>
On Oct 13, 2011, at 9:37 AM, Tabi Timur-B04825 wrote:
> On Wed, Oct 12, 2011 at 3:57 PM, Kumar Gala <galak@kernel.crashing.org> 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.
>
> You forgot to update this description.
will fix and update commit message
>
>> struct uio_mem {
>> const char *name;
>> - unsigned long addr;
>> + phys_addr_t addr;
>
> Please add a comment here saying:
>
> 1) That 'addr' can be a virtual or physical address
The code and everything else makes that clear
> 2) That the kernel guarantees that sizeof(phys_addr_t) >= sizeof(void
> *), so it's safe to use phys_addr_t for a virtual pointer.
The commit message will cover that so I don't plan on add it.
- k
next prev parent reply other threads:[~2011-10-13 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 20:57 Kumar Gala
2011-10-13 14:37 ` Tabi Timur-B04825
2011-10-13 15:32 ` Kumar Gala [this message]
2011-10-13 15:34 ` Timur Tabi
2011-10-13 15:37 ` David Laight
2011-10-13 15:41 ` Timur Tabi
2011-10-13 15:50 ` Kumar Gala
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=9BD33578-CD8E-4784-AC6A-ADE4614E0FC1@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=B04825@freescale.com \
--cc=B18973@freescale.com \
--cc=gregkh@suse.de \
--cc=hjk@hansjkoch.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®