On Thu, 2013-10-17 at 02:30 -0400, Chen Gong wrote:
> On Wed, Oct 16, 2013 at 07:59:09PM -0700, Joe Perches wrote:
[]
> > Maybe add a
> >
> > BUILD_BUG_ON(__builtin_constant_p(l) && __builtin_constant_p(h) && \
> > (h) < (l))
> >
> No, if so, users can't use variables for this macro.
__
On Thu, Oct 17, 2013 at 01:00:42AM +0200, Rafael J. Wysocki wrote:
> On Tuesday, October 08, 2013 10:56:11 AM Daniel Vetter wrote:
> > The drm/i915 driver wants to adjust it's own power policies using the
> > cpu policies as a guideline (we can implicitly boost the cpus through
> > the gpus on some
>>> On 16.10.13 at 20:43, Linus Torvalds wrote:
> So having looked at this some more, I would *really* prefer a
> different solution. The overwriting of the rip/rdp data just really
> annoys me.
>
> Is there any reason to not just do it like the following instead:
>
> - get rid of the "word_siz
--
Es ist Privat
Ich bin George Daniels, ein Banker und Credit-System-Programmierer (HSBC
Bank). Ich sah Ihre E-Mail-Adresse während des Surfens durch die Bank DTC
Bildschirm in mein Büro gestern so beschloss ich, diese Chance zu nutzen
sehr, Sie kennenzulernen. I glaube, wir sollten jede Gelege
On Thu, Oct 17, 2013 at 02:49:57PM +0800, Mark Zhang wrote:
> Hi,
>
> This is the first time I send mail to linux-pwm, I didn't read through
> the mails in this list, so if somebody already asked this question, I'm
> sorry about that.
>
> I wanna set some fops in "struct platform_pwm_backlight_da
On 10/16/13 10:34 PM, Andrew Morton wrote:
On Wed, 16 Oct 2013 17:43:57 +0900 Joonsoo Kim wrote:
There is two main topics in this patchset. One is to reduce memory usage
and the other is to change a management method of free objects of a slab.
The SLAB allocate a struct slab for each slab. Th
>>> On 16.10.13 at 22:40, Andrew Morton wrote:
> On Wed, 16 Oct 2013 12:32:40 +0100 "Jan Beulich" wrote:
>
>> Commit c4fe24485729fc2cbff324c111e67a1cc2f9adea ("sparc: fix PCI device
>> proc file mmap(2)"), while fixing one problem, introduced two new ones:
>> - the function truncates the return
Hi Jean-Christophe,
On 10/16/2013 05:14 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
...
>> +
>> +static inline void st_i2c_set_bits(void __iomem *reg, u32 mask)
>> +{
>> + writel(readl(reg) | mask, reg);
>> +}
>> +
>> +static inline void st_i2c_clr_bits(void __iomem *reg, u32 mask)
>> +{
>>
On Wed, Oct 16, 2013 at 07:14:27PM +0200, Stephen Warren wrote:
> On 10/16/2013 03:06 AM, Peter De Schrijver wrote:
> > On Tue, Oct 15, 2013 at 07:48:57PM +0200, Stephen Warren wrote:
> >> On 10/15/2013 08:52 AM, Peter De Schrijver wrote:
> >>> This patchset introduces common infrastructure for clo
On Wed, Oct 16, 2013 at 11:58:56PM -0700, Joe Perches wrote:
> Date: Wed, 16 Oct 2013 23:58:56 -0700
> From: Joe Perches
> To: Chen Gong
> Cc: tony.l...@intel.com, b...@alien8.de, naveen.n@linux.vnet.ibm.com,
> m.che...@samsung.com, aroza...@redhat.com, linux-a...@vger.kernel.org,
> linux-k
This seems like a regression in terms of separating mechanism and policy.
We have several access control systems available (SELinux, at least) which
can implement this functionality with existing mechanisms using dynamic
policy.
I'm concerned about the long term architectural impact of a prol
On Wed, Oct 16, 2013 at 07:21:12PM +0200, Stephen Warren wrote:
> On 10/16/2013 01:48 AM, Peter De Schrijver wrote:
> > On Tue, Oct 15, 2013 at 10:20:03PM +0200, Stephen Warren wrote:
> >> On 10/15/2013 09:14 AM, Peter De Schrijver wrote:
> >>> Tegra124 introduces a new PLL type, PLLSS. Add support
On 10/15/2013 02:10 PM, Daniel Lezcano wrote:
The Inter Processor Interrupt is used on ARM to tell another processor to do
a specific action. This is mainly used to emulate a timer interrupt on an idle
cpu, force a cpu to reschedule or run a function on another processor context.
Add a tracepoin
Hi all,
Once again this is long overdue so there are many changes.
The kernel patches are not being updated any more because of the
introduction of the vfs-automount changes to the VFS. If there
are needs in this area we will need to discuss how to deal with
them on the mailing list.
Known issue
On 16/10/2013 18:28, Vinod Koul :
Signed-off-by: Vinod Koul
CC: Nicolas Ferre
Acked-by: Nicolas Ferre
---
drivers/dma/at_hdmac.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/dma/at_hdmac.c b/drivers/dma/at_hdmac.c
index c787f38..1ef7457 100644
--- a/
* Stephane Eranian wrote:
> On Wed, Oct 16, 2013 at 7:53 PM, Arnaldo Carvalho de Melo
> wrote:
> > Em Wed, Oct 16, 2013 at 03:13:54PM +0200, Stephane Eranian escreveu:
> >> On Wed, Oct 16, 2013 at 2:46 PM, Ingo Molnar wrote:
> >> > We should also tell user-space that the unit of this counter i
On Wed, Oct 16, 2013 at 06:21:12PM -0500, Benjamin Herrenschmidt wrote:
> On Wed, 2013-10-16 at 11:04 +0200, Hendrik Brueckner wrote:
> > Indeed, two callbacks change the DTR line. The main difference is that
> > tiocmget/tiocmset can be called from user space by ioctl. That's not the
> > case
>
On 16/10/2013 22:14, Greg Kroah-Hartman :
On Tue, Oct 15, 2013 at 11:19:18AM +0200, Nicolas Ferre wrote:
On 14/10/2013 15:59, Jean-Christophe PLAGNIOL-VILLARD :
On 10:43 Thu 10 Oct , Nicolas Ferre wrote:
On older SoC, the "name" field is not filled in the register map.
Fix the way to figur
I need your partnership in a business transaction worth $19.7m USD for you to
handle with me. If interested, kindly get back to me for more details
--
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 a
On Thu, 17 Oct 2013, Vinod Koul wrote:
> On Wed, Oct 16, 2013 at 11:45:48AM -0700, Dan Williams wrote:
> > On Wed, Oct 16, 2013 at 11:29 AM, Guennadi Liakhovetski
> > >
> > > Doesn't this break kernel compilation for a total of 27 commits? Or am I
> > > missing anything?
> >
> > Yes, I think at t
This patch enhances the recovery routine not to write any data/node/meta until
its completion.
If any writes are sent to the disk, it could contaminate the written history
that will be used for further recovery.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/checkpoint.c | 2 +-
fs/f2fs/node.c |
On Thu, 2013-10-17 at 03:38 -0400, Chen Gong wrote:
> the point is we can use GENMASK like GENMASK(end_bit, start_bit) but
> we don't know the value of end_bit/start_bit at compile-time.
True.
The BUILD_BUG_ON idea is just to avoid people using
GENMASK(1, 2)
instead of
GENMASK(2,
On 17 October 2013 00:19, Alexandre Belloni
wrote:
> Other MMC hosts handle a regulator named vmmc-supply that allows to power the
> MMC card or SDIO device before communicating on the bus.
>
> Signed-off-by: Alexandre Belloni
> ---
>
> Changes in v2:
> - use mmc_regulator_get_supply instead of
(2013/10/17 16:23), Jan Beulich wrote:
On 16.10.13 at 22:40, Andrew Morton wrote:
On Wed, 16 Oct 2013 12:32:40 +0100 "Jan Beulich" wrote:
Commit c4fe24485729fc2cbff324c111e67a1cc2f9adea ("sparc: fix PCI device
proc file mmap(2)"), while fixing one problem, introduced two new ones:
- the func
On Thu, Oct 17, 2013 at 01:32:30AM -0700, Joe Perches wrote:
> On Thu, 2013-10-17 at 03:38 -0400, Chen Gong wrote:
> > the point is we can use GENMASK like GENMASK(end_bit, start_bit) but
> > we don't know the value of end_bit/start_bit at compile-time.
>
> True.
>
> The BUILD_BUG_ON idea is just
* Neil Horman wrote:
> On Mon, Oct 14, 2013 at 03:18:47PM -0700, Eric Dumazet wrote:
> > On Mon, 2013-10-14 at 14:19 -0700, Eric Dumazet wrote:
> > > On Mon, 2013-10-14 at 16:28 -0400, Neil Horman wrote:
> > >
> > > > So, early testing results today. I wrote a test module that, allocated
> >
On Thu, 2013-10-17 at 10:40 +0200, Borislav Petkov wrote:
> On Thu, Oct 17, 2013 at 01:32:30AM -0700, Joe Perches wrote:
> > On Thu, 2013-10-17 at 03:38 -0400, Chen Gong wrote:
> > > the point is we can use GENMASK like GENMASK(end_bit, start_bit) but
> > > we don't know the value of end_bit/start_
On 17/10/2013 10:34, Ulf Hansson wrote:
> On 17 October 2013 00:19, Alexandre Belloni
> wrote:
>> Other MMC hosts handle a regulator named vmmc-supply that allows to power the
>> MMC card or SDIO device before communicating on the bus.
>>
>> Signed-off-by: Alexandre Belloni
>> ---
>>
>> Changes i
On Wed, Oct 16, 2013 at 6:28 PM, Vinod Koul wrote:
> As we recently discussed in [1], the DMA_SUCCESS is an misnomer. The dmaengine
> does not acknowledge that dma completed succesfully. It can only signal dma
> was
> completed by it. Hence we should use DMA_COMPLTE as status instead of
> DMA_SU
Hello,
I tried to use x86/kaslr branch to check if how it works with kdump framework.
I found kexec doesn't work. According to the message, it looks like kexec
failing
to find kernel text map area from kcore.
$ sudo /sbin/kexec -p --command-line="ro
root=UUID=cdd5e357-d223-47ee-9d6e-d1fa78b3f
On 2013年10月17日 10:40, Lan Tianyu wrote:
> On 2013年10月17日 09:02, Lan Tianyu wrote:
>> On 2013年10月16日 20:42, Rafael J. Wysocki wrote:
>>> On Wednesday, October 16, 2013 05:26:21 PM Lan Tianyu wrote:
This is a multi-part message in MIME format.
--090400010209000300030201
Con
On Thu, Oct 17, 2013 at 10:14:20AM +0200, Ingo Molnar wrote:
> > > I.e. you would be encoding the counter unit as the suffix, might as well
> > > call it "power/cores.joules" and use the dot as the separator for the
> > > unit, but would be just a compact form to encode the counter->unit
> > > tabl
This patch series is mostly Freescale's SAI SoC Digital Audio Interface driver
implementation. And the implementation is only compatible with device tree
definition.
This patch series is based on linux-next and has been tested on Vybrid VF610
Tower board using device tree.
Added in v1:
- Add
This adds Freescale SAI ASoC Audio support.
This implementation is only compatible with device tree definition.
Features:
o Supports playback/capture
o Supports 16/20/24 bit PCM
o Supports 8k - 96k sample rates
o Supports slave mode only.
Signed-off-by: Alison Wang
---
sound/soc/fsl/Kconfig
(2013/10/17 17:59), HATAYAMA Daisuke wrote:
Hello,
I tried to use x86/kaslr branch to check if how it works with kdump framework.
Sorry, it's a branch of tip repository here:
http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/log/?h=x86/kaslr
--
Thanks.
HATAYAMA, Daisuke
--
To unsubsc
When the CONFIG_REGULATOR is disabled there will be some warnings
printed out.
Signed-off-by: Xiubo Li
---
sound/soc/codecs/sgtl5000.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/sound/soc/codecs/sgtl5000.c b/sound/soc/codecs/sgtl5000.c
index 1f4093f..4e2e4c
This patch add the SAI's edma mux Tx and Rx support.
Signed-off-by: Jingchang Lu
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610.dtsi | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/vf610.dtsi b/arch/arm/boot/dts/vf610.dtsi
index 18e3a4c..391f180 100
This adds the Document for Freescale SAI driver under
Documentation/devicetree/bindings/sound/.
Signed-off-by: Xiubo Li
---
.../devicetree/bindings/sound/fsl-sai.txt | 32 ++
1 file changed, 32 insertions(+)
create mode 100644 Documentation/devicetree/bindings/sound
This is the SGTl5000 codec based audio driver supported with both
playback and capture dai link implemention.
This implementation is only compatible with device tree definition.
Signed-off-by: Alison Wang
---
sound/soc/fsl/Kconfig| 10 +++
sound/soc/fsl/Makefile | 2 +
sound/so
This adds the Document for Freescale VF610 sound driver under
Documentation/devicetree/bindings/sound/.
Signed-off-by: Xiubo Li
---
.../devicetree/bindings/sound/fsl-sgtl5000.txt | 52 ++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindin
This patch add and enable SGT15000 codec support, and also specified
the corresponding SAI node.
Signed-off-by: Xiubo Li
Signed-off-by: Alison Wang ;
+ audio-codec = <&codec>;
+ audio-routing =
+ "MIC_IN", "Mic Jack",
+ "Mic
On Thu, Oct 17, 2013 at 11:07:30AM +0200, Peter Zijlstra wrote:
> The downside to such a sysfs entry will be the scope. It would either
> be pmu wide (unwieldy for many PMUs) or be only per listed event; and
> we really don't want exhaustive event lists in the kernel.
So why not teach perf tool to
This patch add and enable SAI device.
Signed-off-by: Xiubo Li
---
arch/arm/boot/dts/vf610-twr.dts | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/vf610-twr.dts b/arch/arm/boot/dts/vf610-twr.dts
index 1a58678..e4106dd 100644
--- a/arch/arm/boot/dts/vf610-twr.dts
+++ b/
>>> On 17.10.13 at 10:36, HATAYAMA Daisuke wrote:
> (2013/10/17 16:23), Jan Beulich wrote:
> On 16.10.13 at 22:40, Andrew Morton wrote:
>>> On Wed, 16 Oct 2013 12:32:40 +0100 "Jan Beulich" wrote:
>>>
Commit c4fe24485729fc2cbff324c111e67a1cc2f9adea ("sparc: fix PCI device
proc file
On Mon, Oct 14, 2013 at 1:15 PM, Jonas Jensen wrote:
> On 11 October 2013 17:44, Linus Walleij wrote:
>>> The register responsible for doing enable/disable is located
>>> at <0x98100100 0x4>, the clock register is very close at
>>> <0x9810 0x34>.
(...)
> Arnd made a similar comme
On Thu, Oct 17, 2013 at 12:28:59PM +1100, NeilBrown wrote:
> I always run with lockdep enabled, and I have done at least basic testing
Very good!
> >
> > Stuff like:
> >
> > + for (i = 0; i < NR_STRIPE_HASH_LOCKS; i++)
> > + spin_lock_init(conf->hash_locks + i);
> >
> > And:
> >
>
The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
"ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register
change."
need to be applied not only when system is booting, but when
MPU hits OSWR state through CPUIdle too.
Now the same issue is reproduced on boards
On OMAP4+ devices, GIC register context is lost when MPUSS hits the
OSWR. On the CPU wakeup path, ROM code gets executed and one of the
steps in it is to restore the saved context of the GIC.
The ROM code uses GICD != 1 condition to decide how the GIC registers
are handled in wakeup path from OSW
The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
"ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control
register change."
need to be applied not only when system is booting, but when MPU hits
OSWR state through CPUIdle too.
Unfortunately, commit "ARM: OMAP4+: CPU
On Wed, Oct 16, 2013 at 05:13:40PM +0100, Jan Beulich wrote:
> > It preserves *less* state, because the upper 32 bits of rip are now
> > corrupted. Any 64-bit application that actually looks at the FP
> > rip/rdp fields now get the WRONG VALUES.
>
> But again - this isn't being done for ordinary 6
Dear user
your email has exceeded 2GB, which is created by Webmaster, you are currently
running at 2.30GB, you can not Send or receive new messages until you check
your account.Complete the form to verify your account.
Please complete the details below to confirm your account
(1) E-mail:
(2) Na
Sorry, forgot to mention that patches are based on 4a10c2a Linux 3.12-rc2
On 10/17/2013 12:23 PM, Grygorii Strashko wrote:
The same workaround as ff999b8a0983ee15668394ed49e38d3568fc6859
"ARM: OMAP4460: Workaround for ROM bug because of CA9 r2pX GIC control register
change."
need to be applied
>>> On 17.10.13 at 11:27, Gleb Natapov wrote:
> On Wed, Oct 16, 2013 at 05:13:40PM +0100, Jan Beulich wrote:
>> > It preserves *less* state, because the upper 32 bits of rip are now
>> > corrupted. Any 64-bit application that actually looks at the FP
>> > rip/rdp fields now get the WRONG VALUES.
>
On Thu, Oct 17, 2013 at 12:39:55PM +0800, Wei Ni wrote:
> So do you mean it should call the regulator_has_full_constraints() in
> the .init_machine for all machines? If so, this will affect all boards,
> for example, in arch/arm/mach-tegra, if we set full constraints in the
> shared board file teg
> Waking up from system sleep state S3:
> [ cut here ]
> WARNING: CPU: 2 PID: 0 at kernel/time/tick-broadcast.c:667
> tick_broadcast_oneshot_control+0x181/0x190()
Thomas,
this WARN_ON_ONCE happens on resume on my HP ProBook 6555b.
Is it still needed to be verbose in such
On Wed, Oct 16, 2013 at 06:11:45PM +0100, Jiang Liu wrote:
> On 10/16/2013 07:46 PM, Will Deacon wrote:
> >
> >> + } else {
> >> + insn = aarch64_insn_gen_nop();
> >
> > You could make the code more concise by limiting your patching ability to
> > branch immediates. Then a nop is simply
On 17/10/13 08:27, Maxime COQUELIN wrote:
> ...
>>> >> +
>>> >> +static struct of_device_id st_i2c_match[] = {
>>> >> + { .compatible = "st,comms-ssc-i2c", },
>> > the rules is to put the first soc that use the ip in the compatible
>> > as st,sti7100-scc-i2c
> Ok. There are no plans to upstream
On Thu, Oct 17, 2013 at 01:07:12AM +0200, Peter Zijlstra wrote:
> On Wed, Oct 16, 2013 at 11:03:19PM +0200, Peter Zijlstra wrote:
> > Anyway; if you want to have a go at this, feel free.
>
> OK, couldn't help myself; completely untested patch below.
>
> I think the full once copy it best for the
On Wed, Oct 16, 2013 at 06:57:53PM -0700, Guenter Roeck wrote:
> do you plan to send this patch upstream anytime soon ?
It'll go next time I send stuff if it hasn't already.
signature.asc
Description: Digital signature
On Thu, Oct 17, 2013 at 10:33:33AM +0100, Jan Beulich wrote:
> >>> On 17.10.13 at 11:27, Gleb Natapov wrote:
> > On Wed, Oct 16, 2013 at 05:13:40PM +0100, Jan Beulich wrote:
> >> > It preserves *less* state, because the upper 32 bits of rip are now
> >> > corrupted. Any 64-bit application that act
Hi,
Xiubo Li wrote:
[...]
> diff --git a/sound/soc/fsl/fsl-pcm-dma.c b/sound/soc/fsl/fsl-pcm-dma.c
> new file mode 100644
> index 000..c4d925e
> --- /dev/null
> +++ b/sound/soc/fsl/fsl-pcm-dma.c
> @@ -0,0 +1,51 @@
[...]
> +
> +static int fsl_sai_probe(struct platform_device *pdev)
> +{
> +
On Wed, Oct 16, 2013 at 06:14:50PM +0100, Jiang Liu wrote:
> On 10/16/2013 11:36 PM, Jiang Liu wrote:
> > On 10/16/2013 06:51 PM, Will Deacon wrote:
> >> Take care here:
> >>
> >>- This doesn't guarantee that CPUs exclusively see new_insn (they
> >> may see old_insn, even after patching)
>
>>> On 16.10.13 at 19:05, Arjan van de Ven wrote:
>>> if you have found cases where this matters... maybe you found a new security
>>> issue...
>>
>> Iirc I could convince myself that in the cited cases the warnings
>> were there for no reason.
>
> can you pick one on a source level ?
> (and the
Am Donnerstag, den 17.10.2013, 17:01 +0800 schrieb Xiubo Li:
> This adds the Document for Freescale VF610 sound driver under
> Documentation/devicetree/bindings/sound/.
>
> Signed-off-by: Xiubo Li
> ---
> .../devicetree/bindings/sound/fsl-sgtl5000.txt | 52
> ++
> 1 file
>>> On 17.10.13 at 11:41, Gleb Natapov wrote:
> On Thu, Oct 17, 2013 at 10:33:33AM +0100, Jan Beulich wrote:
>> >>> On 17.10.13 at 11:27, Gleb Natapov wrote:
>> > On Wed, Oct 16, 2013 at 05:13:40PM +0100, Jan Beulich wrote:
>> >> > It preserves *less* state, because the upper 32 bits of rip are n
Hi Naveen,
On Thursday, October 17, 2013 08:41:13 AM Naveen Krishna Chatradhi wrote:
> On Exynos5250, the FALL interrupt related en, status and clear bits are
> available at an offset of
> 16 in INTEN, INTSTAT registers and at an offset of
> 12 in INTCLEAR register.
>
> On Exynos5420, the FALL i
2013/10/16 Geyslan Gregório Bem :
> 2013/10/16 Greg KH :
>> On Wed, Oct 16, 2013 at 12:57:35PM -0300, Geyslan G. Bem wrote:
>>> Casting (void *) value returned by kzalloc is useless
>>> as mentioned in Documentation/CodingStyle, Chap 14.
>>>
>>> Signed-off-by: Geyslan G. Bem
>>> ---
>>> drivers/s
2013/10/16 Geyslan G. Bem :
> Casting (void *) value returned by kmalloc is useless
> as mentioned in Documentation/CodingStyle, Chap 14.
>
> Signed-off-by: Geyslan G. Bem
> ---
> drivers/staging/dgap/dgap_parse.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/st
Em Wed, 16 Oct 2013 10:56:02 -0400
"Chen, Gong" escreveu:
> This patch adds a new interface to decode memory device (type 17)
> to help error reporting on DIMMs.
>
> Original-author: Tony Luck
> Signed-off-by: Chen, Gong
> Acked-by: Naveen N. Rao
Reviewed-by: Mauro Carvalho Chehab
> ---
>
Hi,
On Thu, Oct 17, 2013 at 05:01:14PM +0800, Xiubo Li wrote:
> When the CONFIG_REGULATOR is disabled there will be some warnings
> printed out.
A little confused by the title. But after looking at the comments,
is the patch just gonna add some debug info for the case when the
CONFIG_REGULATOR's
While fixing a simple crash on kvm module unload
1: rate_limit timer can fire after we free its key's module memory.
I noticed other deficiencies in jump_label/static_key code
(The most important is 4.)
2: jump_label_rate_limit() uses an initializator and thus cannot be used
more than once, l
When '.enabled.counter == 1', static_key_slow_dec_deferred() gets
silently dropped if the decrease is already pending.
We print a warning if this happens and because .enabled.counter cannot
go below 1 before the decrease has finished, the number of ignored
static_key_slow_dec_deferred() is kept an
We can cancel deferred static_key_slow_dec() instead of increasing
.enabled.counter.
Timer now won't fire before 'timeout' since last increase, so this patch
further stabilizes the case of frequent switching.
Signed-off-by: Radim Krčmář
---
include/linux/jump_label_ratelimit.h | 5 +
kernel
On Wed, Oct 16, 2013 at 04:25:35PM +0100, Christophe Leroy wrote:
> The patch adds WAN support for Infineon PEF2256 E1 Chipset.
>
> Signed-off-by: Jerome Chantelauze
> Acked-by: Christophe Leroy
> +static ssize_t fs_attr_mode_store(struct device *dev,
> + struct device_att
Patching of jump labels does not have to depend on any other init code,
so we should do it as soon as possible because static_keys cannot be
used before that.
If we find it does depend on something, the init case of patching should
be modified.
Signed-off-by: Radim Krčmář
---
There should be no
Hi,
Xiubo Li wrote:
> When the CONFIG_REGULATOR is disabled there will be some warnings
> printed out.
>
> Signed-off-by: Xiubo Li
> ---
> sound/soc/codecs/sgtl5000.c | 13 -
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/sound/soc/codecs/sgtl5000.c b/sound/soc
Simple replacement where possible.
Saves us problematic access to the structure and allows optimalizations
and bug fixes to take place.
Signed-off-by: Radim Krčmář
---
arch/x86/kvm/lapic.c | 7 ---
kernel/events/core.c | 6 +++---
2 files changed, 7 insertions(+), 6 deletions(-)
diff --git
Fix a bug when we free module memory while timer is pending by marking
deferred static keys and flushing the timer on module unload.
Also make static_key_rate_limit() useable more than once.
Reproducer: (host crasher)
modprobe kvm_intel
(sleep 1; echo quit) \
| qemu-kvm -kernel /dev/null
We implemented the optimized branch selection in higher levels of api.
That made static_keys very unintuitive, so this patch introduces another
element to jump_table, carrying one bit that tells the underlying code
which branch to optimize.
It is now possible to select optimized branch for every j
On 10/07/2013 10:21 PM, Robert C Jennings wrote:
> Introduce use of the unused SPLICE_F_MOVE flag for vmsplice to zap
> pages.
>
> When vmsplice is called with flags (SPLICE_F_GIFT | SPLICE_F_MOVE) the
> writer's gift'ed pages would be zapped. This patch supports further work
> to move vmsplice'd
Em Wed, 16 Oct 2013 10:56:03 -0400
"Chen, Gong" escreveu:
> In latest UEFI spec(by now it is 2.4) memory error definition
> for CPER (UEFI 2.4 Appendix N Common Platform Error Record)
> adds some new fields. These fields help people to locate
> memory error on actual DIMM location.
>
> Original-
On Thu, Oct 17, 2013 at 10:51:52AM +0100, Jan Beulich wrote:
> >>> On 17.10.13 at 11:41, Gleb Natapov wrote:
> > On Thu, Oct 17, 2013 at 10:33:33AM +0100, Jan Beulich wrote:
> >> >>> On 17.10.13 at 11:27, Gleb Natapov wrote:
> >> > On Wed, Oct 16, 2013 at 05:13:40PM +0100, Jan Beulich wrote:
> >>
Hi,
Xiubo Li wrote:
The subject has a wrong name for the codec "SGT1..." instead of
"SGTL...", which will make it difficult to search for this thread in
mail archives or in commit messages once this patches should be applied!
Lothar Waßmann
--
_
Em Wed, 16 Oct 2013 10:56:04 -0400
"Chen, Gong" escreveu:
> After H/W error happens under FFM enabled mode, lots of information
> are shown but some important parts like DIMM location missed. This
> patch is used to show these extra fileds.
>
> Original-author: Tony Luck
> Signed-off-by: Chen,
Em Wed, 16 Oct 2013 19:24:10 +0200
Borislav Petkov escreveu:
> On Wed, Oct 16, 2013 at 10:56:05AM -0400, Chen, Gong wrote:
> > Keep up only the most important fields for memory error
> > reporting. The detail information will be moved to perf/trace
> > interface.
> >
> > Suggested-by: Tony Luck
On Thu 17-10-13 00:36:41, Péter András Felvégi wrote:
> From: Peter A. Felvegi
>
> The UDF driver was not strict enough about checking the IDs in the
> VSDs when mounting, which resulted in reading through all the sectors
> of the block device in some unfortunate cases. Eg, trying to mount my
> u
Em Wed, 16 Oct 2013 20:35:32 +
"Luck, Tony" escreveu:
> > Are there any changes with regards to that, like some enforcement policy
> > for BIOS manufacturers to make it right?
>
> I am using a cricket bat to beat BIOS teams that implement eMCA to make
> sure they get the labels in SMBIOS rig
Em Wed, 16 Oct 2013 20:47:05 +
"Luck, Tony" escreveu:
> > Also, I suspect that, if an error happens to affect more than one DIMM
> > (e. g. part of the location is not available for a given error),
> > that the DIMM label will also not be properly shown.
>
> There are a couple of cases here:
Il 17/10/2013 12:10, Radim Krčmář ha scritto:
> Fix a bug when we free module memory while timer is pending by marking
> deferred static keys and flushing the timer on module unload.
>
> Also make static_key_rate_limit() useable more than once.
>
> Reproducer: (host crasher)
> modprobe kvm_inte
* Peter Zijlstra [2013-10-08 12:25:07]:
> From: Oleg Nesterov
>
> It is functionally equivalent to
>
> struct rcu_sync_struct {
> atomic_t counter;
> };
>
> static inline bool rcu_sync_is_idle(struct rcu_sync_struct *xxx)
> {
> r
>>> On 17.10.13 at 12:23, Gleb Natapov wrote:
> On Thu, Oct 17, 2013 at 10:51:52AM +0100, Jan Beulich wrote:
>> >>> On 17.10.13 at 11:41, Gleb Natapov wrote:
>> > KVM obviously knows the complete state of virtual CPU. It can figure the
>> > situation above by looking at CS descriptor, not need to
Il 17/10/2013 12:10, Radim Krčmář ha scritto:
> Simple replacement where possible.
> Saves us problematic access to the structure and allows optimalizations
> and bug fixes to take place.
I think you should introduce this first as a simple wrapper around
static_key_slow_inc, and then add the bells
On 10/17/2013 05:37 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Thu, Oct 17, 2013 at 12:39:55PM +0800, Wei Ni wrote:
>
>> So do you mean it should call the regulator_has_full_constraints() in
>> the .init_machine for all machines? If so, this will affect all boards,
>> for examp
On Thu, Oct 17, 2013 at 11:37:48AM +0100, Jan Beulich wrote:
> >>> On 17.10.13 at 12:23, Gleb Natapov wrote:
> > On Thu, Oct 17, 2013 at 10:51:52AM +0100, Jan Beulich wrote:
> >> >>> On 17.10.13 at 11:41, Gleb Natapov wrote:
> >> > KVM obviously knows the complete state of virtual CPU. It can fig
On Thu, Oct 17, 2013 at 02:51:34AM +0100, Wang, Yalin wrote:
> Hi Will,
Hello,
> I am happy to notify that our stability test has passed,
> And this Crash don't happen again,
> So seems this patch work now .
Great!
> We has merged it into our release SW .
> Could I know if this patch will be
Il 17/10/2013 12:10, Radim Krčmář ha scritto:
> While fixing a simple crash on kvm module unload
>
> 1: rate_limit timer can fire after we free its key's module memory.
>
> I noticed other deficiencies in jump_label/static_key code
> (The most important is 4.)
>
> 2: jump_label_rate_limit() uses
On Wed, 16 Oct 2013 18:36:19 -0500
Steve French wrote:
> cp --reflink opens the target file for O_WRONLY before invoking the
> (BTRFS) ioctl for clone file, but for copy offload over the network
> the SMB2 specification requires that the target file be open O_RDWR.
>
> I may be able to upgrade t
On 10/14/2013 05:08 PM, Vyacheslav Tyrtov wrote:
From: Tarek Dakhran
Add EDCS(Exynos Dual Cluster Support) for Samsung Exynos5410 SoC.
This enables all 8 cores, 4 x A7 and 4 x A15 run at the same time.
IIUC, the 5410 has a CCI-400 bug preventing to use the two clusters at
the same time. Righ
Commit 040a0a37 "mutex: Add support for wound/wait style locks" used
"!__builtin_constant_p(p == NULL)" but gcc 3.x cannot handle such expression
correctly, leading to boot failure when built with CONFIG_DEBUG_MUTEXES=y.
Fix it by explicitly passing a bool which tells whether p != NULL or not.
Si
On Thu, Oct 17, 2013 at 10:27:13AM +0200, Guennadi Liakhovetski wrote:
> On Thu, 17 Oct 2013, Vinod Koul wrote:
>
> > On Wed, Oct 16, 2013 at 11:45:48AM -0700, Dan Williams wrote:
> > > On Wed, Oct 16, 2013 at 11:29 AM, Guennadi Liakhovetski
> > > >
> > > > Doesn't this break kernel compilation fo
1 - 100 of 655 matches
Mail list logo
