Updating to pickup a couple of configuration tweaks that were done
as part of a bump to the 3.4 linux-yocto tree for the beagleboard.
In particular, this updates DVI and USB settings to enable the
perhipherals out of the box.
(From OE-Core rev: 3c562b8360edf52aea6280849fa33e8a0f34742b)
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the machine and meta SRCREVs to the latest 3.4.x -stable
release.
See git whatchanged v3.4.10..v3.4.11 for the full changelog.
(From OE-Core rev: b164d9776802784a2fee01f2ab267dab4c2beafe)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the meta SRCREV to pickup a newer emgd for the fri2 and
sys940x.
(From OE-Core rev: abb23d987184f76fb922af15508f2e251399e3ed)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta SRCREVs to pickup the following configuration change:
594994c meta: use profiling and latencytop features in yocto bsps
(From OE-Core rev: df0197810e72337093ea6ced1c8b28eeeef8a7a8)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86-64.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86-64 core-image-x11 kvm
Implements [YOCTO #2550].
(From OE-Core rev: cbb6431b3ee9128ea15c9ae0a19e7d2998ffc561)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
KVM, paravirtualization and virtio drivers are now activated
in runqemu using the kvm option flag for qemux86.
Host CPU features are also exported to guest OS (Yocto Linux).
Usage example: runqemu qemux86 core-image-x11 kvm
Implements [YOCTO #2550].
(From OE-Core rev: a35d03e2eb905de4eadc9c7df5b50bff1fb7f897)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
uprobes depends on functionality provided by perf events. After
uprobes was enabled in the standard kernel the mpc8315 board showed
link errors due to missing perf event functions.
This problem isn't isolated to the board or powerpc arch, but all
other boards have PERF_EVENTS enabled. To fix this, we make UPROBE_EVENT
select PERF_EVENTS, and any new boards will be protected from the
same failure.
We also update the configuration fragments since CONFIG_UPROBES depends on
CONFIG_PERF_EVENTS being set, so PERF_EVENTS needs to be added whenever
uprobes are enabled.
[YOCTO #3111]
(From OE-Core rev: b681b74624d1c8c4c98b2a121828e010fc5c3a25)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the meta branch SRCREV to pick up virtio and kvm guest
configuration fragments.
79947f1 meta: add paravirtualized KVM guest config fragment
3ed86ed meta: add MMIO support in virtio config fragment
(From OE-Core rev: b6b5b501fbe7158f190e887c3edc1214bb3671ed)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It was reported that the kernel configuration checks for custom yocto
kernels had the following output:
NOTE: validating kernel configuration
grep: /meta-series: No such file or directory
grep: /meta-series: No such file or directory
WARNING: Can't find any BSP hardware or required configuration fragments.
WARNING: Looked at //cfg///hdw_frags.txt and //cfg///required_frags.txt in directory: //cfg//
NOTE: Tasks Summary: Attempted 375 tasks of which 367 didn't need to be rerun and all succeeded.
which is not inspire confidence in the output of the process.
Completely inhibiting the check is one option to remove the messages,
but that removes the ability see output, which can help move users to
a better or more fully configured linux-yocto based kernel.
To fix this, we have to ensure that the path to the meta-series is
always valid, and that the tools can deal with not all files existing
in the audit directory.
Since custom yocto kernels do not set KMETA (they don't have a meta branch),
we ensure that a default of 'meta' is passed to the audit ('meta' is always
valid), and that kconf_check itself can deal with an incomplete set of
input audit files.
The net result is output like this (using a defconfig with invalid options
for the kernel being built):
NOTE: validating kernel configuration
This BSP sets 19 invalid/obsolete kernel options.
These config options are not offered anywhere within this kernel.
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/invalid.cfg
There were 1 instances of config fragment errors.
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/fragment_errors.txt
The full list can be found in your kernel src dir at:
meta/cfg/standard/qemux86/missing_required.cfg
(From OE-Core rev: 4d1b7dae063ee4c35c426306d0e22f11ce112c72)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This was noticed by the following warnings of files that should have been removed!
WARNING: QA Issue: kernelshark: Files/directories were installed but not shipped
/usr/share
/usr/share/trace-cmd
/usr/share/trace-cmd/plugins
/usr/share/trace-cmd/plugins/plugin_blk.so
/usr/share/trace-cmd/plugins/plugin_sched_switch.so
/usr/share/trace-cmd/plugins/plugin_kmem.so
/usr/share/trace-cmd/plugins/plugin_kvm.so
/usr/share/trace-cmd/plugins/plugin_function.so
/usr/share/trace-cmd/plugins/plugin_jbd2.so
/usr/share/trace-cmd/plugins/plugin_hrtimer.so
/usr/share/trace-cmd/plugins/plugin_mac80211.so
/usr/share/trace-cmd/plugins/.debug
/usr/share/trace-cmd/plugins/.debug/plugin_blk.so
/usr/share/trace-cmd/plugins/.debug/plugin_sched_switch.so
/usr/share/trace-cmd/plugins/.debug/plugin_kmem.so
/usr/share/trace-cmd/plugins/.debug/plugin_kvm.so
/usr/share/trace-cmd/plugins/.debug/plugin_function.so
/usr/share/trace-cmd/plugins/.debug/plugin_jbd2.so
/usr/share/trace-cmd/plugins/.debug/plugin_hrtimer.so
/usr/share/trace-cmd/plugins/.debug/plugin_mac80211.so
(From OE-Core rev: c3cff64708cb078405f5ecd9bca6801031786bc4)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When x32 is the tuning for a x86 MACHINE, the kernel should also have
CONFIG_X86_X32=y. This adds a x32 fragment that can be used to trigger
the right ABI.
The commit also contains a check for mx32 in TUNE_FEATURES, and if
present, the new fragment will be appended to KERNEL_FEATURES and
trigger the support in the kernel.
cc: Saul Wold <sgw@linux.intel.com>
(From OE-Core rev: bf689c60caa905eb8866101b9e99dd4ae246a2ca)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is sometimes useful for KERNEL_FEATURES to be set in a machine
or other configuration file. The linux-yocto recipes currently
initialize the variable, which clobbers any values set by .conf
files.
Appending to the variables allows these settings to propagate to
the kernel configuration, while maintaining the existing set of
added kernel features.
(From OE-Core rev: 7121fe8d836fc178e9ab8f0e6f8eb34a99325c81)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating to 3.4.10 which has been soaking for a bit now, as well
as picking up the following meta commits from Tom Z:
a82db2f meta: have systemtap use kprobes and uprobes feature
d5d5b80 meta: add kprobes support to ktypes/standard
b32d373 meta: add kprobes feature
d40ed99 meta: have uprobe feature use uprobe.cfg
a69d1db meta: add uprobe.cfg
(From OE-Core rev: fb71d8c3ab735739baedcb5c8c44b028890d8a5e)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The first import of 3.4.9-rt17 only picked up part of the import due
to a merge conflict with the modified files, and then SRCREVs being
generated from the pre-merge commit.
This SRCREV update picks up the rest of the modified files for full
-rt support.
(From OE-Core rev: d1ec0b64018dafaa6e47233b3465fbe4189e6280)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the 3.4 kernel to -rt17.
As well as picking up the normal set of bug fixes, this update fixes
a boot issue that was introduced during merging of kernel.org -stable
updates into the -rt branches (in the timekeeping code).
(From OE-Core rev: 0c060a81ade685aee5492e0273f199850dffaf76)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.2/3.4 linux-yocto SRCREVs to pickup the following fix:
arm: Fix linking errors with binutils 2.23
We end up with linking errors on arm using latest binutils
because we are linking asm generated objects which use -march=all
generating different attributes into object and use some c objects
e.g. misc.o which use different march therefore generating a
different set of attributes into object. When linking is done
the ld complains since it finds incompatible attributes and ends
up with errors like
error: DIV usage mismatch between arch/arm/boot/compressed/head.o and
output
error: DIV usage mismatch between arch/arm/boot/compressed/misc.o and
output
error: DIV usage mismatch between arch/arm/boot/compressed/decompress.o
and output
error: DIV usage mismatch between arch/arm/boot/compressed/lib1funcs.o
and output
This patch fixes it by providing correct march to assembly routines
which than matches with output of ld.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(From OE-Core rev: e67ffb708522a622d149641ea09b249259ed3fb4)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Importing the following tools SRCREV:
kgit-meta: exclude explicit branches from name calculations
kernel branches are constructed during patching of the tree by
constructing a '/' based hierarchy of names as each branch
directive is encountered.
But if a "branch $name $branchpoint" is used, the entire branch
name is supplied so no additions to the hierarchy should
happen. As such, that type of branch command should not be part
of branch name calculation and preparation.
(From OE-Core rev: a3884938233c8a2d6861b1d4e6be5b9824d3b131)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When patches fail to apply, the status of all pending patches should
be exported to the logs and to the user. Currently, a missing export
of GUILT_BASE makes it look more like an internal error, than a 'normal'
patch failure:
| [ERROR] unable to complete push
| pending patches are:
| Patches directory doesn't exist, try guilt-init
With this variable exported, we have this:
| [INFO] validating against known patches (qemux86-standard-meta)
| error: patch failed: Makefile:2
| error: Makefile: patch does not apply
| To force apply this patch, use 'guilt push -f'
| [ERROR] unable to complete push
| pending patches are:
| links/files/0002-makefile-patch.patch
(From OE-Core rev: b2b2512cbc4196fa0f814be3677517dab30e5b52)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
commit 7a79f7412 [linux-yocto: make KBRANCH the exception and not the rule]
ensures that a request branch is always built. The implementation of this
guarantee is a branch switch before the build starts. But that switch may
be before all patches are applied. If the proper routines are not called,
no patches can be applied to the tree.
Updating the SRCREV to pickup this fix:
updateme: use branch command when forcing branch switches
When forcing a branch switch to the desired branch we should be
using the proper 'branch' command. Since without this call, the
proper variables will not be set, and patches can't be applied
to the tree.
(From OE-Core rev: bede3086cb9ab0f79fb7775528b646817b2b9af0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The qemu-config initscript was only starting oprofile-server, so move it
to the oprofileui-server recipe.
(From OE-Core rev: 3063126e2c8ec72e900a48f7048aaf9662606792)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Increase SRCREV to include an upstream patch that fixes the configure
script so that the server can be built separately without gtk+ and
avahi-ui, and create a separate recipe for the server.
Also fix the RDEPENDS so that oprofile actually gets pulled in by the
client and the server.
Part of the fix for [YOCTO #1690].
(From OE-Core rev: 971fbbd50ae147805fc7498b72a046be5bffc3c7)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since kernelshark depends on trace-cmd, there is no reason to
install and package the plugins that are part of trace-cmd.
[YOCTO #238]
(From OE-Core rev: d6614b0ac7c83b2e17e68903a85fc8374e936c1a)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
As discussed on the mailing lists, using a suffix to package names is
hard and has lead to many recipes having to do PKGSUFFIX games. Its
looking extremely hard to scale nativesdk much further without hacking
many recipes.
By comparison, using a prefix like multilib does works much better and
doesn't involve "hacking" as many recipes. This change converts nativesdk
to use a prefix using the existing multilib infrastructure.
(From OE-Core rev: 81813c0e322dc04ce4b069117188d8a54dfddb8c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
perf depends on bison and flex for event parsing - add them as
dependencies.
(From OE-Core rev: f04b0ddb7a392425ba5890026564bc3521a32c67)
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To support custom repositories that set a SRCREV and that only have
a single master branch, do_validate_branches needs a special case
for 'master'. We can't delete and recreate the branch, since you
cannot delete the current branch, instead we must reset the branch
to the proper SRCREV.
(From OE-Core rev: de5bb5879fa3282c46dc1ede36af34eaab8f647f)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
In the kernel's tools/perf/Makefile CFLAGS was previously hard coded to
contain "-I/usr/include/slang" to work with hosts that have
"/usr/include/slang/slang.h" as well as hosts that have
"/usr/include/slang.h". This path can cause compile warnings like:
cc1: warning: '/usr/include/slang' doesn't exists.
or
cc1: warning: include location "/usr/include/slang" is unsafe for
cross-compilation [-Wpoison-system-directories]
Then in some cases warnings become errors if WERROR is enabled hence
build errors.
In coordination with a kernel fix, we can fix this error for all
kernels by modifying the perf Makefile within the staged kernel
source.
(From OE-Core rev: 4e0daf05ed04e9fb4343032c6290a379f53b89f3)
Signed-off-by: Liang Li <liang.li@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
kmod will fail to build with the following error because O_CLOEXEC is
not defined:
| libkmod/libkmod-module.c: In function 'kmod_module_get_initstate':
| libkmod/libkmod-module.c:1640: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-module.c:1640: error: (Each undeclared identifier is reported only once
| libkmod/libkmod-module.c:1640: error: for each function it appears in.)
| libkmod/libkmod-module.c: In function 'kmod_module_get_refcnt':
| libkmod/libkmod-module.c:1754: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-module.c: In function 'kmod_module_get_sections':
| libkmod/libkmod-module.c:1913: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-file.c: In function 'kmod_file_open':
| libkmod/libkmod-file.c:282: error: 'O_CLOEXEC' undeclared (first use in this function)
| libkmod/libkmod-file.c:282: error: (Each undeclared identifier is reported only once
| libkmod/libkmod-file.c:282: error: for each function it appears in.)
Since we are only using kmod-native for depmod, and it's a non-threaded
user of this libary being built this should be safe to override O_CLOEXEC.
Keep in mind this is ONLY effecting the native builds and not what is
being shipped in the root file system.
(From OE-Core rev: edcb57fe308979cc5b92359d064e32bb70d4ad76)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This helps in appending to this regexp from bbappends
coming from other layers who want to leverage linux-yocto
with minimum tweaks by using a standard prefefined machine
from linux-yocto
(From OE-Core rev: 32ba716e71fb7a16f13c83ab6c8cc51de56b3be2)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the meta SRCREV to pickup this fix:
meta: rename virto.scc to virtio.scc
The virtio configuration block is misnamed. BSPs that include it with
the proper name, now throw an error (as they should). So fixing the
name of the fragment fixes the build.
(From OE-Core rev: c6b335099224d590109a8bcda22bf54c597c7eee)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
To streamline the creation of build time branches (branches that are
not always present in the upstream kernel repository), linux-yocto-tiny
should specify a default kernel branch. By setting the default branch
(KBRANCH_DEFAULT) and also setting the build branch (KBRANCH) to that
default, the tools will allow the board description to be processed
and no branching forced.
(From OE-Core rev: 07e422138b89e4f4a0cc911db70e2ce953b7623b)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Removes a make install-python_ext when not present since
older versions of perf lack this install rule
This also fixes a library issue on older kernels building with
a newer toolchain where libaries that would previously be pulled
in are no longer. So we add them manually.
(From OE-Core rev: 70b17a893bd2e1bbba8ea16619b02a60e7c4b8d8)
Signed-off-by: Matthew McClintock <msm@freescale.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kern-tools scripts can support a meta branch and directory of a name that
isn't "meta", but they need the name passed through the environment variable
KMETA. ensuring that KMETA is exported in the shell environment sets the stage
to support flexible meta branch name.
(From OE-Core rev: 9b90c8ace04c88ac6105f0bf686f9abc70fe8074)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A BSP specific KBRANCH assignment is no longer a required
element to locate and build a yocto kernel. As such we can
set the default kbranch, and remove all other explicit
assignments.
KBRANCH is still used, and if it is changed from the
default, that branch will be built.
(From OE-Core rev: 7984a9f6ccd00bf282c9eedab7ab933add68448c)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The kernel branch is no longer required by the yocto-kern-tools
to locate BSP feature descriptions (it is the MACHINE:KTYPE
descriptor), so we no longer require that the BSP branch be
explicitly set.
If a kernel branch is explicitly set, it is now used to trigger
a checks to ensure that the branch really is being built.
Otherwise the branch that the machine description creates will
be built (just as it always was).
This further simplies the use and configuration of a linux-yocto
based kernel recipe.
(From OE-Core rev: 3cac3ce65abae9dc253641a2004440a2b38fd44d)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-yocto 3.4 recipe with consolidated fixes, BSPs
and cleanups.
From the kernel meta branch:
28bcd46 meta: move emgd features to staging
6c01949 meta: Crystal Forest Machine Created.
3c19c4d meta/qemuppc: remove redundant profiling options
a5da4d5 meta: kgdb: update configuration for out of box functionality
1d13e00 meta: update status/series and patches for v3.4
b96c408 fsl-mpc8315e-rdb: replace leading dot with hash in cfg file
7c9a3b0 usb: fix scc and cfg filename collision with ktypes/base/
aa0e1f6 kconfig: make CONFIG_BLOCK=y part of base config
3d1a2f2 kconfig: add tty/serial file to hardware listing
60b600f routerstationpro: specify chosen filesystems in audit input.
8b5c8c7 routerstationpro: add config data for audit purposes
d7ae8fa meta: add ath79 Kconfig to hardware listing.
And from the standard branch:
c77666c powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr.
c262f3e powerpc: Uprobes port to powerpc
d40e73d powerpc: Add trap_nr to thread_struct
6a64190 Revert "This is the port of uprobes to powerpc. Usage is similar to x86."
e422119 Revert "powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr."
d4ef82f keys: kill task_struct->replacement_session_keyring
1cc141e keys: kill the dummy key_replace_session_keyring()
090ca45 keys: change keyctl_session_to_parent() to use task_work_add()
61bc7a8 genirq: reimplement exit_irq_thread() hook via task_work_add()
5ee34dd task_work_add: generic process-context callbacks
70754de move key_repace_session_keyring() into tracehook_notify_resume()
6f70bc1 powerpc: uprobes: removed external declaration of uprobe_get_swbp_addr.
e5f6a4c This is the port of uprobes to powerpc. Usage is similar to x86.
2bc4597 On RISC architectures like powerpc, instructions are fixed size. Instruction analysis on such pl
8893371 perf probe: Detect probe target when m/x options are absent
544d531a perf probe: Provide perf interface for uprobes
103b503 tracing: Fix kconfig warning due to a typo
9bb012e tracing: Provide trace events interface for uprobes
b9b7281 tracing: Extract out common code for kprobes/uprobes trace events
91f0360 tracing: Modify is_delete, is_return from int to bool
a8600f2 uprobes/core: Decrement uprobe count before the pages are unmapped
a252056 uprobes/core: Make background page replacement logic account for rss_stat counters
3efc15b uprobes/core: Optimize probe hits with the help of a counter
20f3d76 uprobes/core: Allocate XOL slots for uprobes use
77bfad8 uprobes/core: Handle breakpoint and singlestep exceptions
7196d9a uprobes/core: Rename bkpt to swbp
c99bc18 uprobes/core: Make order of function parameters consistent across functions
7e9be99 uprobes/core: Make macro names consistent
c4247f2 uprobes: Update copyright notices
f066ff9 uprobes/core: Move insn to arch specific structure
e91cf65 uprobes/core: Remove uprobe_opcode_sz
942b91c uprobes/core: Make instruction tables volatile
56c1e99 uprobes: Move to kernel/events/
0a7ad1c uprobes/core: Clean up, refactor and improve the code
3760d62 uprobes, mm, x86: Add the ability to install and remove uprobes breakpoints
Two BSP updates:
- Crystal Forest Machine has been added
- routerstationpro configuration updates for 3.4
(From OE-Core rev: bd05dcb634cbb4022b4189985585f73c86f01fae)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The v3.4.7 -stable update has been released, updating all in-tree
BSPs to this new baseline.
(From OE-Core rev: 89a0587d5affe8d8986efce7738b7b3774792154)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add in a workaround to avoid host infection detection build failures
from the slang include directory in perf. I'll defer to Bruce to
fix this properly but we need a workaround now as this is breaking
builds.
(From OE-Core rev: 4fd4b2eafb5f4ff2ef85d7f5ff3238a41c34313b)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This change breaks firmware loading on 64 bit platforms. This therefore
reverts commit ce2665b6ae77770d69ffbc4d45c96ce829d16738.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Latest version is 1.0.0 but in rc4 for now.
(From OE-Core rev: 6172f1fed9850180a3a84ca62cc0741d132031e4)
Signed-off-by: Radu Moisan <radu.moisan@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: ce2665b6ae77770d69ffbc4d45c96ce829d16738)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is considered good practice to use the build system provided
variables instead of directly specify hardcoded paths.
(From OE-Core rev: 095f9c056373a252c0ba2679d8e6f4ad932a958d)
Signed-off-by: Javier Martinez Canillas <javier@dowhile0.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield
Cristian Iorga
Saul Wold
Paul Eggleton
Richard Purdie
Christopher Larson
Tom Zanussi
Liang Li
Matthew McClintock
Khem Raj
Radu Moisan
Javier Martinez Canillas