From: Rik van Riel
Only run vtime_user_enter, vtime_user_exit, and the user enter & exit
trace points when we are entering or exiting user state, respectively.
The KVM code in guest_enter and guest_exit already take care of calling
vtime_guest_enter and vtime_guest_exit, respectively.
The RCU
On 10/03/15 14:26, Borislav Petkov wrote:
On Tue, Mar 10, 2015 at 02:22:22PM +, Sudeep Holla wrote:
I was able to reproduce this and now I realise I had CONFIG_AMD_NB
disabled in my config earlier which hid this issue previously, sorry
for that.
The below patch fixed the issue on my
* Arnaldo Carvalho de Melo wrote:
> Em Tue, Mar 10, 2015 at 11:03:31AM +0100, Ingo Molnar escreveu:
> > So I got this error today:
> >
> > ┌─Warning:───┐
> > │The vmlinux file can't be used. │
> > │Kernel samples will not be resolved.│
> > │
Current context tracking symbols are designed to express living state.
As such they are prefixed with "IN_": IN_USER, IN_KERNEL.
Now we are going to use these symbols to also express state transitions
such as context_tracking_enter(IN_USER) or context_tracking_exit(IN_USER).
But while the "IN_"
On Mon, Mar 9, 2015 at 4:41 PM, Tony Lindgren wrote:
> * Bin Liu [150309 14:35]:
>> On Mon, Mar 9, 2015 at 4:26 PM, Tony Lindgren wrote:
>> > * Felipe Balbi [150309 14:21]:
>> >> On Mon, Mar 09, 2015 at 04:17:29PM -0500, Bin Liu wrote:
>> >> > On Mon, Mar 9, 2015 at 4:13 PM, Felipe Balbi
Ingo,
Please pull the nohz/guest branch that can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
nohz/guest
This is 4.1 material.
HEAD: 126a6a542446f1a49b9f3c69237c87df3eb4e6e1
---
Some measurements showed that disabling the tick on the host
From: Rik van Riel
The host kernel is not doing anything while the CPU is executing
a KVM guest VCPU, so it can be marked as being in an extended
quiescent state, identical to that used when running user space
code.
The only exception to that rule is when the host handles an
interrupt, which is
On Tue, Mar 10, 2015 at 02:22:22PM +, Sudeep Holla wrote:
> I was able to reproduce this and now I realise I had CONFIG_AMD_NB
> disabled in my config earlier which hid this issue previously, sorry
> for that.
>
> The below patch fixed the issue on my Intel i7 box. I can post this
>
On 3/10/15 12:06 AM, Namhyung Kim wrote:
Hi Arnaldo,
On Mon, Mar 09, 2015 at 10:21:35AM -0300, Arnaldo Carvalho de Melo wrote:
For trace I need to take advantage of the fact that each mmap is ordered
already and then just sort by the timestamp in the mmap head, etc.
In retrospect, the
On Mon, Mar 09, 2015 at 09:43:18PM -0700, Paul E. McKenney wrote:
> On Mon, Mar 09, 2015 at 04:49:43PM -0700, Paul E. McKenney wrote:
> > On Mon, Mar 09, 2015 at 04:39:47PM -0700, Paul E. McKenney wrote:
> > > On Mon, Mar 09, 2015 at 02:40:21PM -0700, Paul E. McKenney wrote:
> > > > On Mon, Mar
On Wed, Mar 04, 2015 at 05:35:22PM -0500, Matthew Hiles wrote:
> [3.763182] i2c_hid i2c-ITE8386:00: Could not register for ITE8386:00
> interrupt, irq = -1, ret = -22
> [3.773742] i2c_hid: probe of i2c-ITE8386:00 failed with error -22
> [3.788298] i2c_hid i2c-ATML1000:00: Could not
On Mon, Mar 09, 2015 at 02:35:42PM -0700, Paul E. McKenney wrote:
> On Mon, Mar 09, 2015 at 09:36:52AM +, Alexander Gordeev wrote:
> > On Mon, Mar 09, 2015 at 09:34:04AM +0100, Alexander Gordeev wrote:
> > > Hi Paul,
> > >
> > > Here is cleanup of RCU tree initialization rebased on linux-rcu
On Tuesday 10 March 2015 16:26:26 Aleksey Makarov wrote:
> The OCTEON SATA controller is currently found on cn71XX devices.
>
> Cc: Arnd Bergmann
> Acked-by: Hans de Goede
> Signed-off-by: David Daney
> Signed-off-by: Vinita Gupta
> Signed-off-by: Aleksey Makarov
> ---
>
[cc: Oleg, Borislav]
On Tue, Mar 10, 2015 at 7:03 AM, Andy Lutomirski wrote:
> As far as I can tell, these fields have been set to zero on save and
> ignored on restore since Linux was imported into git. Rename them
> '__pad1' and '__pad2' to avoid confusion and to allow them to be
> recycled
[cc: Oleg, Borislav]
On Tue, Mar 10, 2015 at 7:03 AM, Andy Lutomirski wrote:
> The comment in the signal code says that apps can save/restore other
> segments on their own. It's true that apps can *save* SS on their
> own, but there's no way for apps to restore it: SYSCALL effectively
> resets
On Tue, Mar 10, 2015 at 01:01:07PM +0100, Petr Mladek wrote:
> On Mon 2015-03-09 09:40:55, Josh Poimboeuf wrote:
> > On Mon, Mar 09, 2015 at 02:25:28PM +0100, Petr Mladek wrote:
> > > +
> > > mutex_unlock(_mutex);
> > > }
> > >
> > > @@ -736,6 +748,7 @@ static int klp_init_object(struct
On Wed, Feb 18, 2015 at 3:50 AM, Benjamin Herrenschmidt
wrote:
> On Tue, 2015-02-17 at 20:57 -0800, Greg Kroah-Hartman wrote:
>
>> > Acked-by: Rob Herring
>>
>> Thanks, I'll queue these up after 3.20-rc1 is out.
It doesn't look like these 2 patches got applied.
Rob
--
To unsubscribe from this
On Tue 10-03-15 06:03:23, Christoph Hellwig wrote:
> On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
> > Any updates?
>
> Please just add disk quota support to tmpfs so thast the standard quota
> netlink notifications can be used.
If I understand the problem at hand, they are
On Tue, Mar 10, 2015 at 11:53:35AM +, Sudeep Holla wrote:
Hi Boris,
On 10/03/15 11:37, Borislav Petkov wrote:
> Hi,
>
> I just triggered this is on rc3 + tip/master which has your patch. This
> is an Intel SNB. Ideas, already fixed?
>
No, not seen this before. I will test tip/master on my
On Mon, Mar 09, 2015 at 11:34:50AM -0500, Josh Poimboeuf wrote:
> Personally I don't think the "4.x" numbers add anything to the
> understanding of the document.
Maybe the reason you think so is that you are quite familiar with the kernel,
but we should also take care of the ones who are not
On Tue, Mar 10, 2015 at 12:23:03PM +, Hanjun Guo wrote:
> On 2015年03月07日 01:47, Lorenzo Pieralisi wrote:
> > On Wed, Feb 25, 2015 at 08:39:58AM +, Hanjun Guo wrote:
> >> From: Al Stone
> >>
> >> ACPI reduced hardware mode is disabled by default, but ARM64
> >> can only run properly in
On Tue, 10 Mar 2015, Peter Zijlstra wrote:
> On Mon, Mar 09, 2015 at 04:48:43PM -0400, Eric B Munson wrote:
> > Currently, pages which are marked as unevictable are protected from
> > compaction, but not from other types of migration. The mlock
> > desctription does not promise that all page
Op 10-03-15 om 13:37 schreef Peter Zijlstra:
> On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote:
>> +static int __sched __mutex_lock_check_stamp(struct rt_mutex *lock,
>> +struct ww_acquire_ctx *ctx)
>> +{
>> +#ifdef
On Tue, Mar 10, 2015 at 11:01:34AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Mar 10, 2015 at 01:00:35PM +0100, Jiri Olsa escreveu:
> > On Mon, Mar 09, 2015 at 08:28:45PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Mon, Mar 09, 2015 at 08:11:19PM -0300, Arnaldo Carvalho de Melo
> > >
On Tue, Mar 10, 2015 at 3:02 PM, Andy Lutomirski wrote:
> On Tue, Mar 10, 2015 at 7:00 AM, Denys Vlasenko
> wrote:
>> On Tue, Mar 10, 2015 at 2:26 PM, Andy Lutomirski wrote:
>>> usersp is IMO tolerable. The nasty thing is the FIXUP_TOP_OF_STACK /
>>> RESTORE_TOP_OF_STACK garbage, and this
On 10/03/15 13:00, Peter Zijlstra wrote:
On Tue, Mar 10, 2015 at 01:53:51PM +0100, Peter Zijlstra wrote:
It would be nicer if we could prevent this in the core so we're not
reliant on every PMU driver doing the same verification. My initial
thought was that seemed like unnecessary duplication
Hi Dave,
here is wireless-drivers pull request for 4.0, changelog below. Please
let me know if there are any problems.
Kalle
The following changes since commit acf8dd0a9d0b9e4cdb597c2f74802f79c699e802:
udp: only allow UFO for packets from SOCK_DGRAM sockets (2015-03-02 22:19:29
-0500)
are
Em Tue, Mar 10, 2015 at 11:03:31AM +0100, Ingo Molnar escreveu:
> So I got this error today:
>
> ┌─Warning:───┐
> │The vmlinux file can't be used. │
> │Kernel samples will not be resolved.│
> ││
> │
The comment in the signal code says that apps can save/restore other
segments on their own. It's true that apps can *save* SS on their
own, but there's no way for apps to restore it: SYSCALL effectively
resets SS to __USER_DS, so any value that user code tries to load
into SS gets lost on entry
Sorry, forgot to CC Oleg and Borislav. Let me know if you want me to
forward the rest of the thread to you.
On Tue, Mar 10, 2015 at 7:03 AM, Andy Lutomirski wrote:
> Patch 1 is IMO a bug fix.
>
> Patch 2 is a cleanup and avoids some confusion. It's also sort of an
> API break (no ABI change)
2015-03-10 14:06 GMT+01:00 Mathias Nyman :
> On 10.03.2015 11:40, Jörg Otte wrote:
>> If I plug in my USB DVB-T stick I get the following in dmesg:
>>
>> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
>> state.
>> dvb-usb: will pass the complete MPEG2 transport stream to
> So the problem is that event_init() is what will return the pmu, so we
> cannot make decisions on it until after that returns.
I took a look into hacking something into perf_try_init_event, but it
ends up duplicating all of the existing tests and looks really out of
place.
> Maybe we can pull
Hi
10.03.2015, 02:09, "David Fries" :
> diff --git a/drivers/w1/slaves/w1_therm.c b/drivers/w1/slaves/w1_therm.c
> index 1f11a20..39a9e6a 100644
> --- a/drivers/w1/slaves/w1_therm.c
> +++ b/drivers/w1/slaves/w1_therm.c
> @@ -59,9 +59,20 @@ MODULE_ALIAS("w1-family-"
As far as I can tell, these fields have been set to zero on save and
ignored on restore since Linux was imported into git. Rename them
'__pad1' and '__pad2' to avoid confusion and to allow them to be
recycled some day.
I'm intentionally avoiding calling either of them __pad0: the field
formerly
Patch 1 is IMO a bug fix.
Patch 2 is a cleanup and avoids some confusion. It's also sort of an
API break (no ABI change) because it removes a struct field. But that
struct field has never done anything at all as far as I can tell.
AFAICT this series got bogged down in discussion about patch 2
On Tue, Mar 10, 2015 at 7:00 AM, Denys Vlasenko
wrote:
> On Tue, Mar 10, 2015 at 2:26 PM, Andy Lutomirski wrote:
>> usersp is IMO tolerable. The nasty thing is the FIXUP_TOP_OF_STACK /
>> RESTORE_TOP_OF_STACK garbage, and this patch is the main step toward
>> killing that off completely. I've
Em Tue, Mar 10, 2015 at 01:00:35PM +0100, Jiri Olsa escreveu:
> On Mon, Mar 09, 2015 at 08:28:45PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Mar 09, 2015 at 08:11:19PM -0300, Arnaldo Carvalho de Melo escreveu:
> > > Em Mon, Mar 09, 2015 at 06:51:21PM -0300, Arnaldo Carvalho de Melo
> > >
On Tue, Mar 10, 2015 at 2:26 PM, Andy Lutomirski wrote:
> usersp is IMO tolerable. The nasty thing is the FIXUP_TOP_OF_STACK /
> RESTORE_TOP_OF_STACK garbage, and this patch is the main step toward
> killing that off completely. I've still never convinced myself that
> there aren't
On 03/09/2015 09:49 PM, Fam Zheng wrote:
> + if (!cmds || ncmds <= 0 || ncmds > EP_MAX_BATCH)
> + return -EINVAL;
> + cmd_size = sizeof(struct epoll_ctl_cmd) * ncmds;
> + /* TODO: optimize for small arguments like select/poll with a stack
> + * allocated buffer */
> +
Hi Wolfram,
You can add my
Acked-by and Tested-By: Ludovic Desroches
Tested on sama5d3, some problems with at24 eeprom on sama5d4 but it
doesn't come from the i2c quirks patch series.
Regards
Ludovic
On Sun, Mar 08, 2015 at 09:28:45AM +0100, Wolfram Sang wrote:
> On Wed, Feb 25, 2015 at
* Andy Lutomirski wrote:
> On Mon, Mar 9, 2015 at 9:57 PM, Ingo Molnar wrote:
> >
> > * Andy Lutomirski wrote:
> >
> >> On Mon, Mar 9, 2015 at 9:48 AM, Ingo Molnar wrote:
> >> >
> >> > now I get this build failure:
> >> >
> >> > make[1]: Entering directory
> >> >
On Tue, Mar 10, 2015 at 2:21 PM, Ingo Molnar wrote:
>> Since this patch does add two extra MOVs,
>> I did benchmark these patches. They add exactly one cycle
>> to system call code path on my Sandy Bridge CPU.
>
> Hm, but that's the wrong direction, we should try to make it faster,
> and to clean
On Tuesday 10 March 2015 10:42:09 Alexandre Belloni wrote:
> >
> > I actually added a bunch of these in other places, but have stopped
> > doing so because Russell didn't like them, and I tend to follow
> > his argument now that it's actually pretty confusing.
> >
> > In case of at91, we can do
On 03/09/2015 09:13 PM, Krzysztof Kozlowski wrote:
> On pon, 2015-03-09 at 20:46 +0900, Beomho Seo wrote:
>> On 03/09/2015 08:02 PM, Krzysztof Kozlowski wrote:
>>> 2015-03-09 1:35 GMT+01:00 Beomho Seo :
On 03/08/2015 05:13 AM, Sebastian Reichel wrote:
> On Mon, Mar 02, 2015 at 07:10:35PM
On 03/09/2015 07:01 PM, Krzysztof Kozlowski wrote:
> 2015-03-09 1:36 GMT+01:00 Beomho Seo :
>> On 03/08/2015 05:14 AM, Sebastian Reichel wrote:
>>> Hi,
>>>
>>> On Mon, Mar 02, 2015 at 07:10:36PM +0900, Jaewon Kim wrote:
From: Beomho Seo
This patch adds device driver of max77843
This patch fix some spelling typo found in gadget.xml.
It is because this file is generated from comments in sources,
I had to fix comments in the source, instead of xml file itself.
Signed-off-by: Masanari Iida
---
drivers/usb/gadget/composite.c | 4 ++--
include/linux/usb/gadget.h | 2 +-
On Tue, 03 Mar, at 07:34:33AM, Ingo Molnar wrote:
>
> So why are interrupts disabled around page table operations to begin
> with? It's not like any of this can execute on two CPUs at once, nor
> can this be executed from interrupt context.
>
> So, shouldn't we only protect the EFI calls
On Tue, 03 Mar, at 07:48:50AM, Ingo Molnar wrote:
>
> Also clean up the save_pgd global variable while at it.
>
> untested as well.
>
> Thanks,
>
> Ingo
>
> ==>
> From 166625ceaef68fcbeee63adc63c02d75abcaf0db Mon Sep 17 00:00:00 2001
> From: Ingo Molnar
> Date: Tue, 3 Mar
2015-03-06 13:52 GMT+01:00 Matthias Brugger :
> This patch enables the pin controller for Mediatek SoCs.
>
> Signed-off-by: Matthias Brugger
Applied to v4.0-next/soc
> ---
> arch/arm/mach-mediatek/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/mach-mediatek/Kconfig
On Tue, Mar 10, 2015 at 12:42:33PM +0100, Olaf Hering wrote:
> It would be nice to change .proc_name to KBUILD_MODNAME before v4.0 is
> released. We carry a patch which adds this field. Of cource we can just
> change the patch, but if code gets touched upstream anyway...
Please send a patch.
The OCTEON SATA controller is currently found on cn71XX devices.
Cc: Arnd Bergmann
Acked-by: Hans de Goede
Signed-off-by: David Daney
Signed-off-by: Vinita Gupta
Signed-off-by: Aleksey Makarov
---
.../devicetree/bindings/ata/ahci-platform.txt | 1 +
> * Denys Vlasenko wrote:
>
> > > So there are now +2 instructions (5 instead of 3) in the
> > > system_call path, but there are -2 instructions in the SYSRETQ
> > > path,
> >
> > Unfortunately, no. [...]
>
> So I assumed that it was an equivalent transformation, given that
> none of the
Hi Aneesh,
On 03/03/15 12:16, Aneesh Kumar K.V wrote:
> Stefan Strogin writes:
>
>> When CONFIG_CMA_BUFFER_LIST is configured a file is added to debugfs:
>> /sys/kernel/debug/cma/cma-/buffers contains a list of currently allocated
>> CMA buffers for each CMA region (N stands for number of CMA
On Tue, Mar 10, 2015 at 6:21 AM, Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
>> > So there are now +2 instructions (5 instead of 3) in the
>> > system_call path, but there are -2 instructions in the SYSRETQ
>> > path,
>>
>> Unfortunately, no. [...]
>
> So I assumed that it was an equivalent
This patch assigns the more appropriate void* type to the mmio750 variable
eliminating an unnecessary volatile qualifier in the process. Additionally it
updates parameter types as necessary where those parameters interact with
mmio750, removes unnecessary casts and updates the type of the
* Andy Lutomirski wrote:
> > Since this patch does add two extra MOVs,
> > I did benchmark these patches. They add exactly one cycle
> > to system call code path on my Sandy Bridge CPU.
>
> Personally, I'm willing to pay that cycle. It could be a bigger
> savings on context switch, and the
On 03/09/2015 10:47 PM, Tim Kryger wrote:
> The current workaround of clearing fifos and retrying a fixed number
> of times isn't ideal but I'm not sure what else can be done given the
> way this hardware works.
But hanging the machine is not an acceptable outcome.
Since the hang stems from the
On 10 March 2015 at 13:06, Dan Carpenter wrote:
> You should have said that in the patch description or under the ---
> cut off. But anyway, it's not ok. And we'll need to redo this patch.
> Breaking up patches into logical changes is sort of tricky because
> everything touches everything else
* Denys Vlasenko wrote:
> > So there are now +2 instructions (5 instead of 3) in the
> > system_call path, but there are -2 instructions in the SYSRETQ
> > path,
>
> Unfortunately, no. [...]
So I assumed that it was an equivalent transformation, given that none
of the changelogs spelled
On Tue, Mar 10, 2015 at 6:18 AM, Denys Vlasenko wrote:
> On 03/10/2015 01:51 PM, Ingo Molnar wrote:
>>
>> * Denys Vlasenko wrote:
>>
>>> PER_CPU(old_rsp) usage is simplified - now it is used only
>>> as temp storage, and userspace stack pointer is immediately stored
>>> in pt_regs->sp on syscall
On Mar 10, 2015 1:12 AM, "joeyli" wrote:
>
> Hi,
>
> On Mon, Mar 09, 2015 at 02:10:37PM +0200, Boaz Harrosh wrote:
> > On 03/06/2015 01:09 AM, Andy Lutomirski wrote:
> > <>
> > >
> > > I will be shocked if a standard of this form ever appears. Modern
> > > systems *don't have e820*. The BIOSes
On 03/10/2015 01:51 PM, Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
>> PER_CPU(old_rsp) usage is simplified - now it is used only
>> as temp storage, and userspace stack pointer is immediately stored
>> in pt_regs->sp on syscall entry, instead of being used later,
>> on syscall exit.
>>
>>
> -Original Message-
> From: Tejun Heo [mailto:hte...@gmail.com] On Behalf Of Tejun Heo
> Sent: Monday, March 9, 2015 2:23 PM
> To: Du, Changbin
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] workqueue: detect uninitated work_struct and BUG() if
> true
> > @@ -1295,6 +1295,9 @@
On Mon, Mar 9, 2015 at 9:57 PM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> On Mon, Mar 9, 2015 at 9:48 AM, Ingo Molnar wrote:
>> >
>> > now I get this build failure:
>> >
>> > make[1]: Entering directory
>> > '/home/mingo/tip/tools/testing/selftests/x86'
>> > gcc -m32 -o sigreturn_32
Hi Alexei
Please find some comments and suggestions below.
On Mon, Mar 9, 2015 at 11:10 PM, Alexei Starovoitov wrote:
> Signed-off-by: Alexei Starovoitov
> ---
> man2/bpf.2 | 593
>
> 1 file changed, 593 insertions(+)
> create
2015-03-10 5:54 GMT+01:00 Hongzhou Yang :
> Base on v4.0-rc1, resend it.
>
>
> Add pinctrl,GPIO and EINT node to mt8173.dtsi.
>
> Signed-off-by: Hongzhou Yang
applied to v4.0-next/arm64
Thanks,
Matthias
> ---
> arch/arm64/boot/dts/mediatek/mt8173-pinfunc.h
On Tue, Mar 10, 2015 at 5:51 AM, Ingo Molnar wrote:
>
> * Denys Vlasenko wrote:
>
>> PER_CPU(old_rsp) usage is simplified - now it is used only
>> as temp storage, and userspace stack pointer is immediately stored
>> in pt_regs->sp on syscall entry, instead of being used later,
>> on syscall
2015-03-10 19:20 GMT+09:00 Gilad Broner :
>>> +static bool inject_cmd_hang_tr(struct ufs_hba *hba)
>>> +{
>>> + int tag;
>>> +
>>> + tag = find_first_bit(>outstanding_reqs, hba->nutrs);
>>> + if (tag == hba->nutrs)
>>> + return 0;
>>> +
>>> + __clear_bit(tag,
* Viresh Kumar wrote:
> On 27 February 2015 at 17:21, Viresh Kumar wrote:
> > Hi Thomas/Ingo,
> >
> > This is in response to the suggestions Ingo gave [1] on the shortcomings of
> > clockevents core's state machine.
> >
> > This first separates out the RESUME functionality from other states as
On Mon, Mar 09, 2015 at 09:02:19PM +, Mel Gorman wrote:
> On Sun, Mar 08, 2015 at 08:40:25PM +, Mel Gorman wrote:
> > > Because if the answer is 'yes', then we can safely say: 'we regressed
> > > performance because correctness [not dropping dirty bits] comes before
> > > performance'.
>
On Tue, Mar 10, 2015 at 12:47:44PM +, Lorenzo Stoakes wrote:
> On 10 March 2015 at 12:36, Sudip Mukherjee wrote:
> > but it is introducing two new build warnings:
> >
> > drivers/staging/sm750fb/sm750_hw.c: In function ‘hw_sm750_map’:
> > drivers/staging/sm750fb/sm750_hw.c:67:2: warning:
Hi,
Le mercredi 04 mars 2015 à 02:13 +0200, Matthias Bonne a écrit :
> I am trying to understand how mutexes work in the kernel, and I think
> there might be a race between mutex_trylock() and mutex_unlock(). More
> specifically, the race is between the functions
> __mutex_trylock_slowpath and
On Tue, Mar 10, 2015 at 10:51:41AM +0900, Kyungmin Park wrote:
> Any updates?
Please just add disk quota support to tmpfs so thast the standard quota
netlink notifications can be used.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 10.03.2015 11:40, Jörg Otte wrote:
> If I plug in my USB DVB-T stick I get the following in dmesg:
>
> dvb-usb: found a 'TerraTec/qanu USB2.0 Highspeed DVB-T Receiver' in warm
> state.
> dvb-usb: will pass the complete MPEG2 transport stream to the software
> demuxer.
> DVB: registering new
Hi,
I'm resending the patch from here:
http://lkml.iu.edu/hypermail/linux/kernel/1502.3/00286.html
GCC fixincludes always change that header to comply with C standard.
Here is the comment from fixincludes code:
/* Fix for machine name #ifdefs that are not in the namespace reserved
by the C
On Tue, Mar 10, 2015 at 01:53:51PM +0100, Peter Zijlstra wrote:
> > It would be nicer if we could prevent this in the core so we're not
> > reliant on every PMU driver doing the same verification. My initial
> > thought was that seemed like unnecessary duplication of the ctx checking
> > above,
On Mon, Mar 09, 2015 at 09:28:28AM -0400, Tejun Heo wrote:
> Now that %pb[l] formatting is now in mainline, this can go forward.
> Here's the updated patch which uses printf instead of the fixed buffer
> when printing cpus. I couldn't find a better option at the moment and
> am still appending
On Tue, Mar 10 2015, Tejun Heo wrote:
> Hello,
>
> On Tue, Mar 10, 2015 at 11:47:47AM +0100, Rasmus Villemoes wrote:
>> I can't explain why num_to_str apparently becomes slightly slower (the
>> patch essentially didn't touch it), but the put_dec_ helpers in any case
>> make up for that.
>
>
On Tue 10 Mar 04:55 PDT 2015, Mark Brown wrote:
> Currently probe deferral prints a message every time a device requests
> deferral at info severity (which is displayed by default). This can have
> an impact on system boot times with serial consoles and is generally quite
> noisy.
>
> Since
On Tue, Mar 10, 2015 at 12:05:21PM +, Mark Rutland wrote:
> On Tue, Mar 10, 2015 at 11:27:23AM +, Peter Zijlstra wrote:
> > On Mon, Mar 09, 2015 at 12:46:30PM +, Suzuki K. Poulose wrote:
> > > From: "Suzuki K. Poulose"
> > >
> > > Don't allow grouping hardware events from different
On Tue, 2015-03-10 at 11:06 +, Mark Brown wrote:
> On Tue, Mar 10, 2015 at 10:10:56AM +0200, Ivan T. Ivanov wrote:
> > On Mon, 2015-03-09 at 18:28 +, Mark Brown wrote:
>
> > > > About the API usage, point taken. GPIO requesting part is more important
> > > > in this case. pinctrl core
* Denys Vlasenko wrote:
> PER_CPU(old_rsp) usage is simplified - now it is used only
> as temp storage, and userspace stack pointer is immediately stored
> in pt_regs->sp on syscall entry, instead of being used later,
> on syscall exit.
>
> Instead of PER_CPU(old_rsp) and task->thread.usersp,
Add the {xen-pvscsi: } prefix in pr_fmt and remove DPRINTK, then
replace all DPRINTK with pr_debug.
Also fixed up some comments just as eliminate redundant whitespace
and format the code.
These will make the code easier to read.
Signed-off-by: Tao Chen
---
drivers/xen/xen-scsiback.c | 75
On 10 March 2015 at 12:36, Sudip Mukherjee wrote:
> but it is introducing two new build warnings:
>
> drivers/staging/sm750fb/sm750_hw.c: In function ‘hw_sm750_map’:
> drivers/staging/sm750fb/sm750_hw.c:67:2: warning: passing argument 1 of
> ‘ddk750_set_mmio’ discards ‘volatile’ qualifier from
Hello, Aleksa.
On Tue, Mar 10, 2015 at 07:19:06PM +1100, Aleksa Sarai wrote:
> I'm not sure how to check for equality between two `css_set`s (or just two
> `css`s). Is there a function to do so? Also, I'm not sure if there's a nice
> way
You can compare the css pointers for equality.
> of
On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote:
> +static int __sched __mutex_lock_check_stamp(struct rt_mutex *lock,
> + struct ww_acquire_ctx *ctx)
On that; should we rename this to __ww_mutex_check_wound() ? or
something to
On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote:
> +#ifdef CONFIG_WW_MUTEX_RTMUTEX
> +static void ww_mutex_lock_acquired(struct ww_mutex *ww,
> +struct ww_acquire_ctx *ww_ctx)
> +{
> +#ifdef CONFIG_DEBUG_MUTEXES
> + /*
> + * If
Hello,
On Tue, Mar 10, 2015 at 11:47:47AM +0100, Rasmus Villemoes wrote:
> I can't explain why num_to_str apparently becomes slightly slower (the
> patch essentially didn't touch it), but the put_dec_ helpers in any case
> make up for that.
Unrelated code changes affecting performance in
On Tue, Mar 10, 2015 at 01:37:40PM +0100, Peter Zijlstra wrote:
> On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote:
> > +static int __sched __mutex_lock_check_stamp(struct rt_mutex *lock,
> > + struct ww_acquire_ctx *ctx)
> > +{
> >
On 29/01/15 12:24, Nicholas Mc Guire wrote:
> The return type of wait_for_completion_timeout is unsigned long not
> int. This patch fixes up the declarations only.
>
> Signed-off-by: Nicholas Mc Guire
> ---
>
> v2: fixed subject line
> v3: fixed patch description as recommended by Dan Carpenter
On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote:
> +static int __sched __mutex_lock_check_stamp(struct rt_mutex *lock,
> + struct ww_acquire_ctx *ctx)
> +{
> +#ifdef CONFIG_WW_MUTEX_RTMUTEX
> + struct ww_mutex *ww =
On Tue, Mar 10, 2015 at 02:40:30PM +0300, Dan Carpenter wrote:
> On Tue, Mar 10, 2015 at 09:57:06AM +, Lorenzo Stoakes wrote:
> > This patch assigns the more appropriate void* type to the mmio750 variable
> > eliminating an unnecessary volatile qualifier in the process. Additionally
> > it
>
On Fri, Mar 6, 2015 at 8:47 AM, Josh Boyer wrote:
> Hi All,
>
> Commit 5c1de006e8e66 (cpupower Makefile change to help run the tool
> without 'make install') added an rpath to the cpupower binary. From
> what I can understand, this is to make it easier to run cpupower from
> the local build
On 20/02/15 16:34, Nicholas Mc Guire wrote:
> This is only an API consolidation and should make things more readable by
> replacing var * HZ / 1000 by msecs_to_jiffies(var).
>
> Signed-off-by: Nicholas Mc Guire
> ---
>
> v2: fixed missing closing parenthesis in pxafb_disable_controller.
>
Am Dienstag, 10. März 2015, 12:07:50 schrieb Mark Brown:
> On Tue, Mar 10, 2015 at 12:22:06AM +0100, Heiko Stuebner wrote:
> > When {devm_}regulator_get returns -EPROBE_DEFER the driver in question
> > will
> > try probing again at a later time. So don't spam the log with failure
> > messages as
Hi Austin,
Does pids limit make sense in the root cgroup?
>>>
>>> I would say it kind of does, although I would just expect it to track
>>> /proc/sys/kernel/pid_max (either as a read-only value, or as an
>>> alternative way to set it).
>>
>> Personally, that seems unintuitive.
On Fri, Feb 27, 2015 at 05:57:08PM +0100, Sebastian Andrzej Siewior wrote:
> diff --git a/kernel/locking/mutex.c b/kernel/locking/mutex.c
> index 16b2d3cc88b0..0a652ba46081 100644
> --- a/kernel/locking/mutex.c
> +++ b/kernel/locking/mutex.c
> @@ -106,6 +106,7 @@ void __sched mutex_lock(struct
On Fri, 06 Mar, at 04:39:12PM, Peter Jones wrote:
>
> So again: do we really need or want to do this?
One thing that we totally lose the ability to do is use the capsule
interface for things *other* than firmware updates, e.g.
https://lkml.org/lkml/2013/10/16/327
Also, requiring embedded or
This commit is consequence of making x86 MMCONFIG code available for all
architectures. Current code has old name fashion so for the sake of
making it more understandable and express where it comes from,
we are changing functions/variables/macros etc. name *mmconfig* -> *ecam*
Signed-off-by:
On 2015年03月07日 01:47, Lorenzo Pieralisi wrote:
On Wed, Feb 25, 2015 at 08:39:58AM +, Hanjun Guo wrote:
From: Al Stone
ACPI reduced hardware mode is disabled by default, but ARM64
can only run properly in ACPI hardware reduced mode, so select
ACPI_REDUCED_HARDWARE_ONLY if ACPI is enabled
601 - 700 of 1866 matches
Mail list logo
