On Fri, Feb 15, 2013 at 8:09 PM, Haiyang Zhang haiya...@microsoft.com wrote:
+/* Allocate framebuffer memory */
+#define FOUR_MEGA (4*1024*1024)
+#define NALLOC 10
+static void *hvfb_getmem(void)
+{
+ ulong *p;
+ int i, j;
+ ulong ret = 0;
+
+ if (screen_fb_size
On Mon, Feb 18, 2013 at 02:12:23PM +0800, Li Zefan wrote:
commit 205a872bd6f9a9a09ef035ef1e90185a8245cc58 (cgroup: fix lockdep
warning for event_control) solved a deadlock by introducing a new
bug.
Move cgrp-event_list to a temporary list doesn't mean you can traverse
this list locklessly,
Hi Mel,
See below.
On 02/05/2013 07:57 PM, Mel Gorman wrote:
On Mon, Feb 04, 2013 at 04:06:24PM -0800, Andrew Morton wrote:
The ifdefs aren't really needed here and I encourage people to omit
them. This keeps the header files looking neater and reduces the
chances of things later breaking
On 02/18/2013 03:54 PM, Vincent Guittot wrote:
On 15 February 2013 20:40, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
Hi Vincent,
On 02/15/2013 06:58 PM, Vincent Guittot wrote:
Hi Srivatsa,
I have run some tests with you branch (thanks Paul for the git tree)
and you will find
On 2013/2/18 18:36, Kirill A. Shutemov wrote:
On Mon, Feb 18, 2013 at 02:12:23PM +0800, Li Zefan wrote:
commit 205a872bd6f9a9a09ef035ef1e90185a8245cc58 (cgroup: fix lockdep
warning for event_control) solved a deadlock by introducing a new
bug.
Move cgrp-event_list to a temporary list doesn't
On 02/18/2013 04:04 PM, Srivatsa S. Bhat wrote:
On 02/18/2013 03:54 PM, Vincent Guittot wrote:
On 15 February 2013 20:40, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
Hi Vincent,
On 02/15/2013 06:58 PM, Vincent Guittot wrote:
Hi Srivatsa,
I have run some tests with you branch
On Mon, Feb 18, 2013 at 11:14:27AM +0100, Christian Ruppert wrote:
This patch makes the SDA hold time configurable through device tree.
It was tested on a hybrid of i2c/next and arc-3.8-baseline (see
https://github.com/foss-for-synopsys-dwc-arc-processors/linux/commits/arc-3.8-baseline)
since
On Mon, 18 Feb 2013, Srivatsa S. Bhat wrote:
Lockup observed while running this patchset, with CPU_IDLE and INTEL_IDLE
turned
on in the .config:
smpboot: CPU 1 is now offline
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 11
Pid: 0, comm: swapper/11 Not tainted
commit 205a872bd6f9a9a09ef035ef1e90185a8245cc58 (cgroup: fix lockdep
warning for event_control) solved a deadlock by introducing a new
bug.
Move cgrp-event_list to a temporary list doesn't mean you can traverse
this list locklessly, because at the same time cgroup_event_wake() can
be called and
On 18 February 2013 11:51, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
On 02/18/2013 04:04 PM, Srivatsa S. Bhat wrote:
On 02/18/2013 03:54 PM, Vincent Guittot wrote:
On 15 February 2013 20:40, Srivatsa S. Bhat
srivatsa.b...@linux.vnet.ibm.com wrote:
Hi Vincent,
On 02/15/2013
On 02/18/2013 04:24 PM, Thomas Gleixner wrote:
On Mon, 18 Feb 2013, Srivatsa S. Bhat wrote:
Lockup observed while running this patchset, with CPU_IDLE and INTEL_IDLE
turned
on in the .config:
smpboot: CPU 1 is now offline
Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 11
Am 11.02.2013 11:31, schrieb Mika Westerberg:
We now have two transport mediums: USB and I2C, where sensor hubs can
exists. So instead of constraining the driver to only these two we let it
to match any HID bus as long as the group is HID_GROUP_SENSOR_HUB.
Signed-off-by: Mika Westerberg
Namjae Jeon linkinj...@gmail.com writes:
+ if (MSDOS_SB(inode-i_sb)-options.nfs == FAT_NFS_NOSTALE_RO) {
+ if (inode-i_ino == MSDOS_ROOT_INO)
+ stat-ino = MSDOS_ROOT_INO;
Can we simply set i_pos = MSDOS_ROOT_INO in fat_read_root()? If so, I
think we can
://code.google.com/p/kgtp/wiki/HOWTO (Chinese) to get more info
about howto use KGTP.
Now, KGTP 20130218 release.
You can get the package for it from
http://kgtp.googlecode.com/files/kgtp_20130218.tar.bz2
or
svn co https://kgtp.googlecode.com/svn/tags/20130218
The main change of this release is add watch
On Mon, Feb 18, 2013 at 12:03:04PM +0100, Alexander Holler wrote:
Am 11.02.2013 11:31, schrieb Mika Westerberg:
We now have two transport mediums: USB and I2C, where sensor hubs can
exists. So instead of constraining the driver to only these two we let it
to match any HID bus as long as the
Namjae Jeon linkinj...@gmail.com writes:
-nfs -- This option maintains an index (cache) of directory
- inodes by i_logstart which is used by the nfs-related code to
- improve look-ups.
+nfs= stale_rw|nostale_ro
Strange space after nfs=.
--
OGAWA Hirofumi
Maksim Pikhenko pikhe...@gmail.com writes:
Fixing a code style issue.
Signed-off-by: Maksim Pikhenko pikhe...@gmail.com
Acked-by: OGAWA Hirofumi hirof...@mail.parknet.co.jp
---
fs/fat/inode.c |1 -
1 file changed, 1 deletion(-)
diff --git a/fs/fat/inode.c b/fs/fat/inode.c
index
On Mon, 18 Feb 2013, Tim Sander wrote:
Here is a transtribed backtrace for easier reading:
c0010fac t dump_backtrace
c022c188 T dump_stack
c022c71c t __schedule_bug
c022fb28 t __schedule
c0230644 t rt_spin_lock_slowlock
c0230ba8 T rt_spin_lock
c003a9b8 T __wake_up
c0052a44 t
On Fri, Feb 15, 2013 at 08:37:13PM +0100, Peter Huewe wrote:
- for (i = 0; i 256; i++) {
- outb((unsigned char) DAC_TEST_PARMS[0], (pVBInfo-P3c8 + 1));
- outb((unsigned char) DAC_TEST_PARMS[1], (pVBInfo-P3c8 + 1));
- outb((unsigned char)
On 02/16/2013 08:33 AM, Anil Kumar wrote:
Add the needed sections to enable audio support on
Devkit8000 when booted with DT blob.
Signed-off-by: Anil Kumar anilk...@gmail.com
Looks good:
Acked-by: Peter Ujfalusi peter.ujfal...@ti.com
---
This patch is based on top of kernel 3.8-rc5 and
Am 18.02.2013 12:12, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:03:04PM +0100, Alexander Holler wrote:
Am 11.02.2013 11:31, schrieb Mika Westerberg:
We now have two transport mediums: USB and I2C, where sensor hubs can
exists. So instead of constraining the driver to only these two we
On Fri, Feb 15, 2013 at 08:37:11PM +0100, Peter Huewe wrote:
The tempal variable is assigned and then immediately overwritten.
- remove everything without effect.
The inb is kept for possible side effects.
This was dead code after we removed old mode = 14 support in
34c13ee2b staging:
On Mon, Feb 18, 2013 at 12:22:58PM +0100, Alexander Holler wrote:
Am 18.02.2013 12:12, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:03:04PM +0100, Alexander Holler wrote:
Am 11.02.2013 11:31, schrieb Mika Westerberg:
We now have two transport mediums: USB and I2C, where sensor hubs can
When implementing network protocols in user space, one has to implement
fake file descriptors to represent the sockets for the protocol.
Polling on such fake file descriptors is a problem (poll/select/epoll accept
only true file descriptors) and forces protocol implementers to use various
(Resending, since it seems, LAKML doesn't accept patches with subject
prefix only as RFC, but requires PATCH prefix also)
Hi,
This series adds minimal support to boot Linux on platforms having
AM43 based SoC's.
This is being sent as an RFC to seek opinion about modification in
twd to register
Return percpu clock event on local timer register. It is the boot cpu
that calls this and it can use the returned percpu clock event to
register a clock event in the case of SMP configuration with one core.
This helps to have a booting Kernel even if no other timer is
registered for clock tick.
Register percpu local timer for scheduler tick in the case of one core
SMP configuration. In other cases - secondary cpu's as well as boot
cpu's having more than one core, this is being registered as per
existing boot flow, with a difference that they happens after delay
calibration. Registering
Selecting DEBUG_AM33XXUART1 routes low level debug messages to first
UART instance of AM335x based SoC's. This selection is valid for
upcoming AM43 based SoC's too. Make this information available upon
configuring.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/Kconfig.debug | 3 +++
1
Add Kconfig option for AM43 family of SoC's, these are ARM Cortex A9
based (SMP configuration with 1 core).
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/mach-omap2/Kconfig | 11 +++
1 file changed, 11 insertions(+)
diff --git a/arch/arm/mach-omap2/Kconfig
Describe minimal DT boot machine details for AM43 based SoC's. AM43
family of SoC's are ARM Cortex-A9 based with one core in SMP
configuration. Low level debug could be achieved by selecting
DEBUG_AM33XXUART1. To boot AM43 SoC, this change is sufficient w.r.t
Kernel (considering the fact that
DT source (minimal) for AM4372 SoC. Those represented here are the
minimal DT nodes necessary to get kernel booting.
Signed-off-by: Afzal Mohammed af...@ti.com
---
arch/arm/boot/dts/am4372.dtsi | 55 +++
1 file changed, 55 insertions(+)
create mode 100644
AM43 SoC is in pre-silicon stage, meanwhile it has been modelled in
a pre-silicon platform. To validate and boot Linux in pre-silicon
platform that emulates an AM43 SoC, add DT build support.
As bootloader is not used, bootargs is passed through DT.
Note: This would be replaced by an original
Add an optional property to find clock-frequency from DT. This helps
as a fallback mechanism in case there is no representation of clock
tree in DT.
Signed-off-by: Afzal Mohammed af...@ti.com
---
Documentation/devicetree/bindings/arm/twd.txt | 7 ++-
arch/arm/kernel/smp_twd.c
This patch fixes an instance of DMA buffer on stack(being passed to
usb_control_msg) for the wireless USB version of the Agere Orinoco card driver.
It also fixes the missing audit for the return value of firmware download
routine. Found using smatch.
Signed-off-by: Kumar Amit Mehta
Am 18.02.2013 12:33, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:22:58PM +0100, Alexander Holler wrote:
Am 18.02.2013 12:12, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:03:04PM +0100, Alexander Holler wrote:
Am 11.02.2013 11:31, schrieb Mika Westerberg:
We now have two
OGAWA Hirofumi hirof...@mail.parknet.co.jp writes:
+if (parent (len FAT_FID_SIZE_WITH_PARENT)) {
+*lenp = FAT_FID_SIZE_WITH_PARENT;
+return 255;
+} else if (len FAT_FID_SIZE_WITHOUT_PARENT) {
+*lenp = FAT_FID_SIZE_WITHOUT_PARENT;
+
On Mon, Feb 18, 2013 at 2:18 PM, Daniel J Blueman
dan...@numascale-asia.com wrote:
On Monday, 18 February 2013 06:10:02 UTC+8, Jiri Slaby wrote:
Hi,
You still feel the sour taste of the kswapd craziness in v3.7 thread,
right? Welcome to the hell, part two :{.
I believe this started
On Mon, Feb 18, 2013 at 12:37:52PM +0100, Alexander Holler wrote:
Am 18.02.2013 12:33, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:22:58PM +0100, Alexander Holler wrote:
Am 18.02.2013 12:12, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:03:04PM +0100, Alexander Holler wrote:
Am
Jonathan Andrews jon at jonshouse.co.uk writes:
What about a yield alignment mechanism for user space. IE the process
calls the kernel with a request schedule me first after a yeild - then
the process at least has whatever the timer granularity is to do
something timing critical... add a
On 14/02/13 23:54, Andrew Morton wrote:
This patch adds userspace interfaces which will require manpage
updates. Please Cc Michael and work with him on getting those changes
completed.
Right. It adds the efd_mask structure. As far as I understand how it
works is that the actual user-space
From: Lad, Prabhakar prabhakar@ti.com
The patch adds support for THS7353 video amplifier.
The the THS7353 amplifier is very much similar to the
existing THS7303 video amplifier driver.
This patch appropriately makes changes to the existing
ths7303 driver and adds support for the THS7353.
This
When memory allocation using, kmalloc() fails, report appropriate error value.
Signed-off-by: Kumar Amit Mehta gmate.a...@gmail.com
---
drivers/net/wireless/hostap/hostap_ap.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/hostap/hostap_ap.c
Am 18.02.2013 12:54, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:37:52PM +0100, Alexander Holler wrote:
Am 18.02.2013 12:33, schrieb Mika Westerberg:
On Mon, Feb 18, 2013 at 12:22:58PM +0100, Alexander Holler wrote:
Am 18.02.2013 12:12, schrieb Mika Westerberg:
On Mon, Feb 18, 2013
On Monday, February 18, 2013 06:26:34 AM Li, Fei wrote:
-Original Message-
From: Rafael J. Wysocki [mailto:r...@sisk.pl]
Sent: Friday, February 15, 2013 1:38 AM
To: Miklos Szeredi
Cc: Pavel Machek; Goswin von Brederlow; Li, Fei; Brown, Len;
mi...@redhat.com;
Hi Stephen,
On Monday, February 18, 2013 12:17:07 PM Stephen Rothwell wrote:
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in
drivers/acpi/scan.c between commits 668192b67820 (PCI: acpiphp: Move
host bridge hotplug to pci_root.c) and ab1a2e038ff2 (ACPI / PCI: Make
Hi Stephen,
On Monday, February 18, 2013 12:11:05 PM Stephen Rothwell wrote:
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in
drivers/acpi/internal.h between commits 668192b67820 (PCI: acpiphp: Move
host bridge hotplug to pci_root.c) and ab1a2e038ff2 (ACPI / PCI: Make
with linux-next-20130207 and
linux-next-20130218 by doing an SCI-eject request on a hot-plugged dimm.
Are there more patches in development for safe memory hot-remove?
thanks,
- Vasilis
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
On 8 February 2013 19:05, Vincent Guittot vincent.guit...@linaro.org wrote:
On my smp platform which is made of 5 cores in 2 clusters, I have the
nr_busy_cpu field of sched_group_power struct that is not null when the
platform is fully idle. The root cause seems to be:
During the boot
Am Montag, 18. Februar 2013, 12:16:41 schrieb Thomas Gleixner:
On Mon, 18 Feb 2013, Tim Sander wrote:
Here is a transtribed backtrace for easier reading:
c0010fac t dump_backtrace
c022c188 T dump_stack
c022c71c t __schedule_bug
c022fb28 t __schedule
c0230644 t rt_spin_lock_slowlock
Hi,
This patchset removes CPU hotplug's dependence on stop_machine() from the CPU
offline path and provides an alternative (set of APIs) to preempt_disable() to
prevent CPUs from going offline, which can be invoked from atomic context.
The motivation behind the removal of stop_machine() is to
A straight-forward (and obvious) algorithm to implement Per-CPU Reader-Writer
locks can also lead to too many deadlock possibilities which can make it very
hard/impossible to use. This is explained in the example below, which helps
justify the need for a different algorithm to implement flexible
Add the support for defining and initializing percpu-rwlocks at compile time
for those users who would like to use percpu-rwlocks really early in the boot
process (even before dynamic per-CPU allocations can begin).
Cc: David Howells dhowe...@redhat.com
Signed-off-by: Srivatsa S. Bhat
Using global rwlocks as the backend for per-CPU rwlocks helps us avoid many
lock-ordering related problems (unlike per-cpu locks). However, global
rwlocks lead to unnecessary cache-line bouncing even when there are no
writers present, which can slow down the system needlessly.
Per-cpu counters
If we are dealing with a nester percpu reader, we can optimize away quite
a few costly operations. Improve that fastpath further, by avoiding the
unnecessary addition and subtraction of 'READER_PRESENT' to reader_refcnt,
by rearranging the code a bit.
Signed-off-by: Srivatsa S. Bhat
CPU hotplug (which will be the first user of per-CPU rwlocks) has a special
requirement with respect to locking: the writer, after acquiring the per-CPU
rwlock for write, must be allowed to take the same lock for read, without
deadlocking and without getting complaints from lockdep. In comparison,
On 12/05/2012 06:10 AM, Andrew Morton wrote:
static inline C functions would be preferred if possible. Feel free to
fix up the wrong crufty surrounding code as well ;-)
Convert the macros in the CPU hotplug code to static inline C functions.
Signed-off-by: Srivatsa S. Bhat
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() to prevent CPUs from going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Signed-off-by: Srivatsa S.
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() to prevent CPUs from going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Signed-off-by: Srivatsa S.
We need not use the raw_spin_lock_irqsave/restore primitives because
all CPU_DYING notifiers run with interrupts disabled. So just use
raw_spin_lock/unlock.
Signed-off-by: Srivatsa S. Bhat srivatsa.b...@linux.vnet.ibm.com
---
kernel/sched/core.c | 12 +---
1 file changed, 5
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from going
offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
The cpu idle code invokes clockevents_notify() during idle state transitions
and the cpu offline code invokes it during the CPU_DYING phase. There
seems to be a race-condition between the two, where the clockevents_lock
never gets released, ending in a lockup. This can be fixed by synchronizing
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc: H.
The CPU_DYING notifier modifies the per-cpu pointer pmu-box, and this can
race with functions such as uncore_pmu_to_box() and uncore_pci_remove() when
we remove stop_machine() from the CPU offline path. So protect them using
get/put_online_cpus_atomic().
Cc: H. Peter Anvin h...@zytor.com
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Also,
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs fom
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
From: Paul E. McKenney paul.mcken...@linaro.org
The _cpu_down() function invoked as part of the CPU-hotplug offlining
process currently invokes __stop_machine(), which is slow and inflicts
substantial real-time latencies on the entire system. This patch
substitutes stop_one_cpu() for
Simply dropping HOTPLUG_CPU from the dependency list of STOP_MACHINE will
lead to the following kconfig issue, reported by Fengguang Wu:
warning: (HAVE_TEXT_POKE_SMP) selects STOP_MACHINE which has unmet direct
dependencies (SMP MODULE_UNLOAD)
So drop HOTPLUG_CPU and add HAVE_TEXT_POKE_SMP to
Since stop_machine() is no longer used in the CPU offline path, we cannot
disable CPU hotplug using preempt_disable()/local_irq_disable() etc. We
need to use the newly introduced get/put_online_cpus_atomic() APIs.
Reflect this in the documentation.
Cc: Rob Landley r...@landley.net
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
The OMAP4 Blaze Tablet is TI OMAP4 processor-based
development platform in a tablet formfactor.
The platform contains many of the features found in
present-day handsets (such as audio, video, wireless
functions and user interfaces) and in addition
contains features for software development and
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context (in
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from
going offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Cc:
The pcrypt_aead_init_tfm() function access the cpu_online_mask without
disabling CPU hotplug. And it looks like it can afford to sleep, so use
the get/put_online_cpus() APIs to protect against CPU hotplug.
Cc: Steffen Klassert steffen.klass...@secunet.com
Cc: Herbert Xu
This patch makes the SDA hold time configurable through device tree.
It was tested on a hybrid of i2c/next and arc-3.8-baseline (see
https://github.com/foss-for-synopsys-dwc-arc-processors/linux/commits/arc-3.8-baseline)
since our platform is ARC based and this architecture is not yet
supported
This patch is for kernel V3.7.9
From 8796f4a2175a323aaa49ea8dd0fe68678dd5dccd Mon Sep 17 00:00:00 2001
From: ybu y...@qti.qualcomm.com
Date: Mon, 18 Feb 2013 19:52:01 +0800
Subject: [PATCH] Fix rq-lock vs logbuf_lock unlock race
fix up the fallout from commit 07354eb1a74d1 (locking printk:
Per-CPU rwlocks ought to give better performance than global rwlocks.
That is where the per-CPU component comes in. So introduce the necessary
per-CPU variables that would be necessary at the reader and the writer sides,
and add the support for dynamically initializing per-CPU rwlocks.
These
Once stop_machine() is gone from the CPU offline path, we won't be able to
depend on preempt_disable() or local_irq_disable() to prevent CPUs from going
offline from under us.
Use the get/put_online_cpus_atomic() APIs to prevent CPUs from going offline,
while invoking from atomic context.
Hi,
This patch is a second attempt to add basic support of OMAP4 Blaze Tablet
software development platform - in this case using only Device Tree.
Additional information about this platform can be found here:
http://www.svtronics.com/omap?product_id=15
Ruslan Bilovol (1):
ARM: DTS: OMAP4: Add
There are places where preempt_disable() or local_irq_disable() are used
to prevent any CPU from going offline during the critical section. Let us
call them as atomic hotplug readers (atomic because they run in atomic,
non-preemptible contexts).
Today, preempt_disable() or its equivalent works
If interrupt handlers can also be readers, then one of the ways to make
per-CPU rwlocks safe, is to disable interrupts at the reader side before
trying to acquire the per-CPU rwlock and keep it disabled throughout the
duration of the read-side critical section.
The goal is to avoid cases such as:
This patchset provides the Freescale PAMU (Peripheral Access Management Unit)
driver
and the corresponding IOMMU API implementation. PAMU is the IOMMU present on
Freescale
QorIQ platforms. PAMU can authorize memory access, remap the memory address,
and remap
the I/O transaction type.
This set
Add a new field in the device (powerpc) archdata structure for storing iommu
domain
information pointer. This pointer is stored when the device is attached to a
particular
domain.
Signed-off-by: Varun Sethi varun.se...@freescale.com
---
- no change.
arch/powerpc/include/asm/device.h |4
Each iommu window can have access permissions associated with it. Extended the
window_enable API to incorporate window access permissions.
Signed-off-by: Varun Sethi varun.se...@freescale.com
---
drivers/iommu/iommu.c |5 +++--
include/linux/iommu.h |7 ---
2 files changed, 7
Added the following domain attributes for the FSL PAMU driver:
1. Added new iommu stash attribute, which allows setting of the
LIODN specific stash id parameter through IOMMU API.
2. Added an attribute for enabling/disabling DMA to a particular
memory window.
3. Added domain attribute to
The pci controller structure has a provision to store the device strcuture
pointer of the corresponding platform device. Currently this information is
not stored during fsl pci controller initialization. This information is
required while dealing with iommu groups for pci devices connected to the
601 - 700 of 1098 matches
Mail list logo
