All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Gardner <rob.gardner@hp.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: "Magenheimer,
	Dan (HP Labs Fort Collins)" <dan.magenheimer@hp.com>,
	xen-devel@lists.xensource.com
Subject: Re: Recent trace patch not arch-neutral
Date: Mon, 31 Oct 2005 16:03:16 -0700	[thread overview]
Message-ID: <4366A2B4.6070406@hp.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D32E6D0@liverpoolst.ad.cl.cam.ac.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]

Ian Pratt wrote:

>>A recent patch to trace.c uses a call to rdtscll() which is 
>>x86-specific.  Is there an arch-neutral call that can be used 
>>instead?  Or do arch's need to implement this?  (And if the 
>>latter, should we choose a more generic name?)
>>    
>>
>
>The tracebuffer code has always used the cycle counter, so if you've
>previously been compiling it for ia64 it must have previously been using
>some more arch neutral way of accessing it...
>  
>


The deal with this is that the default was always trace=n so the trace 
macros never expanded to anything unless you wanted them to. One of the 
things that Keir did in "cleaning up" my code was to totally eliminate 
all conditional compilation. That's why this problem is suddenly showing 
up on ia64.

Now, to answer Dan's question- the rdtscll thing is just a time stamp 
counter, expressed in cycles. So on ia64 you could probably replace it 
with an asm statement to read ar.itc to make everything work. We just 
need a little wrapper to do the right thing for each architecture. Now 
Dan, if you were more conveniently located, perhaps we could work 
together and fix this. ;)

Rob


Rob


[-- Attachment #1.2: Type: text/html, Size: 1606 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2005-10-31 23:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 22:18 Recent trace patch not arch-neutral Ian Pratt
2005-10-31 23:03 ` Rob Gardner [this message]
2005-10-31 23:26   ` Rob Gardner
2005-11-01  6:18     ` Muli Ben-Yehuda
2005-11-01  6:38       ` Rob Gardner
2005-11-01  6:45         ` Muli Ben-Yehuda
2005-11-01  9:27     ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-11-02 17:47 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-01 13:25 Magenheimer, Dan (HP Labs Fort Collins)
2005-11-01 13:59 ` Keir Fraser
2005-10-31 22:32 Magenheimer, Dan (HP Labs Fort Collins)
2005-10-31 21:33 Magenheimer, Dan (HP Labs Fort Collins)

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=4366A2B4.6070406@hp.com \
    --to=rob.gardner@hp.com \
    --cc=dan.magenheimer@hp.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.