linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: nleeder@codeaurora.org (Neil Leeder)
To: linux-arm-kernel@lists.infradead.org
Subject: accessing vfpinstr macros from outside vfp directory
Date: Tue, 29 Mar 2011 17:04:38 -0400	[thread overview]
Message-ID: <4D924966.2050707@codeaurora.org> (raw)

(Resending: forgot to add Russell to To: list; subject change to avoid it getting lost in 
code review thread, was Re: [PATCH v4 2/3] [ARM] perfevents: Add support for Scorpion 
performance monitors)

Russell,

On 3/16/2011 5:13 AM, Jean Pihet wrote:
 > On Tue, Mar 15, 2011 at 4:58 PM, Sheetal Sahasrabudhe
 > <sheetals@codeaurora.org>  wrote:
 >> Hi Will/Jean,
 >>
 >> On Mon, March 14, 2011 6:35 pm, Bryan Huntsman wrote:
 >>> On 03/09/2011 09:16 AM, Sheetal Sahasrabudhe wrote:
 >>>> This commit adds support for performance monitors provided by
 >>>> Qualcomm Scorpion and ScorpionMP processor to perfevents.
 >>>>
 >>>> Signed-off-by: Sheetal Sahasrabudhe<sheetals@codeaurora.org>
 >>>> Reviewed-by: Jean Pihet<j-pihet@ti.com>
 >>>> Reviewed-by: Will Deacon<will.deacon@arm.com>
 >>>> ---
 >>>>   arch/arm/include/asm/perf_event.h |    2 +
 >>>>   arch/arm/kernel/perf_event.c      |   11 +
 >>>>   arch/arm/kernel/perf_event_msm.c  |  679 +++++++++++++++++++++++++++++++++++++
 >>>>   3 files changed, 692 insertions(+), 0 deletions(-)
 >>>>   create mode 100644 arch/arm/kernel/perf_event_msm.c
 >>>>
 >>>
 >>> ...
 >>>
 >>>> diff --git a/arch/arm/kernel/perf_event_msm.c b/arch/arm/kernel/perf_event_msm.c
 >>>> new file mode 100644
 >>>> index 0000000..4e42f27
 >>>> --- /dev/null
 >>>> +++ b/arch/arm/kernel/perf_event_msm.c
 >> [...]
 >>
 >>>> +#include<asm/vfp.h>
 >>>> +#include<asm/system.h>
 >>>> +#include "../vfp/vfpinstr.h"
 >>>
 >>> Sorry I didn't see this earlier.  Is there another way to get the info
 >>> you need that wouldn't use a relative include path?  If the info from
 >>> vfpinstr.h is now needed outside of the vfp directory, can it be moved
 >>> to a common header instead?  Thanks.
 > Good catch! Sorry I did not catch this one while reviewing the code.
 >
 >>>
 >>> - Bryan
 >>
 >> I see other files under vfp that include this header.
 >> So if we were to implement Bryan's suggestion, I think a separate patch that moves the 
header and updates all the depdendencies would be more appropriate.
 >> Are you okay with the relative include path for vfpinstr.h in this patch for now or 
would you want to see an update to move vfpinstr.h to include/asm?.
 >
 > Adding Russell and Nicolas for the VFP question.
 > Only fmrx and fmxr are used from "../vfp/vfpinstr.h". Can those be
 > moved to arch/arm/include/asm/vfp.h?
 >
 > What is the best solution to this?
 >
 > Regards,
 > Jean
 >

Any opinions on what would be the best thing to do here? Choices appear to be:

1) allow the relative include path of ../vfp/vfpinstr.h
2) move the definitions of fmrx, fmxr from vfp/vfpinstr.h to include/asm/vfp.h
3) move vfp/vfpinstr.h to include/asm
4) other...?

If it helps, I can create a patch for whichever is considered the preferred solution.

Thanks,
Neil (Standing in temporarily for Sheetal while she is on leave of absence)

 >>
 >> Thanks,
 >> Sheetal
 >>

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum

             reply	other threads:[~2011-03-29 21:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 21:04 Neil Leeder [this message]
2011-04-01 17:27 ` accessing vfpinstr macros from outside vfp directory Will Deacon
2011-04-01 21:54   ` Bryan Huntsman
2011-04-03 12:24     ` Will Deacon
2011-04-04 14:16       ` Neil Leeder

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=4D924966.2050707@codeaurora.org \
    --to=nleeder@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).