[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 4 of 5 v3] xen: tracing: introduce per-scheduler trace event IDs
On lun, 2013-03-11 at 10:57 +0000, George Dunlap wrote: > On 09/03/13 10:40, Dario Faggioli wrote: > > TBH, I haven't done any xenalyze modification, corresponding to this. > > However, I'm not really sure it's necessary. > > It does change the trace records slightly, by adding in the extra > scheduler ID at the top. It just requires propagating the changes in > trace.h from the xen tree to xenalyze -- not hard to do; > Oh, I see... Then I guess I just failed to spot anything like that was needed, perhaps because everything was JustWorking^TM, at least to my inexperienced eyes. :-) > I jut wanted to > know if you happened to have the patch lying around so I wouldn't have > to go through and do it. No worries. :-) > Ok, so, I think we should go for a "whoever gets to it first tell it to the other (e.g., by Cc-ing him to the patch ;-P), to avoid duplicating the (although small) effort" policy... Is that fine with you? Dario -- <<This happens because I choose it to happen!>> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) Attachment:
signature.asc _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |