Add perf_probe_event__copy() to copy perf_probe_event
data structure and sub data structures under given source
perf_probe_event.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
Introduce perf_cache object and interfaces to create,
add entry, commit, and delete the object.
perf_cache represents a file for the cached perf-probe
definitions on one binary file or vmlinux which has its
own build id. The probe cache file is located under the
build-id cache directory of the
Recover and export synthesize_perf_probe_point() which had
once introduced but disabled long time. This renew the
code and re-enable it.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
Fix to add a NULL check for strndup when parsing
probe trace command.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "perf probe: Allow wildcard for cached events"
---
tools/perf/util/probe-event.c |4
1 file changed, 4 insertions(+)
diff
Fix to add a NULL check for strndup when parsing
probe trace command.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "perf probe: Allow wildcard for cached events"
---
tools/perf/util/probe-event.c |4
1 file changed, 4 insertions(+)
diff --git
Add perf_probe_event__copy() to copy perf_probe_event
data structure and sub data structures under given source
perf_probe_event.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/probe-event.c | 76
Introduce perf_cache object and interfaces to create,
add entry, commit, and delete the object.
perf_cache represents a file for the cached perf-probe
definitions on one binary file or vmlinux which has its
own build id. The probe cache file is located under the
build-id cache directory of the
Recover and export synthesize_perf_probe_point() which had
once introduced but disabled long time. This renew the
code and re-enable it.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/probe-event.c |
From: Masami Hiramatsu
Add --cache option to cache the probe definitions. This
just saves the result of the dwarf analysis to probe cache.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Rename and export build_id_cache__cachedir() for retrieving
use of the path of cache directory for given build_id.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/build-id.c | 12
From: Masami Hiramatsu
Add --cache option to cache the probe definitions. This
just saves the result of the dwarf analysis to probe cache.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Changes in v11:
- Check failure of probe_cache operations and warn it.
Changes in
Rename and export build_id_cache__cachedir() for retrieving
use of the path of cache directory for given build_id.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/build-id.c | 12 +---
Hi,
Resend: Sorry, I missed some last patches...
Here is the 11th version of the patchset for probe-cache and
initial SDT support.
Here is the previous v10: https://lkml.org/lkml/2016/6/8/318
And v9: https://lkml.org/lkml/2016/5/28/103
This version fixes some bugs and changes codes according
Hi,
Resend: Sorry, I missed some last patches...
Here is the 11th version of the patchset for probe-cache and
initial SDT support.
Here is the previous v10: https://lkml.org/lkml/2016/6/8/318
And v9: https://lkml.org/lkml/2016/5/28/103
This version fixes some bugs and changes codes according
Fix rm_rf() to handle non-regular files correctly. This fix
includes two changes;
- Fix to use lstat(3) instead of stat(3) since if the target
file is a symbolic link, rm_rf() should unlink the symbolic
link itself, not the file which pointed by the symlink.
- Fix to unlink non-regular
Fix rm_rf() to handle non-regular files correctly. This fix
includes two changes;
- Fix to use lstat(3) instead of stat(3) since if the target
file is a symbolic link, rm_rf() should unlink the symbolic
link itself, not the file which pointed by the symlink.
- Fix to unlink non-regular
Add perf_probe_event__copy() to copy perf_probe_event
data structure and sub data structures under given source
perf_probe_event.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
Add perf_probe_event__copy() to copy perf_probe_event
data structure and sub data structures under given source
perf_probe_event.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/probe-event.c | 76
It used to be the case that state had an rwlock that was locked for write
by downgrades, but for read for upgrades (opens). Well, the problem is
if there are two competing opens for the same state, they step on
each other toes potentially leading to leaking file descriptors
from the state
It used to be the case that state had an rwlock that was locked for write
by downgrades, but for read for upgrades (opens). Well, the problem is
if there are two competing opens for the same state, they step on
each other toes potentially leading to leaking file descriptors
from the state
To avoid racing entry into nfs4_get_vfs_file().
Make init_open_stateid() return with locked stateid to be unlocked
by the caller.
Signed-off-by: Oleg Drokin
---
fs/nfsd/nfs4state.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git
To avoid racing entry into nfs4_get_vfs_file().
Make init_open_stateid() return with locked stateid to be unlocked
by the caller.
Signed-off-by: Oleg Drokin
---
fs/nfsd/nfs4state.c | 16 +---
1 file changed, 13 insertions(+), 3 deletions(-)
diff --git a/fs/nfsd/nfs4state.c
Allo glob wildcard for reusing cached/SDT events. E.g.
# perf probe -x /usr/lib64/libc-2.20.so -a %sdt_libc:\*
This example adds probes for all SDT in libc.
Note that the SDTs must have been scanned by perf buildid-cache.
Signed-off-by: Masami Hiramatsu
---
Changes in
Allo glob wildcard for reusing cached/SDT events. E.g.
# perf probe -x /usr/lib64/libc-2.20.so -a %sdt_libc:\*
This example adds probes for all SDT in libc.
Note that the SDTs must have been scanned by perf buildid-cache.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Split off
From: Masami Hiramatsu
To improbe usability, support %[PROVIDER:]SDTEVENT format to
add new probes on SDT and cached events.
e.g.
# perf probe -x /lib/libc-2.17.so %lll_lock_wait_private
Added new event:
sdt_libc:lll_lock_wait_private (on
From: Masami Hiramatsu
To improbe usability, support %[PROVIDER:]SDTEVENT format to
add new probes on SDT and cached events.
e.g.
# perf probe -x /lib/libc-2.17.so %lll_lock_wait_private
Added new event:
sdt_libc:lll_lock_wait_private (on %lll_lock_wait_private in
Support @BUILDID or @FILE suffix for SDT events. This allows
perf to add probes on SDTs/pre-cached events on given FILE
or the file which has given BUILDID (also, this complements
BUILDID.)
For example, both gcc and libstdc++ has same SDTs as below.
If you would like to add a probe on
Search SDT/cached event from all probe caches if user doesn't
pass any binary. With this, we don't have to specify target
binary for SDT and named cached events (which start with %).
E.g. without this, a target binary must be passed with -x.
# perf probe -x /usr/lib64/libc-2.20.so -a
Add for_each_probe_cache_entry() wrapper macro
for hiding list in probe_cache.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splitted from "perf probe: Allow wildcard for cached events"
---
tools/perf/util/probe-file.c |8
Support @BUILDID or @FILE suffix for SDT events. This allows
perf to add probes on SDTs/pre-cached events on given FILE
or the file which has given BUILDID (also, this complements
BUILDID.)
For example, both gcc and libstdc++ has same SDTs as below.
If you would like to add a probe on
Search SDT/cached event from all probe caches if user doesn't
pass any binary. With this, we don't have to specify target
binary for SDT and named cached events (which start with %).
E.g. without this, a target binary must be passed with -x.
# perf probe -x /usr/lib64/libc-2.20.so -a
Add for_each_probe_cache_entry() wrapper macro
for hiding list in probe_cache.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splitted from "perf probe: Allow wildcard for cached events"
---
tools/perf/util/probe-file.c |8
tools/perf/util/probe-file.h |2 ++
2 files
From: Masami Hiramatsu
Show SDT and pre-cached events by perf-list with "sdt". This also
shows the binary and build-id where the events are placed only
when there are same name events on different binaries.
e.g.
# perf list sdt
List of pre-defined
From: Masami Hiramatsu
perf buildid-cache --add scans given binary and add
the SDT events to probe cache. "sdt_" prefix is appended for
all SDT providers to avoid event-name clash with other pre-defined
events. It is possible to use the cached SDT events as
From: Masami Hiramatsu
Allow user to set group name for adding new event.
Note that user must ensure that the group name doesn't
conflict with existing group name carefully.
E.g. Existing group name can conflict with other events.
Especially, using the group name
From: Masami Hiramatsu
Skip SDTs placed in invalid (non-exist, or older version)
binaries. Note that perf-probe --cache --list and
perf-probe --cache --del still handle all the caches
including invalid binaries.
Signed-off-by: Masami Hiramatsu
From: Masami Hiramatsu
Show SDT and pre-cached events by perf-list with "sdt". This also
shows the binary and build-id where the events are placed only
when there are same name events on different binaries.
e.g.
# perf list sdt
List of pre-defined events (to be used in -e):
From: Masami Hiramatsu
perf buildid-cache --add scans given binary and add
the SDT events to probe cache. "sdt_" prefix is appended for
all SDT providers to avoid event-name clash with other pre-defined
events. It is possible to use the cached SDT events as other cached
events, via perf probe
From: Masami Hiramatsu
Allow user to set group name for adding new event.
Note that user must ensure that the group name doesn't
conflict with existing group name carefully.
E.g. Existing group name can conflict with other events.
Especially, using the group name reserved for kernel
modules can
From: Masami Hiramatsu
Skip SDTs placed in invalid (non-exist, or older version)
binaries. Note that perf-probe --cache --list and
perf-probe --cache --del still handle all the caches
including invalid binaries.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Changes in
From: Hemant Kumar
This patch serves the initial support to identify and list SDT events in
binaries.
When programs containing SDT markers are compiled, gcc with the help of
assembler
directives identifies them and places them in the section ".note.stapsdt". To
find
From: Masami Hiramatsu
perf-probe --del removes caches when --cache is given.
Note that the delete pattern is not same as normal events.
If you cached probes with event name, --del "eventname"
works as expected. However, if you skipped it, the cached
probes
From: Masami Hiramatsu
perf probe --list shows all cached probes when --cache
is given. Each caches are shown with on which binary that
probed. e.g.
-
# perf probe --cache vfs_read \$params
# perf probe --cache -x /lib64/libc-2.17.so getaddrinfo
From: Masami Hiramatsu
Before analyzing debuginfo, try to find a corresponding entry
from probe cache always. This does not depend on --cache,
the --cache enables to store/update cache, but looking up
the cache is always enabled.
Signed-off-by: Masami Hiramatsu
From: Masami Hiramatsu
perf-probe --del removes caches when --cache is given.
Note that the delete pattern is not same as normal events.
If you cached probes with event name, --del "eventname"
works as expected. However, if you skipped it, the cached
probes doesn't have actual event name. In
From: Masami Hiramatsu
perf probe --list shows all cached probes when --cache
is given. Each caches are shown with on which binary that
probed. e.g.
-
# perf probe --cache vfs_read \$params
# perf probe --cache -x /lib64/libc-2.17.so getaddrinfo \$params
# perf probe --cache --list
From: Hemant Kumar
This patch serves the initial support to identify and list SDT events in
binaries.
When programs containing SDT markers are compiled, gcc with the help of
assembler
directives identifies them and places them in the section ".note.stapsdt". To
find
these markers from the
From: Masami Hiramatsu
Before analyzing debuginfo, try to find a corresponding entry
from probe cache always. This does not depend on --cache,
the --cache enables to store/update cache, but looking up
the cache is always enabled.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
Hi Richard,
On Tue, 14 Jun 2016 19:04:44 +0200, Richard Cochran write:
>> Well, I guess I should have said, I am not too familiar with the
>> breadth of current audio hardware, high end or low end. Of course I
>> would like to see even consumer devices work with AVB, but it is up to
>> the ALSA
Fix to add a NULL check for strndup when parsing
probe trace command.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "perf probe: Allow wildcard for cached events"
---
tools/perf/util/probe-event.c |4
1 file changed, 4 insertions(+)
diff
Rename and export build_id_cache__cachedir() for retrieving
use of the path of cache directory for given build_id.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/build-id.c | 12
Fix rm_rf() to handle non-regular files correctly. This fix
includes two changes;
- Fix to use lstat(3) instead of stat(3) since if the target
file is a symbolic link, rm_rf() should unlink the symbolic
link itself, not the file which pointed by the symlink.
- Fix to unlink non-regular
Move the state selection logic inside from the caller,
always making it return correct stp to use.
Signed-off-by: J . Bruce Fields
Signed-off-by: Oleg Drokin
---
fs/nfsd/nfs4state.c | 27 ---
1 file changed, 12 insertions(+),
From: Masami Hiramatsu
Add --cache option to cache the probe definitions. This
just saves the result of the dwarf analysis to probe cache.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Hi Richard,
On Tue, 14 Jun 2016 19:04:44 +0200, Richard Cochran write:
>> Well, I guess I should have said, I am not too familiar with the
>> breadth of current audio hardware, high end or low end. Of course I
>> would like to see even consumer devices work with AVB, but it is up to
>> the ALSA
Fix to add a NULL check for strndup when parsing
probe trace command.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "perf probe: Allow wildcard for cached events"
---
tools/perf/util/probe-event.c |4
1 file changed, 4 insertions(+)
diff --git
Rename and export build_id_cache__cachedir() for retrieving
use of the path of cache directory for given build_id.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/build-id.c | 12 +---
Fix rm_rf() to handle non-regular files correctly. This fix
includes two changes;
- Fix to use lstat(3) instead of stat(3) since if the target
file is a symbolic link, rm_rf() should unlink the symbolic
link itself, not the file which pointed by the symlink.
- Fix to unlink non-regular
Move the state selection logic inside from the caller,
always making it return correct stp to use.
Signed-off-by: J . Bruce Fields
Signed-off-by: Oleg Drokin
---
fs/nfsd/nfs4state.c | 27 ---
1 file changed, 12 insertions(+), 15 deletions(-)
diff --git
From: Masami Hiramatsu
Add --cache option to cache the probe definitions. This
just saves the result of the dwarf analysis to probe cache.
Signed-off-by: Masami Hiramatsu
Signed-off-by: Masami Hiramatsu
---
Changes in v11:
- Check failure of probe_cache operations and warn it.
Changes in
These three patches do the much discussed job of making nfsd state handling
more robust in face of races where several opens arrive for the same file
at the same time from the same client.
This does not yet handle a case when one of those opens gets an error
and others don't.
Also this is
Introduce perf_cache object and interfaces to create,
add entry, commit, and delete the object.
perf_cache represents a file for the cached perf-probe
definitions on one binary file or vmlinux which has its
own build id. The probe cache file is located under the
build-id cache directory of the
Recover and export synthesize_perf_probe_point() which had
once introduced but disabled long time. This renew the
code and re-enable it.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
These three patches do the much discussed job of making nfsd state handling
more robust in face of races where several opens arrive for the same file
at the same time from the same client.
This does not yet handle a case when one of those opens gets an error
and others don't.
Also this is
Introduce perf_cache object and interfaces to create,
add entry, commit, and delete the object.
perf_cache represents a file for the cached perf-probe
definitions on one binary file or vmlinux which has its
own build id. The probe cache file is located under the
build-id cache directory of the
Recover and export synthesize_perf_probe_point() which had
once introduced but disabled long time. This renew the
code and re-enable it.
Signed-off-by: Masami Hiramatsu
---
Changes in v10:
- Splited from "Add --cache option to cache the probe definitions"
---
tools/perf/util/probe-event.c |
Hi,
Here is the 11th version of the patchset for probe-cache and
initial SDT support.
Here is the previous v10: https://lkml.org/lkml/2016/6/8/318
And v9: https://lkml.org/lkml/2016/5/28/103
This version fixes some bugs and changes codes according to
Arnaldo's comments.
Changes in v11:
-
Hi,
Here is the 11th version of the patchset for probe-cache and
initial SDT support.
Here is the previous v10: https://lkml.org/lkml/2016/6/8/318
And v9: https://lkml.org/lkml/2016/5/28/103
This version fixes some bugs and changes codes according to
Arnaldo's comments.
Changes in v11:
-
Hi Heiko,
On 2016/6/14 21:27, Heiko Stübner wrote:
Am Montag, 13. Juni 2016, 10:10:10 schrieb Frank Wang:
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is
Hi Heiko,
On 2016/6/14 21:27, Heiko Stübner wrote:
Am Montag, 13. Juni 2016, 10:10:10 schrieb Frank Wang:
The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
than rk3288 and before, and most of phy-related registers are also
different from the past, so a new phy driver is
Hi Richard,
> On Mon, Jun 13, 2016 at 01:47:13PM +0200, Richard Cochran wrote:
>> 3. ALSA support for tunable AD/DA clocks. The rate of the Listener's
>>DA clock must match that of the Talker and the other Listeners.
>>Either you adjust it in HW using a VCO or similar, or you do
>>
Hi Richard,
> On Mon, Jun 13, 2016 at 01:47:13PM +0200, Richard Cochran wrote:
>> 3. ALSA support for tunable AD/DA clocks. The rate of the Listener's
>>DA clock must match that of the Talker and the other Listeners.
>>Either you adjust it in HW using a VCO or similar, or you do
>>
Dave Hansen wrote:
> On 06/14/2016 01:16 PM, Nadav Amit wrote:
>> Dave Hansen wrote:
>>
>>> On 06/14/2016 09:47 AM, Nadav Amit wrote:
Lukasz Anaczkowski wrote:
>> From: Andi Kleen
Dave Hansen wrote:
> On 06/14/2016 01:16 PM, Nadav Amit wrote:
>> Dave Hansen wrote:
>>
>>> On 06/14/2016 09:47 AM, Nadav Amit wrote:
Lukasz Anaczkowski wrote:
>> From: Andi Kleen
>> +void fix_pte_leak(struct mm_struct *mm, unsigned long addr, pte_t *ptep)
>> +{
Hi all,
An update is overdue so here it is.
It's mostly a bug fix update.
autofs
==
The package can be found at:
ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5
It is autofs-5.1.2.tar.[gz|xz]
No source rpm is there as it can be produced by using:
rpmbuild -ts autofs-5.1.2.tar.gz
and
Hi all,
An update is overdue so here it is.
It's mostly a bug fix update.
autofs
==
The package can be found at:
ftp://ftp.kernel.org/pub/linux/daemons/autofs/v5
It is autofs-5.1.2.tar.[gz|xz]
No source rpm is there as it can be produced by using:
rpmbuild -ts autofs-5.1.2.tar.gz
and
>From 48552e96e4e33f8830cb6a59154fe148425532fd Mon Sep 17 00:00:00 2001
From: Chunfeng Yun
Date: Wed, 15 Jun 2016 10:58:10 +0800
Subject: [PATCH v4,0/5] Add MediaTek USB3 DRD Driver
These patches introduce the MediaTek USB3 dual-role controller
driver.
The driver can
add a DT binding doc for MediaTek USB3 DRD driver
Signed-off-by: Chunfeng Yun
---
.../devicetree/bindings/usb/mt8173-mtu3.txt| 86
1 file changed, 86 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/mt8173-mtu3.txt
Some resources, such as IPPC register etc, shared with device
driver are moved into common glue layer when xHCI driver is the
host side of dual-role mode and they should be changed as optional
properties if they are required ones before. For clarity, add
a new part of binding to support host side
>From 48552e96e4e33f8830cb6a59154fe148425532fd Mon Sep 17 00:00:00 2001
From: Chunfeng Yun
Date: Wed, 15 Jun 2016 10:58:10 +0800
Subject: [PATCH v4,0/5] Add MediaTek USB3 DRD Driver
These patches introduce the MediaTek USB3 dual-role controller
driver.
The driver can be configured as Dual-Role
add a DT binding doc for MediaTek USB3 DRD driver
Signed-off-by: Chunfeng Yun
---
.../devicetree/bindings/usb/mt8173-mtu3.txt| 86
1 file changed, 86 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/mt8173-mtu3.txt
diff --git
Some resources, such as IPPC register etc, shared with device
driver are moved into common glue layer when xHCI driver is the
host side of dual-role mode and they should be changed as optional
properties if they are required ones before. For clarity, add
a new part of binding to support host side
On Tue, Jun 14, 2016 at 7:44 PM, Nadav Amit wrote:
> Andy Lutomirski wrote:
>
>> On Tue, Jun 14, 2016 at 7:35 PM, Nadav Amit wrote:
>>> Andy Lutomirski wrote:
>>>
On Tue, Jun 14, 2016 at 2:37 PM, Dave
On Tue, Jun 14, 2016 at 7:44 PM, Nadav Amit wrote:
> Andy Lutomirski wrote:
>
>> On Tue, Jun 14, 2016 at 7:35 PM, Nadav Amit wrote:
>>> Andy Lutomirski wrote:
>>>
On Tue, Jun 14, 2016 at 2:37 PM, Dave Hansen
wrote:
> On 06/14/2016 01:16 PM, Nadav Amit wrote:
>> Dave Hansen
Make IPPC register optional to support host side of dual-role mode,
due to it is moved into common glue layer for simplification.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 32 +++-
1 file changed, 27 insertions(+), 5
USB3 DRD driver is added for MT8173-EVB, and xHCI driver
becomes its subnode
Signed-off-by: Chunfeng Yun
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 46 +--
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 28
2 files
Make IPPC register optional to support host side of dual-role mode,
due to it is moved into common glue layer for simplification.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 32 +++-
1 file changed, 27 insertions(+), 5 deletions(-)
diff --git
USB3 DRD driver is added for MT8173-EVB, and xHCI driver
becomes its subnode
Signed-off-by: Chunfeng Yun
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 46 +--
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 28
2 files changed, 65 insertions(+), 9
This patch adds support for the MediaTek USB3 controller
integrated into MT8173. It can be configured as Dual-Role
Device (DRD), Peripheral Only and Host Only (xHCI) modes.
Signed-off-by: Chunfeng Yun
---
drivers/usb/Kconfig|2 +
This patch adds support for the MediaTek USB3 controller
integrated into MT8173. It can be configured as Dual-Role
Device (DRD), Peripheral Only and Host Only (xHCI) modes.
Signed-off-by: Chunfeng Yun
---
drivers/usb/Kconfig|2 +
drivers/usb/Makefile |1 +
> > This may also possibly help to save cycles due to high usage and
> > contention when using a generic kmem_cache (when they stay separate
> > from others, thanks for the precision!).
>
> Have you measured this?
>
> This isn't applicable for 4.7-rc at this time, _unless_ it fixes a bug,
>
> > This may also possibly help to save cycles due to high usage and
> > contention when using a generic kmem_cache (when they stay separate
> > from others, thanks for the precision!).
>
> Have you measured this?
>
> This isn't applicable for 4.7-rc at this time, _unless_ it fixes a bug,
>
On Tue, Jun 14, 2016 at 01:08:08PM +0200, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 3:04:27 AM CEST kbuild test robot wrote:
> > >> drivers/usb/core/of.c:32:21: error: redefinition of
> > >> 'usb_of_get_child_node'
> > struct device_node *usb_of_get_child_node(struct device_node
On Tue, Jun 14, 2016 at 01:08:08PM +0200, Arnd Bergmann wrote:
> On Wednesday, June 8, 2016 3:04:27 AM CEST kbuild test robot wrote:
> > >> drivers/usb/core/of.c:32:21: error: redefinition of
> > >> 'usb_of_get_child_node'
> > struct device_node *usb_of_get_child_node(struct device_node
Andy Lutomirski wrote:
> On Tue, Jun 14, 2016 at 7:35 PM, Nadav Amit wrote:
>> Andy Lutomirski wrote:
>>
>>> On Tue, Jun 14, 2016 at 2:37 PM, Dave Hansen
>>> wrote:
On 06/14/2016 01:16 PM, Nadav
Andy Lutomirski wrote:
> On Tue, Jun 14, 2016 at 7:35 PM, Nadav Amit wrote:
>> Andy Lutomirski wrote:
>>
>>> On Tue, Jun 14, 2016 at 2:37 PM, Dave Hansen
>>> wrote:
On 06/14/2016 01:16 PM, Nadav Amit wrote:
> Dave Hansen wrote:
>
>> On 06/14/2016 09:47 AM, Nadav Amit
On Tue, Jun 14 2016 at 10:30pm -0400,
Martin K. Petersen wrote:
> > "Mike" == Mike Snitzer writes:
>
> Mike,
>
> Mike> so long story short: making this change to remove this so-called
> Mike> "stupid behaviour" will require code like
> Mike>
On Tue, Jun 14 2016 at 10:30pm -0400,
Martin K. Petersen wrote:
> > "Mike" == Mike Snitzer writes:
>
> Mike,
>
> Mike> so long story short: making this change to remove this so-called
> Mike> "stupid behaviour" will require code like
> Mike> drivers/md/dm-thin.c:issue_discard(() to check
On Tue, Jun 14, 2016 at 2:05 PM, Winkler, Tomas wrote:
wrote:
> Few storage technology such is EMMC, UFS, and NVMe support RPMB
>hardware partition with common protocol and frame layout.
> The RPMB partition cannot be accessed via standard block layer,
On Tue, Jun 14, 2016 at 2:05 PM, Winkler, Tomas wrote:
wrote:
> Few storage technology such is EMMC, UFS, and NVMe support RPMB
>hardware partition with common protocol and frame layout.
> The RPMB partition cannot be accessed via standard block layer, but
>by a set of
101 - 200 of 2110 matches
Mail list logo