mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Richard Henderson <rth@twiddle.net>,
	Jay Estabrook <jay.estabrook@hp.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] alpha: pci sysfs resources
Date: Wed, 18 Feb 2009 11:56:50 -0800	[thread overview]
Message-ID: <200902181156.50547.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20090217104653.GA25856@jurassic.park.msu.ru>

On Tuesday, February 17, 2009 2:46 am Ivan Kokshaysky wrote:
> This closes http://bugzilla.kernel.org/show_bug.cgi?id=10893
> which is a showstopper for X development on alpha.
>
> The generic HAVE_PCI_MMAP code (drivers/pci-sysfs.c) is not
> very useful since we have to deal with three different types
> of MMIO address spaces: sparse and dense mappings for old
> ev4/ev5 machines and "normal" 1:1 MMIO space (bwx) for ev56 and
> later.
> Also "write combine" mappings are meaningless on alpha - roughly
> speaking, alpha does write combining, IO reordering and other
> optimizations by default, unless user splits IO accesses
> with memory barriers.
>
> I think the cleanest way to deal with resource files on alpha
> is to convert the default no-op pci_create_resource_files() and
> pci_remove_resource_files() for !HAVE_PCI_MMAP case into __weak
> functions and override them with alpha specific ones.
>
> Another alpha hook is needed for "legacy_" resource files
> to handle sparse addressing (pci_adjust_legacy_attr).
>
> With the "standard" resourceN files on ev56/ev6 libpciaccess
> works "out of the box". Handling of resourceN_sparse/resourceN_dense
> files on older machines obviously requires some userland work.
>
> Sparse/dense stuff has been tested on sx164 (pca56/pyxis, normally
> uses bwx IO) with the kernel hacked into "cia compatible" mode.

Excellent, thanks Ivan.  I've applied this one to my linux-next branch.  
Should make userspace stuff on the ev56/6 machines that much easier.

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2009-02-18 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 10:46 Ivan Kokshaysky
2009-02-18 19:56 ` Jesse Barnes [this message]

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=200902181156.50547.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=akpm@linux-foundation.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jay.estabrook@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rth@twiddle.net \
    /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®