Hello
I’m having a performances problems in my driver that I develope.
I would like to know if there are tools to analyze/profileing drivers performance. (like that tools for User Mode Applications)
Thanks in advance.
Hello
I’m having a performances problems in my driver that I develope.
I would like to know if there are tools to analyze/profileing drivers performance. (like that tools for User Mode Applications)
Thanks in advance.
What kind of driver is it? What is your exact problem?
I think there is a tool from Compuware to “time” parts of your driver, but
I’ve never used it.
Le Wed, 12 Dec 2007 02:30:18 -0500 (EST), xxxxx@gmail.com a ecrit:
Hello
I’m having a performances problems in my driver that I develope.
I would like to know if there are tools to analyze/profileing drivers
performance. (like that tools for User Mode Applications)Thanks in advance.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminarsTo unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
–
EA
TrueTime and (and possibly) TrueCoverage. They used to be part of
DriverStudio (???), but I have no idea of what their deal is these days.
I can’t say that I ever really used either of them, but assuming that
DriverStudio is still priced the way is used to be, then they would have
to do everything including your taxes to even be worth considering.
The following is just a marginally informed opinion. For what it is
worth, speaking as a former longtime, very satisfied SoftICE user who
has been known to defend it when it is disparaged from time to time on
this list, and occasional BoundsChecker user as well, I personally found
pretty much everything that was bundled with either of these products,
tripling their prices in the process, to be not remotely worth even a
25% increase in cost, and in some cases, like the hot VisualBasic
performance tuning tools that came with DeveloperStudio, the whole thing
was just insulting.
Good luck,
mm
Edouard A. wrote:
What kind of driver is it? What is your exact problem?
I think there is a tool from Compuware to “time” parts of your driver, but
I’ve never used it.Le Wed, 12 Dec 2007 02:30:18 -0500 (EST), xxxxx@gmail.com a ecrit:
> Hello
> I’m having a performances problems in my driver that I develope.
> I would like to know if there are tools to analyze/profileing drivers
> performance. (like that tools for User Mode Applications)
>
> Thanks in advance.
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
DriverStudio, aka SoftIce, was discontinued last year as Compuware disbanded
the former Numega operation.
The Intel Vtune product is available for $$$. Microsoft’s kernrate is a free
tool, as is KrView for free.
On Dec 12, 2007 5:58 AM, Martin O’Brien wrote:
> TrueTime and (and possibly) TrueCoverage. They used to be part of
> DriverStudio (???), but I have no idea of what their deal is these days.
> I can’t say that I ever really used either of them, but assuming that
> DriverStudio is still priced the way is used to be, then they would have
> to do everything including your taxes to even be worth considering.
>
> The following is just a marginally informed opinion. For what it is
> worth, speaking as a former longtime, very satisfied SoftICE user who
> has been known to defend it when it is disparaged from time to time on
> this list, and occasional BoundsChecker user as well, I personally found
> pretty much everything that was bundled with either of these products,
> tripling their prices in the process, to be not remotely worth even a
> 25% increase in cost, and in some cases, like the hot VisualBasic
> performance tuning tools that came with DeveloperStudio, the whole thing
> was just insulting.
>
> Good luck,
>
> mm
>
> Edouard A. wrote:
> > What kind of driver is it? What is your exact problem?
> >
> > I think there is a tool from Compuware to “time” parts of your driver,
> but
> > I’ve never used it.
> >
> > Le Wed, 12 Dec 2007 02:30:18 -0500 (EST), xxxxx@gmail.com a ecrit:
> >> Hello
> >> I’m having a performances problems in my driver that I develope.
> >> I would like to know if there are tools to analyze/profileing drivers
> >> performance. (like that tools for User Mode Applications)
> >>
> >> Thanks in advance.
> >>
> >>
> >> —
> >> NTDEV is sponsored by OSR
> >>
> >> For our schedule of WDF, WDM, debugging and other seminars visit:
> >> http://www.osr.com/seminars
> >>
> >> To unsubscribe, visit the List Server section of OSR Online at
> >> http://www.osronline.com/page.cfm?name=ListServer
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
–
Mark Roddy
I used true time once, it introduced a bug in a disk filter driver I was
timing for a customer (the joys of DriverStudio), it nicely wiped out the
disk image that we ware testing against. Like all Compuware tools of the
last few years, they should be paying you not the other way around.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply
“Martin O’Brien” wrote in message
news:xxxxx@ntdev…
> TrueTime and (and possibly) TrueCoverage. They used to be part of
> DriverStudio (???), but I have no idea of what their deal is these days. I
> can’t say that I ever really used either of them, but assuming that
> DriverStudio is still priced the way is used to be, then they would have
> to do everything including your taxes to even be worth considering.
>
> The following is just a marginally informed opinion. For what it is
> worth, speaking as a former longtime, very satisfied SoftICE user who has
> been known to defend it when it is disparaged from time to time on this
> list, and occasional BoundsChecker user as well, I personally found pretty
> much everything that was bundled with either of these products, tripling
> their prices in the process, to be not remotely worth even a 25% increase
> in cost, and in some cases, like the hot VisualBasic performance tuning
> tools that came with DeveloperStudio, the whole thing was just insulting.
>
> Good luck,
>
> mm
>
> Edouard A. wrote:
>> What kind of driver is it? What is your exact problem?
>>
>> I think there is a tool from Compuware to “time” parts of your driver,
>> but
>> I’ve never used it.
>>
>> Le Wed, 12 Dec 2007 02:30:18 -0500 (EST), xxxxx@gmail.com a ecrit:
>>> Hello
>>> I’m having a performances problems in my driver that I develope.
>>> I would like to know if there are tools to analyze/profileing drivers
>>> performance. (like that tools for User Mode Applications)
>>>
>>> Thanks in advance.
>>>
>>>
>>> —
>>> NTDEV is sponsored by OSR
>>>
>>> For our schedule of WDF, WDM, debugging and other seminars visit:
>>> http://www.osr.com/seminars
>>>
>>> To unsubscribe, visit the List Server section of OSR Online at
>>> http://www.osronline.com/page.cfm?name=ListServer
>
What do you mean by performance problems? The application is not getting data fast enough? You cannot dma fast enough from the device and lose data? How did you measure your performance?
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@gmail.com
Sent: Tuesday, December 11, 2007 11:30 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Driver performance
Hello
I’m having a performances problems in my driver that I develope.
I would like to know if there are tools to analyze/profileing drivers performance. (like that tools for User Mode Applications)
Thanks in advance.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
Don,
I used true time once, it introduced a bug in a disk filter driver I was timing for a customer
Although I have always been a devoted fan of SI, I have to admit that you have a strong point here - indeed, from time to time it presented, softly speaking, “not-so-accurate” picture of the system state. This is particularly true for memory-mapped IO - it just had some delays, so that you were made believe a change that you had applied to memory-mapped registers did not have an effect…
I would say that tools like SI are more useful for disassembling the OS, rather than actually debugging your driver…
Anton Bassov
> I would say that tools like SI are more useful for disassembling the OS,
rather than
No.
dumpbin /disasm is better, so is WinDbg which can save the command-line talk to
the log file.
–
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
> ----------
From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Maxim S. Shatskih[SMTP:xxxxx@storagecraft.com]
Reply To: Windows System Software Devs Interest List
Sent: Wednesday, December 12, 2007 10:40 PM
To: Windows System Software Devs Interest List
Subject: Re:[ntdev] Driver performance> I would say that tools like SI are more useful for disassembling the OS,
rather thanNo.
dumpbin /disasm is better, so is WinDbg which can save the command-line talk to
the log file.
Well, both are pretty lame comparing to IDA Pro. SI was great if one needed quickly look into some part of OS code. Just one hotkey, find requested function (via name or symbols), look and leave SI. Much faster than above mentioned. BTW, SI also supported log file.
In past years I used SI mainly for this purpose, for debugging code without sources, to catch asserts, see debug output and for quick examination of OS or my drivers state. Very rarely as a source debugger but it is because I don’t use debuggers at all I miss it sometimes; it stopped work after some XP SP2 fix.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
Like Michal, I was a die hard SI user, and used it in pretty much
exactly the same manner as he. Having gotten used to WinDbg, however,
I really can’t imagine going back to using SoftICE alone now, even if it
were a practical option. However, I did very much enjoy using both
WinDbg and SoftICE, and I wish it were still an option. It also still
does a few things that WinDbg, to the best of my knowledge can not, or
at least doesn’t do very well, assuming you’re working on a target that
SI supports, which isn’t a whole lot these days, reasonably speaking.
In particular, SoftICE will not generally be thwarted by most anti-kd
technologies that make WinDbg pretty much useless, like repeated INT 1,
which is key if you ever have the misfortune of having to deal with
pretty much anything by Symantec., for example. I gather that it is
possible to debug user mode and kernel mode simultaneously using WinDbg,
but SoftICE makes it trivial, which is occasionally wonderful, and this
is probably SoftICE’s best remaining feature, but one that I don’t use
much. It’s Ethernet transport was also occasionally just about the best
thing ever, if it meant not having to go to a client’s site for
something small, or more commonly and more importantly you could at
least have some idea of what the problem is before you show up, perhaps
eliminating a second trip.
All that being said, it definitely had its issues. It was indeed a
miserable source debugger, but I don’t think that is how most people
really used it in it’s later years, symbol handling was huge pain in the
ass, and, although it supposedly supported WinDbg extensions, that was
no my experience, which gave it many fewer specific capabilities, and
then of course there were keyboard/mouse issues, and the original video
support was a disaster. What I think gets left out of this discussion
is that back when I started doing this stuff on my own (~ 1999), it
cost much less than a two machine WinDbg setup, and was really the only
option for someone like myself who was just starting and doing this on
his own time and dollar. Finally, while it took some getting used to,
really like WinDbg today, but, as I recall, it also had different but
serious issues back then as well.
mm
Michal Vodicka wrote:
> ----------
> From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Maxim S. Shatskih[SMTP:xxxxx@storagecraft.com]
> Reply To: Windows System Software Devs Interest List
> Sent: Wednesday, December 12, 2007 10:40 PM
> To: Windows System Software Devs Interest List
> Subject: Re:[ntdev] Driver performance
>
>> I would say that tools like SI are more useful for disassembling the OS,
> rather than
>
> No.
>
> dumpbin /disasm is better, so is WinDbg which can save the command-line talk to
> the log file.
>
Well, both are pretty lame comparing to IDA Pro. SI was great if one needed quickly look into some part of OS code. Just one hotkey, find requested function (via name or symbols), look and leave SI. Much faster than above mentioned. BTW, SI also supported log file.In past years I used SI mainly for this purpose, for debugging code without sources, to catch asserts, see debug output and for quick examination of OS or my drivers state. Very rarely as a source debugger but it is because I don’t use debuggers at all
I miss it sometimes; it stopped work after some XP SP2 fix.
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
>> I would say that tools like SI are more useful for disassembling the OS, rather than
No. dumpbin /disasm is better
What are you going to do the very first time you encounter a line like ‘jmp dword ptr[eax]’ in a dump file??? At which point are you going to continue your examination???
so is WinDbg which can save the command-line talk to the log file.
Well, this is at least something - WinDbg is at least interactive. However, it is not that convenient to use for the purpose of disassembling code - you see just a dozen lines of code; memory is in a different window (again, just few lines of it, which hardly helps you when examining large structures); registers are yet in another windows; and, in any case, stepping from one line to another or requesting a dump of a new memory range takes quite a while . WinDbg is good for source-level debugging - after all, this is what it is meant to be used for…
Anton Bassov