Mike Frysinger wrote:
> On Wednesday 20 June 2007, H. Peter Anvin wrote:
>> Andi Kleen wrote:
asm-i386/msr.h should not be exported to userspace at all, it contains
nothing but kernel-internal helpers.
>>> Actually rdtsc and rdtscll and potentially rdpmc which is in there can be
>>> very
On Wednesday 20 June 2007, H. Peter Anvin wrote:
> Andi Kleen wrote:
> >> asm-i386/msr.h should not be exported to userspace at all, it contains
> >> nothing but kernel-internal helpers.
> >
> > Actually rdtsc and rdtscll and potentially rdpmc which is in there can be
> > very useful in user space
On Wednesday 20 June 2007, H. Peter Anvin wrote:
Andi Kleen wrote:
asm-i386/msr.h should not be exported to userspace at all, it contains
nothing but kernel-internal helpers.
Actually rdtsc and rdtscll and potentially rdpmc which is in there can be
very useful in user space if you know
Mike Frysinger wrote:
On Wednesday 20 June 2007, H. Peter Anvin wrote:
Andi Kleen wrote:
asm-i386/msr.h should not be exported to userspace at all, it contains
nothing but kernel-internal helpers.
Actually rdtsc and rdtscll and potentially rdpmc which is in there can be
very useful in user
Andi Kleen wrote:
>> asm-i386/msr.h should not be exported to userspace at all, it contains
>> nothing but kernel-internal helpers.
>
> Actually rdtsc and rdtscll and potentially rdpmc which is in there can be
> very
> useful in user space if you know what you're doing. Unfortunately a lot of
Andi Kleen wrote:
asm-i386/msr.h should not be exported to userspace at all, it contains
nothing but kernel-internal helpers.
Actually rdtsc and rdtscll and potentially rdpmc which is in there can be
very
useful in user space if you know what you're doing. Unfortunately a lot of
its
> asm-i386/msr.h should not be exported to userspace at all, it contains
> nothing but kernel-internal helpers.
Actually rdtsc and rdtscll and potentially rdpmc which is in there can be very
useful in user space if you know what you're doing. Unfortunately a lot of its
users don't,
but not
On Mon, Jun 18, 2007 at 10:02:21AM -0400, Mike Frysinger wrote:
> > This is wrong for two reasons:
> >
> > - MSRs are not accessible in user space.
> > - .section .fixup is not applicable to user space.
> >
> > Anything MSR-related should be protected by __KERNEL__ instead.
> >
> > This NAK
On Monday 18 June 2007, H. Peter Anvin wrote:
> Mike Frysinger wrote:
> > Most of the macros in msr.h already use __asm__ and __volatile__, this
> > patch brings the rest into line. This is needed since these get exported
> > into userspace (need to use strict __asm__ vs asm when gcc compiles
Mike Frysinger wrote:
> Most of the macros in msr.h already use __asm__ and __volatile__, this patch
> brings the rest into line. This is needed since these get exported into
> userspace (need to use strict __asm__ vs asm when gcc compiles with GNU
> extensions turned off).
> ---
> diff --git
Most of the macros in msr.h already use __asm__ and __volatile__, this patch
brings the rest into line. This is needed since these get exported into
userspace (need to use strict __asm__ vs asm when gcc compiles with GNU
extensions turned off).
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
Most of the macros in msr.h already use __asm__ and __volatile__, this patch
brings the rest into line. This is needed since these get exported into
userspace (need to use strict __asm__ vs asm when gcc compiles with GNU
extensions turned off).
Signed-off-by: Mike Frysinger [EMAIL PROTECTED]
---
Mike Frysinger wrote:
Most of the macros in msr.h already use __asm__ and __volatile__, this patch
brings the rest into line. This is needed since these get exported into
userspace (need to use strict __asm__ vs asm when gcc compiles with GNU
extensions turned off).
---
diff --git
On Monday 18 June 2007, H. Peter Anvin wrote:
Mike Frysinger wrote:
Most of the macros in msr.h already use __asm__ and __volatile__, this
patch brings the rest into line. This is needed since these get exported
into userspace (need to use strict __asm__ vs asm when gcc compiles with
GNU
On Mon, Jun 18, 2007 at 10:02:21AM -0400, Mike Frysinger wrote:
This is wrong for two reasons:
- MSRs are not accessible in user space.
- .section .fixup is not applicable to user space.
Anything MSR-related should be protected by __KERNEL__ instead.
This NAK doesn't apply to
asm-i386/msr.h should not be exported to userspace at all, it contains
nothing but kernel-internal helpers.
Actually rdtsc and rdtscll and potentially rdpmc which is in there can be very
useful in user space if you know what you're doing. Unfortunately a lot of its
users don't,
but not
16 matches
Mail list logo
