Bug 13997 - --all-modules vs remote compilation/execution
Summary: --all-modules vs remote compilation/execution
Status: NEW
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-19 12:58 UTC by Frank Ch. Eigler
Modified: 2012-04-19 18:20 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Ch. Eigler 2012-04-19 12:58:44 UTC 
--all-module conflicts with our two remoting facilities, to the extent that the insert_loaded_modules() logic is executed on the compilation host rather than on the execution site.
Comment 1 Josh Stone 2012-04-19 18:20:43 UTC 
Note that right now with multiple simultaneous remotes, we only split the compilation base on unique (kernel release, architecture) pairs.  If we start incorporating more data about the remote into compilation, then we'll have to split these up further.

We could just do separate compilation for all remotes regardless, and then trust the caching to collapse pass-3/4 work.  We'd always be duplicating earlier passes though.