Add the command line argument -a (--allow) to usbip bind to specify
networks allowed to attach to the device and code to store the ACLs in
sysfs.
Signed-off-by: Kurt Kanzenbach
Signed-off-by: Dominik Paulus
Signed-off-by: Tobias Polzer
---
drivers/staging/usbip/userspace/doc/usbip.8 | 8
On Tue, 10 Sep 2013, David Howells wrote:
> James Morris wrote:
>
> > > > This missed the merge for 3.12. Do you want me to queue the changes
> > > > up,
> > > > or do you want to send a pull request again after -rc1 ?
> > >
> > > Can you queue them up now in your 'next' branch?
> >
> >
Not all new program versions necessarily introduce
non-backwards-compatible protocol changes. We thus move the definition
of the protocol version from configure.ac to usbip_network.h, where it
logically belongs to.
Signed-off-by: Dominik Paulus
Signed-off-by: Tobias Polzer
---
On Wed, 11 Sep 2013 11:21:49 -0400
Konrad Rzeszutek Wilk wrote:
> >
> > I'm trying to understand how this will fix it for you. Are you sure you
> > removed 'xen_nopvspin'?
>
> Yes.
> >
> > If you are calling static_key_slow_inc() before jump_label_init(), then
> > it should still fail. The
Jaegeuk,
My tests include forced kernel panics while fsstress is running, which
generates a lot of recovery activity. Sorry I wasn't more clear.
I understand your concern, which is why I first tried to keep the
fs_lock in the xattr_handler->set() path from VFS while removing it
from the call
On Wed, 11 Sep 2013 08:23:31 -0700
"Paul E. McKenney" wrote:
> C'mon, Steven! I did say "after treating injuries"! In the opinion
> of the surgeon, the only option was to ampute what was left of either
> the _cpu(), _task(), _thread(), or _you(). Heck, the damage was so
> severe that we
On Wed, Sep 11, 2013 at 06:32:38PM +0300, Mika Westerberg wrote:
> The I2C core now prepares runtime PM on behalf of the I2C client device, so
> only thing the driver needs to do is to call pm_runtime_put() at the end of
> its ->probe().
>
> This patch converts ASoC codec drivers to use this
On Mon, Sep 09, 2013 at 01:08:47PM +0200, Michal Hocko wrote:
> On Fri 06-09-13 22:59:16, Hugh Dickins wrote:
> > Hit divide-by-0 in vmpressure_work_fn(): checking vmpr->scanned before
> > taking the lock is not enough, we must check scanned afterwards too.
>
> As vmpressure_work_fn seems the be
On 09/11/2013 05:25 AM, John Tapsell wrote:
Hi,
I'm consistently and constantly hitting a deadlock.
console_callback in drivers/tty/vt/vt.c does: console_lock() and then calls:
do_blank_screen, which calls:
vc->vc_sw->con_blank(..) which can be a pointer to the function:
The I2C core now prepares runtime PM on behalf of the I2C client device, so
only thing the driver needs to do is to call pm_runtime_put() at the end of
its ->probe().
This patch converts I2C client drivers under drivers/misc to use this
model.
Signed-off-by: Mika Westerberg
---
The I2C core now prepares runtime PM on behalf of the I2C client device, so
only thing the driver needs to do is to call pm_runtime_put() at the end of
its ->probe().
This patch converts wm8994 driver to use this model.
Signed-off-by: Mika Westerberg
---
drivers/mfd/wm8994-core.c | 5 ++---
1
Em Wed, Sep 11, 2013 at 04:42:57PM +0200, Stephane Eranian escreveu:
> Arnaldo,
>
> Do you have all those changes in a git tree somewhere.
> I want to help test and debug this part too.
> Thanks.
Right now its all in my perf/urgent branch at:
On Wed, 11 Sep 2013 10:25:45 -0400
Konrad Rzeszutek Wilk wrote:
> > It seems to imply line 53 is the originating bug, so that would be:
> >
> > 47 if (type == JUMP_LABEL_ENABLE) {
> > 48 /*
> > 49 * We are enabling this jump label. If it is not a nop
Starting from commit 06c017fdd4dc48451a29ac37fc1db4a3f86b7f40
"timekeeping: Hold timekeepering locks in do_adjtimex and hardpps"
(3.10 kernels), the xtime write seqlock is held across calls to
__do_adjtimex(), which includes a call to notify_cmos_timer(), and hence
schedule_delayed_work().
This
This patch adds runtime PM support for the SPI bus analogous to what has
been done for the I2C bus. This means that the SPI core prepares runtime PM
for a client device just before a driver is about to be bound to it.
Devices that are not bound to any driver are not prepared for runtime PM.
In
On Wed, Sep 11, 2013 at 10:56:33AM -0400, Steven Rostedt wrote:
> On Wed, 11 Sep 2013 10:25:45 -0400
> Konrad Rzeszutek Wilk wrote:
>
> > > It seems to imply line 53 is the originating bug, so that would be:
> > >
> > > 47 if (type == JUMP_LABEL_ENABLE) {
> > > 48 /*
>
Hi,
This is second version of the patches. The previous version can be found
here:
http://www.spinics.net/lists/linux-i2c/msg13152.html
With the advent of ACPI 5.0 we are starting to see I2C client devices
described in ACPI namespace that support power management by the means of
The IvyBridge event CYCLE_ACTIVITY:CYCLES_LDM_PENDING can only
be measured on counters 0-3 when HT is off. When HT is on, you
only have counters 0-3.
If you program it on the eight counters for 1s on a 3GHz
IVB laptop running a noploop, you see:
2 747 527
On Wed, Sep 11, 2013 at 6:13 AM, Peter Zijlstra wrote:
> On Tue, Sep 10, 2013 at 02:43:06PM -0700, Linus Torvalds wrote:
>> That said, looking at your patch, I get the *very* strong feeling that
>> we could make a macro that does all the repetitions for us, and then
>> have a
>>
>>
The I2C core now prepares runtime PM on behalf of the I2C client device, so
only thing the driver needs to do is to call pm_runtime_put() at the end of
its ->probe().
This patch converts ASoC codec drivers to use this model.
Signed-off-by: Mika Westerberg
---
sound/soc/codecs/wm2200.c | 12
Dear User
Your e-mail has exceeded 2 GB, which is created by our
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 information below to update your account
(1)
On Mon, 9 Sep 2013 13:07:08 -0700 (PDT)
David Rientjes wrote:
> > /*
> > * If this task is not being ptraced on exit, then wait for it
> > * to finish before killing some other task unnecessarily.
> > */
> > - if
The I2C core now prepares runtime PM on behalf of the I2C client device, so
only thing the driver needs to do is to call pm_runtime_put() at the end of
its ->probe().
This patch converts s5p-tv driver to use this model.
Signed-off-by: Mika Westerberg
---
On Wed, 2013-09-11 at 14:21 +, Christoph Lameter wrote:
> On Wed, 11 Sep 2013, Mike Galbraith wrote:
>
> > Mind saying why? To me, creating properties of exclusive sets of CPUs
> > that the interface which manages sets and their properties is not fully
> > aware of is a dainbramaged thing
On Wed, Sep 11, 2013 at 08:31:54AM +0200, Marek Szyprowski wrote:
> Hello,
>
> On 9/10/2013 9:45 PM, Rob Herring wrote:
> >On 09/10/2013 04:13 AM, Marek Szyprowski wrote:
> >> It is not needed to include asm/dma-contiguous.h header to compile
> >> reserved memory initialization code, so remove it
From: Aaron Lu
This patch adds runtime PM support for the I2C bus in a similar way that
has been done for PCI bus already. This means that the I2C bus core
prepares runtime PM for a client device just before a driver is about to be
bound to it. Devices that are not bound to any driver are not
If the SPI device is enumerated from ACPI namespace (it has an ACPI handle)
it might have ACPI methods that needs to be called in order to transition
the device to different power states (such as _PSx).
We follow what has been done for platform and I2C buses here and attach the
SPI device to the
Fix an issue affecting lttng-modules with Linux kernels starting with
3.10.
This patch depends on Linux kernel patch:
"timekeeping: introduce timekeeping_is_busy()"
Starting from Linux kernel commit
06c017fdd4dc48451a29ac37fc1db4a3f86b7f40 "timekeeping: Hold
timekeepering locks in do_adjtimex
On Thu, Sep 05, 2013 at 01:12:52PM +0200, Ingo Molnar wrote:
>
> Could you try the latest -tip tree at:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>
> In particular this fix:
>
>5a8e01f8fa51 sched/cputime: Do not scale when utime == 0
>
> Could perhaps fix the
On 09/11/2013 09:26 AM, Steven Rostedt wrote:
On Wed, 11 Sep 2013 07:28:09 -0300
"Luis Claudio R. Goncalves" wrote:
Hello,
I saw two different occurrences of "BUG: sleeping function called from
invalid context" happening on 3.10.10-rt7. The first one happened on
drm_vblank_get() ->
On Wed, Sep 11, 2013 at 10:28:26AM -0400, Waiman Long wrote:
> The sequence lock (seqlock) was originally designed for the cases
> where the readers do not need to block the writers by making the
> readers retry the read operation when the data change.
>
> Since then, the use cases have been
On Wed, 11 Sep 2013 11:16:43 -0400
Peter Hurley wrote:
> > The funny part is, there's a comment there that shows that this was
> > done even for "PREEMPT_RT". Unfortunately, the call to
> > "get_scanout_position()" can call functions that use the rt-mutex
> > "sleeping spin locks" and it breaks
From: Josh Boyer
In cachefiles_check_auxdata(), we allocate auxbuf but fail to free it if we get
determine there's an error or that the data is stale.
Further, assigning the output of vfs_getxattr() to auxbuf->len gives problems
with checking for errors as auxbuf->len is a u16. We don't
From: Lv Zheng
If the I2C client device is enumerated from ACPI namespace it might have
ACPI methods that needs to be called in order to transition the device to
different power states (such as _PSx).
Implement this for I2C client devices by checking if the device has an ACPI
handle and if
On Wed, Sep 11, 2013 at 08:29:55AM +0100, Lee Jones wrote:
> Only if you print out every regulator, clock, GPIO pin and things of
> this nature. Key hardware blocks such as; SD, Flash, USB, Eth, HDMI,
> Audio, UART, GPIO and I2C controllers and Sensors I think deserve a
> one line "I'm here and
The I2C core now prepares runtime PM on behalf of the I2C client device, so
only thing the driver needs to do is to call pm_runtime_put() at the end of
->probe().
This patch converts bma150 and mpu3050 input drivers to use this model.
While we are there remove call to
Am 22.08.2013 00:02, schrieb Linus Walleij:
> On Tue, Aug 20, 2013 at 12:04 AM, Laurent Pinchart
> wrote:
>> On Wednesday 31 July 2013 01:44:53 Linus Walleij wrote:
>
>>> I don't see how sharing works here, or how another user, i.e. another one
>>> than the user wanting to recieve the IRQ, can
On 09/11/2013 06:13 AM, Peter Zijlstra wrote:
> On Tue, Sep 10, 2013 at 02:43:06PM -0700, Linus Torvalds wrote:
>> That said, looking at your patch, I get the *very* strong feeling that
>> we could make a macro that does all the repetitions for us, and then
>> have a
>>
>>
Em Wed, Sep 11, 2013 at 11:53:41AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Sep 11, 2013 at 04:42:57PM +0200, Stephane Eranian escreveu:
> > Do you have all those changes in a git tree somewhere.
> > I want to help test and debug this part too.
> > Thanks.
> Right now its all in my
I got this hard lockup running my perf_fuzzer on 3.11 on a core2.
I guess I should try to reproduce it on linus-git but was hoping
I could wait until -rc1 before trying that.
I'm not really sure where to report lockups like this because it's sort
of unclear what exactly the problem is. perf?
On Wed, Sep 11, 2013 at 10:26:07AM -0400, Steven Rostedt wrote:
> On Wed, 11 Sep 2013 07:13:02 -0700
> "Paul E. McKenney" wrote:
>
> > On Mon, Sep 09, 2013 at 03:34:26PM -0700, Paul E. McKenney wrote:
> > > On Mon, Sep 09, 2013 at 05:59:17PM -0400, Steven Rostedt wrote:
> > > > On Mon, 9 Sep
On Thu, Sep 05, 2013 at 10:43:53AM -0400, Dave Jones wrote:
> Channel will never be < 0, as it's unsigned.
Yes, Aravind, please take care of this.
Thanks.
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Arnaldo,
Do you have all those changes in a git tree somewhere.
I want to help test and debug this part too.
Thanks.
On Tue, Sep 10, 2013 at 10:16 PM, Arnaldo Carvalho de Melo
wrote:
> Em Tue, Sep 10, 2013 at 04:58:47PM -0300, Arnaldo Carvalho de Melo escreveu:
>> So we must have the handling
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> This is trivial change, just use well-defined macro.
Acked-by: Christoph Lameter
--
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
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> With build-time size checking, we can overload the RCU head over the LRU
> of struct page to free pages of a slab in rcu context. This really help to
> implement to overload the struct slab over the struct page and this
> eventually reduce memory usage
On Wed, 11 Sep 2013 09:47:17 -0400
Konrad Rzeszutek Wilk wrote:
The merge conflict resolution looks good. Now to look at this bug.
> On Tue, Sep 10, 2013 at 07:48:44PM -0700, H. Peter Anvin wrote:
> > Hi Linus,
> >
> > One more x86 tree for this merge window. This tree improves the
> >
This one on top of stable 3.6.11 git.
Thank you, Steven.
---
[ Upstream commit 27c505ca84e164ec66ad55dcf3f5befaac83f10a ]
Commit a01c34f72e7cd2624570818f579b5ab464f93de2 (radeon kms: do not
flush uninitialized hotplug work) moved work initialisation phase to
the last step of
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> We don't need to free slab management object in rcu context,
> because, from now on, we don't manage this slab anymore.
> So put forward freeing.
Acked-by: Christoph Lameter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> Now there is no user colouroff, so remove it.
Acked-by: Christoph Lameter
--
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
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> We can get cachep using page in struct slab_rcu, so remove it.
Acked-by: Christoph Lameter
--
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
On Mon, Sep 09, 2013 at 10:32:59PM +0100, Andrew Pinski wrote:
> This patch adds full support of the ABI to the ARM64 target.
This description is too short. Please describe what the ABI is, what are
the commonalities with AArch64 and AArch32, what other non-obvious
things had to be done (like
On Wed, Sep 11, 2013 at 09:45:34AM -0400, Vivek Goyal wrote:
> I am looking forward to that new version. CCing Dave Young. He is also
> looking into it and going through history of patches.
Ok, I'll CC you guys on the submission - I'd need any and all feedback I
can get on that topic.
Thanks.
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> It is more understandable that kmem_getpages() return struct page.
> And, with this, we can reduce one translation from virt addr to page and
> makes better code than before. Below is a change of this patch.
Acked-by: Christoph Lameter
--
To unsubscribe
On Wed, 11 Sep 2013, Mike Galbraith wrote:
> Mind saying why? To me, creating properties of exclusive sets of CPUs
> that the interface which manages sets and their properties is not fully
> aware of is a dainbramaged thing to do.
cpusets is being replaced by cgropus. And the mechanism adds
On Thu, 22 Aug 2013, Joonsoo Kim wrote:
> And, therefore we should check pfmemalloc in page flag of first page,
> but current implementation don't do that. virt_to_head_page(obj) just
> return 'struct page' of that object, not one of first page, since the SLAB
> don't use __GFP_COMP when
On Tue, 10 Sep 2013, Lucas De Marchi wrote:
> >>> > The ordering is more of a recommendation than a necessity. Systems
> >>> > should work oksy if the modules are loaded in the wrong order.
> >>> >
> >>> > The only issue if the drivers are loaded in the wrong order is that
> >>> > full- and
The sequence lock (seqlock) was originally designed for the cases
where the readers do not need to block the writers by making the
readers retry the read operation when the data change.
Since then, the use cases have been expanded to include situations
where a thread does not need to change the
This patch modifies read_seqbegin_or_lock() and need_seqretry() to
use newly introduced read_seqlock() and read_sequnlock() primitives
so that they won't change the sequence number even if they fall back
to take the lock. This is OK as no change to the protected data
structure is being made. It
On 09/08/2013 10:18 PM, Lan Tianyu wrote:
On 2013年09月07日 08:15, Rafael J. Wysocki wrote:
On Friday, September 06, 2013 10:24:44 AM Lan Tianyu wrote:
According ACPI 5.0 spec Section 19.1.8
"For bridges, translate addresses across the bridge, this is the
offset that must be added to the address
> It seems to imply line 53 is the originating bug, so that would be:
>
> 47 if (type == JUMP_LABEL_ENABLE) {
> 48 /*
> 49 * We are enabling this jump label. If it is not a nop
> 50 * then something must have gone wrong.
> 51
On Wed, 11 Sep 2013 07:13:02 -0700
"Paul E. McKenney" wrote:
> On Mon, Sep 09, 2013 at 03:34:26PM -0700, Paul E. McKenney wrote:
> > On Mon, Sep 09, 2013 at 05:59:17PM -0400, Steven Rostedt wrote:
> > > On Mon, 9 Sep 2013 17:40:26 -0400
> > > Mathieu Desnoyers wrote:
> > >
> > > > Agreed. So
On 09/11/2013 05:33 AM, David Vrabel wrote:
On 10/09/13 16:31, Boris Ostrovsky wrote:
This is the Linux side of Xen PMU support for PV guests, including dom0. Only
kernel changes are here, toolstack patch will be provided separately.
Here is description from the hypervisor patch submission
On Wed, 11 Sep 2013, Joonsoo Kim wrote:
> Anyway, could you review my previous patchset, that is, 'overload struct slab
> over struct page to reduce memory usage'? I'm not sure whether your answer is
> ack or not.
I scanned over it before but I was not able to see if it was correct on
first
Em Wed, Sep 11, 2013 at 07:55:03AM +0200, Ingo Molnar escreveu:
> 16645 perf_event_open(0x1eb7f00, 0x, 0, 0x, 0) = -1 EINVAL
> (Invalid argument)
>
> Caused by:
>
> 575a9aab0f85 perf tools: Add attr->mmap2 support
>
> We must not force mmap2 support to be present on the
On Mon, Sep 09, 2013 at 03:34:26PM -0700, Paul E. McKenney wrote:
> On Mon, Sep 09, 2013 at 05:59:17PM -0400, Steven Rostedt wrote:
> > On Mon, 9 Sep 2013 17:40:26 -0400
> > Mathieu Desnoyers wrote:
> >
> > > Agreed. So how about rcu_is_online() ?
> >
> > Nope, what about
From: Wei Yongjun
The dereference to 'pdata' should be moved below the NULL test.
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/msm/msm_gpu.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/msm_gpu.c b/drivers/gpu/drm/msm/msm_gpu.c
index
On Tue, 10 Sep 2013, Joe Perches wrote:
> Use the likely mechanism already around valid
> pointer tests to better choose when to memset
> to 0 allocations with __GFP_ZERO
Ok but that is not that important since the first ptr check is only for
debuggin.
Acked-by: Christoph Lameter
--
To
On Wed, Sep 11, 2013 at 07:54:28PM +0800, Ming Lei wrote:
> On Sat, Sep 7, 2013 at 3:36 AM, Neil Horman wrote:
> > The direct firmware loading interface is a bit quiet about failures.
> > Failures
>
> Because there are several pre-defined search paths, and generally the
> requested firmware
On 09/11/2013 05:29 PM, Viresh Kumar wrote:
> On 11 September 2013 16:44, Srivatsa S. Bhat
> wrote:
>> Hmm? The problem is not about merely updating the policy->cpu field; the
>> main issue is that the existing code was not letting the cpufreq-stats
>> code know that we updated the policy->cpu
On Thu, Sep 05, 2013 at 12:44:34PM +0900, Alexandre Courbot wrote:
> On Thu, Sep 5, 2013 at 4:56 AM, Stephen Warren wrote:
> > On 09/04/2013 05:29 AM, Alexandre Courbot wrote:
> >> Add gpiod_get() and gpiod_put() functions that provide safer handling of
> >> GPIOs.
> >>
> >> These functions put
On Wed, Sep 11, 2013 at 09:47:17AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 10, 2013 at 07:48:44PM -0700, H. Peter Anvin wrote:
> > Hi Linus,
> >
> > One more x86 tree for this merge window. This tree improves the
> > handling of jump labels, so that most of the time we don't have to do
On Wed, 11 Sep 2013 09:47:17 -0400
Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 10, 2013 at 07:48:44PM -0700, H. Peter Anvin wrote:
> Which means that all of the arch_spin_unlock (which are inlined) and such
> will now be patched over.
>
> But perhaps they are not suppose to be enabled in the
Usual story. I'm trying to narrow down on a tracing bug I'd reported that we
had no
understanding of (https://lkml.org/lkml/2013/8/27/646) and had hacked up
trinity to just only use perf fds, and left it running overnight.
Woke up to _another_ bug.
WARNING: CPU: 1 PID: 23361 at
On Wed, Sep 11, 2013 at 01:44:19PM +0200, Borislav Petkov wrote:
> On Tue, Sep 10, 2013 at 03:52:24PM -0700, H. Peter Anvin wrote:
> > Borislav Petkov has been working on a fixed mapping of UEFI memory,...
>
> ... who will back from vacation on Monday and will be sending out a new
> RFC version.
On Tue, Sep 10, 2013 at 06:57:55PM -0400, Josh Boyer wrote:
[..]
> > +static ssize_t secureboot_enabled_show(struct kobject *kobj,
> > + struct kobj_attribute *attr, char
> > *buf)
> > +{
> > + /* TODO: Change it once secureboot patches are in */
> > +
On Tue, Sep 10, 2013 at 03:40:09PM -0700, Greg KH wrote:
> On Tue, Sep 10, 2013 at 05:44:29PM -0400, Vivek Goyal wrote:
> > User space kexec-tools need to know whether to verify signature of kernel
> > image being loaded. This patch exports two knobs to user space. One is
> > for knowing if
On Tue, Sep 10, 2013 at 07:48:44PM -0700, H. Peter Anvin wrote:
> Hi Linus,
>
> One more x86 tree for this merge window. This tree improves the
> handling of jump labels, so that most of the time we don't have to do
> a massive initial patching run. Furthermore, we will error out of the
> jump
> "H" == H Peter Anvin writes:
H> On 09/10/2013 08:00 PM, Linus Torvalds wrote:
>> On Tue, Sep 10, 2013 at 7:46 PM, John Stoffel wrote:
>>>
Linus> The timing absolutely sucks, but it looks like the SSD in my
Linus> main workstation just died on me.
>>>
>>> What model, if you care to
When building a 64-bit kernel we get following compiler warning:
drivers/mfd/wm8994-core.c: In function ‘wm8994_i2c_probe’:
drivers/mfd/wm8994-core.c:758:19: warning: cast from pointer to integer of
different size [-Wpointer-to-int-cast]
Fix this by casting the of_id->data to kernel_ulong_t as
On Wed, 2013-09-11 at 11:32 +0900, Yasuaki Ishimatsu wrote:
> (2013/09/11 7:47), Toshi Kani wrote:
> > cpu_up() has #ifdef CONFIG_MEMORY_HOTPLUG code blocks, which
> > call mem_online_node() to put its node online if offlined and
> > then call build_all_zonelists() to initialize the zone list.
> >
On 09/11/2013 03:32 AM, Thomas Petazzoni wrote:
Commit ebd97be635 ('PCI: remove ARCH_SUPPORTS_MSI kconfig option')
removes the ARCH_SUPPORTS_MSI Kconfig option that allowed
architectures to indicate whether they support PCI MSI or not. Now,
PCI MSI support can be compiled in on any architecture
On Wed, 2013-09-11 at 13:06 +0200, Peter Zijlstra wrote:
> On Wed, Sep 11, 2013 at 10:25:30AM +0200, Peter Zijlstra wrote:
> > On Tue, Sep 10, 2013 at 06:59:57PM -0700, Andy Lutomirski wrote:
>
> > > It looks like the intel_idle code can get confused if TIF_NEED_RESCHED
> > > is set but the
On Wed, 11 Sep 2013 07:28:09 -0300
"Luis Claudio R. Goncalves" wrote:
> Hello,
>
> I saw two different occurrences of "BUG: sleeping function called from
> invalid context" happening on 3.10.10-rt7. The first one happened on
> drm_vblank_get() -> i915_get_vblank_timestamp() and was flooding
On Wed, Sep 11, 2013 at 03:13:23PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 10, 2013 at 02:43:06PM -0700, Linus Torvalds wrote:
> > That said, looking at your patch, I get the *very* strong feeling that
> > we could make a macro that does all the repetitions for us, and then
> > have a
> >
> >
Hi Gu,
2013/9/11 Gu Zheng :
> Hi Jaegeuk, Chao,
>
> On 09/10/2013 08:52 AM, Jaegeuk Kim wrote:
>
>> Hi,
>>
>> At first, thank you for the report and please follow the email writing
>> rules. :)
>>
>> Anyway, I agree to the below issue.
>> One thing that I can think of is that we don't need to use
Hi Russ,
The usage of fs_locks is for the recovery, so it doesn't matter
with stress-testing.
Actually what I've concerned is that we should not grab two or
more fs_locks in the same call path.
Thanks,
2013/9/11 Russ Knize :
> Hi Jaegeuk/Gu,
>
> I've removed the lock and have been stress-testing
On Wednesday, September 11, 2013 10:15:53 AM Guennadi Liakhovetski wrote:
> On Wed, 11 Sep 2013, Viresh Kumar wrote:
>
> > On 10 September 2013 22:37, Guennadi Liakhovetski
> > wrote:
> > > On Tue, 10 Sep 2013, Viresh Kumar wrote:
> > >> Quite straight forward actually..
> > >
> > > Apparently,
On (09/11/13 08:37), Steven Rostedt wrote:
> >
> > I'll prepare a proper patch for stable.
> >
>
> I took a crack at it. How's this look?
as far as I understand this is 27c505ca84e164ec66ad55dcf3f5befaac83f10a
on top of a01c34f72e7cd2624570818f579b5ab464f93de2 [both backported] with
moved
Hi,
2013/9/11 Chao Yu
>
> Hi Kim,
>
> I did some tests as you mention of using random instead of spin_lock.
> The test model is as following:
> eight threads race to grab one of eight locks for one thousand times,
> and I used four methods to generate lock num:
>
> 1.atomic_add_return(1,
Signed-off-by: Charles Keepax
---
A bit of confusion with merging this last time because I
messed up the CCs, is safe to merge this patch on its own
now.
drivers/gpio/gpio-arizona.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/gpio/gpio-arizona.c
On Tue, Sep 10, 2013 at 02:43:06PM -0700, Linus Torvalds wrote:
> That said, looking at your patch, I get the *very* strong feeling that
> we could make a macro that does all the repetitions for us, and then
> have a
>
> GENERATE_RMW(atomic_sub_and_test, LOCK_PREFIX "subl", "e", "")
The below
On Wednesday, September 11, 2013 02:08:44 PM Viresh Kumar wrote:
> On 11 September 2013 01:16, Rafael J. Wysocki wrote:
> > On Tuesday, September 10, 2013 08:44:18 PM Viresh Kumar wrote:
>
> >> Now Second question, is this fine to have multiple PRECHANGE notfications
> >> before any POSTCHANGE
From: Lan Tianyu
cpufreq_set_policy() has been changed to origin __cpufreq_set_policy()
and policy->lock has been converted to rewrite lock by commit 5a01f2.
So remove the comment.
Acked-by: Viresh Kumar
Signed-off-by: Lan Tianyu
---
This patch is based on patch "cpufreq: rename
On Wed, Sep 11, 2013 at 06:07:28PM +0800, Tang Chen wrote:
> This patch-set is based on tj's suggestion, and not fully tested.
> Just for review and discussion. And according to tj's suggestion,
> implemented a new function memblock_alloc_bottom_up() to allocate
> memory from bottom upwards,
The following files moved files out of Documentation/vm/
c6dd897f ("mm: move page-types.c from Documentation to tools/vm")
f0f57b2b ("move hugepage test examples to tools/testing/selftests/vm)
Remove these files from vm/00-INDEX.
The following commits added new files do Documentation/vm/
On 09/11/2013 06:08 AM, Viresh Kumar wrote:
On 11 September 2013 08:58, Lan Tianyu wrote:
From 668e1b6fd94b5c0e56a651b4c60cbbc7a6868b46 Mon Sep 17 00:00:00 2001
From: Lan Tianyu
Date: Wed, 11 Sep 2013 11:31:15 +0800
Subject: [PATCH] Cpufreq/governor: Remove fossil comment
The Turn-on time of the regulator depends on the regulator device's
electrical characteristics. Sometimes regulator turn-on time also
depends on the capacitive load on the given platform and it can be
more than the datasheet value.
The driver provides the enable-time as per datasheet.
Add
On Wed, 11 Sep 2013 12:06:49 +0300
Sergey Senozhatsky wrote:
> On (09/11/13 00:29), Steven Rostedt wrote:
> > 3.6.11.9-rc1 stable review patch.
> > If anyone has any objections, please let me know.
> >
>
> Hello,
> Steven, this patch makes r100_irq_process() unhappy and there
> is additional
The ARMv8-A Architecture Reference Manual is now publicly available:
http://infocenter.arm.com/help/topic/com.arm.doc.ddi0487a/index.html
Please note that free registration is required to be able to download
(as per the previous ARM ARM and other documentation on ARM infocenter).
It contains
>On Tue, Sep 10, 2013 at 11:32:47PM +0200, azurIt wrote:
>> >On Tue, Sep 10, 2013 at 11:08:53PM +0200, azurIt wrote:
>> >> >On Tue, Sep 10, 2013 at 09:32:53PM +0200, azurIt wrote:
>> >> >> Here is full kernel log between 6:00 and 7:59:
>> >> >> http://watchdog.sk/lkml/kern6.log
>> >> >
>> >> >Wow,
401 - 500 of 1346 matches
Mail list logo
