On Wed 09-10-13 20:43:50, Richard Weinberger wrote:
> CC'ing mm folks.
> Please see below.
Added Fenguang to CC since he is the author of this code.
> Am 09.10.2013 19:26, schrieb Toralf Förster:
> > On 10/08/2013 10:07 PM, Geert Uytterhoeven wrote:
> >> On Sun, Oct 6, 2013 at 11:01 PM, Toralf
On Thu, Oct 03, 2013 at 05:12:15AM +0100, Suman Anna wrote:
> Hi Mark,
>
> > On Fri, Sep 27, 2013 at 05:06:38PM +0100, Kumar Gala wrote:
> >>
> >> On Sep 17, 2013, at 2:30 PM, Suman Anna wrote:
> >>
> >>> HwSpinlock IP is present only on OMAP4 and other newer SoCs,
> >>> which are all device-tree
On Wed, 2013-10-09 at 14:29 -0700, Paul E. McKenney wrote:
> From: "Paul E. McKenney"
>
> The sparse checking for rcu_assign_pointer() was recently upgraded
> to reject non-__kernel address spaces. This also rejects __rcu,
> which is almost always the right thing to do. However, the use in
>
On Thu, Oct 03, 2013 at 05:04:15AM +0100, Suman Anna wrote:
> Hi Mark,
>
> On 10/01/2013 03:36 AM, Mark Rutland wrote:
> > Hi Suman,
> >
> > Apologies for replying to a subthread, due to an earlier mistake on my
> > part I don't have the original to hand.
>
> No issues, thanks for your review.
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
notifier_chain_unregister() is legitimate: It is deleting an element
Dear Beloved Friend,
I am Mrs Nicole Marois Benoite, and i have been suffering from ovarian
cancer disease and the doctor says that i have just few days to leave. I am
from (Paris) France but based in Africa Burkina Faso since eleven years ago as
a business woman dealing with gold
From: Josh Triplett
rcu_assign_pointer needs to use ACCESS_ONCE to make the assignment to
the destination pointer volatile, to protect against compilers too
clever for their own good.
In addition, since rcu_assign_pointer force-casts the source pointer to
add the __rcu address space (overriding
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
bond_alb_handle_active_change() is legitimate: It is assigning a pointer
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
br_multicast_del_pg() and br_multicast_new_port_group() are legitimate:
On Thu, Oct 10, 2013 at 5:35 AM, Martin Nyhus wrote:
> After 5addcf0a (nouveau: add runtime PM support (v0.9)) I'm getting kernel
> panics immediately after resuming from suspend. Unfortunately it happens so
> early that I don't get any more info than the blinking keyboard lights...
>
> The
Hi,
The series is based on Tero's V8 of patches[1] - enables the use of
cpufreq-cpu0 generic driver for all OMAP and related derivatives.
I will stop copy pasting the series complete history and point at [2].
Main changes since V5:
- no more clock driver as part of this series[3] - instead
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ipip6_tunnel_unlink() is legitimate: It is assigning a pointer to an
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
sta_info_hash_del() are legitimate: They are assigning a pointer to an
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip_ra_control() is legitimate: It is assigning a pointer to an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
bond_change_active_slave(), bond_enslave(), and __bond_release_one()
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
__br_mdb_del() is legitimate: They are assigning a pointer to an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip6gre_tunnel_unlink() is legitimate: It is assigning a pointer to an
OMAP3+ supports both device tree and non-device tree boot.
Device tree bindings for OMAP3+ is supposed to be added via dts following:
Documentation/devicetree/bindings/power/opp.txt
Since we now have device tree entries for OMAP3+ cpu OPPs,
The current code wrongly adds duplicate OPPs. So, dont
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip6_tnl_unlink() is legitimate: It is assigning a pointer to an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
dn_insert_route() is legitimate: It is assigning a pointer to an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
cfg80211_combine_bsses() and cfg80211_bss_update() are legitimate:
They
Hello!
This series features updates to allow sparse to do a better job of
statically analyzing RCU usage:
1. Apply ACCESS_ONCE() to rcu_assign_pointer()'s target to prevent
comiler mischief. Also require that the source pointer be from
the kernel address space. Sometimes
On Wed, Oct 09, 2013 at 09:55:19AM -0400, Don Zickus wrote:
> On Tue, Oct 08, 2013 at 07:08:11PM -0300, Marcelo Tosatti wrote:
> > On Tue, Oct 08, 2013 at 09:37:05AM -0400, Don Zickus wrote:
> > > On Mon, Oct 07, 2013 at 10:05:17PM -0300, Marcelo Tosatti wrote:
> > > > Implement reset of kernel
Add Keyboard Matrix information to N900's DTS file.
This patch maps the keys exactly as the original
board code.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap3-n900.dts | 55
1 file changed, 55 insertions(+)
diff --git
Add device tree support for twl4030 keypad driver and update the
Documentation with twl4030 keypad device tree binding information.
This patch also adds a twl4030 keypad node to the twl4030.dtsi file,
so that board files can just add the keymap.
Tested on Nokia N900.
Signed-off-by: Sebastian
Hey Bjorn
On Wed, 2013-10-09 at 15:02 -0600, Bjorn Helgaas wrote:
> I handle many arch/x86/pci changes, so help those patches get to the
> PCI patchwork.
[]
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e61c2e8..d1ab647 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6338,6 +6338,7 @@ S:
For communicating with driver is used gpio bitbanging because TD028 does
not have a standard compliant SPI interface. It is a 3-wire thing with
direction reversal.
Communication with display is used only during panel enable/disable so it's
not performance issue.
Signed-off-by: Marek Belisko
On 10/09/2013 02:04 PM, Bjorn Helgaas wrote:
> On Wed, Oct 9, 2013 at 3:02 PM, Bjorn Helgaas wrote:
>> I handle many arch/x86/pci changes, so help those patches get to the
>> PCI patchwork.
>>
>> Signed-off-by: Bjorn Helgaas
>
> I'll merge this via the PCI tree unless anybody objects.
>
On Wed, Oct 09, 2013 at 01:37:05PM -0700, H. Peter Anvin wrote:
> A very common use case would be where a device contains an FPGA but is
> presented to the user as a product, often having its own device driver
> to drive the programmed device and/or additional logic. From *that*
> point of view
This is similar to what it is done on X86: biovecs are prevented from merging
otherwise every dma requests would be forced to bounce on the swiotlb buffer.
Signed-off-by: Stefano Stabellini
Changes in v7:
- remove the extra autotranslate check in biomerge.c.
---
arch/arm/include/asm/io.h |
From: Julien Grall
The commit "arm: introduce a global dma_ops pointer" introduce compilation issue
when CONFIG_SND_SOC_SAMSUNG is enabled.
sound/soc/samsung/dma.c:345:27: error: conflicting types for 'dma_ops'
/local/home/julien/works/arndale/linux/arch/arm/include/asm/dma-mapping.h:16:28:
Use xen_alloc_coherent_pages and xen_free_coherent_pages to allocate or
free coherent pages.
We need to be careful handling the pointer returned by
xen_alloc_coherent_pages, because on ARM the pointer is not equal to
phys_to_virt(*dma_handle). In fact virt_to_phys only works for kernel
direct
Call xen_dma_map_page, xen_dma_unmap_page, xen_dma_sync_single_for_cpu,
xen_dma_sync_single_for_device from swiotlb-xen to ensure cpu/device
coherency of the pages used for DMA, including the ones belonging to the
swiotlb buffer.
Signed-off-by: Stefano Stabellini
---
drivers/xen/swiotlb-xen.c |
When mapping/unmapping grant refs, call
set_phys_to_machine to update the P2M with the new mappings for
autotranslate guests.
Signed-off-by: Stefano Stabellini
---
drivers/xen/grant-table.c | 17 +++--
1 files changed, 15 insertions(+), 2 deletions(-)
diff --git
Signed-off-by: Stefano Stabellini
Changes in v7:
- use dev_warn instead of pr_warn.
---
drivers/xen/swiotlb-xen.c |1 +
lib/swiotlb.c |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/drivers/xen/swiotlb-xen.c b/drivers/xen/swiotlb-xen.c
index
Introduce xen_dma_map_page, xen_dma_unmap_page,
xen_dma_sync_single_for_cpu and xen_dma_sync_single_for_device.
They have empty implementations on x86 and ia64 but they call the
corresponding platform dma_ops function on arm and arm64.
Signed-off-by: Stefano Stabellini
---
On Wed, Oct 9, 2013 at 3:02 PM, Bjorn Helgaas wrote:
> I handle many arch/x86/pci changes, so help those patches get to the
> PCI patchwork.
>
> Signed-off-by: Bjorn Helgaas
I'll merge this via the PCI tree unless anybody objects.
> ---
> MAINTAINERS |1 +
> 1 file changed, 1 insertion(+)
I handle many arch/x86/pci changes, so help those patches get to the
PCI patchwork.
Signed-off-by: Bjorn Helgaas
---
MAINTAINERS |1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index e61c2e8..d1ab647 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -6338,6 +6338,7
On Wed, Oct 09, 2013 at 01:52:02PM -0700, Joe Perches wrote:
> There is no need to have OOM error messages after
> devm_kzalloc failures as the call already does a
> dump_stack() on OOM.
>
> This removal reduces overall object code size a small
> amount and overall code size by ~1000 lines.
>
>
Allow __set_phys_to_machine to be called for autotranslate guests.
It can be used to keep track of phys_to_machine changes, however we
don't do anything with the information at the moment.
Signed-off-by: Stefano Stabellini
---
arch/x86/xen/p2m.c |6 +++---
1 files changed, 3 insertions(+),
Signed-off-by: Stefano Stabellini
Acked-by: Catalin Marinas
CC: will.dea...@arm.com
---
arch/arm64/include/asm/dma-mapping.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm64/include/asm/dma-mapping.h
b/arch/arm64/include/asm/dma-mapping.h
index
Modify xen_create_contiguous_region to return the dma address of the
newly contiguous buffer.
Signed-off-by: Stefano Stabellini
Acked-by: Konrad Rzeszutek Wilk
Reviewed-by: David Vrabel
Changes in v4:
- use virt_to_machine instead of virt_to_bus.
---
arch/x86/xen/mmu.c|4 +++-
Implement xen_swiotlb_set_dma_mask, use it for set_dma_mask on arm.
Signed-off-by: Stefano Stabellini
---
arch/arm/xen/mm.c |1 +
drivers/xen/swiotlb-xen.c | 12
include/xen/swiotlb-xen.h |2 ++
3 files changed, 15 insertions(+), 0 deletions(-)
diff --git
Xen on arm and arm64 needs SWIOTLB_XEN: when running on Xen we need to
program the hardware with mfns rather than pfns for dma addresses.
Remove SWIOTLB_XEN dependency on X86 and PCI and make XEN select
SWIOTLB_XEN on arm and arm64.
At the moment always rely on swiotlb-xen, but when Xen starts
We can't simply override arm_dma_ops with xen_dma_ops because devices
are allowed to have their own dma_ops and they take precedence over
arm_dma_ops. When running on Xen as initial domain, we always want
xen_dma_ops to be the one in use.
Signed-off-by: Stefano Stabellini
Acked-by: Catalin
xen_swiotlb_alloc_coherent needs to allocate a coherent buffer for cpu
and devices. On native x86 is sufficient to call __get_free_pages in
order to get a coherent buffer, while on ARM (and potentially ARM64) we
need to call the native dma_ops->alloc implementation.
Introduce
Introduce physical to machine and machine to physical tracking
mechanisms based on rbtrees for arm/xen and arm64/xen.
We need it because any guests on ARM are an autotranslate guests,
therefore a physical address is potentially different from a machine
address. When programming a device to do
IOMMU_HELPER is needed because SWIOTLB calls iommu_is_span_boundary,
provided by lib/iommu_helper.c.
Signed-off-by: Stefano Stabellini
Reviewed-by: Konrad Rzeszutek Wilk
CC: will.dea...@arm.com
CC: li...@arm.linux.org.uk
Changes in v7:
- dma_mark_clean: empty implementation;
- in dma_capable
We can't simply override arm_dma_ops with xen_dma_ops because devices
are allowed to have their own dma_ops and they take precedence over
arm_dma_ops. When running on Xen as initial domain, we always want
xen_dma_ops to be the one in use.
Signed-off-by: Stefano Stabellini
Suggested-by: Catalin
Hi all,
this patch series enables xen-swiotlb on arm and arm64.
It has been heavily reworked compared to the previous versions in order
to achieve better performances and to address review comments.
We are not using dma_mark_clean to ensure coherency anymore. We call the
platform implementation
> Summary
> ---
>
> Although the extreme case shows a nice improvement, I'm skeptical if it
> is worth doing for real world applications.
You did the experiment, and credit to you for not going "I did the work,
now include it" but rather for publishing the results so we can learn
from them.
Hi Xiao,
On Wed, Oct 09, 2013 at 09:25:19AM +0800, Xiao Jin wrote:
> From: xiao jin
> Date: Wed, 9 Oct 2013 09:09:46 +0800
> Subject: [PATCH] xhci: correct the usage of USB_CTRL_SET_TIMEOUT
As I mentioned in another email, you need to use `git send-email` to
avoid putting these extra lines in
Hello,
How
are you? hope fine, I Want to
introduce my self to you before I go
further, My Name is Hassana. I will like to have a good
relationship with you, if you wouldn't mind, I will like to hear from
you soon I
have something very important I will like to tell you. Thanks and God
bless you,
On Fri, Aug 30, 2013 at 08:43:56AM -0700, H. Peter Anvin wrote:
> On 08/29/2013 04:51 PM, HATAYAMA Daisuke wrote:
> >
> > This is not a regression just as Eric explains.
> >
> > There is also my explanation in the description of the 2nd patch. I
> > should have described so here explicitly.
> >
Hi Xiao,
Thanks for taking the time to submit this patch. Comments below.
On Wed, Oct 09, 2013 at 09:42:36AM +0800, Xiao Jin wrote:
> From: xiao jin
> Date: Wed, 9 Oct 2013 09:38:45 +0800
> Subject: [PATCH] xhci-hub.c: handle command_trb that may be link TRB
I won't be able to apply your
On Wed, Oct 9, 2013 at 12:12 PM, Eric W. Biederman
wrote:
> ebied...@xmission.com (Eric W. Biederman) writes:
>
>> But I will go through and read the old fusermount code before I get too
>> much farther just so I understand what I am potentially breaking.
>
> Grr.
>
> So I have just read the
On Wed, 2013-10-09 at 21:46 +0200, Alexander Gordeev wrote:
> On Wed, Oct 09, 2013 at 12:12:51PM -0700, Nicholas A. Bellinger wrote:
> > Just a heads up that the scsi-mq alpha branch has been updated to Jen's
> > latest linux-block/new-queue containing hch's recent blk-mq
> > improvements, along
On Wed, 2013-10-09 at 14:44 -0500, Yoder Stuart-B08248 wrote:
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Wednesday, October 09, 2013 2:22 PM
> > To: Yoder Stuart-B08248
> > Cc: Wood Scott-B07421; Kim Phillips; Christoffer Dall; Alex Williamson;
> >
On Tue, Oct 08, 2013 at 02:40:45PM -0600, Jonathan Corbet wrote:
> OK, so this is a real nit, but...in the changelog:
>
> > static inline void rcu_sync_enter(struct rcu_sync_struct *xxx)
> > {
> > atomic_inc(>counter);
> > synchronize_sched();
> >
On Wed, 2013-10-09 at 12:16 -0700, gre...@linuxfoundation.org wrote:
> On Wed, Oct 09, 2013 at 07:02:25PM +, Yoder Stuart-B08248 wrote:
> > Have been thinking about this issue some more. As Scott mentioned,
> > 'wildcard' matching for a driver can be fairly done in the platform
> > bus
Devs,
Ever since we moved from 2.6.* to 3.*, I've noticed some very odd MM behavior
I'd like to run past you. It's pretty difficult to replicate, but I've figured
out a fairly straightforward method. But first, the issue:
Our systems with 72GB of RAM on a 3.2 kernel eventually converge on
On Wed, Oct 09, 2013 at 12:12:51PM -0700, Nicholas A. Bellinger wrote:
> Just a heads up that the scsi-mq alpha branch has been updated to Jen's
> latest linux-block/new-queue containing hch's recent blk-mq
> improvements, along with Alexander's patch for the is_flush_fua +
> queue_depth=1 bug.
> -Original Message-
> From: Wood Scott-B07421
> Sent: Wednesday, October 09, 2013 2:22 PM
> To: Yoder Stuart-B08248
> Cc: Wood Scott-B07421; Kim Phillips; Christoffer Dall; Alex Williamson;
> linux-kernel@vger.kernel.org; a.mota...@virtualopensystems.com;
> ag...@suse.de; Sethi
Em Wed, Oct 09, 2013 at 04:16:26PM -0300, Arnaldo Carvalho de Melo escreveu:
> So while merging what I have in my perf/core branch I got to Vitillo's, as
> peterz called it, "inlining" of addr2line, i.e. using libbfd to do that work,
> it will look if lbfd is in EXTLIBS and if so, use it,
After 5addcf0a (nouveau: add runtime PM support (v0.9)) I'm getting
kernel panics immediately after resuming from suspend. Unfortunately it
happens so early that I don't get any more info than the blinking
keyboard lights...
The nouveau tree still panics up to 2fb9d6c, which fails before I
Em Wed, Oct 09, 2013 at 06:17:43PM +0200, Stephane Eranian escreveu:
> This patch disables the mmap2 record format support
> for now. The support needs a bit more work to cover
> VM_CLONE cases.
>
> The patch leaves attr->mmap2 defined, but returns
> an error if it is set. That ensures no
[Patch ping #5]
On Thursday, October 03, 2013 04:16:07 pm Alexey Neyman wrote:
> On Thursday, October 03, 2013 12:14:38 pm Bjorn Helgaas wrote:
> > On Mon, Sep 23, 2013 at 12:15 AM, Alexey Neyman wrote:
> > > [Resending due to no response to the original message in a week]
> > >
> > > Hi all,
>
On Wed, Oct 09, 2013 at 07:02:25PM +, Yoder Stuart-B08248 wrote:
> Have been thinking about this issue some more. As Scott mentioned,
> 'wildcard' matching for a driver can be fairly done in the platform
> bus driver. We could add a new flag to the platform driver struct:
>
> diff --git
On 10/09/2013 10:50 AM, Mark Rutland wrote:
On Tue, Oct 08, 2013 at 05:33:23PM +0100, Gregory CLEMENT wrote:
On 08/10/2013 18:05, Sebastian Hesselbarth wrote:
On 10/08/2013 03:41 PM, Mark Rutland wrote:
On Tue, Oct 08, 2013 at 01:24:28PM +0100, Sebastian Hesselbarth wrote:
This add a
On Wed, 2013-10-09 at 14:02 -0500, Yoder Stuart-B08248 wrote:
> Have been thinking about this issue some more. As Scott mentioned,
> 'wildcard' matching for a driver can be fairly done in the platform
> bus driver. We could add a new flag to the platform driver struct:
>
> diff --git
So while merging what I have in my perf/core branch I got to Vitillo's, as
peterz called it, "inlining" of addr2line, i.e. using libbfd to do that work,
it will look if lbfd is in EXTLIBS and if so, use it, otherwise we continue
exec'in the addr2line tool.
Since this appears when doing the
On Tue, 8 Oct 2013, Tim Bird wrote:
> It also fixes a bug where kmemleak was only partially enabled in some
> configurations.
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
ebied...@xmission.com (Eric W. Biederman) writes:
> But I will go through and read the old fusermount code before I get too
> much farther just so I understand what I am potentially breaking.
Grr.
So I have just read the fusermount umount code and the hack that it uses
before there was
On Wed, Oct 09, 2013 at 09:02:31PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 09, 2013 at 08:16:13PM +0200, Jakub Jelinek wrote:
> > Confirmed as gcc bug, filed http://gcc.gnu.org/PR58670
> > Seems all of 4.[6-9] miscompile it. Will have a look tomorrow
> > unless somebody beats me to it. But
Hi folks,
Just a heads up that the scsi-mq alpha branch has been updated to Jen's
latest linux-block/new-queue containing hch's recent blk-mq
improvements, along with Alexander's patch for the is_flush_fua +
queue_depth=1 bug.
The branch @ v3.12-rc3 is available here:
Have been thinking about this issue some more. As Scott mentioned,
'wildcard' matching for a driver can be fairly done in the platform
bus driver. We could add a new flag to the platform driver struct:
diff --git a/drivers/base/platform.c b/drivers/base/platform.c
index 4f8bef3..4d6cf14 100644
On Wed, Oct 09, 2013 at 08:16:13PM +0200, Jakub Jelinek wrote:
> Confirmed as gcc bug, filed http://gcc.gnu.org/PR58670
> Seems all of 4.[6-9] miscompile it. Will have a look tomorrow
> unless somebody beats me to it. But historically, the case where
> asm goto labels jump to fallthru basic
Add rcu_sync_struct->exclusive boolean set by rcu_sync_init(),
it obviously controls the exclusiveness of rcu_sync_enter().
This is what percpu_down_write() actually wants.
We turn ->gp_wait into "struct completion gp_comp", it is used
as a resource counter in "exclusive" mode. Otherwise we only
Change rcu_sync_enter() to return "need_sync" to let the caller
know whether we did the FAST -> SLOW transition or not.
This is particularly useful in exclusive mode, for example
percpu_down_write() can avoid clear_fast_ctr() if rcu_sync_enter()
returns F.
Signed-off-by: Oleg Nesterov
---
Hello.
On top of "[PATCH 0/6] Optimize the cpu hotplug locking -v2".
> OK.. I'll give up trying to wreck this stuff ;-)
This hopefully means I can resend this ;) at least for review/record.
Changes:
- rediffed
- added "#define gp_wait" for consistency with rss_lock
-
On Wed, Oct 9, 2013 at 11:16 AM, Jakub Jelinek wrote:
>
> Confirmed as gcc bug, filed http://gcc.gnu.org/PR58670
> Seems all of 4.[6-9] miscompile it. Will have a look tomorrow
> unless somebody beats me to it. But historically, the case where
> asm goto labels jump to fallthru basic block had
Hi Rafael,
Just wondering if you would like anything changed in this patch in
order to get it into 3.13. I'd prefer not missing yet another merge
window...
Thanks,
Zoran
On 25 September 2013 15:31, Zoran Markovic wrote:
> From: Benoit Goby
>
> Rather than hard-lock the kernel, dump the
If CONFIG_COMMON_CLK_DEBUG is defined, clk_debug_create_one() is
called to populate a debugfs directory with a few entries that are
common for all clock types.
If an error happens after creating the first one debugfs_remove() is
called on the clock's directory. The problem with this is that no
>Hi azur,
>
>On Mon, Oct 07, 2013 at 01:01:49PM +0200, azurIt wrote:
>> >On Thu, Sep 26, 2013 at 06:54:59PM +0200, azurIt wrote:
>> >> On Wed, Sep 18, 2013 at 02:19:46PM -0400, Johannes Weiner wrote:
>> >> >Here is an update. Full replacement on top of 3.2 since we tried a
>> >> >dead end and it
CC'ing mm folks.
Please see below.
Am 09.10.2013 19:26, schrieb Toralf Förster:
> On 10/08/2013 10:07 PM, Geert Uytterhoeven wrote:
>> On Sun, Oct 6, 2013 at 11:01 PM, Toralf Förster
>> wrote:
Hmm, now pages_dirtied is zero, according to the backtrace, but the
BUG_ON()
asserts
Once the PCIe device assigned to a guest VM (via VFIO) gets detached from the
iommu domain
(when guest terminates), its PAMU table entry is disabled. So, this would
prevent the device
from being used once it's assigned back to the host.
This patch allows for creation of a default DMA window
Factor out PCI specific code in the PAMU driver.
Signed-off-by: Varun Sethi
---
drivers/iommu/fsl_pamu_domain.c | 81 +++
1 file changed, 40 insertions(+), 41 deletions(-)
diff --git a/drivers/iommu/fsl_pamu_domain.c b/drivers/iommu/fsl_pamu_domain.c
index
On Fri, Oct 04, 2013 at 11:05:48AM +0900, Inki Dae wrote:
> 2013/10/4 Olof Johansson :
> > "If PD_N is LOW, then the device is in Deep power-down completely,
> > even if supply rail is ON; for the device to be able to operate, the
> > PD_N pin must be HIGH."
> I still think the pin could be
And I am starting to think that this change should also fix the
while_each_thread() problems in this particular case.
In generak the code like
rcu_read_lock();
task = find_get_task(...);
rcu_read_unlock();
rcu_read_lock();
t = task;
do {
On Wed, Oct 09, 2013 at 04:46:56PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 09, 2013 at 04:33:59PM +0200, Peter Zijlstra wrote:
> > On Wed, Oct 09, 2013 at 04:07:34PM +0200, Peter Zijlstra wrote:
> > > Once I force a x86_64 build using the 'same' config it goes away and
> > > generates
On Wed, Oct 9, 2013 at 3:04 AM, HATAYAMA Daisuke
wrote:
> (2013/10/08 22:38), Dave Anderson wrote:
>>
>>
>>
>> - Original Message -
>>>
>>> (2013/10/07 22:21), Dave Anderson wrote:
>>>
- Original Message -
>
> (2013/10/03 22:47), Dave Anderson wrote:
>>>
>>>
>>
Currently, code include opp.h twice. Remove one inclusion
of opp.h
Signed-off-by: Manish Badarkhe
---
:100644 100644 574b16b... 93c29f4... M drivers/devfreq/exynos/exynos5_bus.c
drivers/devfreq/exynos/exynos5_bus.c |1 -
1 file changed, 1 deletion(-)
diff --git
From: "John W. Linville"
Date: Wed, 9 Oct 2013 11:28:41 -0400
> Please pull this batch of fixes intended for 3.12...
>
> Most of the bits are for iwlwifi -- Johannes says:
>
> "I have a fix for WoWLAN/D3, a PCIe device fix, we're removing a
> warning, there's a fix for RF-kill while scanning
On 10/9/13 11:40 AM, Stephane Eranian wrote:
On Wed, Oct 9, 2013 at 7:19 PM, David Ahern wrote:
On 10/9/13 10:39 AM, Stephane Eranian wrote:
Looks like the easiest thing to do for perf is to revert:
Revert "perf tools: Add default handler for mmap2 events"
git revert
On Wed, Oct 09, 2013 at 03:05:08PM +0300, Illia Smyrnov wrote:
> This patch fixes MCSPI FIFO buffer support when transmit-and-receive
> (full duplex) mode is used. In this mode FIFO can be used for RX or
> for TX or for both directions. If FIFO used for both directions the buffer
> is split into
On Mon, 30 Sep 2013, Konrad Rzeszutek Wilk wrote:
> On Fri, Sep 27, 2013 at 05:10:04PM +0100, Stefano Stabellini wrote:
> > This is similar to what it is done on X86: biovecs are prevented from
> > merging
> > otherwise every dma requests would be forced to bounce on the swiotlb
> > buffer.
> >
linux-next tree to the master branch of the
> > > repository below:
> > >
> > > git://gitorious.org/thierryreding/linux-next.git
> > >
> > > A next-20131009 tag is also provided for convenience.
> > >
> > > Gained a few conflicts, but nothin
On Wed, Oct 09, 2013 at 05:04:21PM +0300, Mika Westerberg wrote:
> 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).
Acked-by: Mark Brown
On Tue, Oct 08, 2013 at 07:31:02PM +0530, Laxman Dewangan wrote:
> As per the devicetree binding document of TPS65090, the "regulators"
> subnode should be under the parent node, not outside of parent node.
> Hence to get the regulator node, the correct call is
> of_get_child_by_name() rather than
On Wed, Oct 09, 2013 at 05:44:38PM +0100, Anthony Olech wrote:
Applied, thanks. Please format your patches as covered in
SubmittingPatches - use subjects appropriate to the subsystem and keep
noise like the above after the ---. I've fixed these and the strange
capitalisation when applying.
201 - 300 of 1358 matches
Mail list logo
