[Dev] External kernel module building and kernel ABI/API check.

Jacek Pielaszkiewicz j.pielaszkie at samsung.com
Wed Dec 18 08:41:13 GMT 2013


Hi MyungJoo

            I have moved abi-checker into tools directory and I have added
short description in Documentation directory (patch
https://review.tizen.org/gerrit/#/c/13873/). 

Best regards

 

 


 

Jacek Pielaszkiewicz

Samsung R&D Institute Poland

Samsung Electronics

Email:  <mailto:j.pielaszkie at samsung.com> j.pielaszkie at samsung.com

 

 

From: 함명주 [mailto:myungjoo.ham at samsung.com] 
Sent: Monday, December 16, 2013 12:39 PM
To: Jacek Pielaszkiewicz
Cc: dev at lists.tizen.org; artem.bityutskiy at linux.intel.com
Subject: Re: RE: Re: [Dev] External kernel module building and kernel
ABI/API check.

 

Hi Jacek,

 

The question 3 was simply for the location of your code; i.e., creating
another 1st-level subdirectory in kernel source tree seemed inappropriate.
Like other "tools" such as "get-maintainer", "check-patch", ... , it seems
that your code belongs to "tools/abi-checker". For later upstreaming, it
seemed tools/* is appropriate.

 

For "Documentation" entry, you can start push what you already have. You
can later make it more concrete.

 

Cheers,

MyungJoo.

 

------- Original Message -------

Sender : Jacek Pielaszkiewicz< <mailto:j.pielaszkie at samsung.com>
j.pielaszkie at samsung.com> Senior Software Engineer/SRPOL-Kernel & System
Framework (SSD)/삼성전자

Date : 2013-12-13 17:39 (GMT+09:00)

Title : RE: Re: [Dev] External kernel module building and kernel ABI/API
check.

 

Hi MyungJoo

My answer below.

Best regards


Jacek Pielaszkiewicz
Samsung R&D Institute Poland
Samsung Electronics
Email:  <mailto:j.pielaszkie at samsung.com> j.pielaszkie at samsung.com



> -----Original Message-----
> From: MyungJoo Ham [ <mailto:myungjoo.ham at samsung.com>
mailto:myungjoo.ham at samsung.com]
> Sent: Friday, December 13, 2013 7:23 AM
> To: Jacek Pielaszkiewicz;  <mailto:artem.bityutskiy at linux.intel.com>
artem.bityutskiy at linux.intel.com
> Cc:  <mailto:dev at lists.tizen.org> dev at lists.tizen.org
> Subject: Re: Re: [Dev] External kernel module building and kernel
> ABI/API check.
> 
> > Hi
> >
> > It was about the API used by external kernel modules.
> >
> >
> > Best regards
> 
> Hi Jacek,
> 
> 1. Could you please add a simple Documentation (Kernel/Documentation/*
> ?) about it?

In my last patch on tizen.org I added sample external module to show how to
use tools. 
Of course I will add some additional documentation to present more details.

> 2. Have you considered using the tool at host in host(x86)-target(arm)
> environment?

> 3. Could you consider using Kernel/tools/* directory for this abi-
> checker?

Regarding to your next two questions. My original plan was to use up a lot
of available 
functionality/mechanisms from the kernel. Therefore I used Module.symvers
file as basic 
source to get information about all exported kernel symbols and their
version (CRC).
I needed simple tool that performs operations like:
- Compare Module.symvers files for two different kernel version
- Compare kernel Module.symvers with similar file for kernel module
- Extract from external module all kernel symbols use be the module and 
  creates output file in format compatible with Module.symvers file. 

I didn't find tool that meet my needs therefore I decided to develop own. 
Most of operations performed by the tools are not depend on target 
architecture (text Module.symvers files testing). 

Regarding to module symbols extraction I use libelf to read ELF files. 
I tested the tool on x86 and it works fine.

> 
> 
> ps. I've rebased your gerrit patch; however, I'll wait a bit more for
> further review.
> 
> Cheers,
> MyungJoo.
> 
> >
> >
> >
> >
> > Jacek Pielaszkiewicz
> > Samsung R&D Institute Poland
> > Samsung Electronics
> > Email:  <mailto:j.pielaszkie at samsung.com> j.pielaszkie at samsung.com
> >
> >
> >
> > > -----Original Message-----
> > > From: Artem Bityutskiy [ <mailto:artem.bityutskiy at linux.intel.com>
mailto:artem.bityutskiy at linux.intel.com]
> > > Sent: Wednesday, December 11, 2013 12:45 PM
> > > To: Jacek Pielaszkiewicz
> > > Cc:  <mailto:dev at lists.tizen.org> dev at lists.tizen.org
> > > Subject: Re: [Dev] External kernel module building and kernel
> > > ABI/API check.
> > >
> > > On Tue, 2013-12-10 at 13:13 +0100, Jacek Pielaszkiewicz wrote:
> > > > Hi everyone,
> > > >
> > > >
> > > >       I would like to ask all of you for comments and also I
> would
> > > > like to present results of our works related to kernel and
> > > > external kernel modules build.
> > > >
> > > >
> > > >       We have the following plans:
> > > > 1. Deliver environment to build external kernel modules 2.
> Provide
> > > > functionality that detects changes in kernel ABI/API.
> > >
> > > From your e-mail it sounds like ABI/ABI that you refer to is about
> > > the internal kernel symbols.
> > >
> > > Could you please define more specifically what API/ABI in question
> is.
> > >
> > > --
> > > Best Regards,
> > > Artem Bityutskiy
> >
> >
> > _______________________________________________
> > Dev mailing list
> >  <mailto:Dev at lists.tizen.org> Dev at lists.tizen.org
> >  <https://lists.tizen.org/listinfo/dev>
https://lists.tizen.org/listinfo/dev
> >
> >
> >
> >
> >
> >
> >



 

 

--

MyungJoo Ham (함명주), PHD

System S/W Lab, S/W Platform Team, Software Center
Samsung Electronics
Cell: +82-10-6714-2858

 


 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131218/713edad1/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.gif
Type: image/gif
Size: 14036 bytes
Desc: not available
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131218/713edad1/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.jpg
Type: image/jpeg
Size: 2988 bytes
Desc: not available
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131218/713edad1/attachment-0001.jpg>


More information about the Dev mailing list