Re: [PATCH][1/6] perfctr-2.7.3 for 2.6.7-rc1-mm1: core

[Andrew Morton]

Mikael Pettersson <mikpe@xxxxxxxxx> wrote:
>
> Andrew Morton writes:
>  > Random points:
>  > 
>  > 
>  > - In __vperfctr_set_cpus_allowed(), is it possible for a process to
>  >   generate that printk deliberately, thus spamming the logs?
> 
> On a HT P4, yes that's possible. Should I put in a rate limit?

Spose so - __printk_ratelimit().  Or simply turn the message off until the
next reboot.

>  > - perfctr_set_cpus_allowed() does task_lock().  Should that be
>  >   vperfctr_task_lock() instead?
> 
> vperfctr_task_lock() _is_ task_lock() when HT P4s are possible.

I know.  I was asking whether that could should have used the macro rather
than open-coding the task_lock().  Whatever.

>  >   Please update the locking comment over task_lock() to represent this
>  >   new usage.
> 
> You mean add a comment there to the effect that set_cpus_allowed()
> may do a task_lock()?

That comment describes what data structures are protected by task_lock(). 
If you're aware of missing info or if you're protecting new data via
task_lock(), please update the comment.

>  > - Why does sys_vperfctr_open() call ptrace_check_attach()?  (I suspect
>  >   I'd know that if there was API documentation?)
> 
> In the remote-control case, we must check that the opening process
> has the right to control the target process. I'm using the same
> rules as ptrace(ATTACH) does, hence the ptrace_check_attach() call.

OK.  The term "remote control" has not been defined by you, so I'm to
assume that it refers to one process initiating perfctr instrumentation
against another, in some fashion.  Please feel my minor frustration ;)

>  >   These big structures should be dynamically allocated.
> 
> There's room for a temp copy in the perfctr state object, which as
> you've noticed is an entire page. That should reduce stack usage.

hm, not sure I understand that, but whatever.  Please fix up the big stack
users, especially those which do copy_*_user, or non-atomic memory
allocations.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/