Thanks. yes, that is the reason. I just found that our block driver is not using request queue because our device is flash memory. -Gangadhar On Thu, Jul 7, 2011 at 3:23 PM, Tao Ma <tm@xxxxxx> wrote: > On 07/07/2011 05:41 PM, Gangadhar Mylapuram wrote: >> Hi, >> >> As for my understanding I no need to handle (BLKRESTART, BLKTRACESTOP, >> BLKTRACESETUP ..) in my device ioctl handling. It is block l/O layer >> which intercepts the >> statistics and does the job. >> >> But for my device (not sda or hda), blktrace only show the Q events. >> It is not showing even C (completed) events. Do I need to add the >> support in my device ioctl handling code? > These trace pointers are only recorded if they are met. > So I guess the reason is that your device implements your own > make_request_fn(So you can see 'Q' event) and no other trace point is > met at all. > > Thanks, > Tao > -- To unsubscribe from this list: send the line "unsubscribe linux-btrace" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
