Hi Jens,
On 10/21/2015 03:20 AM, Kilian, Jens wrote:
> I'd like to use a version of wait_event_killable() with a timeout, but it
> seems to be missing? I found a mention of it in a recent LKML message though:
>
> https://lkml.org/lkml/2015/10/14/337
>
> Does this patch look reasonable?
Non-MMU systems fail to build with
In file included from init/main.c:50:0:
include/linux/rmap.h:274:1: error:
expected declaration specifiers or ‘...’ before ‘{’ token
Fixes: c3f568752340 ("mm: support madvise(MADV_FREE)")
Cc: Minchan Kim
Signed-off-by: Guenter Roeck
---
Hi,
i wrote:
> > Truncation nowadays has to take into respect that UTF-8 may
> > consist of multiple bytes and should avoid to leave incomplete
> > byte sequences.
> > (Does the kernel have a function for this ?)
Jan Kara wrote:
> Well, such truncation function would have to be specific to
发自我的 iPhone
> 在 2015年10月21日，下午9:49，Peter Zijlstra 写道：
>
>> On Wed, Oct 21, 2015 at 09:42:12PM +0800, Wangnan (F) wrote:
>> How can an eBPF program access a !local event:
>>
>> when creating perf event array we don't care which perf event
>> is for which CPU, so perf program can access any
AUF DEINE ANTWORT WARTEND
Ich bin mit diesem Medium, um Sie über die Transaktion zur Abgabe von
$ 2150 (einundzwanzig Millionen fünfhunderttausend US-Dollar) auf meinem
Bank in China, Sie als Empfänger zu informieren. Es ist 100% sicher, wobei der
Finanzvorstand des verstorbenen
On 10/21/2015 06:36 AM, Arnd Bergmann wrote:
> On Wednesday 21 October 2015 18:30:05 Masahiro Yamada wrote:
>>>
I am trying to implement OF_EARLYCON_DECLARE() for that.
I was just wondering if console_initcall() should work as well.
As I said, I noticed the
On Wed, Oct 21, 2015 at 09:42:12PM +0800, Wangnan (F) wrote:
> How can an eBPF program access a !local event:
>
> when creating perf event array we don't care which perf event
> is for which CPU, so perf program can access any perf event in
> that array.
So what is stopping the eBPF thing from
Thomas,
On Tue, 20 Oct 2015 21:23:29 +0200 (CEST), Thomas Gleixner wrote:
> On Tue, 20 Oct 2015, Thomas Petazzoni wrote:
> > As discussed on IRC, another simpler (code line wise) solution is to
> > simply clear the IRQ_NOAUTOEN flag in the irq-armada-370-xp, which
> > brings us back to what
Commit d17cab4451df1 ("irqchip: Kill off set_irq_flags usage") changed
the code of armada_370_xp_mpic_irq_map() from using set_irq_flags() to
irq_set_probe().
While the commit log seems to imply that there are no functional
changes, there are indeed functional changes introduced by this
commit:
On Wed, 2015-10-21 at 16:18 +0300, Dāvis Mosāns wrote:
> 2015-10-21 10:33 GMT+03:00 Johannes Thumshirn :
> > On Tue, 2015-10-20 at 20:41 +0300, Dāvis Mosāns wrote:
> > > 2015-08-21 7:29 GMT+03:00 Dāvis Mosāns :
> > > > When pci_pool_alloc fails in mvs_task_prep then task->lldd_task
> > > > stays
>
Em Wed, Oct 21, 2015 at 10:43:48AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Oct 21, 2015 at 10:48:16AM +0200, Ingo Molnar escreveu:
> > 5) --no-children
> >
> > I agree that 'perf top -g --no-children' looks more intuitive than 'perf
> > top -g'.
>
> So, what do you propose, to
You have Been Issued with the SUM of 1.1 Million Euro from the Weir Family
Donation.Kindly get in Touch with your details Following:
Full Names ... Address: Phone No: Country ... Age ..
Check Link HTTP://www.bbc.com/news/uk-scotland-glasgow-west-18801698
We await your reply.
Chris and
On Tue, Oct 20, 2015 at 11:46:37AM -0700, Andi Kleen wrote:
> +++ b/arch/x86/kernel/cpu/perf_event_intel.c
> @@ -2844,7 +2844,7 @@ static void intel_pmu_cpu_starting(int cpu)
> /*
>* Deal with CPUs that don't clear their LBRs on power-up.
>*/
> - intel_pmu_lbr_reset();
>
On Wed, Oct 21, 2015 at 12:54 AM, Scott Wood wrote:
> On Mon, 2015-09-21 at 16:03 +0200, Tomeu Vizoso wrote:
>> Instead of trying to match and probe platform and AMBA devices right
>> after each is registered, delay their probes until device_initcall_sync.
>>
>> This means that devices will start
On 2015/10/21 20:17, Peter Zijlstra wrote:
On Wed, Oct 21, 2015 at 07:49:34PM +0800, Wangnan (F) wrote:
If our task is sampling cycle events during a function is running,
and if two cores start that function overlap:
Time: ...A
Core 0: sys_write\
In some cases, we could start a new i2c transfer with the RXRDY flag
set. It is not a clean state and it leads to print annoying error
messages even if there no real issue. The cause is only having garbage
data in the Receive Holding Register because of a weird behavior of the
RXRDY flag.
From: Cyrille Pitchen
In some cases a NACK interrupt may be pending in the Status Register (SR)
as a result of a previous transfer. However at91_do_twi_transfer() did not
read the SR to clear pending interruptions before starting a new transfer.
Hence a NACK interrupt rose as soon as it was
Em Wed, Oct 21, 2015 at 10:48:16AM +0200, Ingo Molnar escreveu:
>
> * Arnaldo Carvalho de Melo wrote:
>
> > I was bitten by the --children thing and took some time to get used to it,
> > so I
> > can relate to that...
> >
> > I think we should revert this change in callchain default, enough
From: Rasmus Villemoes
The kernel now has kstrdup_const/kfree_const for reusing .rodata
(typically string literals) when possible; there's no reason to
duplicate that logic in the tracing system. Moreover, as the comment
above core_kernel_data states, it may not always return true for
.rodata -
From: Dmitry Safonov <0x7f454...@gmail.com>
Extend module command for function filter selection with globbing.
It uses the same globbing as function filter.
sh# echo '*alloc*:mod:*' > set_ftrace_filter
Will trace any function with the letters 'alloc' in the name in any
module but not in
Christoph Hellwig writes:
> Jens, Ming:
>
> are you fine with the one liner change to get back to the old I/O
> pattern? While it looks like the cards fault I'd like to avoid this
> annoying regression.
I'm not Jens or Ming, but your patch looks fine to me, though you'll
want to remove the
From: Tal Shorer
Allow a trace events header file to disable compilation of its
trace events by defining the preprocessor macro NOTRACE.
This could be done, for example, according to a Kconfig option.
Link:
http://lkml.kernel.org/r/1438432079-11704-3-git-send-email-tal.sho...@gmail.com
From: Tal Shorer
Add a new options to trace Kconfig, CONFIG_TRACING_EVENTS_GPIO, that is
used for enabling/disabling compilation of gpio function trace events.
Link:
http://lkml.kernel.org/r/1438432079-11704-4-git-send-email-tal.sho...@gmail.com
Acked-by: Linus Walleij
Signed-off-by: Tal
From: Dmitry Safonov <0x7f454...@gmail.com>
ftrace_match parameters are very related and I reduce the number of local
variables & parameters with it.
This is also preparation for module globbing as it would introduce more
realated variables & parameters.
Link:
From: Dmitry Safonov <0x7f454...@gmail.com>
By now there isn't any subcommand for mod.
Before:
sh$ echo '*:mod:ipv6:a' > set_ftrace_filter
sh$ echo '*:mod:ipv6' > set_ftrace_filter
had the same results, but now first will result in:
sh$ echo '*:mod:ipv6:a' >
From: Dmitry Safonov <0x7f454...@gmail.com>
Link:
http://lkml.kernel.org/r/1443545176-3215-5-git-send-email-0x7f454...@gmail.com
Signed-off-by: Dmitry Safonov <0x7f454...@gmail.com>
Signed-off-by: Steven Rostedt
---
Documentation/trace/ftrace.txt | 17 +
1 file changed, 17
From: Dmitry Safonov <0x7f454...@gmail.com>
"Not" is too abstract variable name - changed to clear_filter.
Removed ftrace_match_module_records function: comparison with !* or *
not does the general code in filter_parse_regex() as it works without
mod command for
sh# echo '!*' >
From: Rasmus Villemoes
To cover the common case of sorting an array of pointers, Daniel
Wagner recently modified the library sort() to use a specific swap
function for size==8, in addition to the size==4 case which was
already handled. Since sizeof(long) is either 4 or 8,
ftrace_swap_ips() is
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: ddd70280bf0e92ad81a9526971409603fba21679
Dmitry Safonov (5):
ftrace: Remove redundant strsep in mod_callback
ftrace: Clarify code for mod command
ftrace: Introduce ftrace_glob structure
Caesar,
On Tue, Oct 20, 2015 at 9:42 PM, Caesar Wang wrote:
> I think the description is right, maybe need other decriptions.
> The tshut polarity is low in a short period of time when the TSADC
> controller is reset.
>
> In other words,
>
> If T < (setting temperature), the OTP output the
Hi Jie,
[auto build test ERROR on asoc/for-next -- if it's inappropriate base, please
suggest rules for selecting the more suitable base]
url:
https://github.com/0day-ci/linux/commits/Jie-Yang/ASoC-Intel-sst-only-use-sst-firmware-when-DW-DMAC-is-available/20151021-203247
config: i386
On 21 October 2015 at 15:24, Borislav Petkov wrote:
> On Wed, Oct 21, 2015 at 02:57:47PM +0200, Ard Biesheuvel wrote:
>> ... For the remaining cases, which is the vast majority, no such
>> assumptions can be made, and since the UEFI runtime regions are
>> typically populated with a bunch of
Em Wed, Oct 21, 2015 at 11:31:57AM +0800, Wangnan (F) escreveu:
>
>
> On 2015/10/21 3:12, Arnaldo Carvalho de Melo wrote:
> >Em Wed, Oct 14, 2015 at 12:41:15PM +, Wang Nan escreveu:
> >>This patch introduces bpf__{un,}probe() functions to enable callers to
> >>create kprobe points based on
On Tue, Oct 20, 2015 at 11:46:35AM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Automatically disable collecting branch flags and cycles with
> --call-graph lbr. This allows avoiding a bunch of extra MSR
> reads in the PMI on Skylake.
>
> When the kernel doesn't support the new flags they
Hi Greg,
> On Oct 21, 2015, at 00:03 , Greg Kroah-Hartman
> wrote:
>
> On Tue, Oct 20, 2015 at 10:13:14PM +0300, Pantelis Antoniou wrote:
>> We are going to need the overlays to appear on sysfs with runtime
>> global properties (like master enable) so turn them into kobjects.
>
> Why kobjects
From: Heiko Schocher
Date: Sat, 17 Oct 2015 06:04:34 +0200
> On some boards the energy enable detect mode leads in
> trouble with some switches, so make the enabling of
> this mode configurable through DT.
> Therefore the property "smsc,disable-energy-detect" is
> introduced.
>
> Patch 1
Em Wed, Oct 21, 2015 at 10:21:36AM +0900, Namhyung Kim escreveu:
> On Tue, Oct 20, 2015 at 03:44:04PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Oct 20, 2015 at 07:21:16PM +0200, Frederic Weisbecker escreveu:
> > > On Tue, Oct 20, 2015 at 10:06:51AM -0300, Arnaldo Carvalho de Melo wrote:
>
On Wed, Oct 21, 2015 at 02:57:47PM +0200, Ard Biesheuvel wrote:
> ... For the remaining cases, which is the vast majority, no such
> assumptions can be made, and since the UEFI runtime regions are
> typically populated with a bunch of PE/COFF images (each of which
> consists of text + data),
From: Nikesh Oswal
A binary search is much more efficient rather than iterating
over the rbtree in ascending order which the current code is
doing.
During initialisation the reg defaults are written to the
cache in a large chunk and these are always sorted in the
ascending order so for this
On 2015-10-21 09:19, Austin S Hemmelgarn wrote:
Hmm, dm-de...@redhat.org seems to have bounced for me. Any ideas why
RedHat would be blocking inbound mail from Google's mail servers?
On 2015-10-20 11:12, Austin S Hemmelgarn wrote:
I think I've stumbled upon a bug in DM-RAID. The primary
On Wed, Oct 21, 2015 at 01:51:24AM +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> The correct scope for looking up the objects to generate data packages for
> data-only subnodes pointed to by another data-only subnode is the scope
> of the parent of that subnode and not the scope
Em Wed, Oct 21, 2015 at 10:06:45AM +0200, Ingo Molnar escreveu:
> * Arnaldo Carvalho de Melo wrote:
> > Indeed, finding a default that is deemed adequate for most people is,
> > ho-hum,
> > difficult 8-)
> > Ingo, what do you think?
> So I think the new default is a lot more intuitive,
Em Wed, Oct 21, 2015 at 11:25:25AM +0200, Ingo Molnar escreveu:
> * Peter Zijlstra wrote:
> > On Tue, Oct 20, 2015 at 05:25:07PM -0300, Arnaldo Carvalho de Melo wrote:
> > > From: Andi Kleen
> > > Add a missing field to the perf_event_attr debug output.
> > > +++ b/tools/perf/util/evsel.c
> >
Hi all,
after fixing task migrations for SCHED_DEADLINE, I started to see some
lockdep-related warnings that look like this:
[ 794.428081] WARNING: CPU: 1 PID: 0 at
/home/luca/Src/GRUB/linux-reclaiming/kernel/locking/lockdep.c:3407
lock_release+0x3f4/0x440()
[ 794.428439] releasing a pinned
On 10/21/2015 04:21 AM, Masahiro Yamada wrote:
> Hi.
>
>
>
>
> I think there are three places where console could be enabled.
>
> [1] earlycon
>
> Each driver entry is declared with
> EARLYCON_DECLARE() or OF_EARLYCON_DECLARE()
>
>
>
> [2] console_init()
>
> Each entry is declared with
On 2015-10-20 11:12, Austin S Hemmelgarn wrote:
I think I've stumbled upon a bug in DM-RAID. The primary symptom is that when
creating a new DM-RAID based device (using either LVM or dmsetup) in a RAID1
configuration, it very quickly claims one by one that all of the disks failed
except the
On 17-10-15, 09:40, Viresh Kumar wrote:
> Hehe, no.
>
> Okay here is the problem statement:
>
> We have two supplies for a device and the device node will have
> something like:
>
> name1-supply = <>;
> name2-supply = <>;
>
> And the OPP node needs to have voltages for both of them:
>
>
2015-10-21 10:33 GMT+03:00 Johannes Thumshirn :
> On Tue, 2015-10-20 at 20:41 +0300, Dāvis Mosāns wrote:
>> 2015-08-21 7:29 GMT+03:00 Dāvis Mosāns :
>> > When pci_pool_alloc fails in mvs_task_prep then task->lldd_task
>> > stays
>> > NULL but it's later used in mvs_abort_task as slot which is
On Tue, Oct 20, 2015 at 11:46:33AM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> This fixes a bug added with the earlier 90405aa02. The bug
> could lead to lost LBR call stacks. When restoring the LBR
> state we need to use the TOS of the previous context, not
> the current context. To do that
On (10/21/15 06:22), David Miller wrote:
> memcpy() _never_ works for avoiding unaligned accessed.
>
> I repeat, no matter what you do, no matter what kinds of casts or
> fancy typing you use, memcpy() _never_ works for this purpose.
:
> There is one and only one portable way to access
Hello Krzysztof,
On 10/21/2015 02:43 PM, Krzysztof Kozlowski wrote:
> 2015-10-21 17:45 GMT+09:00 Javier Martinez Canillas :
>>
>> Hello Krzysztof,
>>
>> Patch looks good to me, I've only one comment.
>>
>> On 10/21/2015 03:33 AM, Krzysztof Kozlowski wrote:
>>> Extend the Samsung Exynos maintainer
From: Sowmini Varadhan
Date: Wed, 21 Oct 2015 08:36:28 -0400
> + memcpy((u8 *)p, , sizeof(tmp));
memcpy() _never_ works for avoiding unaligned accessed.
I repeat, no matter what you do, no matter what kinds of casts or
fancy typing you use, memcpy() _never_ works for this
On Wed 21-10-15 21:26:19, Tetsuo Handa wrote:
> >From 0c50792dfa6396453c89c71351a7458b94d3e881 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Wed, 21 Oct 2015 21:15:30 +0900
> Subject: [PATCH] mm,vmscan: Use accurate values for zone_reclaimable() checks
>
> Since "struct zone"->vm_stat[]
On 2015/10/21 16:53, Namhyung Kim wrote:
Hi,
On Wed, Oct 14, 2015 at 12:41:37PM +, Wang Nan wrote:
From: He Kuang
This patch adds new bison rules for specifying an alias name to a perf
event, which allows cmdline refer to previous defined perf event through
its name. With this patch
From: Sowmini Varadhan
Date: Wed, 21 Oct 2015 06:54:42 -0400
> On (10/21/15 08:57), Steffen Klassert wrote:
>> > --- a/net/xfrm/xfrm_user.c
>> > +++ b/net/xfrm/xfrm_user.c
>> > @@ -2659,7 +2659,7 @@ static int xfrm_notify_sa(struct xfrm_state *x,
>> > const struct km_event *c)
>> >
On TI's Keystone platforms, several peripherals such as the
gbe ethernet switch, 10gbe ethernet switch and PCIe controller
require the use of a SerDes for converting SoC parallel data into
serialized data that can be output over a high-speed electrical
interface, and also converting high-speed
On 21 October 2015 at 14:49, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>>
>> * Matt Fleming wrote:
>>
>> > > > Right, we could do that, but then we wouldn't be able to support
>> > > > creation/updating variables at runtime, such as when you install a
>> > > > distribution for the first
This patch adds the serdes phy driver dts bindings
for the keystone PCIe host driver.
Signed-off-by: WingMan Kwok
---
arch/arm/boot/dts/k2e.dtsi | 10 ++
arch/arm/boot/dts/keystone.dtsi | 10 ++
2 files changed, 20 insertions(+)
diff --git a/arch/arm/boot/dts/k2e.dtsi
This patch updates the Keystone PCI driver to use the
generic Keystone serdes driver for serdes initialization
and configuration. The generic serdes driver supports
peripherals on Keystone platforms that require serdes.
Signed-off-by: WingMan Kwok
---
drivers/pci/host/pci-keystone.c | 24
On TI's Keystone platforms, several peripherals such as the
gbe ethernet switch, 10gbe ethernet switch and PCIe controller
require the use of a SerDes for converting SoC parallel data into
serialized data that can be output over a high-speed electrical
interface, and also converting high-speed
From: Steffen Klassert
Date: Wed, 21 Oct 2015 08:57:04 +0200
> On Mon, Oct 19, 2015 at 05:23:29PM -0400, Sowmini Varadhan wrote:
>> On sparc, deleting established SAs (e.g., by restarting ipsec
>> at the peer) results in unaligned access messages via
>> xfrm_del_sa -> km_state_notify ->
Hello Mark,
Am 21.10.2015 um 14:19 schrieb Mark Brown:
On Mon, Oct 19, 2015 at 08:27:13AM +0200, Heiko Schocher wrote:
--- /dev/null
+++ b/arch/arm/boot/dts/tps65023.dtsi
If this file is needed there is something broken, if this file is not
needed then it is just noise since everything in
Hi,
thanks for detailed reports. For now I did some research on the case of
file name truncation.
> ===
> "fs/isofs/rock.c coarsely truncates file names of 254 or 255 bytes length"
>
* Ingo Molnar wrote:
>
> * Matt Fleming wrote:
>
> > > > Right, we could do that, but then we wouldn't be able to support
> > > > creation/updating variables at runtime, such as when you install a
> > > > distribution for the first time, or want to boot a new kernel filename
> > > >
2015-10-21 17:45 GMT+09:00 Javier Martinez Canillas :
>
> Hello Krzysztof,
>
> Patch looks good to me, I've only one comment.
>
> On 10/21/2015 03:33 AM, Krzysztof Kozlowski wrote:
> > Extend the Samsung Exynos maintainer entry to match SoC documentation
> > and SoC dt-bindings directories.
On 21/10/15 12:13, Sudeep Holla wrote:
On 21/10/15 12:01, Ulf Hansson wrote:
On 21 October 2015 at 12:25, Sudeep Holla wrote:
[..]
Yes that was my intention for splitting the patches per SoC group.
Many SoC maintainers prefer that.
Hold on! All patches that changes the DT parsing to
Hi,
Sorry for replying so later...
From: Tom Zanussi [mailto:tom.zanu...@linux.intel.com]
>
>This is v10 of the 'hist triggers' patchset. It adds some major new
>features - 'named' hist triggers and support for multiple hist
>triggers on a single event - basically all of the features and
Can you *please* start a new thread with each posting?
This is absolutely unmanageable.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
On (10/21/15 06:54), Sowmini Varadhan wrote:
> But __alignof__(*p) is 8 on sparc, and without the patch I get
> all types of unaligned access. So what do you suggest as the fix?
Even though the alignment is, in fact, 8 (and that comes from
struct xfrm_lifetime_cfg), if uspace is firmly attached
On Wed, Oct 21, 2015 at 09:42:40AM +0200, Peter Rosin wrote:
> On 2015-10-21 09:21, Peter Rosin wrote:
> > On 2015-10-20 15:27, Ludovic Desroches wrote:
> >> On Mon, Oct 19, 2015 at 12:49:03PM +0200, Peter Rosin wrote:
> >>> On 2015-10-19 10:51, Ludovic Desroches wrote:
> Hi Peter,
>
>
On 10/20/2015 09:20 PM, Masahiro Yamada wrote:
> Hi Peter,
> (+ Rob Herring, Stefan Agner)
>
> 2015-10-20 23:00 GMT+09:00 Peter Hurley :
>> On 10/19/2015 11:36 PM, Masahiro Yamada wrote:
>>> The input clock frequency varies from device to device, but the
>>> earlycon uses the fixed frequency
Currentlly, we use Synopsys DesignWare DMA Controller for
baytrail/haswell/broadwell ADSP firmware loading, but for
skylake, we don't use it, compiling sst-firmware.c may
introduce error when CONFIG_DW_DMAC_CORE is not enabled:
sound/built-in.o: In function `sst_dma_new':
(.text+0xd7b38):
On Wed, Oct 21, 2015 at 10:53:31AM +0100, Eric Anholt wrote:
> Dave suggested it was time to just send a pull request on the driver, so
> here goes:
Given I suggested the same:
Acked-by: Daniel Vetter
>
> The following changes since commit 6ff33f3902c3b1c5d0db6b1e2c70b6d76fba357f:
>
>
>From 0c50792dfa6396453c89c71351a7458b94d3e881 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Wed, 21 Oct 2015 21:15:30 +0900
Subject: [PATCH] mm,vmscan: Use accurate values for zone_reclaimable() checks
Since "struct zone"->vm_stat[] is array of atomic_long_t, an attempt
to reduce frequency
On 2015年10月21日 00:46, Randy Dunlap wrote:
On 10/19/15 22:26, Stephen Rothwell wrote:
Hi all,
Changes since 20151019:
on x86_64:
when CONFIG_DW_DMAC is not enabled.
sound/built-in.o: In function `sst_dma_new':
(.text+0xd7b38): undefined reference to `dw_dma_probe'
sound/built-in.o: In
On Mon, Oct 19, 2015 at 08:27:13AM +0200, Heiko Schocher wrote:
> --- /dev/null
> +++ b/arch/arm/boot/dts/tps65023.dtsi
If this file is needed there is something broken, if this file is not
needed then it is just noise since everything in it needs to be
overridden by users anyway. Either way
On Wed, Oct 21, 2015 at 07:49:34PM +0800, Wangnan (F) wrote:
> If our task is sampling cycle events during a function is running,
> and if two cores start that function overlap:
>
> Time: ...A
> Core 0: sys_write\
> \
>\
> Core
On 21.10.2015 13:42, Lorenzo Pieralisi wrote:
On Wed, Oct 21, 2015 at 01:27:33PM +0200, Tomasz Nowicki wrote:
On 21.10.2015 13:02, Liviu Dudau wrote:
On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
On 14.10.2015 08:29, Jiang Liu wrote:
Introduce common interface
On Oct 21, 2015, at 9:14 PM, Jungseok Lee wrote:
Whoops!
> [Only Akashi and James]
>
> On Oct 21, 2015, at 3:38 PM, AKASHI Takahiro wrote:
>
> Hi Akashi and James,
>
> Am I the only person who have experienced kernel panic with this series?
> I have observed NULL pointer kernel panic with the
On Mon, Oct 19, 2015 at 05:30:42PM -0600, Stephen Warren wrote:
> From: Stephen Warren
>
> Convert the binding to provide a PHY per lane, rather than a PHY per
> "pad" block in the hardware. This will allow the driver to easily know
> which lanes are used by clients, and thus only enable those
[Only Akashi and James]
On Oct 21, 2015, at 3:38 PM, AKASHI Takahiro wrote:
Hi Akashi and James,
Am I the only person who have experienced kernel panic with this series?
I have observed NULL pointer kernel panic with the following two ways.
- $ sudo echo c > /proc/sysrq-trigger
- perf record
On Wed, Oct 21, 2015 at 12:18:32PM +0100, Lee Jones wrote:
> On Wed, 21 Oct 2015, Mark Brown wrote:
> > On Wed, Oct 21, 2015 at 09:46:33AM +0100, Lee Jones wrote:
> > > On Tue, 20 Oct 2015, Andrew F. Davis wrote:
> > It is however the normal way we write compatible strings - the class
> >
On 10/21/2015 06:12 AM, Oliver Neukum wrote:
> On Tue, 2015-10-20 at 14:16 -0400, Peter Hurley wrote:
>> ECHO is on by default and the cdc-acm driver does not implement the
>> put_char() and flush_chars() tty driver methods, which made the
>> problem
>> _way worse_, since every echoed char is sent
European Parliament
36 St Peter's St, London N1 8JT,
United Kingdom.
In consideration of the legislative resolution reached by the European
Parliament in conjunctions with the European Central Bank on financial and
allied matters,following eries of complaints and petitions received from the
On Tue, Oct 20, 2015 at 08:02:34PM -0700, Alexei Starovoitov wrote:
> This helper is used to send raw data from eBPF program into
> special PERF_TYPE_SOFTWARE/PERF_COUNT_SW_BPF_OUTPUT perf_event.
> User space needs to perf_event_open() it (either for one or all cpus) and
> store FD into
On 2015/10/21 19:56, Peter Zijlstra wrote:
On Wed, Oct 21, 2015 at 07:34:28PM +0800, Wangnan (F) wrote:
If you want to actually disable the event: pmu->stop() will make it
stop, and you can restart using pmu->start().xiezuo
I also prefer totally disabling event because our goal is to reduce
On 20 October 2015 at 18:29, Marcus Overhagen
wrote:
> I tested again with a 4.2 kernel but the bug is still present and
> happens more often. So far nobody has responded.
> I don't know what to do, and whether it's related to usb, mmc or mfd.
> Please advise.
Sorry for the delay. I was hoping
Hi Ulf,
Do you have any remarks or comments to the series?
Best regards,
Marcin
2015-10-15 18:25 GMT+02:00 Marcin Wojtas :
> Hi,
>
> Thank you for reviewing the patches. According to your remarks and some
> new ideas I prepared third patchset. I modified my HW and now I could
> check operation
On 2015/10/21 16:09, Namhyung Kim wrote:
Hi Frederic,
On Tue, Oct 20, 2015 at 07:21:16PM +0200, Frederic Weisbecker wrote:
On Tue, Oct 20, 2015 at 10:06:51AM -0300, Arnaldo Carvalho de Melo wrote:
Em Tue, Oct 20, 2015 at 02:19:50PM +0200, Frederic Weisbecker escreveu:
On Tue, Oct 20, 2015
On Wed, Oct 21, 2015 at 07:34:28PM +0800, Wangnan (F) wrote:
> >If you want to actually disable the event: pmu->stop() will make it
> >stop, and you can restart using pmu->start().xiezuo
>
> I also prefer totally disabling event because our goal is to reduce
> sampling overhead as mush as
In the vsock vmci_transport driver, sock_put wasn't safe to call
in interrupt context, since that may call the vsock destructor
which in turn calls several functions that should only be called
from process context. This change defers the callling of these
functions to a worker thread. All these
On Wed, Oct 21, 2015 at 07:39:22AM -0400, Steven Rostedt wrote:
> On Wed, 21 Oct 2015 10:01:42 +0200
> Peter Zijlstra wrote:
>
> > > I should probably add a "if (in_nmi()) return" somewhere.
> >
> > But if there's an arch that doesn't use a separate NMI stack, the NMI
> > might cause the
On Wed, Oct 21, 2015 at 07:49:13PM +0800, Jiang Liu wrote:
> On 2015/10/21 19:27, Tomasz Nowicki wrote:
> > On 21.10.2015 13:02, Liviu Dudau wrote:
> >> On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
> >>> On 14.10.2015 08:29, Jiang Liu wrote:
> Introduce common interface
Signed-off-by: Ludovic Barre
Signed-off-by: Lee Jones
---
.../devicetree/bindings/remoteproc/st-rproc.txt| 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/st-rproc.txt
diff --git
This functionality is especially useful during the testing phase. When
used in conjunction with Mailbox's Test Framework we can trivially conduct
end-to-end testing i.e. boot co-processor, send and receive messages to
the co-processor, then shut it down again (repeat as required).
Signed-off-by:
On 2015/10/21 19:33, Peter Zijlstra wrote:
On Wed, Oct 21, 2015 at 06:31:04PM +0800, xiakaixu wrote:
The RFC patch set contains the necessary commit log [1].
That's of course the wrong place, this should be in the patch's
Changelog. It doesn't become less relevant.
In some scenarios we
ST's platforms often have multiple co-processors (usually ST40s or ST231s)
on-board. This provides the Linux-side infrastructure to flash and boot
them successfully.
This set has been tested on an STiH410-B2120.
v3 => v4:
Suggested-by: Suman Anna
- Move to using 'reserved-memory' API
-
Signed-off-by: Lee Jones
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 5f46784..322f5b4 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1538,6 +1538,7 @@ F:drivers/phy/phy-miphy365x.c
F: drivers/phy/phy-stih407-usb.c
F:
Signed-off-by: Ludovic Barre
Signed-off-by: Lee Jones
---
arch/arm/boot/dts/stih407-family.dtsi | 40 +++
1 file changed, 40 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-family.dtsi
b/arch/arm/boot/dts/stih407-family.dtsi
index 1e4e01925..15c20b6 100644
On 2015/10/21 19:27, Tomasz Nowicki wrote:
> On 21.10.2015 13:02, Liviu Dudau wrote:
>> On Wed, Oct 21, 2015 at 11:57:53AM +0200, Tomasz Nowicki wrote:
>>> On 14.10.2015 08:29, Jiang Liu wrote:
Introduce common interface acpi_pci_root_create() and related data
structures to create PCI
701 - 800 of 2156 matches
Mail list logo
