Project

General

Profile

Actions
Copy link

Feature #6690

closed

Support extracting of build commands for external Linux kernel modules

Added by Evgeny Novikov over 8 years ago. Updated about 8 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Evgeny Novikov
Category:
* Build commands extracting
Target version:
-
Start date:
02/02/2016
Due date:
% Done:

0%

Estimated time:
Published in build:
32bc780

Description

Now LKBCE can extract build commands just for internal Linux kernel modules.

Related issues 2 (0 open — 2 closed)

Blocks Klever - Feature #6662: Develop tests for rule specificationsRejected02/01/2016

Actions
Blocks Klever - Feature #6663: Port tests for environment models generation from LDV ToolsClosedIlja Zakharov02/01/2016

Actions
Actions
Copy link
 #1

Updated by Evgeny Novikov about 8 years ago

  • Status changed from New to Open
  • Assignee set to Evgeny Novikov
  • Priority changed from High to Urgent

One more welcome feature of Klever.

Actions
Copy link
 #2

Updated by Evgeny Novikov about 8 years ago

  • Status changed from Open to Closed
  • Published in build set to 32bc780

Supported since 32bc780.

To verify external Linux kernel modules one needs to place their archive like other job files and specify an archive path and target modules in a job. For instance:

  • to verify all external modules: 
    "Linux kernel": {
  "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
  "modules": ["all"]
}
  • to verify all external modules from directory S and U-double_mutex_lock.ko:
    "Linux kernel": {
  "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
  "modules": ["S", "U-double_mutex_lock.ko"]
}
  • to verify all external modules from directory S:
    "Linux kernel": {
  "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
  "modules": ["S"]
}
  • to verify U-double_mutex_lock.ko:
    "Linux kernel": {
  "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
  "modules": ["U-double_mutex_lock.ko"]
}
  • to verify S/S-mutex_lock.ko:
    "Linux kernel": {
  "external modules archive": "32_7--test-mutex_lock.tar.bz2", 
  "modules": ["S/S-mutex_lock.ko"]
}

At the moment just one archive with external Linux kernel modules can be specified per a job (sub-job). This is the most flexible solution since we can easily configure a remaining part of a job (sub-job) independently for each archive.

Actions
Copy link

Also available in: Atom PDF