Add device tree binding support for the QCOM BAM DMA driver.
Signed-off-by: Andy Gross agr...@codeaurora.org
---
.../devicetree/bindings/dma/qcom_bam_dma.txt | 48
1 file changed, 48 insertions(+)
create mode 100644
This patch set introduces the dmaengine driver for the Qualcomm Bus Access
Manager (BAM) DMA controller present on MSM 8x74 devices. A number of the
on-chip devices have their own BAM DMA controller and use it to move data
between system memory and peripherals or between two peripherals.
The
On Mon, Feb 3, 2014 at 2:05 PM, Arnd Bergmann a...@arndb.de wrote:
On Monday 03 February 2014 19:18:38 Liviu Dudau wrote:
On Mon, Feb 03, 2014 at 06:58:56PM +, Arnd Bergmann wrote:
On Monday 03 February 2014 18:43:48 Liviu Dudau wrote:
[snip]
Agree. This is the RFC version. I didn't
Hi Sarah,
On Mon, Jan 20, 2014 at 8:35 PM, Sarah Sharp
sarah.a.sh...@linux.intel.com wrote:
Hi Markus,
I'm the xHCI driver maintainer, and it helps to Cc me on USB 3.0 bug
reports.
On Sat, Dec 28, 2013 at 07:24:20AM +0100, Markus Rechberger wrote:
just received following log snippset:
On Mon, 27 Jan 2014 09:01:19 -0500 Dan Streetman ddstr...@ieee.org wrote:
Currently, zswap is writeback cache; stored pages are not sent
to swap disk, and when zswap wants to evict old pages it must
first write them back to swap cache/disk manually. This avoids
swap out disk I/O up front,
On 02/03/2014 02:39 PM, David Rientjes wrote:
Commit c65c1877bd68 (slub: use lockdep_assert_held) incorrectly required
that add_full() and remove_full() hold n-list_lock. The lock is only
taken when kmem_cache_debug(s), since that's the only time it actually
does anything.
Require that the
From: Kenneth Heitke khei...@codeaurora.org
Qualcomm's PMIC Arbiter SPMI controller functions as a bus master and
is used to communication with one or more PMIC (slave) devices on the
SPMI bus. The PMIC Arbiter is actually a hardware wrapper around the
SPMI controller that provides concurrent
The System Power Management Interface (SPMI) is a high-speed,
low-latency, bi-directional, two-wire serial bus suitable for real-time
control of voltage and frequency scaled multi-core application
processors and its power management of auxiliary components. SPMI
obsoletes a number of legacy,
SPMI states that a slave may contain two register spaces, the Base
register space is a 5-bit byte-addressable space accessed via the
Register Read/Write and Register Zero Write command sequences, and the
Extended register space: a 16-bit byte-addressable space accessed via
the Extended Read/Write
The Qualcomm PMIC Arbiter, in addition to being a basic SPMI controller,
also implements interrupt handling for slave devices. Note, this is
outside the scope of SPMI, as SPMI leaves interrupt handling completely
unspecified.
Extend the driver to provide a irq_chip implementation and chained irq
Signed-off-by: Josh Cartwright jo...@codeaurora.org
---
.../bindings/spmi/qcom,spmi-pmic-arb.txt | 60 ++
1 file changed, 60 insertions(+)
create mode 100644
Documentation/devicetree/bindings/spmi/qcom,spmi-pmic-arb.txt
diff --git
Signed-off-by: Josh Cartwright jo...@codeaurora.org
---
Documentation/devicetree/bindings/spmi/spmi.txt | 41 +
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spmi/spmi.txt
diff --git
From: Kenneth Heitke khei...@codeaurora.org
System Power Management Interface (SPMI) is a specification
developed by the MIPI (Mobile Industry Process Interface) Alliance
optimized for the real time control of Power Management ICs (PMIC).
SPMI is a two-wire serial interface that supports up to 4
2014-02-03, OGAWA Hirofumi hirof...@mail.parknet.co.jp:
Namjae Jeon linkinj...@gmail.com writes:
From: Namjae Jeon namjae.j...@samsung.com
Make the fibmap call the return the proper physical block number for any
offset request in the fallocated range.
Signed-off-by: Namjae Jeon
Hi Sebastian,
On Thu, Jan 30, 2014 at 11:31:32AM +0100, Sebastian Hesselbarth wrote:
On 01/30/14 11:24, Gregory CLEMENT wrote:
On 25/01/2014 19:19, Sebastian Hesselbarth wrote:
This patch set fixes clk init order that went upside-down with
v3.14. I haven't really investigated what caused
From: Rob Herring r...@kernel.org
Commit 00b2c76a6a include/linux/of.h: make for_each_child_of_node()
reference its args when CONFIG_OF=n fixed warnings for unused
variables, but introduced variable used uninitialized warnings.
Simply initializing the variables would result in set but not used
On Sun, Feb 02, 2014 at 02:45:58PM +0900, Namjae Jeon wrote:
From: Namjae Jeon namjae.j...@samsung.com
This testcase(001) tries to test various corner cases
for fcollapse range functionality over different type of extents.
Signed-off-by: Namjae Jeon namjae.j...@samsung.com
Signed-off-by:
On Mon, 27 Jan 2014 18:03:04 +0800 Weijie Yang weijie.y...@samsung.com wrote:
swapoff clear swap_info's SWP_USED flag prematurely and free its resources
after that. A concurrent swapon will reuse this swap_info while its previous
resources are not cleared completely.
These late freed
On Monday, February 03, 2014 12:44:08 PM Mika Westerberg wrote:
On Sun, Feb 02, 2014 at 01:19:33AM +0100, Rafael J. Wysocki wrote:
On Monday, January 27, 2014 01:37:17 AM Rafael J. Wysocki wrote:
Hi All,
ACPIPHP can be simplified a bit on top of some PCI and ACPI changes merged
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Subsequent changes will require the ACPI core to acquire the lock
protecting the ACPIPHP hotplug contexts, so move the definition of
the lock to the core and change its name to be more generic.
Signed-off-by: Rafael J. Wysocki
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
If a PCI bridge with an ACPIPHP context attached is removed via
sysfs, the code path executed as a result is the following:
pci_stop_and_remove_bus_device_locked
pci_remove_bus
pcibios_remove_bus
acpi_pci_remove_bus
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Commit 9217a984671e (ACPI / hotplug / PCI: Use global PCI rescan-remove
locking) modified ACPIPHP to protect its PCI device removal and addition
code paths from races against sysfs-driven rescan and remove operations
with the help of PCI
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
According to the changelog of commit 29ed1f29b68a (PCI: pciehp: Fix null
pointer deref when hot-removing SR-IOV device) it is unsafe to walk the
bus-devices list of a PCI bus and remove devices from it in direct order,
because that may lead to
On Mon, 3 Feb 2014 15:23:40 -0800 Andrew Morton a...@linux-foundation.org
wrote:
On Mon, 27 Jan 2014 18:03:04 +0800 Weijie Yang weijie.y...@samsung.com
wrote:
swapoff clear swap_info's SWP_USED flag prematurely and free its resources
after that. A concurrent swapon will reuse this
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpiphp_check_bridge() called by acpiphp_check_host_bridge()
does things that require PCI rescan-remove locking around it,
make acpiphp_check_host_bridge() use that locking.
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
---
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
If a PCI bridge with an ACPIPHP context attached is removed via
sysfs, the code path executed as a result is the following:
pci_stop_and_remove_bus_device_locked
pci_remove_bus
pcibios_remove_bus
acpi_pci_remove_bus
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The err label in register_slot() is only jumped to from one place,
so move the code under the label to that place and drop the label.
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
Tested-by: Mika Westerberg
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
After recent PCI core changes related to the rescan/remove locking,
the ACPIPHP's disable_slot() function is only called under the
general PCI rescan/remove lock, so it doesn't have to use
dev_in_slot() any more to avoid race conditions. Make it
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Add proper kerneldoc comments describing acpiphp_enumerate_slots()
and acpiphp_remove_slots().
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
Tested-by: Mika Westerberg mika.westerb...@linux.intel.com
---
On Mon, Feb 03, 2014 at 05:07:48PM -0600, Rob Herring wrote:
An interesting question however is what the transition plan is to
have the code shared between arm32 and arm64: We will certainly need
to share at least the dw-pcie and the generic SBSA compliant pci
implementation.
You might
On Mon, 3 Feb 2014, Paul E. McKenney wrote:
Hello!
The add_full() function currently has a lockdep_assert_held() requiring
that the kmem_cache_node structure's -list_lock be held. However,
this lock is not acquired by add_full()'s caller deactivate_slab()
in the full-node case unless
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
If trim_stale_devices() calls acpi_bus_trim() directly, we can
save a potentially costly acpi_bus_get_device() invocation. After
making that change acpiphp_bus_trim() would only be called from one
place, so move the code from it to that place
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
If a struct acpi_device pointer is passed to acpiphp_no_hotplug()
instead of an ACPI handle, the function won't need to call
acpi_bus_get_device(), which may be costly, any more. Then,
trim_stale_devices() can call acpiphp_no_hotplug() passing
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
After recent modifications of the ACPI core making it create a struct
acpi_device object for every namespace node representing a device
regardless of the current status of that device the ACPIPHP code
can store a struct acpi_device pointer
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
acpiphp_bus_add() is only called from one place, so move the code out
of it into that place and drop it. Also make that code use
func_to_acpi_device() to get the struct acpi_device pointer it needs
instead of calling acpi_bus_get_device() which
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpi_hotplug_notify_cb() does not use its data argument any
more, the second argument of acpi_install_hotplug_notify_handler()
can be dropped, so do that and update its callers accordingly.
Signed-off-by: Rafael J. Wysocki
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
After recent PCI core changes related to the rescan/remove locking,
the code sections under crit_sect mutexes from ACPIPHP slot objects
are always executed under the general PCI rescan/remove lock.
For this reason, the crit_sect mutexes are
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
A few lines of code can be cut from hotplug_event() by defining
and initializing the slot variable at the top of the function,
so do that.
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
---
drivers/pci/hotplug/acpiphp_glue.c | 19
On Mon, 3 Feb 2014, Andrew Morton wrote:
How do you define huge bloat if the size of vmlinux doesn't increase?
Don't be silly. The size of all the object files increase *hugely*.
yup, I disable this in my allmodconfig testing, to great effect.
That being said, I do think the text
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Introduce a new function, acpi_get_data_full(), working in analogy
with acpi_get_data() except that it can execute a callback provided
as its 4th argument right after acpi_ns_get_attached_data() has
returned a success.
That will allow Linux to
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Make hotplug_event() use acpi_handle_debug() instead of an open-coded
debug message printing and clean up the messages printed by it.
Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
Tested-by: Mika Westerberg
On Mon, 27 Jan 2014 18:03:04 +0800 Weijie Yang weijie.y...@samsung.com wrote:
When swapon the same S_ISBLK blockdev concurrent, the allocated two
swap_info could hold the same block_device, because claim_swapfile()
allow the same holder(here, it is sys_swapon function).
To prevent this
On 02/04/2014 12:16 AM, Willy Tarreau wrote:
On Thu, Jan 30, 2014 at 11:31:32AM +0100, Sebastian Hesselbarth wrote:
On 01/30/14 11:24, Gregory CLEMENT wrote:
On 25/01/2014 19:19, Sebastian Hesselbarth wrote:
This patch set fixes clk init order that went upside-down with
v3.14. I haven't
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since the only existing caller of acpiphp_check_host_bridge(),
which is acpi_pci_root_scan_dependent(), already has a struct
acpi_device pointer needed to obtain the ACPIPHP context, it
doesn't make sense to execute acpi_bus_get_device() on its
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The ACPI-based PCI hotplug (ACPIPHP) code currently attaches its
hotplug context objects directly to ACPI namespace nodes representing
hotplug devices. However, after recent changes causing struct
acpi_device to be created for every namespace
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
There is a slight possibility for the ACPI device object pointed to
by adev in acpi_hotplug_notify_cb() to become invalid between the
acpi_bus_get_device() that it comes from and the subsequent dereference
of that pointer under get_device().
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
To avoid the need to install a hotplug notify handler for each ACPI
namespace node representing a device and having a matching scan
handler, move the check whether or not the ejection of the given
device is enabled through its scan handler from
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since acpi_bus_notify() is executed on all notifications for all
devices anyway, make it execute acpi_device_hotplug() for all
hotplug events instead of installing notify handlers pointing to
the same function for all hotplug devices.
This
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Since hotplug_event() can get the ACPI handle needed for debug
printouts from its context argument, there's no need to pass the
handle to it. Moreover, the second argument's type may be changed
to (struct acpiphp_context *), because that's what
On Mon, 3 Feb 2014, a...@linux-foundation.org wrote:
From: Petr Tesarik ptesa...@suse.cz
Subject: arch/x86/mm/numa_32.c: fix the initialization of physnode_map
With DISCONTIGMEM, the mapping between a pfn and its owning node is
initialized using data provided by the BIOS. However, the
On Mon, Feb 03, 2014 at 05:08:11PM -0600, Larry Finger wrote:
On 02/03/2014 02:39 PM, David Rientjes wrote:
Commit c65c1877bd68 (slub: use lockdep_assert_held) incorrectly required
that add_full() and remove_full() hold n-list_lock. The lock is only
taken when kmem_cache_debug(s), since
Commit c65c1877bd68 (slub: use lockdep_assert_held) incorrectly required
that add_full() and remove_full() hold n-list_lock. The lock is only
taken when kmem_cache_debug(s), since that's the only time it actually
does anything.
Require that the lock only be taken under such a condition.
On Mon, Feb 03, 2014 at 03:31:40PM -0800, David Rientjes wrote:
On Mon, 3 Feb 2014, Paul E. McKenney wrote:
Hello!
The add_full() function currently has a lockdep_assert_held() requiring
that the kmem_cache_node structure's -list_lock be held. However,
this lock is not acquired by
On 02/02/2014 10:54 PM, Alexey Perevalov wrote:
Dear John, hello
could we figure out without Thomas advice?
Maybe it worth to propose timerfd and posix timer flag unification patch?
That would likely get his attention (and possibly wrath)... so not a
bad idea! ;)
thanks
-john
--
To
From: Stephen Warren swar...@nvidia.com
(This is upstream 75fae117a5db ALSA: hda/hdmi - allow PIN_OUT to be
dynamically enabled, backported to stable 3.10 through 3.12. 3.13 and
later can take the original patch.)
Commit 384a48d71520 ALSA: hda: HDMI: Support codecs with fewer cvts
than pins
On Sat 01-02-14 15:45:18, Fabian Frederick wrote:
init_inodecache is only called by __init init_udf_fs.
Thanks. Added to my tree.
Honza
Signed-off-by: Fabian Frederick f...@skynet.be
---
fs/udf/super.c | 2 +-
1 file changed, 1
On Sat 01-02-14 16:02:02, Fabian Frederick wrote:
init_inodecache is only called by __init init_ext2_fs.
Thanks added to my tree.
Honza
Signed-off-by: Fabian Frederick f...@skynet.be
---
fs/ext2/super.c | 2 +-
1 file changed, 1
From: Anssi Hannula anssi.hann...@iki.fi
(This is a backport of *part* of upstream 611885bc963a ALSA: hda -
hdmi: Disallow unsupported 2ch remapping on NVIDIA codecs to stable
3.10 through 3.12. Later stable already contain all of the original
patch.)
Mainline commit 611885bc963a ALSA: hda -
On Sat 01-02-14 19:13:00, Fabian Frederick wrote:
init_inodecache is only called by __init init_ext3_fs.
Thanks. Added to my tree.
Honza
Signed-off-by: Fabian Frederick f...@skynet.be
---
fs/ext3/super.c | 2 +-
1 file changed, 1
Hi
03.02.2014, 05:15, David Fries da...@fries.net:
I could submit these patches as in, which would require the previous
set, or I could merge the documentation into the previous set and
resubmit them all since they haven't made it into the kernel tree yet.
Opinions?
Here's a small
On Mon, Feb 03, 2014 at 02:49:32AM -0800, David Rientjes wrote:
On Mon, 3 Feb 2014, Mel Gorman wrote:
Page migration will fail for memory that is pinned in memory with, for
example, get_user_pages(). In this case, it is unnecessary to take
zone-lru_lock or isolating the page and
On Mon, 3 Feb 2014, Vlastimil Babka wrote:
It seems to come from balloon_page_movable() and its test page_count(page) ==
1.
Hmm, I think it might be because compound_head() == NULL here. Holger,
this looks like a race condition when allocating a compound page, did you
only see it once or
This patch series ultimately adds watchdog support for tegra30 and later
chips.
The existing tegra clocksource driver (drivers/clocksource/tegra20_timer.c)
sadly does not distinguish between tegra20 and tegra30 (and later), which
it should have done since the contents of the timer register base
Added timers that are present in tegra30 and later, that are NOT in tegra20.
Also, some of these timer bases are needed in the tegra watchdog driver, so
separate them out into a header file that both the clocksource driver and
the watchdog driver can share them.
Signed-off-by: Andrew Chew
Add a driver for the hardware watchdogs in NVIDIA Tegra SoCs (tegra30 and
later). This driver will configure one watchdog timer that will reset the
system in the case of a watchdog timeout.
This driver binds to the nvidia,tegra30-timer device node and gets its
register base from there.
There are some differences between tegra20's timer registers and tegra30's
(and later). For example, tegra30 has more timers. In addition, watchdogs
are not present in tegra20.
Add this compatibility string in order to be able to distinguish
whether the additional timers and watchdogs are there
On Tue, 28 Jan 2014 17:19:38 -0800 Davidlohr Bueso davidl...@hp.com wrote:
On Tue, 2014-01-28 at 19:36 -0500, Naoya Horiguchi wrote:
On Mon, Jan 27, 2014 at 06:34:17PM -0800, Davidlohr Bueso wrote:
[...]
If this retry is really essential for the fix, please comment the reason
both in
On Fri, Jan 31, 2014 at 11:47:04PM +0100, Maxime Ripard wrote:
On Fri, Jan 31, 2014 at 12:48:09PM +, Mark Brown wrote:
On Fri, Jan 31, 2014 at 11:55:50AM +0100, Maxime Ripard wrote:
+ pm_runtime_enable(pdev-dev);
+ if (!pm_runtime_enabled(pdev-dev)) {
+ ret =
Hi all,
Today's linux-next merge of the parisc-hd tree got a conflict in
arch/parisc/include/asm/elf.h between commit 9dabf60dc4ab (parisc: add
flexible mmap memory layout support) from Linus' tree and commit
13de8ec38997 (parisc: add flexible mmap memory layout support) from the
parisc-hd tree.
On Tue, Jan 28, 2014 at 10:24 AM, Dave Jones da...@redhat.com wrote:
On Tue, Jan 28, 2014 at 05:05:16PM +0800, Tang Chen wrote:
The following path will cause array out of bound.
memblock_add_region() will always set nid in memblock.reserved to
MAX_NUMNODES.
In
Provide a function that does not just delete an entry at a given
index, but also allows passing in an expected item. Delete only if
that item is still located at the specified index.
This is handy when lockless tree traversals want to delete entries as
well because they don't have to do an
The VM maintains cached filesystem pages on two types of lists. One
list holds the pages recently faulted into the cache, the other list
holds pages that have been referenced repeatedly on that first list.
The idea is to prefer reclaiming young pages over those that have
shown to benefit from
The radix tree hole searching code is only used for page cache, for
example the readahead code trying to get a a picture of the area
surrounding a fault.
It sufficed to rely on the radix tree definition of holes, which is
empty tree slot. But this is about to change, though, as shadow
page
shmem mappings already contain exceptional entries where swap slot
information is remembered.
To be able to store eviction information for regular page cache,
prepare every site dealing with the radix trees directly to handle
entries other than pages.
The common lookup functions will filter out
Fengguang Wu's build testing spotted problems with inc_zone_state()
and dec_zone_state() on UP configurations in out-of-tree patches.
inc_zone_state() is declared but not defined, dec_zone_state() is
missing entirely.
Just like with *_zone_page_state(), they can be defined like their
Previously, page cache radix tree nodes were freed after reclaim
emptied out their page pointers. But now reclaim stores shadow
entries in their place, which are only reclaimed when the inodes
themselves are reclaimed. This is problematic for bigger files that
are still in use after they have a
Reclaim will be leaving shadow entries in the page cache radix tree
upon evicting the real page. As those pages are found from the LRU,
an iput() can lead to the inode being freed concurrently. At this
point, reclaim must no longer install shadow pages because the inode
freeing code needs to
This code used to have its own lru cache pagevec up until a0b8cab3
(mm: remove lru parameter from __pagevec_lru_add and remove parts of
pagevec API). Now it's just add_to_page_cache() followed by
lru_cache_add(), might as well use add_to_page_cache_lru() directly.
Signed-off-by: Johannes Weiner
Page cache radix tree slots are usually stabilized by the page lock,
but shmem's swap cookies have no such thing. Because the overall
truncation loop is lockless, the swap entry is currently confirmed by
a tree lookup and then deleted by another tree lookup under the same
tree lock region.
Use
Make struct radix_tree_node part of the public interface and provide
API functions to create, look up, and delete whole nodes. Refactor
the existing insert, look up, delete functions on top of these new
node primitives.
This will allow the VM to track and garbage collect page cache radix
tree
Changes in this revision
o Fix vmstat build problems on UP (Fengguang Wu's build bot)
o Clarify why optimistic radix_tree_node-private_list link checking
is safe without holding the list_lru lock (Dave Chinner)
o Assert locking balance when the list_lru isolator says it dropped
the
On Mon, 3 Feb 2014, Alexey Dobriyan wrote:
kstrimdup() creates a whitespace-trimmed duplicate of the passed in
null-terminated string. This is useful for strings coming from sysfs that
often include trailing whitespace due to user input.
I think kernel should be strict in what it
On Fri, Jan 31, 2014 at 11:49:01AM -0500, Johannes Weiner wrote:
On Wed, Jan 29, 2014 at 02:11:02PM +0900, Minchan Kim wrote:
It's interesting timing, I posted this patch Yew Year's Day
and receives indepth design review Lunar New Year's Day. :)
It's almost 0-day review. :)
That's the
On Tue, 4 Feb 2014, Joonsoo Kim wrote:
I think that you need more code to skip this type of page correctly.
Without page_mapped() check, this code makes migratable pages be skipped,
since if page_mapped() case, page_count() may be more than zero.
So I think that you need following change.
Quoting David Rientjes (2014-02-03 17:05:04)
The last we heard, I think Sebastian is looking to redo this series and
this patch is no longer needed. Sebastian?
Hi David, Alexey,
I am in the process of reworking the patches. I'm not sure if Andrew
was just interested in having the kstrimdup
On Mon, 3 Feb 2014, Sebastian Capella wrote:
I am in the process of reworking the patches. I'm not sure if Andrew
was just interested in having the kstrimdup utility function available.
I think the point Alexey is making is that whitespace is already stripped
by the shell unless quoted; it
At Korea Linux Forum last fall, Linus asked, haven't I been hearing
about Tux3 for ten years? I said, no, that was Tux2, completely
different. You only heard about Tux3 for six years.
Well, that is about long enough to keep hearing about an out of tree
filesystem. Last time we talked about
On Mon, Feb 03 2014, Michal Hocko wrote:
On Thu 30-01-14 16:28:27, Greg Thelen wrote:
On Thu, Jan 30 2014, Michal Hocko wrote:
On Wed 29-01-14 11:08:46, Greg Thelen wrote:
[...]
The series looks useful. We (Google) have been using something similar.
In practice such a low_limit (or
On Mon, 3 Feb 2014 13:41:01 -0800, Andrew Morton wrote:
On Tue, 4 Feb 2014 01:50:44 +0900 Ryusuke Konishi
konishi.ryus...@lab.ntt.co.jp wrote:
With this ioctl the segment usage entries in the SUFILE can be
updated from userspace.
This is useful, because it allows the userspace GC to
Add description of NILFS_IOCTL_SET_SUINFO ioctl in
Documentation/filesystems/nilfs2.txt to make it up-to-date.
Signed-off-by: Ryusuke Konishi konishi.ryus...@lab.ntt.co.jp
Cc: Andreas Rohner andreas.roh...@gmx.net
---
Documentation/filesystems/nilfs2.txt |7 +++
1 file changed, 7
On Mon, Feb 03, 2014 at 05:20:46PM -0800, David Rientjes wrote:
On Tue, 4 Feb 2014, Joonsoo Kim wrote:
I think that you need more code to skip this type of page correctly.
Without page_mapped() check, this code makes migratable pages be skipped,
since if page_mapped() case, page_count()
On Mon, 03 Feb 2014 14:06:12 +0900
Namhyung Kim namhy...@kernel.org wrote:
Ping!
Hi Namhyung,
I plan on getting these ready for the 3.15 queue. There was a bit too
much in 3.14 to add these on top of at the last minute.
Currently, I'm working on some bugs at work as well as some things I
On Tue, 4 Feb 2014, Joonsoo Kim wrote:
Okay. It can't fix your situation. Anyway, *normal* anon pages may be mapped
and have positive page_count(), so your code such as
'!page_mapping(page) page_count(page)' makes compaction skip these *normal*
anon pages and this is incorrect behaviour.
On 02/03/14 09:24, Jon Medhurst (Tixy) wrote:
On Thu, 2014-01-23 at 15:05 -0500, David Long wrote:
From: David A. Long dave.l...@linaro.org
Make the instruction interpreter call back to semantic action functions
through a function pointer array provided by the invoker. The interpreter
decodes
On 02/03/14 09:57, Jon Medhurst (Tixy) wrote:
On Thu, 2014-01-23 at 15:05 -0500, David Long wrote:
From: David A. Long dave.l...@linaro.org
Change the generic ARM probes code to pass in the opcode and
architecture-specific
structure separately instead of using struct kprobe, so we do not
Binaries compiled for arm may run on arm64 if CONFIG_COMPAT is
selected. Set LSM_MMAP_MIN_ADDR to 32768 if ARM64 COMPAT to
prevent selinux failures launching 32-bit static executables that
are mapped at 0x8000.
Signed-off-by: Colin Cross ccr...@android.com
---
security/Kconfig | 2 +-
1 file
On 02/03/14 10:45, Jon Medhurst (Tixy) wrote:
On Thu, 2014-01-23 at 15:05 -0500, David Long wrote:
From: David A. Long dave.l...@linaro.org
Now that arm uprobes support has been made separate from the arm kprobes code
the Kconfig can be changed to reflect that.
Signed-off-by: David A. Long
On Mon, Feb 03, 2014 at 06:00:56PM -0800, David Rientjes wrote:
On Tue, 4 Feb 2014, Joonsoo Kim wrote:
Okay. It can't fix your situation. Anyway, *normal* anon pages may be mapped
and have positive page_count(), so your code such as
'!page_mapping(page) page_count(page)' makes compaction
On 02/03/2014 11:42 PM, Masami Hiramatsu wrote:
(2014/02/03 20:48), Chen Gang wrote:
On 02/02/2014 10:40 AM, Masami Hiramatsu wrote:
(2014/02/01 21:17), Chen Gang wrote:
When CONFIG_KRETPROBES disabled, cleanup_rp_inst() is useless too. It
is only called by unregister_kretprobes() which is in
On Mon, 03 Feb 2014 17:28:16 -0800 Sebastian Capella
sebastian.cape...@linaro.org wrote:
Quoting David Rientjes (2014-02-03 17:05:04)
The last we heard, I think Sebastian is looking to redo this series and
this patch is no longer needed. Sebastian?
Hi David, Alexey,
I am in the
1201 - 1300 of 1358 matches
Mail list logo
