From: Stephane Eranian <eranian@hpl.hp.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 8/18] 2.6.17.9 perfmon2 patch for review: event sets and multiplexing support
Date: Wed, 6 Sep 2006 07:50:31 -0700 [thread overview]
Message-ID: <20060906145031.GE13962@frankl.hpl.hp.com> (raw)
In-Reply-To: <20060823155148.a2945c4e.akpm@osdl.org>
Andrew,
On Wed, Aug 23, 2006 at 03:51:48PM -0700, Andrew Morton wrote:
> >
> > +struct pfm_event_set *pfm_find_set(struct pfm_context *ctx, u16 set_id,
> > + int alloc)
> > +{
> > + kmem_cache_t *cachep;
> > + struct pfm_event_set *set, *new_set, *prev;
> > + unsigned long offs;
> > + size_t view_size;
> > + void *view;
> > +
> > + PFM_DBG("looking for set=%u", set_id);
> > +
> > + /*
> > + * shortcut for set 0: always exist, cannot be removed
> > + */
> > + if (set_id == 0 && !alloc)
> > + return list_entry(ctx->list.next, struct pfm_event_set, list);
> > +
> > + prev = NULL;
> > + list_for_each_entry(set, &ctx->list, list) {
> > + if (set->id == set_id)
> > + return set;
> > + if (set->id > set_id)
> > + break;
> > + prev = set;
> > + }
> > +
> > + if (!alloc)
> > + return NULL;
> > +
> > + cachep = ctx->flags.mapset ? pfm_set_cachep : pfm_lg_set_cachep;
> > +
> > + new_set = kmem_cache_alloc(cachep, SLAB_ATOMIC);
>
> SLAB_ATOMIC is unreliable. Is it possible to use SLAB_KERNEL here? If
> coms ecallers can sleep and others cannot then passing in the gfp_flags
> would permit improvement here.
>
I made some changes and now I know I execute this part of the function
with interrupts disabled, holding only the perfmon context lock. I assume
SLAB_KERNEL means, we can sleep. I think I can make this change safely.
>
> > + if (ctx->flags.mapset) {
> > + view_size = PAGE_ALIGN(sizeof(struct pfm_set_view));
> > + view = vmalloc(view_size);
>
> vmalloc() sleeps, so this _could_ have used SLAB_ATOMIC.
>
I am not sure I follow you here. Are you talking about eh kmem_cache_alloc()
above?
> > +static struct page *pfm_view_map_pagefault(struct vm_area_struct *vma,
> > + unsigned long address, int *type)
> > +{
> > + void *kaddr;
> > + struct page *page;
> > +
> > + kaddr = vma->vm_private_data;
> > + if (kaddr == NULL) {
> > + PFM_DBG("no view");
> > + return NOPAGE_SIGBUS;
> > + }
> > +
> > + if ( (address < (unsigned long) vma->vm_start) ||
> > + (address > (unsigned long) (vma->vm_start + PAGE_SIZE)) )
>
> Should that be >=?
Yes.
Thanks.
--
-Stephane
next prev parent reply other threads:[~2006-09-06 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 8:05 Stephane Eranian
2006-08-23 22:51 ` Andrew Morton
2006-09-06 14:50 ` Stephane Eranian [this message]
2006-09-07 2:21 ` Andrew Morton
2006-09-08 6:26 ` Stephane Eranian
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=20060906145031.GE13962@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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®