Al Viro:
> Different ->i_mutex; you are holding one on the parent directory already.
Let me make sure. In your scenario,
- processA writes something into the union, and the unioning fs operates
the writable layer. After sb_start_write() succeeds, processA should
not block by the reason of
On Fri, Mar 22, 2013 at 11:27:16PM -0400, Mike Snitzer wrote:
> On Fri, Mar 22 2013 at 7:16pm -0400,
> Darrick J. Wong wrote:
>
> > On Fri, Mar 22, 2013 at 06:34:28PM -0400, Mike Snitzer wrote:
> > > On Fri, Mar 22 2013 at 4:11pm -0400,
> > > Darrick J. Wong wrote:
> > >
> > > > The new
On Sat, Mar 23, 2013 at 11:49:11AM +0900, J. R. Okajima wrote:
>
> Al Viro:
> > The scenario, BTW, looks so:
> > process A does sb_start_write() (on your upper layer)
> > process B tries to freeze said upper layer and blocks, waiting for A to
> > finish
> > process C grabs ->i_mutex in your
On Sat, Mar 23 2013, Aaron Lu wrote:
> In August 2010, Jens and Alan discussed about "Runtime PM and the block
> layer". http://marc.info/?t=12825910841=1=2
> And then Alan has given a detailed implementation guide:
> http://marc.info/?l=linux-scsi=133727953625963=2
>
> To test:
> # ls -l
Exynos5440 has two PCIe controllers which can be used as root complex
for PCIe interface.
Signed-off-by: Jingoo Han
---
arch/arm/boot/dts/exynos5440-ssdk5440.dts |8 +++
arch/arm/boot/dts/exynos5440.dtsi | 32 +
2 files changed, 40 insertions(+), 0
Enable PCIe support for Exynos5440 which has two PCIe controllers.
Signed-off-by: Jingoo Han
---
arch/arm/Kconfig |1 +
arch/arm/mach-exynos/Kconfig |1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig
index
Exynos5440 has a PCIe controller which can be used as Root Complex.
This driver supports a PCIe controller as Root Complex mode.
Signed-off-by: Surendranath Gurivireddy Balla
Signed-off-by: Siva Reddy Kallam
Signed-off-by: Jingoo Han
---
.../devicetree/bindings/pci/exynos-pcie.txt|
From: Thomas Petazzoni
As agreed by the community, PCI host drivers will now be stored in
drivers/pci/host. This commit adds this directory and the related
Kconfig/Makefile changes to allow new drivers to be added in this
directory.
Signed-off-by: Thomas Petazzoni
Signed-off-by: Jingoo Han
From: Thierry Reding
This function can be used to parse a bus-range property as specified by
device nodes representing PCI bridges.
Signed-off-by: Thierry Reding
Signed-off-by: Jingoo Han
---
drivers/of/of_pci.c| 25 +
include/linux/of_pci.h |1 +
2 files
From: Andrew Murray
This patch factors out common implementations patterns to reduce overall kernel
code and provide a means for host bridge drivers to directly obtain struct
resources from the DT's ranges property without relying on architecture specific
DT handling. This will make it easier to
Please pull b186affe0c9d39e4d3152cd34bffea8fe1fa17f4 from
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
tags/upstream-linus
to receive the following updates:
drivers/ata/Kconfig | 13 +++--
drivers/ata/ahci.c| 2 ++
drivers/ata/ata_piix.c
On Fri, 2013-03-22 at 15:41 +, Christoph Lameter wrote:
> The control is via the cpu_partial field in /sys/kernel/slab//
>
> There is also slabs_cpu_partial which gives a view as to how many objects
> are cached in each per cpu structure. Do a cat
>
> /sys/kernel/*/slabs_cpu_partial to get
On Fri, Mar 22, 2013 at 11:27:16PM -0400, Mike Snitzer wrote:
> So the big difference is the thinp-test-suite uses intermediate linear
> DM layers above the slower sd device (spindle/data) -- whereas in your
> setup the origin device is direct to sd (8:0).
I would think the difference is because
From: Lin Ming
Add a flag REQ_PM to identify the request is PM related, such requests
will not change the device request queue's runtime status. It is
intended to be used in driver's runtime PM callback, so that driver can
perform some IO to the device there with the queue's runtime status
In August 2010, Jens and Alan discussed about "Runtime PM and the block
layer". http://marc.info/?t=12825910841=1=2
And then Alan has given a detailed implementation guide:
http://marc.info/?l=linux-scsi=133727953625963=2
To test:
# ls -l /sys/block/sda
From: Lin Ming
When a request is added:
If device is suspended or is suspending and the request is not a
PM request, resume the device.
When the last request finishes:
Call pm_runtime_mark_last_busy().
When pick a request:
If device is resuming/suspending, then only PM request
From: Lin Ming
With the introduction of REQ_PM, modify sd's runtime suspend operation
functions to use that flag so that the operations to put the device into
runtime suspended state(i.e. sync cache and stop device) will not affect
its runtime PM status.
Signed-off-by: Lin Ming
Signed-off-by:
From: Lin Ming
Add runtime pm helper functions:
void blk_pm_runtime_init(struct request_queue *q, struct device *dev)
- Initialization function for drivers to call.
int blk_pre_runtime_suspend(struct request_queue *q)
- If any requests are in the queue, mark last busy and return -EBUSY.
From: Lin Ming
Uses block layer runtime pm helper functions in
scsi_runtime_suspend/resume for devices that take advantage of it.
Remove scsi_autopm_* from sd open/release path and check_events path.
Signed-off-by: Lin Ming
Signed-off-by: Aaron Lu
Acked-by: Alan Stern
---
On 03/22/2013 11:09 PM, Jens Axboe wrote:
> On Fri, Mar 15 2013, Aaron Lu wrote:
>> In August 2010, Jens and Alan discussed about "Runtime PM and the block
>> layer". http://marc.info/?t=12825910841=1=2
>> And then Alan has given a detailed implementation guide:
>>
On Fri, Mar 22 2013 at 7:16pm -0400,
Darrick J. Wong wrote:
> On Fri, Mar 22, 2013 at 06:34:28PM -0400, Mike Snitzer wrote:
> > On Fri, Mar 22 2013 at 4:11pm -0400,
> > Darrick J. Wong wrote:
> >
> > > The new writethrough strategy for dm-cache issues a bio to the origin
> > > device,
> > >
>
> sizeof() when applied to a pointer typed expression gives the size of the
> pointer,
> not that of the pointed data.
>
> Signed-off-by: Wei Yongjun
> ---
> drivers/mailbox/mailbox.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mailbox/mailbox.c
Hi Linus,
On Fri, Mar 22, 2013 at 10:37 PM, Linus Torvalds
wrote:
> On Fri, Mar 22, 2013 at 4:04 AM, Emmanuel Benisty wrote:
>>
>> I was trying your patchset and my machine died while building a
>> package. I could reproduce the bug the (only) two times I tried.
>> There's a poor quality
8), done.
> remote: Total 184570 (delta 165819), reused 166851 (delta 149091)
> Receiving objects: 100% (184570/184570), 25.60 MiB | 886 KiB/s, done.
> Resolving deltas: 100% (165819/165819), completed with 5985 local objects.
> Checking out files: 100% (42561/42561), done.
> $ cd
On Fri, Mar 22, 2013 at 01:11:51PM -0700, Darrick J. Wong wrote:
> The new writethrough strategy for dm-cache issues a bio to the origin device,
> remaps the bio to the cache device, and issues the bio to the cache device.
> However, the block layer modifies bi_sector and bi_size, so we need to
>
On 2013年03月23日 03:17, Yoder Stuart-B08248 wrote:
> allmodconfig is creating config combinations that don't
> happen in a normal build (at least currently)-- 64-bit build
> that enables EPAPR_PARAVIRT but not PPC_BOOK3E_64.
if it should not happen.
can we add dependency to let it will never
Al Viro:
> The scenario, BTW, looks so:
> process A does sb_start_write() (on your upper layer)
> process B tries to freeze said upper layer and blocks, waiting for A to finish
> process C grabs ->i_mutex in your upper layer
> process C does vfs_write(), which blocks, since there's a pending
On 03/22/2013 06:55 AM, Lubomir Rintel wrote:
> Signed-off-by: Lubomir Rintel
A commit description would be useful.
> arch/arm/boot/dts/bcm2835.dtsi |5 +
> arch/arm/configs/bcm2835_defconfig |3 +-
> drivers/char/hw_random/Kconfig | 12 +++
>
On 03/22/2013 06:55 AM, Lubomir Rintel wrote:
> Signed-off-by: Lubomir Rintel
A commit description would be useful.
> arch/arm/configs/bcm2835_defconfig |4 +
> drivers/watchdog/Kconfig | 11 +++
> drivers/watchdog/Makefile |1 +
> drivers/watchdog/bcm2835_wdt.c
From: Andi Kleen
Writing _xbegin which is like setjmp in a if is very natural.
Stop checkpatch's whining about this.
Cc: a...@canonical.com
Signed-off-by: Andi Kleen
---
scripts/checkpatch.pl |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/scripts/checkpatch.pl
From: Andi Kleen
This adds the basic RTM (Restricted Transactional Memory)
intrinsics for TSX, implemented with alternative() so that they can be
transparently used without checking CPUID first.
When the CPU does not support TSX we just always jump to the abort handler.
These intrinsics are
From: Andi Kleen
__read/write_lock_failed did execute a PAUSE first thing before
checking the lock. This aborts transactions. Check the lock
state again before executing the pause. This avoids a small
number of extra aborts, and is slightly cheaper too.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
Extend the elide() macro to support adaptation state per lock.
The adaptation keeps track whether the elision is successfull.
When the lock aborts due to internal reasons (e.g. it always
writes a MSR or always does MMIO) disable elision for some time.
The state is kept as a
From: Andi Kleen
rwspinlocks don't support paravirt ops, so add hooks to call lock elision
based on the CPUID bit. We use the standard patching, so the overhead
in the fast path is low when RTM is not supported.
Signed-off-by: Andi Kleen
---
arch/x86/include/asm/spinlock.h | 104
From: Andi Kleen
Add the elision adaption state to struct mutex and use elide_adapt()
This allows mutexes that do not elide to automatically disable
elision on themselves for some time. This means we have a fail-safe
for mutexes that do not elide well and do not need to annotate
very mutex.
From: Andi Kleen
For some locks that have a low chance of not aborting it's
best to just disable transactions.
Add a counter to thread_info to allow to disable tranasctions
for the current task.
I originally experimented with more complicated solutions,
like a magic spinlock type to disable
From: Andi Kleen
Add a module param type for uint static keys. Useful for
time critical flags.
Cc: ru...@rustcorp.co.au
Signed-off-by: Andi Kleen
---
include/linux/moduleparam.h |6 ++
kernel/params.c | 35 +++
2 files changed, 41
From: Andi Kleen
Very straight forward. Use the non-adaptive elision wrappers for
bit spinlocks. This is useful because they perform very poorly
under contention.
The functions are a bit on the big side for inlining now, but
I kept them inline for now.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
Add generic noop macros (act like transaction aborted) for RTM.
The main use case is an occasional _xtest() added to generic
code, without needing ifdefs. On x86+RTM this will use
real TSX instructions.
Signed-off-by: Andi Kleen
---
include/linux/rtm.h | 15 +++
From: Andi Kleen
Add elision adaptation state to the rwlocks and use the generic
adaptation wrapper. This unfortunately increases the size of the rwlock:
6 bytes for NR_CPUS>=2048, otherwise by 2 bytes.
Signed-off-by: Andi Kleen
---
arch/x86/include/asm/rwlock.h | 30
From: Andi Kleen
For tuning the adaptive locking algorithms it's useful to trace adaptive
elision skipping. Add a trace point for this case.
Used in followon patches
Signed-off-by: Andi Kleen
---
include/trace/events/elision.h | 31 +++
1 files changed, 31
From: Andi Kleen
Add basic TSX lock elision infrastructure. This is implemented
using RTM to give more flexibility. A lock is elided by
wrapping an elision check around it: when the lock is free
try to speculatively execute the lock region and fall back
if that fails.
Provide some generic
This patchkit implements TSX lock elision for the kernel locks.
Lock elision uses hardware transactional memory to execute
locks in parallel.
This is just a RFC at this point, so that people can comment
on the code. Please send your feedback.
Code is against v3.9-rc3
Also available from:
From: Andi Kleen
For lock elision we (mostly) use generic elide() macros that
can be added to the lock code with minimal intrusion. Add a generic
version that does nothing and is used when RTM is not available.
Signed-off-by: Andi Kleen
---
include/linux/elide.h | 18 ++
1
From: Andi Kleen
Add generic macros to disable transactions per process.
Without TSX (or other HTM) support this is a noop.
An RTM enabled x86 kernel uses its own version.
Signed-off-by: Andi Kleen
---
include/linux/thread_info.h |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
From: Andi Kleen
May be removed later, but useful for basic sanity checking.
Signed-off-by: Andi Kleen
---
arch/x86/kernel/Makefile |2 ++
arch/x86/kernel/rtm-test.c | 22 ++
2 files changed, 24 insertions(+), 0 deletions(-)
create mode 100644
From: Andi Kleen
Add support for arch_spin_unlock_flags/irq
Only done for the paravirt case, non paravirt just uses the wrappers
in the upper level code.
Cc: jer...@goop.org
Signed-off-by: Andi Kleen
---
arch/x86/include/asm/paravirt.h | 13 +
From: Andi Kleen
The TSX RTM lock elision code needs to distinguish unlocks that reenable
interrupts from others. Add arch_read/write_unlock_irq/flags for rwlocks
similar to the ones for spinlocks. This is opt in by the architecture.
Signed-off-by: Andi Kleen
---
include/linux/rwlock.h
From: Andi Kleen
This is mainly useful for simple statistic counters.
Essentially read-only, writing only clears.
Cc: ru...@rustcorp.co.au
Signed-off-by: Andi Kleen
---
include/linux/moduleparam.h |4
kernel/params.c | 28
2 files changed,
From: Andi Kleen
Elided locks do not allow writing to the lock cache line in the fast
path. This would abort the transaction. They do not actually need
an owner in the speculative fast path, because they do not actually
take the lock. But in the slow path when the lock is taken
they actually
From: Andi Kleen
Inside a elided mutex we cannot tell if the mutex is really locked
or not. Aborting it he safe answer.
Callers who frequently abort (e.g. BUG_ONs) need to be fixed
separately.
Noop without RTM.
Signed-off-by: Andi Kleen
---
include/linux/mutex.h |2 ++
1 files changed,
From: Andi Kleen
Add the standard elide wrapper macros to rwsems to enable
lock elision for rwsems. Main target is mmap_sem.
Signed-off-by: Andi Kleen
---
arch/x86/include/asm/rwsem.h | 23 ++-
arch/x86/kernel/rtm-locks.c |3 +++
include/linux/rwsem.h|3
From: Andi Kleen
lock_is_locked aborts with lock elision. Some code does a lot of lock asserts,
which causes a lot of aborts. Add a _xtest() here so that the checking is only
done when the lock is not elided. This always happens occasionally due to
fallbacks, so there is still enough assert
From: Andi Kleen
Convert the rwsem elision to be adaptive. This requires adding
4/8 bytes to the rwsem for the adaptation state. The algorithm
is the same as for other adaptive lock types. The elision
configuration is split for readers and writers.
Signed-off-by: Andi Kleen
---
From: Andi Kleen
We use the generic elision macros and the mutex hook infrastructure
added earlier. With that attempt to lock elide mutexes using
the elide() macros and the usual elision wrapping pattern.
Lock elision does not allow modifying the lock itself, so it's not
possible to set the
From: Andi Kleen
Add simple implementations of arch_spin_unlock_flags/irq to the Xen
paravirt spinlock code.
Cc: jer...@goop.org
Signed-off-by: Andi Kleen
---
arch/x86/xen/spinlock.c | 17 +
1 files changed, 17 insertions(+), 0 deletions(-)
diff --git
From: Andi Kleen
Document the tunables and the statistics in Documentation/lock-elision.txt
Signed-off-by: Andi Kleen
---
Documentation/lock-elision.txt | 94
1 files changed, 94 insertions(+), 0 deletions(-)
create mode 100644
From: Andi Kleen
Add adaptation support for ticket spinlocks. Each spinlock keeps a skip count
on how often to skip elision. This is controlled by the abort rate.
The actual adaptation algorithm is generic and shared with other lock types.
This avoids us having to tune each spinlock individually
From: Andi Kleen
The TSX RTM lock elision code needs to distinguish spin unlocks that reenable
interrupts from others. Currently this is hidden in the higher level spinlock
code. Add support for calling an architecture specific
arch_spin_unlock_flags/irq
if available.
Signed-off-by: Andi Kleen
Just syntactic overhead. We should probably discuss it among ourselves first
though.
Tim Chen wrote:
>On Fri, 2013-03-22 at 17:21 -0700, H. Peter Anvin wrote:
>> I really, really hate these macros... Not sure they are worth the
>extra noise.
>>
>
>I can do without the macro and I'll remove
On Fri, 2013-03-22 at 22:56 +0100, Thomas Gleixner wrote:
> This is the last release for the 3.6 kernel from my side. Steven is
> going to take over and maintain it until 3.8-rt is stabilized.
>
I have created a new branch in the stable-rt git repo called v3.6-rt.
The first tag for that branch
On Fri, 2013-03-22 at 17:21 -0700, H. Peter Anvin wrote:
> I really, really hate these macros... Not sure they are worth the extra noise.
>
I can do without the macro and I'll remove it.
Wonder the reason that such macro should be avoided?
Tim
--
To unsubscribe from this list: send the line
On Fri, Mar 22, 2013 at 09:52:58PM +0100, Wim Van Sebroeck wrote:
> Hi Guenter,
>
> > Convert to watchdog infrastructure, cleanup, add support for additional
> > chips, and merge with W83697HF and W83697UG watchdog drivers.
> >
> > Tested with W83627UHG, NCT6775, NCT6776. Additional test
c13085e519e8984fede41fa3d6a5502523b10996 is the first bad commit
commit c13085e519e8984fede41fa3d6a5502523b10996
Author: Bob Moore
Date: Fri Mar 8 09:19:38 2013 +
ACPICA: Resource Mgr: Prevent infinite loops in resource walks
Add checks for zero-length resource descriptors in all
On Fri, Mar 22, 2013 at 3:05 PM, Zach Brown wrote:
> On Fri, Mar 22, 2013 at 08:33:19PM +0200, Octavian Purdila wrote:
>> When using a large number of threads performing AIO operations the
>> IOCTX list may get a significant number of entries which will cause
>> significant overhead. For example,
I really, really hate these macros... Not sure they are worth the extra noise.
Tim Chen wrote:
>Macro to facilitate checking the availability of the AVX2 feature.
>
>Signed-off-by: Tim Chen
>---
> arch/x86/include/asm/cpufeature.h | 1 +
> 1 file changed, 1 insertion(+)
>
>diff --git
On Fri, Mar 22 2013, lars.ellenb...@linbit.com wrote:
> From: Lars Ellenberg
>
> Signed-off-by: Philipp Reisner
> Signed-off-by: Lars Ellenberg
> ---
> drivers/block/drbd/drbd_int.h | 13 +
> drivers/block/drbd/drbd_main.c | 26 +-
>
On Friday, March 22, 2013 10:51:05 AM dirk.brande...@gmail.com wrote:
> From: Dirk Brandewie
>
> Use the correct pstate value to calculate the effective frequency.
>
> https://bugzilla.redhat.com/show_bug.cgi?id=923942
> Reported-by: Satish Balay
>
> Signed-off-by: Dirk Brandewie
Well,
On Friday, March 22, 2013 11:06:47 AM Dave Jones wrote:
> On Fri, Mar 22, 2013 at 01:40:49AM +0100, Rafael J. Wysocki wrote:
> > On Thursday, March 21, 2013 01:08:03 AM Rafael J. Wysocki wrote:
> > > On Wednesday, March 20, 2013 11:28:49 AM Dirk Brandewie wrote:
> > > > On 03/20/2013 11:28 AM,
On Fri, Mar 22, 2013 at 3:27 PM, Wim Van Sebroeck wrote:
>
> Please pull from 'master' branch of
> git://www.linux-watchdog.org/linux-watchdog.git
That host seems to be a little sick right now. I'm not getting
anything from it, just a very long wait followed by "Connection reset
by
On Fri, Mar 22, 2013 at 7:29 PM, Benjamin Herrenschmidt
wrote:
> On Fri, 2013-03-22 at 13:03 -0500, Nathan Fontenot wrote:
>> We don't ever free old property values, mainly I assume since we don't keep
>> reference counts and can't know when it is safe to do so. The problem I
>> am starting to
> > + /*
> > +* If sma->complex_count was set while we were spinning,
> > +* we may need to look at things we did not lock here.
> > +*/
> > + if (unlikely(sma->complex_count)) {
> > +
On 03/22/2013 07:01 PM, Michel Lespinasse wrote:
Sorry for the late reply; I've been swamped and am behind on my upstream mail.
On Wed, Mar 20, 2013 at 12:55 PM, Rik van Riel wrote:
+static inline int sem_lock(struct sem_array *sma, struct sembuf *sops,
+ int
On Fri, Mar 22, 2013 at 1:36 PM, Kent Overstreet wrote:
> On Fri, Mar 22, 2013 at 08:33:19PM +0200, Octavian Purdila wrote:
>> When using a large number of threads performing AIO operations the
>> IOCTX list may get a significant number of entries which will cause
>> significant overhead. For
On Fri, Mar 22, 2013 at 06:34:28PM -0400, Mike Snitzer wrote:
> On Fri, Mar 22 2013 at 4:11pm -0400,
> Darrick J. Wong wrote:
>
> > The new writethrough strategy for dm-cache issues a bio to the origin
> > device,
> > remaps the bio to the cache device, and issues the bio to the cache device.
On Thu, 2013-03-21 at 20:36 -0700, Michel Lespinasse wrote:
> On Mon, Mar 18, 2013 at 4:21 PM, Davidlohr Bueso
> wrote:
> > When checking the rbtree, account for more properties:
> >
> >- Both children of a red node are black.
> >- The tree has at least 2**bh(v)-1 internal nodes.
>
> >
On Thu, 2013-03-21 at 20:29 -0700, Michel Lespinasse wrote:
> On Thu, Mar 21, 2013 at 7:51 PM, Davidlohr Bueso
> wrote:
> > On Tue, 2013-03-19 at 11:54 -0600, Shuah Khan wrote:
> >> On Tue, Mar 19, 2013 at 11:14 AM, Davidlohr Bueso
> >> wrote:
> >> > On Tue, 2013-03-19 at 10:29 -0600, Shuah
Sorry for the late reply; I've been swamped and am behind on my upstream mail.
On Wed, Mar 20, 2013 at 12:55 PM, Rik van Riel wrote:
> +static inline int sem_lock(struct sem_array *sma, struct sembuf *sops,
> + int nsops)
> +{
> + int locknum;
> + if
Linus Torvalds writes:
> Regardless, the patch seems to be the right thing to do. It actually
> simplifies /proc, seems to fix the problem for Dave, and is small and
> should be trivial to backport. I've committed it and marked it for
> stable. Let's hope there won't be any nasty surprises, but
Arve Hjønnevåg wrote:
> On Fri, Mar 22, 2013 at 3:31 AM, Eric Wong wrote:
> > Arve Hjønnevåg wrote:
> >> On Thu, Mar 21, 2013 at 8:24 PM, Eric Wong wrote:
> >> >
> >> > With EPOLLET and improper usage (not hitting EAGAIN), the event now
> >> > has a larger window to be lost (as mentioned in my
Each iommu window can have access permissions associated with it. Extended the
window_enable API to incorporate window access permissions.
In case of PAMU each window can have its specific set of permissions.
Signed-off-by: Varun Sethi
---
- no change in v10.
drivers/iommu/iommu.c |5
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
This is required in case of PAMU, as it can support a window size of up
to 64G (even on 32bit).
Signed-off-by: Varun Sethi
---
- no change in v10.
drivers/iommu/amd_iommu.c |2 +-
drivers/iommu/exynos-iommu.c |2 +-
drivers/iommu/intel-iommu.c|2 +-
drivers/iommu/iommu.c
Add an iommu domain pointer to device (powerpc) archdata. Devices
are attached to iommu domains and this pointer provides a mechanism
to correlate between a device and the associated iommu domain. This
field is set when a device is attached to a domain.
Signed-off-by: Varun Sethi
---
- no
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
Hi Lars,
On Thu, Mar 21, 2013 at 07:32:52PM +0100, Lars-Peter Clausen wrote:
> On 03/21/2013 12:56 AM, Sören Brinkmann wrote:
> > Hi,
> >
> > I spent some time working on this and incorporating feedback. Here's an
> > updated proposal for a clock controller for Zynq:
> >
> > Required
In the end it may not be caused by bluetooth, but by ppp.
Found bug reports on ubuntu indicating that 3.8.x panic on ppp disconnection.
Unfortunately, I cannot try without bluetooth with my configuration.
(when wired, phone does not use ppp, but appears as a wired network interface).
Sergio
--
On Fri, Mar 22 2013 at 4:11pm -0400,
Darrick J. Wong wrote:
> The new writethrough strategy for dm-cache issues a bio to the origin device,
> remaps the bio to the cache device, and issues the bio to the cache device.
> However, the block layer modifies bi_sector and bi_size, so we need to
>
On Wed, Jan 09, 2013 at 03:36:44AM +0100, Roland Eggner wrote:
> On 2013-01-08 Tuesday at 15:09 -0800 Marc MERLIN wrote:
> > In its infinite wisdom, lenovo has removed the sysrq key on the latest
> > thinkpads, and replaced it with a stupid ALT+FN+S key combination, which
> > doesn't really work
Il 20/02/2013 17:12, Paolo Bonzini ha scritto:
> Il 06/02/2013 16:15, Paolo Bonzini ha scritto:
>> This series regards the whitelist that is used for the SG_IO ioctl. This
>> whitelist has three problems:
>>
>> * the bitmap of allowed commands is designed for MMC devices (roughly,
>> "play/burn
The mm-of-the-moment snapshot 2013-03-22-15-21 has been uploaded to
http://www.ozlabs.org/~akpm/mmotm/
mmotm-readme.txt says
README for mm-of-the-moment:
http://www.ozlabs.org/~akpm/mmotm/
This is a snapshot of my -mm patch queue. Uploaded at random hopefully
more than once a week.
You
On Fri, 22 Mar 2013, Mark Brown wrote:
> On Fri, Mar 22, 2013 at 05:15:48PM +0100, Guennadi Liakhovetski wrote:
> > AS3711 regulator OF support only evaluates standard regulator DT
> > properties.
>
> It looks like this has no dependencies on the MFD patch, is that
> correct?
Yes, that's
Hi Linus,
Please pull from 'master' branch of
git://www.linux-watchdog.org/linux-watchdog.git
It will fix a boot issues and correct the AcpiMmioSel bitmask in the
sp5100_tco watchdog device driver.
This will update the following files:
sp5100_tco.c | 126
On Fri, Mar 22, 2013 at 12:24 PM, Eric Wong wrote:
...
> Perhaps just using epitem->ws and removing ep->ws can work.
>
> I think the following change to keep wakeup_source in sync with
> epi->state is sufficient to prevent suspend.
>
> But I'm not familiar with suspend. Is it possible to suspend
Linus,
please pull the updates for the 3.9 kernel. There is one bugfix for the
tegra driver. There are two updates regarding email addresses and
MAINTAINERS which I like to have up-to-date so people can be reached
immediately. While we are here, there is on PCI_ID addition.
Thanks,
Wolfram
On Fri, Mar 22, 2013 at 3:31 AM, Eric Wong wrote:
> Arve Hjønnevåg wrote:
>> On Thu, Mar 21, 2013 at 8:24 PM, Eric Wong wrote:
>> >
>> > With EPOLLET and improper usage (not hitting EAGAIN), the event now
>> > has a larger window to be lost (as mentioned in my changelog).
>> >
>>
>> What about
On Fri, Mar 22, 2013 at 02:54:48PM -0700, Andrew Morton wrote:
>
> poke. Nothing got applied. I'll drop
> kmsg-honor-dmesg_restrict-sysctl-on-dev-kmsg.patch, see if that has any
> effect ;)
Oh dear.
Eric, were you going to cleanup your suggestion and send it out?
josh
--
To unsubscribe from
Dear RT Folks,
I'm pleased to announce the 3.8.4-rt1 release.
Again the credit for the heavy lifting goes to Sebastian Siewior, AKA
bigeasy, who took up most of the work to get this out. He's on my
companies engineering team and I hope you trust him as much as I do.
Known issues:
- SLUB
On Fri, Mar 22, 2013 at 11:39:20AM -0400, Ben Collins wrote:
>
> If your company had hardware going to production, you'd want it supported in
> mainline too, I suspect.
And if companies told their hardware partners that they will drop use
of their hardware in future products unless they get
On Fri, Mar 22, 2013 at 08:33:19PM +0200, Octavian Purdila wrote:
> When using a large number of threads performing AIO operations the
> IOCTX list may get a significant number of entries which will cause
> significant overhead. For example, when running this fio script:
Indeed. But you also
1 - 100 of 1286 matches
Mail list logo
