From: David Vrabel <david.vrabel@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel@lists.xensource.com, linux-kernel@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH 2/4] xen/perf: Define .glob for the different hypercalls.
Date: Tue, 3 Jul 2012 17:14:30 +0100 [thread overview]
Message-ID: <4FF31A66.30904@citrix.com> (raw)
In-Reply-To: <1341330038-21686-3-git-send-email-konrad.wilk@oracle.com>
On 03/07/12 16:40, Konrad Rzeszutek Wilk wrote:
> This allows us in perf to have this:
>
> 99.67% [kernel] [k] xen_hypercall_sched_op
> 0.11% [kernel] [k] xen_hypercall_xen_version
>
> instead of the borring ever-encompassing:
>
> 99.13% [kernel] [k] hypercall_page
...
> +ENTRY(xen_hypercall_other)
> + .skip 2272
I can't offhand think of way of doing this, but is there a less fragile
way to do this?
.skip PAGE_SIZE - N * 32 or something ?
David
next prev parent reply other threads:[~2012-07-03 16:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-03 15:40 [PATCH] various Xen fixes for v3.6 (v1) Konrad Rzeszutek Wilk
2012-07-03 15:40 ` [PATCH 1/4] xen/p2m: Optimize the get_phys_to_machine function a bit Konrad Rzeszutek Wilk
2012-07-09 15:41 ` [Xen-devel] " David Vrabel
2012-07-09 16:14 ` Konrad Rzeszutek Wilk
2012-07-03 15:40 ` [PATCH 2/4] xen/perf: Define .glob for the different hypercalls Konrad Rzeszutek Wilk
2012-07-03 16:07 ` Jan Beulich
2012-07-03 16:14 ` David Vrabel [this message]
2012-07-03 16:17 ` [Xen-devel] " Ian Campbell
2012-07-03 17:44 ` Konrad Rzeszutek Wilk
[not found] ` <4FF334E9020000780008D610@nat28.tlf.novell.com>
2012-07-03 17:38 ` Konrad Rzeszutek Wilk
2012-07-03 15:40 ` [PATCH 3/4] xen/acpi: Fix potential memory leak Konrad Rzeszutek Wilk
2012-07-03 15:40 ` [PATCH 4/4] xen/hvc: Fix up checks when the info is allocated Konrad Rzeszutek Wilk
2012-07-03 16:11 ` Jan Beulich
[not found] ` <4FF335C6020000780008D613@nat28.tlf.novell.com>
2012-07-03 17:36 ` Konrad Rzeszutek Wilk
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=4FF31A66.30904@citrix.com \
--to=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
/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).