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<[email protected]> 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 regrads
Jacek Pielaszkiewicz
Samsung R&D Institute Poland
Samsung Electronics
Email: [email protected]
> -----Original Message-----
> From: MyungJoo Ham [mailto:[email protected]]
> Sent: Friday, December 13, 2013 7:23 AM
> To: Jacek Pielaszkiewicz; [email protected]
> Cc: [email protected]
> 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: [email protected]
> >
> >
> >
> > > -----Original Message-----
> > > From: Artem Bityutskiy [mailto:[email protected]]
> > > Sent: Wednesday, December 11, 2013 12:45 PM
> > > To: Jacek Pielaszkiewicz
> > > Cc: [email protected]
> > > 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
> > [email protected]
> > https://lists.tizen.org/listinfo/dev
> >
> >
> >
> >
> >
> >
> >
--
MyungJoo Ham (함명주), PHD
Samsung Electronics
Cell: +82-10-6714-2858
|
|
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev

