[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071213.163505.14070110.davem@davemloft.net>
Date: Thu, 13 Dec 2007 16:35:05 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: gregkh@...e.de
Cc: venkatesh.pallipadi@...el.com, ak@....de, ebiederm@...ssion.com,
rdreier@...co.com, torvalds@...ux-foundation.org,
airlied@...net.ie, davej@...hat.com, mingo@...e.hu,
tglx@...utronix.de, hpa@...or.com, akpm@...ux-foundation.org,
arjan@...radead.org, jesse.barnes@...el.com,
linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com
Subject: Re: [RFC PATCH 08/12] PAT 64b: coherent mmap and sysfs bin ioctl
From: Greg KH <gregkh@...e.de>
Date: Thu, 13 Dec 2007 16:19:32 -0800
> On Thu, Dec 13, 2007 at 03:55:51PM -0800, venkatesh.pallipadi@...el.com wrote:
> > Forward port of coherent-mmap.patch and sysfs-bin-ioctl.patch to x86 tree.
> >
> > TBD: Do we need the ioctl interface to sysfs or get the type attribute
> > through a different sysfs file. And then actually specify the attribute
> > while doing pci_mmap_page_range ;-)
>
> Woah! No, no ioctls on sysfs files, sorry. Not going to happen, do
> this on a /dev file if you want to have ioctls...
Well since we told people to move over to sysfs for PCI
accesses, and that's where mmap() is done via too,
it should be no surprise that we run into problems when
people want to set attributes for the mmap() as was done
for the procfs case.
So you have two choices:
1) Balk on the sysfs pci usage, and erase years of effort
of moving people over to sysfs. Tell them to go back to
procfs so we can add the attribute setting via ioctl()
which is absolutely needed.
2) Relax your restrictions a little bit and allow ioctl()'s
for limited cases, like this one.
Otherwise, propase a way to specify PCI device mmap attributes
which works within your whole-universe sysfs theory of everything
:-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists