On Thu, 2014-08-14 at 11:51 +0100, Peter Zijlstra wrote:
> On Thu, Aug 14, 2014 at 11:17:48AM +0100, Pawel Moll wrote:
> > Has it managed to hold on to the ground between the cracks then? ;-)
> >
> > (asking because can't see it in your perf/core branch on git.kernel.org)
>
> Damn this patch is c
On Thu, Aug 14, 2014 at 11:17:48AM +0100, Pawel Moll wrote:
> Has it managed to hold on to the ground between the cracks then? ;-)
>
> (asking because can't see it in your perf/core branch on git.kernel.org)
Damn this patch is cursed; I've no idea where it went. Lemme stick it in
perf/urgent, thi
On Mon, 2014-07-07 at 13:43 +0100, Peter Zijlstra wrote:
> On Tue, Jul 01, 2014 at 05:06:00PM +0100, Pawel Moll wrote:
> > On Tue, 2014-06-17 at 13:43 +0100, Pawel Moll wrote:
> > > When running a 32-bit userspace on a 64-bit kernel (eg. i386
> > > application on x86_64 kernel or 32-bit arm userspa
On Tue, Jul 01, 2014 at 05:06:00PM +0100, Pawel Moll wrote:
> On Tue, 2014-06-17 at 13:43 +0100, Pawel Moll wrote:
> > When running a 32-bit userspace on a 64-bit kernel (eg. i386
> > application on x86_64 kernel or 32-bit arm userspace on arm64
> > kernel) some of the perf ioctls must be treated w
On Tue, 2014-06-17 at 13:43 +0100, Pawel Moll wrote:
> When running a 32-bit userspace on a 64-bit kernel (eg. i386
> application on x86_64 kernel or 32-bit arm userspace on arm64
> kernel) some of the perf ioctls must be treated with special
> care, as they have a pointer size encoded in the comma
When running a 32-bit userspace on a 64-bit kernel (eg. i386
application on x86_64 kernel or 32-bit arm userspace on arm64
kernel) some of the perf ioctls must be treated with special
care, as they have a pointer size encoded in the command.
For example, PERF_EVENT_IOC_ID in 32-bit world will be e
6 matches
Mail list logo
