This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Is there a roadmap for the STAP development?


On Thu, Feb 16, 2017 at 9:38 PM, David Smith <dsmith@redhat.com> wrote:
> On 02/14/2017 12:00 PM, Arkady wrote:
>> On Tue, Feb 14, 2017 at 6:13 PM, David Smith <dsmith@redhat.com> wrote:
>
> ... stuff deleted ...
>
>>>> * Add RPM spec file supporting automatic build of the kernel driver
>>>> after kernel updates
>>>
>>> What do you mean by "the kernel driver"?
>>
>> I need to build the module automatically every time the kernel
>> updates. I am preparing the RPM/DEB which does the trick, but to have
>> a generic example in /docs/examples would be nice or even a script
>> which generates such RPM based on the stap command line options.
>
> Hmm, interesting. This sounds a bit like the kmod system that rebuilds
> external kernel modules when the kernel gets updated.
>
> ... stuff deleted ...
>> In another approach I am planning to use the shared memory for sending
>> events from the kernel to the user space in one specific case - very
>> frequent system calls. Similarly to transport.c with zero copy API.
>
> Interesting. Yep, that code would be interesting to see.

Here is an example of zero copy support
https://github.com/larytet/YALAS/blob/master/src/shm_fifo.h#L40
and a macro which allocates the data
https://github.com/larytet/YALAS/blob/master/src/driver.h#L284

Arkady.
>
> --
> David Smith
> dsmith@redhat.com
> Red Hat
> http://www.redhat.com
> 256.217.0141 (direct)
> 256.837.0057 (fax)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]