All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Picco <bpicco@meloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc64 - strict devmem
Date: Wed, 05 Mar 2014 13:11:08 +0000	[thread overview]
Message-ID: <20140305131108.GZ29427@zareason> (raw)
In-Reply-To: <1393866035-7939-1-git-send-email-bpicco@meloft.net>

Hi,
David Miller wrote:	[Tue Mar 04 2014, 03:46:26PM EST]
> From: Bob Picco <bpicco@meloft.net>
> Date: Mon,  3 Mar 2014 12:00:35 -0500
> 
> > From: bob picco <bpicco@meloft.net>
> > 
> > This patch adds support to enable STRICT_DEVMEM for sparc64. By selecting the
> > new config option you enable this feature.
> > 
> > CC: Sam Ravnborg <sam@ravnborg.org>
> > Signed-off-by: Bob Picco <bob.picco@oracle.com>
> 
> Ok, I looked more deeply into this and I'm going to rescind my request
> to use kern_addr_valid().
Okay.
> 
> This devmem_is_allowed() seems to also want to allow non-RAM MMIO
> accesses too.
Yes, this is my bad. I expected this issue to come up in the first round but
forgot. I wasn't certain general MMIO access via /dev/mem is of value to
sparc64. One could always turn off the config option.
> 
> So using the iomem resource is probably the way to go.
> 
> Two things:
> 
> 1) We have to make sure caching will be disabled and the side-effect
>    bit will be set in accesses to non-RAM pages.
> 
> 2) Our implementation of devmem_is_allowed() should be aligned as
>    much as possible with other implementations.  Perhaps powerpc
>    is the best example to use.
I'll take a peek at powerpc.

thanx and you're welcome,

bob
> 
> Thanks.
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe sparclinux" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-03-05 13:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 17:00 [PATCH] sparc64 - strict devmem Bob Picco
2014-03-04 20:46 ` David Miller
2014-03-05 13:11 ` Bob Picco [this message]
2014-03-05 20:18 ` Bob Picco

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=20140305131108.GZ29427@zareason \
    --to=bpicco@meloft.net \
    --cc=sparclinux@vger.kernel.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.