Hi Wolfram,
On Thu, Jul 10, 2014 at 5:16 PM, Wolfram Sang w...@the-dreams.de wrote:
This driver has been flagged to drop class based instantiation. The removal
improves boot-up time and is unneeded for embedded controllers. Users have
been
warned to switch for some time now, so we can
-Original Message-
From: linux-scsi-ow...@vger.kernel.org [mailto:linux-scsi-
ow...@vger.kernel.org] On Behalf Of Elliott, Robert (Server Storage)
I added some prints in aio_setup_ring and ioctx_alloc and
rebooted. This time it took much longer to hit the problem. It
survived
Hello Pankaj,
On 9 July 2014 09:30, Pankaj Dubey pankaj.du...@samsung.com wrote:
This patch series, modifies Exynos Power Management Unit (PMU) related code
for converting it into a platform_driver. This is also preparation for moving
PMU related code out of machine folder into a either
On Thu, Jul 10, 2014 at 11:05:05PM -0400, Dave Jones wrote:
When the shrinker doesn't free any memory, don't spew over and over
into the logs. My fuzz tester hits this quite easily, resulting
in dozens of instances of this printk when memory runs low, filling
dmesg, when there's not even any
On Fri, Jul 11, 2014 at 06:02:03AM +, Elliott, Robert (Server Storage)
wrote:
Allowing longer run times before declaring success, the problem
does appear in all of the bisect trees. I just let fio
continue to run for many minutes - no ^Cs necessary.
no-rebase: good for 45 minutes (I
For virtual machine and static identity domains, there may be devices
from different PCI segments associated with the same domain.
So function iommu_support_dev_iotlb() should also match PCI segment
number (iommu unit) when searching for dev_iotlb capable devices.
Signed-off-by: Jiang Liu
Introduce intel_unmap() to reduce duplicated code in intel_unmap_sg()
and intel_unmap_page().
Also let dma_pte_free_pagetable() to call dma_pte_clear_range() directly,
so caller only needs to call dma_pte_free_pagetable().
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
Simplify include/linux/dmar.h a bit based on the fact that
both CONFIG_INTEL_IOMMU and CONFIG_IRQ_REMAP select CONFIG_DMAR_TABLE.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
include/linux/dmar.h | 50 ++
1 file changed, 18
Introduce helper function domain_pfn_within_range() to simplify code
and improve readability.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel-iommu.c | 30 --
1 file changed, 16 insertions(+), 14 deletions(-)
diff --git
Enhance error recovery in function intel_enable_irq_remapping()
by tearing down all created data structures.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel_irq_remapping.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git
Finally enhance pci_root driver to support DMAR device hotplug when
hot-plugging PCI host bridges.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/acpi/pci_root.c | 16 ++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/drivers/acpi/pci_root.c
Implement required callback functions for intel_irq_remapping driver
to support DMAR unit hotplug.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel_irq_remapping.c | 222 ++-
1 file changed, 169 insertions(+), 53 deletions(-)
diff --git
On 06/13/2014 02:39 AM, Mike Turquette wrote:
Quoting Tushar Behera (2014-06-12 00:29:23)
On Wed, Jun 11, 2014 at 10:20 PM, Mike Turquette mturque...@linaro.org
wrote:
Quoting Tushar Behera (2014-06-10 22:32:17)
When the output clock of AUDSS mux is disabled, we are getting kernel
oops
On Intel platforms, an IO Hub (PCI/PCIe host bridge) may contain DMAR
units, so we need to support DMAR hotplug when supporting PCI host
bridge hotplug on Intel platforms.
According to Section 8.8 Remapping Hardware Unit Hot Plug in Intel
Virtualization Technology for Directed IO Architecture
Implement required callback functions for intel-iommu driver
to support DMAR unit hotplug.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel-iommu.c | 206 +++
1 file changed, 151 insertions(+), 55 deletions(-)
diff --git
Introduce functions to support dynamic IOMMU seq_id allocating and
releasing, which will be used to support DMAR hotplug.
Also rename IOMMU_UNITS_SUPPORTED as DMAR_UNITS_SUPPORTED.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/dmar.c| 40
IOMMU units may dynamically attached to/detached from domains,
so we should scan all active IOMMU units when computing iommu_snooping
flag for a domain instead of only scanning IOMMU units associated
with the domain.
Also check snooping and superpage capabilities when hot-adding DMAR units.
According to Intel VT-d specification, _DSM method to support DMAR
hotplug should exist directly under corresponding ACPI object
representing PCI host bridge. But some BIOSes doesn't conform to
this, so search for _DSM method in the subtree starting from the
ACPI object representing the PCI host
Introduce helper function dmar_walk_resources to walk resource entries
in DMAR table and ACPI buffer object returned by ACPI _DSM method
for IOMMU hot-plug.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/dmar.c| 208 +++
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel-iommu.c |7 +++
include/linux/iova.h|5 +
2 files changed, 8 insertions(+), 4 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
index c9e65edaa2ad..cd1ba24c766a
Hi Saravana,
Thanks for trying this..
On 11 July 2014 09:48, Saravana Kannan skan...@codeaurora.org wrote:
The CPUfreq driver moves the cpufreq policy ownership between CPUs when
s/driver/core
CPUs within a cluster (CPUs sharing same policy) go ONLINE/OFFLINE. When
moving policy ownership
Virtual machine domains are created by intel_iommu_domain_init() and
should be destroyed by intel_iommu_domain_destroy(). So avoid freeing
virtual machine domain data structure in free_dmar_iommu() when
doamin-iommu_count reaches zero, otherwise it may cause invalid
memory access because the IOMMU
hi Gleb, Marcelo, Nadav,
Would you please help to review these patches ?
Thanks. :)
On 07/08/2014 09:01 PM, Tang Chen wrote:
ept identity pagetable and apic access page in kvm are pinned in memory.
As a result, they cannot be migrated/hot-removed.
But actually they don't need to be pinned in
When using USB 3.0 pen drive with the [AMD] FCH USB XHCI Controller
[1022:7814], the second hotplugging will experience the USB 3.0 pen
drive is recognized as high-speed device. After bisecting the kernel,
I found the commit number 41e7e056cdc662f704fa9262e5c6e213b4ab45dd
(USB: Allow USB 3.0 ports
Introduce domain_attach_iommu()/domain_detach_iommu() and refine
iommu_attach_domain()/iommu_detach_domain() to make code symmetric
and improve readability.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel-iommu.c | 147 +++
1
Static identity and virtual machine domains may be cached in
iommu-domain_ids array after corresponding IOMMUs have been removed
from domain-iommu_bmp. So we should check domain-iommu_bmp before
decreasing domain-iommu_count in function free_dmar_iommu(), otherwise
it may cause free of inuse
Simplify error handling path by changing iommu_{enable|disable}_translation
to return void.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel-iommu.c | 18 +-
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c
Check the same domain id is allocated for si_domain on each IOMMU,
otherwise the IOTLB flush for si_domain will fail.
Now the rules to allocate and manage domain id are:
1) For normal and static identity domains, domain id is allocated
when creating domain structure. And this id will be
When hot plugging a descrete IOH or a physical processor with embedded
IIO, we need to handle DMAR(or IOMMU) unit in the PCIe host bridge if
DMAR is in use. This patch set tries to enhance current DMAR/IOMMU/IR
drivers to support hotplug and is based on latest Joerg's iommu/next
branch.
Patch
Introduce domain_type_is_vm() and domain_type_is_vm_or_si() to improve
code readability.
Also kill useless macro DOMAIN_FLAG_P2P_MULTIPLE_DEVICES.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
drivers/iommu/intel-iommu.c | 59 +++
1 file
For virtual machine domains, domain-id is a virtual id, and the real
domain id written into context entry is dynamically allocated.
So use the real domain id instead of domain-id when flushing iotlbs
for virtual machine domains.
Signed-off-by: Jiang Liu jiang@linux.intel.com
---
Hi Sarah and Mathias,
As the discussion in http://comments.gmane.org/gmane.linux.usb.general/107011,
I found that [AMD] FCH USB XHCI Controller [1022:7814] the USB 3.0 disk
can't work in SuperSpeed after several times of hotplug. After doing some
experiments and bisection, I found the bug is
Hi Linus,
On Tue, Jul 08, 2014 at 11:27:57AM +0200, Linus Walleij wrote:
On Mon, Jul 7, 2014 at 5:23 PM, Baruch Siach bar...@tkos.co.il wrote:
On Mon, Jul 07, 2014 at 04:51:56PM +0200, Linus Walleij wrote:
This needs someone to step in and provide a replacement, my preferred
mechanism
On Thu, Jul 10, 2014 at 09:08:24PM +, Tian, Kevin wrote:
actually I'm curious whether it's still necessary to __detect__ PCH. Could
we assume a 1:1 mapping between GPU and PCH, e.g. BDW already hard
code the knowledge:
} else if (IS_BROADWELL(dev)) {
On Wed, Jul 09, 2014 at 10:27:24PM +, James Bottomley wrote:
If we fix it at source, why would there be any need to filter? That's
the reason the no_write_same flag was introduced. If we can find and
fix the bug, it can go back into the stable trees as a bug fix, hence
nothing should
Or did I read the patch incorrectly?
Maybe I've implemented something incorrectly? I think I suggested
exactly inverse thing: the check is disabled only when the option is
touched by user:
!force_epp intel_bug_present(pb) = intel_bug_present(pb) (given
that force_epp is false)
I don't
* Sebastian Andrzej Siewior bige...@linutronix.de [140710 08:50]:
On 07/10/2014 09:09 AM, Tony Lindgren wrote:
You can test this pretty easily on beagleboard xm for example
using v3.16-r4:
I tried this with am335x-evm, dra7-evm and beaglebone (omap5-uevm and
am335x-evmsk didn't want to
* Roger Quadros rog...@ti.com [140709 05:39]:
Hi,
The following hardware modules/registers are meant for NAND controller driver
usage:
- NAND I/O control (NAND address, data, command registers)
- Prefetch/Write-post engine
- ECC/BCH engine
However, these registers sit in the GPMC
On Thu, 10 Jul 2014, Hugh Dickins wrote:
On Thu, 10 Jul 2014, Sasha Levin wrote:
On 07/10/2014 01:55 PM, Hugh Dickins wrote:
And finally, (not) holding the i_mmap_mutex:
I don't understand what prompts you to show this particular task.
I imagine the dump shows lots of other tasks which
On Wed, Jul 09, 2014 at 11:59:14, Greg Kroah-Hartman wrote:
On Tue, Jul 01, 2014 at 02:33:43PM +0200, Davide Gianforte wrote:
+ uint32_t ctrl_ext = BPCTL_READ_REG(pbpctl_dev, CTRL_EXT);
- ctrl_ext = BPCTL_READ_REG(pbpctl_dev, CTRL_EXT);
How about just removing the = 0; part of the
I decided to play with my snowball board as that's the easiest arm
board I have to do testing on, and it was reported to me that I broke
function graph tracing on the arm boards. But I haven't booted my
snowball since 3.8. When I tried with the latest kernel, it didn't give
me *any* output. I
It might look nicer if the voltage table was in a separate file. A bit
of a border case, maybe.
On 11/07/14 00:42, Tuomas Tynkkynen wrote:
...
+ nvidia,pmic-voltage-table =
+ 0x1e 70,
+ 0x1f 71,
+ 0x20
Hi all,
Changes since 20140710:
My fixes tree contains:
powerpc: Disable RELOCATABLE for COMPILE_TEST with PPC64
The tty.current tree gained a build failure so I used the version from
next-20140710.
The irqchip tree gained a conflict against the arm64 tree.
The staging tree lost its
On Fri, 11 Jul 2014, Ben Hutchings wrote:
I noticed this change between 3.14.3-rt5 and 3.14.10-rt7:
--- debian/patches/features/all/rt/random-make-it-work-on-rt.patch
(revision 21522)
+++ debian/patches/features/all/rt/random-make-it-work-on-rt.patch
(working copy)
[...]
Hello,
How to reproduce:
1. Prepare a container, enable userns and disable netns
2. use libvirt-lxc to start a container
3. libvirt could not mount sysfs then failed to start.
Then I found that
commit 7dc5dbc879bd0779924b5132a48b731a0bc04a1e says:
Don't allow mounting sysfs unless the caller has
Hi Roger,
From: Tony Lindgren [mailto:t...@atomide.com]
* Roger Quadros rog...@ti.com [140709 05:39]:
Hi,
The following hardware modules/registers are meant for NAND controller driver
usage:
- NAND I/O control (NAND address, data, command registers)
- Prefetch/Write-post engine
- ECC/BCH
On Thu, Jul 10, 2014 at 12:08:59PM +0200, Peter Zijlstra wrote:
Since clock_task is the regular clock minus some local amount, the
difference between two regular clock reads is always a strict upper
bound on clock_task differences.
This is inspiring. Regarding the clock source in load avg
On Friday, July 11, 2014 9:44 AM, Tanmay Inamdar wrote:
On Tue, Jul 8, 2014 at 10:18 AM, Liviu Dudau liviu.du...@arm.com wrote:
On Sun, Jul 06, 2014 at 04:23:43PM +0100, Rob Herring wrote:
On Tue, Jul 1, 2014 at 1:43 PM, Liviu Dudau liviu.du...@arm.com wrote:
This is my resurected attempt
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
Previously we have posted a patch fix a memory crash issue caused by
memoryless node on x86 platforms, please refer to
http://comments.gmane.org/gmane.linux.kernel/1687425
As suggested by David Rientjes, the most suitable fix for the issue
should be to use cpu_to_mem() rather than cpu_to_node()
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
On Fri, Jul 11, 2014 at 11:35:23AM +0900, Alexandre Courbot wrote:
On 07/10/2014 09:58 PM, Daniel Vetter wrote:
On Tue, Jul 08, 2014 at 05:25:57PM +0900, Alexandre Courbot wrote:
page_to_phys() is not the correct way to obtain the DMA address of a
buffer on a non-PCI system. Use the DMA API
From: Varka Bhadram var...@cdac.in
This patch fix the *swith* case indentation and usage issues
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c | 117 +--
1 file changed, 58 insertions(+), 59 deletions(-)
diff --git
According to x86 boot sequence, early_cpu_to_node() always returns
NUMA_NO_NODE when called from numa_init(). So kill useless code
to improve code readability.
Related code sequence as below:
x86_cpu_to_node_map is set until step 2, so it is still the default
value (NUMA_NO_NODE) when accessed at
From: Varka Bhadram var...@cdac.in
This patch fix the 'foo*' bar with 'foo *bar'
and (foo*) with (foo *).
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c | 72 +--
1 file changed, 36 insertions(+), 36 deletions(-)
diff --git
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
In data giovedì 10 luglio 2014 14:05:27, Bjorn Helgaas ha scritto:
On Thu, Jul 10, 2014 at 09:12:44PM +0200, Stephane Eranian wrote:
On Thu, Jul 10, 2014 at 2:13 PM, Fabio Coatti fabio.coa...@gmail.com
wrote:
In data giovedì 10 luglio 2014 10:54:48, Peter Zijlstra ha scritto:
On Thu, Jul
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
With typical CPU hot-addition flow on x86, PCI host bridges embedded
in physical processor are always associated with NOMA_NO_NODE, which
may cause sub-optimal performance.
1) Handle CPU hot-addition notification
acpi_processor_add()
acpi_processor_get_info()
Current kernel only updates _mem_id_[cpu] for onlined CPUs when memory
configuration changes. So kernel may allocate memory from remote node
for a CPU if the CPU is still in absent or offline state even if the
node associated with the CPU has already been onlined. This patch tries
to improve
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
With current implementation, all CPUs within a NUMA node will be
assocaited with another NUMA node if the node has no memory installed.
For example, on a four-node system, CPUs on node 2 and 3 are associated
with node 0 when are no memory install on node 2 and 3, which may
confuse users.
On Fri, Jul 11, 2014 at 11:40:27AM +0900, Alexandre Courbot wrote:
On 07/10/2014 10:04 PM, Daniel Vetter wrote:
On Tue, Jul 08, 2014 at 05:25:59PM +0900, Alexandre Courbot wrote:
On architectures for which access to GPU memory is non-coherent,
caches need to be flushed and invalidated
On Thu, 10 Jul, at 11:00:06AM, Yinghai Lu wrote:
Oh, no.
so efi could allocate buffer above 4g but can not access it?
I'm not exactly sure what's wrong with the buffer - whether it's a case
of not being able to access it properly or somehing buggy in the EFI
code for reading files. No fault
From: Varka Bhadram var...@cdac.in
This patch fix the following spacing issues:
no space before tabs
space required after that ';'
space required before the open parenthesis '(
space prohibited before that ':' (ctx:WxE)
space prohibited before that close
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
On 11/07/2014 03:42, Alexandre Courbot wrote:
On 07/10/2014 06:50 PM, Mikko Perttunen wrote:
Does GK20A itself have any kind of thermal protection capabilities?
Upstream SOCTHERM support is not yet available (though I have a driver
in my tree), so we are thinking of disabling CPU DVFS on boards
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
From: Varka Bhadram var...@cdac.in
Normally any device ids will be above the corresponding device driver
structure. This patch moves the pci device ids and MODULE_DEVICE_TABLE()
above the pci driver structure.
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c |
From: Varka Bhadram var...@cdac.in
This patch fixes the comment style issues
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c | 181 +--
1 file changed, 86 insertions(+), 95 deletions(-)
diff --git
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
From: Quadros, Roger
Instead of hardcoding use the pre-calculated chip-ecc.steps for
configuring number of sectors to process with the BCH algorithm.
This also avoids unnecessary access to the ECC_CONFIG register in
omap_calculate_ecc_bch().
Signed-off-by: Roger Quadros rog...@ti.com
---
On Wednesday, July 02, 2014 3:44 AM, Liviu Dudau wrote:
Several platforms use a rather generic version of parsing
the device tree to find the host bridge ranges. Move the common code
into the generic PCI code and use it to create a pci_host_bridge
structure that can be used by arch code.
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
From: Varka Bhadram var...@cdac.in
This patch convert printk() to netdev_dbg/info/err or dev_info/err/dbg
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c | 58 ---
1 file changed, 26 insertions(+), 32 deletions(-)
diff --git
On 07/11/2014 09:48 AM, Saravana Kannan wrote:
The CPUfreq driver moves the cpufreq policy ownership between CPUs when
CPUs within a cluster (CPUs sharing same policy) go ONLINE/OFFLINE. When
moving policy ownership between CPUs, it also moves the cpufreq sysfs
directory between CPUs and also
Il 11/07/2014 09:37, Jiang Liu ha scritto:
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to
On 10-07-14 22:24, Tom Gundersen wrote:
On Thu, Jul 10, 2014 at 10:08 PM, Arend van Spriel ar...@broadcom.com wrote:
On 10-07-14 10:17, Tom Gundersen wrote:
The name is given by the firmware, so we assume it is predictable.
How about the scenario where one would have multiple broadcom wifi
From: Varka Bhadram var...@cdac.in
This patch moves the remove functionalities after the probe
so that we can see the registered and released resources properly.
Every driver follows the same concept.
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c | 25
Hi Alan,
Thanks for reviewing.
On Thu, 10 Jul 2014, Alan Stern wrote:
On Thu, 10 Jul 2014, Peter Griffin wrote:
This driver adds support for the USB HCD present in STi
SoC's from STMicroelectronics. It has been tested on the
stih416-b2020 board.
This driver file, along with the
From: Varka Bhadram var...@cdac.in
This patch replace ioremap() with the devm_ioremap() so that
the resource will be freed automatically with the probe failed.
Signed-off-by: Varka Bhadram var...@cdac.in
---
drivers/net/ethernet/amd/amd8111e.c |7 ++-
1 file changed, 2 insertions(+), 5
On Fri, Jul 11, 2014 at 9:35 AM, varkabhad...@gmail.com wrote:
--- a/drivers/net/ethernet/amd/amd8111e.c
+++ b/drivers/net/ethernet/amd/amd8111e.c
@@ -197,23 +197,24 @@ static void amd8111e_set_ext_phy(struct net_device *dev)
advert = amd8111e_mdio_read(dev, lp-ext_phy_addr,
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
From: Varka Bhadram var...@cdac.in
This series cleanup for AMD811E ethernet driver
Varka Bhadram (8):
ethernet: amd: move amd111e_remove_one after probe
ethernet: amd: use devm_ioremap()
ethernet: amd: dynamic debug fixes
ethernet: amd: fix comment styles
ethernet: amd: move pci device
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
When CONFIG_HAVE_MEMORYLESS_NODES is enabled, cpu_to_node()/numa_node_id()
may return a node without memory, and later cause system failure/panic
when calling kmalloc_node() and friends with returned node id.
So use cpu_to_mem()/numa_mem_id() instead to get the nearest node with
memory for
1 - 100 of 1880 matches
Mail list logo
