On Thursday 07 May 2015 19:01:13 Brian Norris wrote:
>
> Would this satisfy you?
>
> From: Brian Norris
> Date: Tue, 5 May 2015 17:46:42 -0700
> Subject: [PATCH] mtd: brcmstb_nand: fixup endianness assumptions
>
> All users of this controller (MIPS or ARM) have previously used native
> I/O
On Thursday 07 May 2015 11:52:11 Brian Norris wrote:
> On Thu, May 07, 2015 at 11:25:29AM +0200, Arnd Bergmann wrote:
> > On Wednesday 06 May 2015 14:18:47 Ray Jui wrote:
> > >
> > > On 5/6/2015 2:05 PM, Brian Norris wrote:
> > > > On Wed, May 06, 2015 at 09:17:36PM +0200, Arnd Bergmann wrote:
>
VOP can support BGR formats in all windows thanks to red/blue swap option
provided in WINx_CTRL0 registers. This patch enables support for
ABGR, XBGR, BGR888 and BGR565 formats by using this feature.
Signed-off-by: Tomasz Figa
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 33
On Thu, May 07, 2015 at 11:53:18PM -0700, Stephen Boyd wrote:
> On 05/07, Kevin Hilman wrote:
> > On Thu, May 7, 2015 at 2:03 PM, Stephen Boyd wrote:
> > > On 05/07/15 08:17, Kevin Hilman wrote:
> > >> On Fri, May 1, 2015 at 4:40 PM, Stephen Boyd
> > >> wrote:
> > >>> On 05/01/15 15:07, Heiko
Addition of CLK_RECALC_NEW_RATES flag to support Exynos5420 cpu clk so that
correct divider values are re-calculated after both pre/post
clock notifiers had run for mout_apll clock and mout_kpll clock.
Below is the output of cpupower utility.
Observation their is considreable improvement in
On Fri, May 8, 2015 at 9:27 AM, Lee Jones wrote:
> On Fri, 08 May 2015, Geert Uytterhoeven wrote:
>> On Fri, May 8, 2015 at 8:57 AM, Lee Jones wrote:
>> > On Fri, 08 May 2015, Geert Uytterhoeven wrote:
>> >> On Thu, May 7, 2015 at 9:01 AM, Lee Jones wrote:
>> >> >> I have a follow up question
On 2015/05/05 19:10, He Kuang wrote:
> Convert register number in debuginfo to its index in pt_regs.
>
This seems better introduced after 3/6, since 3/6 is generic
framework. Without 3/6, this can't do anything.
> Signed-off-by: He Kuang
> ---
> tools/perf/arch/x86/util/dwarf-regs.c | 31
EP-2DAD0AFA905A4ACB804C4F82A001242F
--- Original Message ---
Sender : yalin wang
Date : May 08, 2015 13:17 (GMT+05:30)
Title : Re: [EDT] oom_killer: find bulkiest task based on pss value
2015-05-08 13:29 GMT+08:00 Yogesh Narayan Gaur :
>>
>> EP-2DAD0AFA905A4ACB804C4F82A001242F
>> Hi
* Rik van Riel wrote:
> On 05/07/2015 08:29 AM, Ingo Molnar wrote:
> >
> > * Frederic Weisbecker wrote:
> >
> We cannot take the lock_trace(task) from irq context, and we
> probably do not need to anyway, since we do not care about a
> precise stack trace for the task.
> >>>
On 05/06/2015 10:35 PM, Alan Stern wrote:
diff --git a/include/linux/usb/hcd.h b/include/linux/usb/hcd.h
>index 68b1e83..621d9b7 100644
>--- a/include/linux/usb/hcd.h
>+++ b/include/linux/usb/hcd.h
>@@ -383,7 +383,13 @@ struct hc_driver {
>int (*find_raw_port_number)(struct usb_hcd *,
On Fri, May 08, 2015 at 10:34:49AM +0300, Dan Carpenter wrote:
> On Fri, May 08, 2015 at 09:54:44AM +0530, Sudip Mukherjee wrote:
> > On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
> > > On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
> > > > the previous
* Ingo Molnar wrote:
>
> * Vince Weaver wrote:
>
> > So this is just a warning, and I've reported it before, but the
> > perf_fuzzer triggers this fairly regularly on my Haswell system.
> >
> > It looks like fixed counter 0 (retired instructions) being set to
> > fffe
* Vince Weaver wrote:
> On Fri, 1 May 2015, Ingo Molnar wrote:
>
> > So fffe corresponds to 2 events left until overflow,
> > right? And on Haswell we don't set x86_pmu.limit_period AFAICS, so we
> > allow these super short periods.
> >
> > Maybe like on Broadwell we need a
On Fri, May 8, 2015 at 7:07 AM, Warren Clemmons wrote:
>
> [1.] Lenovo SL510 will not resume from suspend
> [2.] When using the following three steps to suspend the laptop the will
> not resume from suspend. The suspend light flash rapidly instead of slowly.
> 1. systemctl suspend
> 2. closing
* Len Brown wrote:
> From: Len Brown
>
> Modern processor familes are on a white-list to remove
> the costly cpu_init_udelay 1. Unknown processor families
> get the traditional 10ms delay in cpu_up().
>
> This seemed more efficient than forcing modern processors
> to exhaustively search
2015-05-08 13:29 GMT+08:00 Yogesh Narayan Gaur :
>
> EP-2DAD0AFA905A4ACB804C4F82A001242F
> Hi Andrew,
>
> Presently in oom_kill.c we calculate badness score of the victim task as per
> the present RSS counter value of the task.
> RSS counter value for any task is usually '[Private (Dirty/Clean)]
Hi Linus,
here is a bunch of GPIO fixes that I collected since -rc1,
nothing controversial, nothing special. Some descriptions
in the signed tag.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26
On 05/08/2015 03:28 PM, Greg Kroah-Hartman wrote:
On Fri, May 08, 2015 at 09:23:40AM +0800, Lu, Baolu wrote:
On 05/08/2015 04:47 AM, Greg Kroah-Hartman wrote:
On Thu, May 07, 2015 at 10:18:15AM +0800, Lu Baolu wrote:
This patch implements device_suspend/device_resume entries for xHC
Fix the 'rpm-pkg' makefile target to always generate the correct
/usr/src/kernel/ symlink; this fails on non-RPM-native systems
eg Ubuntu.
On a non-RPM-native system, the symlink created by rpmbuild points to
the source tree, so the ln -sf commands to overwrite build and source will
create a new
On Friday 08 May 2015 12:54 PM, Yoshihiro Shimoda wrote:
Hi Kishon,
Sent: Thursday, April 02, 2015 5:01 PM
According to the technical update (No. TN-RCS-B011A/E), the UGSTS LOCK
bit location is bit 8, not bits 1 and 0. It also says that the register
address offset of UGSTS is 0x88, not
these functions were just defined and never used. after removing the
functions the variable visorchipset_cache_buffers_in_use is becoming
unused, so removed it as well.
Signed-off-by: Sudip Mukherjee
---
v2: combined both patches of v1 together
On 05/08/2015 02:20 AM, Rafael J. Wysocki wrote:
> On Thursday, May 07, 2015 11:17:21 PM Preeti U Murthy wrote:
>> When a CPU has to enter an idle state where tick stops, it makes a call
>> to tick_broadcast_enter(). The call will fail if this CPU is the
>> broadcast CPU. Today, under such a
When a CPU has to enter an idle state where tick stops, it makes a call
to tick_broadcast_enter(). The call will fail if this CPU is the
broadcast CPU. Today, under such a circumstance, the arch cpuidle code
handles this CPU. This is not convincing because not only do we not
know what the arch
On Fri, May 08, 2015 at 09:54:44AM +0530, Sudip Mukherjee wrote:
> On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
> > > the previous patch of the series made this variable unused.
> >
> > What do you mean?
On Fri, May 08, 2015 at 09:23:40AM +0800, Lu, Baolu wrote:
>
>
> On 05/08/2015 04:47 AM, Greg Kroah-Hartman wrote:
> >On Thu, May 07, 2015 at 10:18:15AM +0800, Lu Baolu wrote:
> >>This patch implements device_suspend/device_resume entries for xHC driver.
> >>device_suspend will be called when a
On Fri, 08 May 2015, Geert Uytterhoeven wrote:
> On Fri, May 8, 2015 at 8:57 AM, Lee Jones wrote:
> > On Fri, 08 May 2015, Geert Uytterhoeven wrote:
> >
> >> On Thu, May 7, 2015 at 9:01 AM, Lee Jones wrote:
> >> >> I have a follow up question regarding interrupt. I see many I2C bus
> >> >>
On Mon, May 04, 2015 at 10:59:39PM -0700, Mitchel Humpherys wrote:
> On Mon, May 04 2015 at 01:05:50 PM, Colin Cross wrote:
> > On Mon, May 4, 2015 at 1:22 AM, Dan Carpenter
> > wrote:
> >> On Thu, Apr 09, 2015 at 06:10:04PM -0700, Mitchel Humpherys wrote:
> >>> We're currently using %lu and
On Fri, 08 May 2015, Peter Griffin wrote:
> On Fri, 08 May 2015, Lee Jones wrote:
> > > > > >
> > > > > > -- compatible : Must be one of: "st,stih407-lpc"
> > > > > > "st,stih416-lpc"
> > > > > > - "st,stih415-lpc" "st,stid127-lpc"
> > > > > > +- compatible
Hi Kishon,
> Sent: Thursday, April 02, 2015 5:01 PM
>
> According to the technical update (No. TN-RCS-B011A/E), the UGSTS LOCK
> bit location is bit 8, not bits 1 and 0. It also says that the register
> address offset of UGSTS is 0x88, not 0x90.
> So, this patch fixes the USBHS_UGSTS_LOCK value
Hi Linus,
Here are some mmc fixes for v.4.1 rc3, based on v4.1-rc2.
Details are as usual found in the signed tag. Please pull this in!
Kind regards
Ulf Hansson
The following changes since commit 5ebe6afaf0057ac3eaeb98defd5456894b446d22:
Linux 4.1-rc2 (2015-05-03 19:22:23 -0700)
are
On Thu, 07 May 2015, Maxime Ripard wrote:
> On Fri, May 01, 2015 at 07:44:05AM +0100, Lee Jones wrote:
> > > > Does Sascha's antidote patch change your opinion? We can use DT to
> > > > declare critical clocks, and in the rare case of the introduction of a
> > > > new DDRFreq-like feature, which
Sorry, I'm reviewing this patchset slowly.
On Wed, May 06, 2015 at 04:28:25PM -0500, J. German Rivera wrote:
> - Migrated MC bus driver to use DPRC API 0.6.
> - Changed IRQ setup infrastructure to be able to program MSIs
> for MC objects in an object-independent way.
>
> Signed-off-by: J.
On Thu, May 7, 2015 at 10:53 AM, Jiang Liu
wrote:
On NUMA systems, an IO device may be associated with a NUMA node.
It may improve IO performance to allocate resources, such as memory
and interrupts, from device local node.
This patch introduces a mechanism to support CPU vector allocation
Hi Vinod,
On Fri, May 08, 2015 at 09:14:26AM +0530, Vinod Koul wrote:
> On Wed, May 06, 2015 at 12:13:42PM +0200, Maxime Ripard wrote:
> > On Wed, May 06, 2015 at 11:31:31AM +0200, Jens Kuske wrote:
> > > The H3 SoC has the same dma engine as the A31 (sun6i), with a
> > > reduced amount of
On Fri, May 08, 2015 at 09:54:44AM +0530, Sudip Mukherjee wrote:
> On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
> > > the previous patch of the series made this variable unused.
> >
> > What do you mean?
Hi Lee,
On Fri, 08 May 2015, Lee Jones wrote:
> > > > >
> > > > > -- compatible : Must be one of: "st,stih407-lpc"
> > > > > "st,stih416-lpc"
> > > > > - "st,stih415-lpc" "st,stid127-lpc"
> > > > > +- compatible : Must be one of: "st,stih407-lpc"
From: Sebastian Andrzej Siewior
This basically reverts commit 068500e08dc8 ("serial: imx: initialized
DMA w/o HW flow enabled") simply because it does not work.
I tested it on various IMX6 boards and the default SDMA firmware, that is
included in ROM, does not work properly. The SDMA interrupt
On 05/07/2015 11:03 PM, Rafael J. Wysocki wrote:
> On Thursday, May 07, 2015 05:54:56 PM One Thousand Gnomes wrote:
>> On Tue, 05 May 2015 14:31:26 +0200
>>
>>> For example, when you wake up from S3 on ACPI-based systems, the best you
>>> can get is what devices have generated the wakeup events,
From: Len Brown
Remove sys_sync() from the kernel's suspend flow.
sys_sync() is extremely expensive in some configurations,
and so the kernel should not force users to pay this cost
on every suspend.
The user-space utilities s2ram and s2disk choose to invoke sync() today.
A user can invoke
On Fri, May 8, 2015 at 8:57 AM, Lee Jones wrote:
> On Fri, 08 May 2015, Geert Uytterhoeven wrote:
>
>> On Thu, May 7, 2015 at 9:01 AM, Lee Jones wrote:
>> >> I have a follow up question regarding interrupt. I see many I2C bus
>> >> drivers
>> >> request interrupt with flag = 0. Why not using
On 05/08/2015 06:41 AM, Vinod Koul wrote:
> Now as far as this series is concerned, rest of it looks good so I am
> willing to merge to if you plan to work on defered probe :) I think its a
> fair bargain!
Deal ;)
I'll take care of the OMAP/daVinci drivers for omap-dma and edma.
--
Péter
--
To
On Tue, 2015-05-05 at 14:16 -0700, Andrew Morton wrote:
> On Tue, 5 May 2015 21:12:12 +1000 Michael Ellerman
> wrote:
>
> > Arch code can set a "dump stack arch description string" which is
> > displayed with oops output to describe the hardware platform.
> > +
> > + len =
On Tue, 05 May 2015, Julia Lawall wrote:
>
>
> On Tue, 5 May 2015, Nicholas Mc Guire wrote:
>
> > On Tue, 05 May 2015, Julia Lawall wrote:
> >
> > > > +@match@
> > > > +identifier f,ret;
> > > > +position p;
> > > > +type T1,T2;
> > > > +@@
> > > > +
> > > > +T1 f(...) {
> > > > + T2 ret;
> >
On Fri, 08 May 2015, Geert Uytterhoeven wrote:
> On Thu, May 7, 2015 at 9:01 AM, Lee Jones wrote:
> >> I have a follow up question regarding interrupt. I see many I2C bus drivers
> >> request interrupt with flag = 0. Why not using IRQF_SHARED?
> >
> > Probably because that particular IRQ is only
On Thu, May 7, 2015 at 9:40 PM, Steven Rostedt wrote:
> [ cut here ]
> WARNING: CPU: 2 PID: 0 at
> /work/autotest/nobackup/linux-test.git/drivers/gpu/drm/i915/intel_uncore.c:566
> hsw_unclaimed_reg_debug.isra.10+0x6c/0x84()
> Unclaimed register detected before writing
On 05/07, Kevin Hilman wrote:
> On Thu, May 7, 2015 at 2:03 PM, Stephen Boyd wrote:
> > On 05/07/15 08:17, Kevin Hilman wrote:
> >> On Fri, May 1, 2015 at 4:40 PM, Stephen Boyd wrote:
> >>> On 05/01/15 15:07, Heiko Stübner wrote:
> Am Freitag, 1. Mai 2015, 13:52:47 schrieb Stephen Boyd:
>
The binding uses assigned-clock-parents when it should use
assigned-clock-rates. Furthermore, the part that describes how
they relate to the assigned-clocks property is not clear about
what is related. Correct and clarify this part of the binding.
Reported-by: Krzysztof Kozlowski
Signed-off-by:
On Thu, 07 May 2015, Peter Griffin wrote:
> Hi Lee,
>
> On Thu, 07 May 2015, Lee Jones wrote:
>
>
>
> > > > Required properties
> > > >
> > > > -- compatible : Must be one of: "st,stih407-lpc" "st,stih416-lpc"
> > > > - "st,stih415-lpc" "st,stid127-lpc"
>
On Thu, May 7, 2015 at 9:01 AM, Lee Jones wrote:
>> I have a follow up question regarding interrupt. I see many I2C bus drivers
>> request interrupt with flag = 0. Why not using IRQF_SHARED?
>
> Probably because that particular IRQ is only used by the I2C
> Controller. I'm not exactly sure that
In order to prepare for the addition of the asynchronous seeding call,
the invocation of seeding the DRBG is moved out into a helper function.
In addition, a block of memory is allocated during initialization time
that will be used as a scratchpad for obtaining entropy. That scratchpad
is used
The added API calls provide a synchronous function call
get_blocking_random_bytes where the caller is blocked until
the nonblocking_pool is initialized.
In addition, an asynchronous API call of get_blocking_random_bytes_cb
is provided which returns immediately to the caller after submitting
the
During initialization, the DRBG now tries to allocate a handle of the
Jitter RNG. If such a Jitter RNG is available during seeding, the DRBG
pulls the required entropy/nonce string from get_random_bytes and
concatenates it with a string of equal size from the Jitter RNG. That
combined string is
The CPU Jitter RNG provides a source of good entropy by
collecting CPU executing time jitter. The entropy in the CPU
execution time jitter is magnified by the CPU Jitter Random
Number Generator. The CPU Jitter Random Number Generator uses
the CPU execution timing jitter to generate a bit stream
Hi,
as of now, the DRBG is only seeded from get_random_bytes. In various
circumstances, the nonblocking_pool behind get_random_bytes may not be fully
seeded from hardware events at the time the DRBG requires to be seeded.
Based on the discussion in [1], the DRBG seeding is updated such that it
The async seeding operation is triggered during initalization right
after the first non-blocking seeding is completed. As required by the
asynchronous operation of random.c, a callback function is provided that
is triggered by random.c once entropy is available. That callback
function performs the
On Sun, Jan 26, 2014 at 4:08 PM, Pavel Machek wrote:
> Dunno. Config option plus sysfs attribute is overdoing it a bit.
Agreed.
Have discussed w/ Rafael, and current plan is to simply delete.
Updated patch on the way...
thanks,
Len Brown, Intel Open Source Technology Center
--
To unsubscribe
From: Len Brown
Replace the hard-coded mdelay(10) in cpu_up() to a variable udelay.
Add a boot-time override, "cpu_init_udelay=N"
Default unchanged at 10ms on all systems.
Signed-off-by: Len Brown
---
Documentation/kernel-parameters.txt | 6 ++
arch/x86/kernel/smpboot.c | 28
From: Len Brown
Modern processor familes are on a white-list to remove
the costly cpu_init_udelay 1. Unknown processor families
get the traditional 10ms delay in cpu_up().
This seemed more efficient than forcing modern processors
to exhaustively search a black-list having all the old
Thanks for testing, Aravind, Borislav,
I went with Ingo's suggestion to made this a quirk.
However, I went with a white-list instead of a black-list,
because fewer comparisons are needed for modern processors.
Families are added infrequently, and finally, we get the option
to stick something
* Andy Lutomirski wrote:
> > So do you mean:
> >
> >this_cpu_set(rcu_state) = IN_KERNEL;
> >...
> >this_cpu_inc(rcu_qs_ctr);
> >this_cpu_set(rcu_state) = IN_USER;
> >
> > ?
> >
> > So in your proposal we'd have an INC and two MOVs. I think we can make
> > it just two simple
On Fri, May 8, 2015 at 3:54 AM, Guenter Roeck wrote:
> On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20150506:
>>
>> The ext4 tree gained a build failure so I used the version from
>> next-20150506.
>>
>> The vfs tree gained a conflict against
On Thu, May 07, 2015 at 01:22:11PM -0400, Peter Hurley wrote:
> On 05/07/2015 01:09 PM, Maciej W. Rozycki wrote:
> > On Mon, 4 May 2015, Peter Hurley wrote:
> >
> Since 2007, 'console=' is a early param synonym for 'earlycon='; IOW,
> the message is new but not the behavior.
> >>>
> >>>
On Sat, Apr 11, 2015 at 09:40:34PM +0200, Robert Jarzmik wrote:
> This is a new driver for pxa SoCs, which is also compatible with the former
> mmp_pdma.
The rationale is fine, is there a plan to remove old mmp_pdma then?
> +config PXA_DMA
> + bool "PXA DMA support"
no prompt?
> +
> +#define
On Tue, 2015-05-05 at 02:06 +0200, Rafael J. Wysocki wrote:
> On Tuesday, April 28, 2015 06:22:05 PM Dan Williams wrote:
> > On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki
> > wrote:
> > > On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
> > >> Changes since v1 [1]: Incorporates
* Hemant Kumar wrote:
>
> On 05/08/2015 09:58 AM, Ingo Molnar wrote:
> >* Hemant Kumar wrote:
> >
> >> # perf kvm stat report -p 60515
> >>Analyze events for pid(s) 60515, all VCPUs:
> >>
> >>VM-EXITSamples Samples% Time%Min Time Max
> >> Time Avg
On Thu, May 07, 2015 at 02:49:39PM +0200, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
> > The TIF_RCU_QS thing is just a fancy way for synchronize_rcu()
> > (being executed on some other CPU not doing RT work) to
> > intelligently wait for the remote (RT work doing) CPU to finish
> >
On 05/08/2015 09:58 AM, Ingo Molnar wrote:
* Hemant Kumar wrote:
# perf kvm stat report -p 60515
Analyze events for pid(s) 60515, all VCPUs:
VM-EXITSamples Samples% Time%Min Time Max
Time Avg time
H_DATA_STORAGE 500635.30% 0.13%
From: Len Brown len.br...@intel.com
Replace the hard-coded mdelay(10) in cpu_up() to a variable udelay.
Add a boot-time override, cpu_init_udelay=N
Default unchanged at 10ms on all systems.
Signed-off-by: Len Brown len.br...@intel.com
---
Documentation/kernel-parameters.txt | 6 ++
In order to prepare for the addition of the asynchronous seeding call,
the invocation of seeding the DRBG is moved out into a helper function.
In addition, a block of memory is allocated during initialization time
that will be used as a scratchpad for obtaining entropy. That scratchpad
is used
On Fri, 08 May 2015, Geert Uytterhoeven wrote:
On Thu, May 7, 2015 at 9:01 AM, Lee Jones lee.jo...@linaro.org wrote:
I have a follow up question regarding interrupt. I see many I2C bus drivers
request interrupt with flag = 0. Why not using IRQF_SHARED?
Probably because that particular
On Sat, Apr 11, 2015 at 09:40:34PM +0200, Robert Jarzmik wrote:
This is a new driver for pxa SoCs, which is also compatible with the former
mmp_pdma.
The rationale is fine, is there a plan to remove old mmp_pdma then?
+config PXA_DMA
+ bool PXA DMA support
no prompt?
+
+#define
On Thu, May 07, 2015 at 01:22:11PM -0400, Peter Hurley wrote:
On 05/07/2015 01:09 PM, Maciej W. Rozycki wrote:
On Mon, 4 May 2015, Peter Hurley wrote:
Since 2007, 'console=' is a early param synonym for 'earlycon='; IOW,
the message is new but not the behavior.
console= had nothing
The CPU Jitter RNG provides a source of good entropy by
collecting CPU executing time jitter. The entropy in the CPU
execution time jitter is magnified by the CPU Jitter Random
Number Generator. The CPU Jitter Random Number Generator uses
the CPU execution timing jitter to generate a bit stream
The added API calls provide a synchronous function call
get_blocking_random_bytes where the caller is blocked until
the nonblocking_pool is initialized.
In addition, an asynchronous API call of get_blocking_random_bytes_cb
is provided which returns immediately to the caller after submitting
the
During initialization, the DRBG now tries to allocate a handle of the
Jitter RNG. If such a Jitter RNG is available during seeding, the DRBG
pulls the required entropy/nonce string from get_random_bytes and
concatenates it with a string of equal size from the Jitter RNG. That
combined string is
Hi,
as of now, the DRBG is only seeded from get_random_bytes. In various
circumstances, the nonblocking_pool behind get_random_bytes may not be fully
seeded from hardware events at the time the DRBG requires to be seeded.
Based on the discussion in [1], the DRBG seeding is updated such that it
The async seeding operation is triggered during initalization right
after the first non-blocking seeding is completed. As required by the
asynchronous operation of random.c, a callback function is provided that
is triggered by random.c once entropy is available. That callback
function performs the
On Tue, 2015-05-05 at 14:16 -0700, Andrew Morton wrote:
On Tue, 5 May 2015 21:12:12 +1000 Michael Ellerman m...@ellerman.id.au
wrote:
Arch code can set a dump stack arch description string which is
displayed with oops output to describe the hardware platform.
+
+ len =
On Tue, 05 May 2015, Julia Lawall wrote:
On Tue, 5 May 2015, Nicholas Mc Guire wrote:
On Tue, 05 May 2015, Julia Lawall wrote:
+@match@
+identifier f,ret;
+position p;
+type T1,T2;
+@@
+
+T1 f(...) {
+ T2 ret;
++...
+* return@p ret
+;
On Sun, Jan 26, 2014 at 4:08 PM, Pavel Machek pa...@ucw.cz wrote:
Dunno. Config option plus sysfs attribute is overdoing it a bit.
Agreed.
Have discussed w/ Rafael, and current plan is to simply delete.
Updated patch on the way...
thanks,
Len Brown, Intel Open Source Technology Center
--
To
On Thu, May 7, 2015 at 9:01 AM, Lee Jones lee.jo...@linaro.org wrote:
I have a follow up question regarding interrupt. I see many I2C bus drivers
request interrupt with flag = 0. Why not using IRQF_SHARED?
Probably because that particular IRQ is only used by the I2C
Controller. I'm not
On Thu, May 7, 2015 at 9:40 PM, Steven Rostedt rost...@goodmis.org wrote:
[ cut here ]
WARNING: CPU: 2 PID: 0 at
/work/autotest/nobackup/linux-test.git/drivers/gpu/drm/i915/intel_uncore.c:566
hsw_unclaimed_reg_debug.isra.10+0x6c/0x84()
Unclaimed register detected
On Tue, 2015-05-05 at 02:06 +0200, Rafael J. Wysocki wrote:
On Tuesday, April 28, 2015 06:22:05 PM Dan Williams wrote:
On Tue, Apr 28, 2015 at 5:25 PM, Rafael J. Wysocki r...@rjwysocki.net
wrote:
On Tuesday, April 28, 2015 02:24:12 PM Dan Williams wrote:
Changes since v1 [1]:
On Thu, 07 May 2015, Peter Griffin wrote:
Hi Lee,
On Thu, 07 May 2015, Lee Jones wrote:
snip
Required properties
-- compatible : Must be one of: st,stih407-lpc st,stih416-lpc
- st,stih415-lpc st,stid127-lpc
+- compatible : Must
On 05/07, Kevin Hilman wrote:
On Thu, May 7, 2015 at 2:03 PM, Stephen Boyd sb...@codeaurora.org wrote:
On 05/07/15 08:17, Kevin Hilman wrote:
On Fri, May 1, 2015 at 4:40 PM, Stephen Boyd sb...@codeaurora.org wrote:
On 05/01/15 15:07, Heiko Stübner wrote:
Am Freitag, 1. Mai 2015, 13:52:47
On 05/08/2015 09:58 AM, Ingo Molnar wrote:
* Hemant Kumar hem...@linux.vnet.ibm.com wrote:
# perf kvm stat report -p 60515
Analyze events for pid(s) 60515, all VCPUs:
VM-EXITSamples Samples% Time%Min Time Max
Time Avg time
H_DATA_STORAGE
* Hemant Kumar hem...@linux.vnet.ibm.com wrote:
On 05/08/2015 09:58 AM, Ingo Molnar wrote:
* Hemant Kumar hem...@linux.vnet.ibm.com wrote:
# perf kvm stat report -p 60515
Analyze events for pid(s) 60515, all VCPUs:
VM-EXITSamples Samples% Time%Min Time
On Thu, May 07, 2015 at 02:49:39PM +0200, Ingo Molnar wrote:
* Ingo Molnar mi...@kernel.org wrote:
The TIF_RCU_QS thing is just a fancy way for synchronize_rcu()
(being executed on some other CPU not doing RT work) to
intelligently wait for the remote (RT work doing) CPU to finish
Thanks for testing, Aravind, Borislav,
I went with Ingo's suggestion to made this a quirk.
However, I went with a white-list instead of a black-list,
because fewer comparisons are needed for modern processors.
Families are added infrequently, and finally, we get the option
to stick something
From: Len Brown len.br...@intel.com
Modern processor familes are on a white-list to remove
the costly cpu_init_udelay 1. Unknown processor families
get the traditional 10ms delay in cpu_up().
This seemed more efficient than forcing modern processors
to exhaustively search a black-list
* Andy Lutomirski l...@amacapital.net wrote:
So do you mean:
this_cpu_set(rcu_state) = IN_KERNEL;
...
this_cpu_inc(rcu_qs_ctr);
this_cpu_set(rcu_state) = IN_USER;
?
So in your proposal we'd have an INC and two MOVs. I think we can make
it just two simple stores
The binding uses assigned-clock-parents when it should use
assigned-clock-rates. Furthermore, the part that describes how
they relate to the assigned-clocks property is not clear about
what is related. Correct and clarify this part of the binding.
Reported-by: Krzysztof Kozlowski
On Fri, May 8, 2015 at 3:54 AM, Guenter Roeck li...@roeck-us.net wrote:
On Thu, May 07, 2015 at 04:47:15PM +1000, Stephen Rothwell wrote:
Hi all,
Changes since 20150506:
The ext4 tree gained a build failure so I used the version from
next-20150506.
The vfs tree gained a conflict against
On Fri, May 08, 2015 at 09:54:44AM +0530, Sudip Mukherjee wrote:
On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
the previous patch of the series made this variable unused.
What do you mean? There was
On Fri, May 08, 2015 at 09:23:40AM +0800, Lu, Baolu wrote:
On 05/08/2015 04:47 AM, Greg Kroah-Hartman wrote:
On Thu, May 07, 2015 at 10:18:15AM +0800, Lu Baolu wrote:
This patch implements device_suspend/device_resume entries for xHC driver.
device_suspend will be called when a USB device
On Fri, May 08, 2015 at 09:54:44AM +0530, Sudip Mukherjee wrote:
On Thu, May 07, 2015 at 10:04:32PM +0200, Greg Kroah-Hartman wrote:
On Thu, May 07, 2015 at 03:06:52PM +0530, Sudip Mukherjee wrote:
the previous patch of the series made this variable unused.
What do you mean? There was
On Friday 08 May 2015 12:54 PM, Yoshihiro Shimoda wrote:
Hi Kishon,
Sent: Thursday, April 02, 2015 5:01 PM
According to the technical update (No. TN-RCS-B011A/E), the UGSTS LOCK
bit location is bit 8, not bits 1 and 0. It also says that the register
address offset of UGSTS is 0x88, not
Hi Linus,
here is a bunch of GPIO fixes that I collected since -rc1,
nothing controversial, nothing special. Some descriptions
in the signed tag.
Please pull them in!
Yours,
Linus Walleij
The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:
Linux 4.1-rc1 (2015-04-26
On 05/08/2015 03:28 PM, Greg Kroah-Hartman wrote:
On Fri, May 08, 2015 at 09:23:40AM +0800, Lu, Baolu wrote:
On 05/08/2015 04:47 AM, Greg Kroah-Hartman wrote:
On Thu, May 07, 2015 at 10:18:15AM +0800, Lu Baolu wrote:
This patch implements device_suspend/device_resume entries for xHC
* Len Brown l...@kernel.org wrote:
From: Len Brown len.br...@intel.com
Modern processor familes are on a white-list to remove
the costly cpu_init_udelay 1. Unknown processor families
get the traditional 10ms delay in cpu_up().
This seemed more efficient than forcing modern
701 - 800 of 1534 matches
Mail list logo
