On Fri, 27 Jul 2012 22:14:59 +0200, Jean Delvare wrote:
> Code not tested yet, my test machine is currently used for a different
> task that cannot be interrupted.
Tested now, works fine.
--
Jean Delvare
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Fri, Jul 27, 2012 at 12:01:16PM -0700, Greg Kroah-Hartman wrote:
> On Fri, Jul 27, 2012 at 04:23:47PM +0100, Mel Gorman wrote:
> > > > --- a/mm/slub.c
> > > > +++ b/mm/slub.c
> > > > @@ -1457,6 +1457,7 @@ static struct page *get_any_partial(stru
> > > > struct zone *zone;
> > > >
>> Hi James.
>> I have a question.
>> If we found the method to notify nfs when unplugging device,
>
Hi James.
> What's that?
I need to check more...
>
>> Can nfsd
>> flush only entry of usb mount ?
>
> Hm, I don't think there's anything that does that now. But I think if
> you look it up and
On Fri, 27 Jul 2012 14:45:18 -0700, you wrote:
>On 07/27/2012 12:08 PM, Bill Davidsen wrote:
>> Have you set the io scheduler to deadline on all members of the array?
>> That's kind of "job one" on older kernels.
>>
>
>I have not, thanks for the tip, I'll look into that now.
Plus I disable the
On Fri, 2012-07-27 at 22:09 -0500, sheng qiu wrote:
> Hi all,
>
> i am comparing network throughput performance under bare-metal case
> with that running VM with assigned-device (assigned NIC). i have two
> physical machines (each has a 10Gbit NIC), one is used as remote
> server (run netserver)
This tree also seems to have ARM stuff in it?
--
Matthew Garrett | mj...@srcf.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read
So after not getting too much positive feedback on my last
attempt at trying to use a non-shrinker method for managing
& purging volatile ranges, I decided I'd go ahead and try
to implement something along Minchan's ERECLAIM LRU list
idea.
Again this patchset has two parts:
The first 3 patches
This patch enables FALLOC_FL_MARK_VOLATILE/UNMARK_VOLATILE
functionality for tmpfs making use of the volatile range
management code.
Conceptually, FALLOC_FL_MARK_VOLATILE is like a delayed
FALLOC_FL_PUNCH_HOLE. This allows applications that have
data caches that can be re-created to tell the
Rework of my first pass attempt at getting ashmem to utilize
the volatile range code, now using the fallocate interface.
In this implementaiton GET_PIN_STATUS is unimplemented, due to
the fact that adding a ISVOLATILE check wasn't considered
terribly useful in earlier reviews. It would be trivial
This changes the earlier shrinker based volatile range
management over to using the LRU_VOLATILE list in mm core.
Again, this is likely has performance issues, as well as
other problems I'm not aware of, so I'd greatly appreciate
any additional feedback or suggestions.
CC: Andrew Morton
CC:
In an attempt to push the volatile range managment even
deeper into the VM code, this is my first attempt at
implementing Minchan's idea of a LRU_VOLATILE list in
the mm core.
This list sits along side the LRU_ACTIVE_ANON, _INACTIVE_ANON,
_ACTIVE_FILE, _INACTIVE_FILE and _UNEVICTABLE lru lists.
This patch provides the volatile range management code
that filesystems can utilize when implementing
FALLOC_FL_MARK_VOLATILE.
It tracks a collection of page ranges against a mapping
stored in an interval-tree. This code handles coalescing
overlapping and adjacent ranges, as well as splitting
fault-injection-add-tool-to-run-command-with-failslab-or-fail_page_alloc.patch
in -mm tree adds tools/testing/fault-injection/failcmd.sh to make it
easier to inject slab/page allocation failures by fault injection.
failcmd.sh prints the following warning when running with arguments
for command.
On Fri, 2012-07-27 at 22:09 -0500, sheng qiu wrote:
> Hi all,
>
> i am comparing network throughput performance under bare-metal case
> with that running VM with assigned-device (assigned NIC). i have two
> physical machines (each has a 10Gbit NIC), one is used as remote
> server (run netserver)
On Fri, Jul 27, 2012 at 6:15 PM, Colin Cross wrote:
> On Fri, Jul 27, 2012 at 4:38 PM, Russell King - ARM Linux
> wrote:
>> On Sat, Jul 28, 2012 at 01:32:50AM +0200, Linus Walleij wrote:
>>> On Wed, Jul 25, 2012 at 4:49 AM, Colin Cross wrote:
>>>
>>> > Many clocks that are used to provide
The following changes since commit 6887a4131da3adaab011613776d865f4bcfb5678:
Linux 3.5-rc5 (2012-06-30 16:08:57 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/ext4_for_linus
for you to fetch changes up to
Hi all,
i am comparing network throughput performance under bare-metal case
with that running VM with assigned-device (assigned NIC). i have two
physical machines (each has a 10Gbit NIC), one is used as remote
server (run netserver) and the other is used as the target tested one
(run netperf with
On 07/27/2012 07:39 PM, Theodore Ts'o wrote:
Ok, I'll add this patch to the random tree. I've modified the commit
message a bit since the speed advertisement of RDRAND is rather
pointless --- processes aren't generating session keys or long term
keys at a high rate, and programs can't count on
Ok, I'll add this patch to the random tree. I've modified the commit
message a bit since the speed advertisement of RDRAND is rather
pointless --- processes aren't generating session keys or long term
keys at a high rate, and programs can't count on /dev/random being
super fast and having
On 07/27/2012 08:33 AM, Rusty Russell wrote:
On Fri, 13 Jul 2012 16:38:51 +0800, Asias He wrote:
Add 'virtio_blk.use_bio=1' to kernel cmdline or 'modprobe virtio_blk
use_bio=1' to enable ->make_request_fn() based I/O path.
This patch conflicts with Paolo's Bonzini's 'virtio-blk: allow
On Fri, Jul 27, 2012 at 5:44 PM, Michel Lespinasse wrote:
> On Fri, Jul 27, 2012 at 1:02 PM, Peter Zijlstra wrote:
>> As it stands rb_erase() isn't inlined and its rather big,
>> why would you want to inline it for augmented callers?
>
> Just as the non-augmented rb_erase() is generated (as a
Add a helper to map a bio to a scatterlist, modelled after
blk_rq_map_sg.
This helper is useful for any driver that wants to create
a scatterlist from its ->make_request_fn method.
Changes in v2:
- Use __blk_segment_map_sg to avoid duplicated code
- Add cocbook style function comment
Cc: Jens
This patch introduces bio-based IO path for virtio-blk.
Compared to request-based IO path, bio-based IO path uses driver
provided ->make_request_fn() method to bypasses the IO scheduler. It
handles the bio to device directly without allocating a request in block
layer. This reduces the IO path in
Split the mapping code in blk_rq_map_sg() to a helper
__blk_segment_map_sg(), so that other mapping function, e.g.
blk_bio_map_sg(), can share the code.
Cc: Jens Axboe
Cc: Tejun Heo
Cc: Shaohua Li
Cc: Rusty Russell
Cc: linux-kernel@vger.kernel.org
Suggested-by: Tejun Heo
Suggested-by: Jens
Hi, Jens & Rusty
This version is rebased against linux-next which resolves the conflict with
Paolo Bonzini's 'virtio-blk: allow toggling host cache between writeback and
writethrough' patch.
Patch 1/3 and 2/3 applies on linus's master as well. Since Rusty will pick up
patch 3/3 so the changes to
This will fix build errors:
block/blk-cgroup.c:609:2: error: unknown type name 'atomic64_t'
block/blk-cgroup.c:609:2: error: implicit declaration of function
'ATOMIC64_INIT' [-Werror=implicit-function-declaration]
Signed-off-by: Fengguang Wu
---
arch/xtensa/Kconfig |1 +
1 file changed, 1
On Fri, Jul 27, 2012 at 6:26 PM, Anton Vorontsov wrote:
> But if you say that it wasn't the case, and no one thought about the
> reducing the debugger in the "evil" way, so be it, I trust you. But I
> still don't trust the phone vendors. They showed their bad attitude
> in many ways towards
On 07/27/2012 06:26 PM, Anton Vorontsov wrote:
On Fri, Jul 27, 2012 at 12:30:49PM -0700, Colin Cross wrote:
The are two use-cases for the mode, one is evil, but another is quite
legitimate.
The evil use case is used by some (ahem) phone manufaturers that want
to have a debuging facilities on a
Hi Yann,
On Sat, Jul 28, 2012 at 02:02:34AM +0200, Yann Cantin wrote:
>
> Signed-off-by: Yann Cantin
> ---
> drivers/input/misc/Kconfig | 21 +
> drivers/input/misc/Makefile |1 +
> drivers/input/misc/ebeam.c | 895
> +++
> 3 files changed, 917
On Fri, Jul 27, 2012 at 9:37 AM, Karel Zak wrote:
>
> The util-linux release v2.22-rc1 is available at
>
>ftp://ftp.kernel.org/pub/linux/utils/util-linux/v2.22/
>
> Feedback and bug reports, as always, are welcomed.
I'm still getting an empty /usr/share/man/ru/man1/, don't know if I'm
doing
On Fri, Jul 27, 2012 at 12:30:49PM -0700, Colin Cross wrote:
> > The are two use-cases for the mode, one is evil, but another is quite
> > legitimate.
> >
> > The evil use case is used by some (ahem) phone manufaturers that want
> > to have a debuging facilities on a production device, but still
On Fri, Jul 27, 2012 at 04:55:07PM -0700, Tejun Heo wrote:
> Convert delayed_work users doing [__]cancel_delayed_work() +
> queue_delayed_work() to mod_delayed_work().
>
> Most conversions are straight-forward. Ones worth mentioning are,
>
> * drivers/edac/edac_mc.c: edac_mc_workq_setup()
On Fri, Jul 27, 2012 at 4:38 PM, Russell King - ARM Linux
wrote:
> On Sat, Jul 28, 2012 at 01:32:50AM +0200, Linus Walleij wrote:
>> On Wed, Jul 25, 2012 at 4:49 AM, Colin Cross wrote:
>>
>> > Many clocks that are used to provide sched_clock will reset during
>> > suspend. If read_sched_clock
On Fri, 27 Jul 2012, Tejun Heo wrote:
> Convert delayed_work users doing [__]cancel_delayed_work() +
> queue_delayed_work() to mod_delayed_work().
>
> Most conversions are straight-forward. Ones worth mentioning are,
>
> * drivers/edac/edac_mc.c: edac_mc_workq_setup() converted to always
>
On Sat, Jul 28, 2012 at 12:53:11AM +0200, Rafael J. Wysocki wrote:
> Hi Paul,
>
> Unfortunately, your commit
>
> commit ca5481c68e9fbcea62bb3c78ae6cccf99ca8fb73
> Author: Paul Mundt
> Date: Tue Jul 10 12:08:14 2012 +0900
>
> sh: pfc: Rudimentary pinctrl-backed GPIO support.
>
> breaks
>> + /* err can be positive if it came from the TPM itself,
>> + * so return a negative value here instead. */
>> + err = -EFAULT;
>
> -EFAULT is definitely wrong (that means a bad pointer was passed), you
> can use -EIO instead.
>
>
On Fri, Jul 27, 2012 at 1:02 PM, Peter Zijlstra wrote:
>On Fri, 2012-07-20 at 05:31 -0700, Michel Lespinasse wrote:
>> --- a/lib/rbtree_test.c
>> +++ b/lib/rbtree_test.c
>> @@ -1,5 +1,6 @@
>> #include
>> #include
>> +#include
>This confuses me.. either its internal to the rb-tree
On Sat, Jul 28, 2012 at 12:07:04AM +0200, Rafael J. Wysocki wrote:
>
> First off, drivers/sh/pfc/pinctrl.c doesn't build after commit
> 5d589b0 (pinctrl: remove pinctrl_remove_gpio_range), because
> sh_pfc_pinctrl_remove() uses the function that has been removed by
> that commit. Fix this by
Signed-off-by: Yann Cantin
---
drivers/hid/hid-core.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index 500844f..1c03586 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1908,6 +1908,9 @@ static const struct
Signed-off-by: Yann Cantin
---
drivers/input/misc/Kconfig | 21 +
drivers/input/misc/Makefile |1 +
drivers/input/misc/ebeam.c | 895 +++
3 files changed, 917 insertions(+)
create mode 100644 drivers/input/misc/ebeam.c
diff --git
Signed-off-by: Yann Cantin
---
drivers/hid/hid-ids.h |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index 41c34f2..8cd4b8e 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -271,6 +271,9 @@
#define
Hi,
This patchset is a test-drive for a new USB input driver for eBeam
devices.
Currently, only the Luidia eBeam classic projection model is supported
(usb id known).
Patch 1 and 2 are here to let the ebeam driver be choose to handle
the device instead of the generic-usb hid one (totally
delayed_work has been annoyingly missing the mechanism to modify timer
of a pending delayed_work - ie. mod_timer() counterpart. delayed_work
users have been working around this using several methods - using an
explicit timer + work item, messing directly with delayed_work->timer,
and canceling
All queueing functions return 1 on success, 0 if the work item was
already pending. Update them to return bool instead. This signifies
better that they don't return 0 / -errno.
This is cleanup and doesn't cause any functional difference.
While at it, fix comment opening for schedule_work_on().
Queueing functions have been using different methods to determine the
local CPU.
* queue_work() superflously uses get/put_cpu() to acquire and hold the
local CPU across queue_work_on().
* delayed_work_timer_fn() uses smp_processor_id().
* queue_delayed_work() calls queue_delayed_work_on()
If @delay is zero and the dealyed_work is idle, queue_delayed_work()
queues it for immediate execution; however, queue_delayed_work_on()
lacks this logic and always goes through timer regardless of @delay.
This patch moves 0 @delay handling logic from queue_delayed_work() to
WORK_STRUCT_PENDING is used to claim ownership of a work item and
process_one_work() releases it before starting execution. When
someone else grabs PENDING, all pre-release updates to the work item
should be visible and all updates made by the new owner should happen
afterwards.
Grabbing PENDING
Queueing operations use WORK_STRUCT_PENDING_BIT to synchronize access
to the target work item. They first try to claim the bit and proceed
with queueing only after that succeeds and there's a window between
PENDING being set and the actual queueing where the task can be
preempted.
There's also a
try_to_grab_pending() will be used by to-be-implemented
mod_delayed_work[_on](). Move try_to_grab_pending() and related
functions above queueing functions.
This patch only moves functions around.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 286
Low WORK_STRUCT_FLAG_BITS bits of work_struct->data contain
WORK_STRUCT_FLAG_* and flush color. If the work item is queued, the
rest point to the cpu_workqueue with WORK_STRUCT_CWQ set; otherwise,
WORK_STRUCT_CWQ is clear and the bits contain the last CPU number -
either a real CPU number or one
This is to prepare for mod_delayed_work[_on]() and doesn't cause any
functional difference.
Signed-off-by: Tejun Heo
---
kernel/workqueue.c | 74 ---
1 files changed, 41 insertions(+), 33 deletions(-)
diff --git a/kernel/workqueue.c
There can be two reasons try_to_grab_pending() can fail with -EAGAIN.
One is when someone else is queueing or deqeueing the work item. With
the previous patches, it is guaranteed that PENDING and queued state
will soon agree making it safe to busy-retry in this case.
The other is if multiple
__cancel_delayed_work() is different from cancel_delayed_work() in
that it uses del_timer() instead of del_timer_sync(). This adds
confusion to already complicated flush / cancel API and given that the
only thing delayed_work->timer does is queueing the work, the
difference between
Convert delayed_work users doing [__]cancel_delayed_work() +
queue_delayed_work() to mod_delayed_work().
Most conversions are straight-forward. Ones worth mentioning are,
* drivers/edac/edac_mc.c: edac_mc_workq_setup() converted to always
use mod_delayed_work() and cancel loop in
Workqueue was lacking a mechanism to modify the timeout of an already
pending delayed_work. delayed_work users have been working around
this using several methods - using an explicit timer + work item,
messing directly with delayed_work->timer, and canceling before
re-queueing, all of which are
* Move timer handling from __cancel_work_timer() to
try_to_grab_pending().
* Make try_to_grab_pending() use -EAGAIN instead of -1 for
busy-looping and drop the ret local variable.
* Add proper function comment to try_to_grab_pending().
This makes the code a bit easier to understand and will
delayed_work->timer.function is currently initialized during
queue_delayed_work_on(). Export delayed_work_timer_fn() and set
delayed_work timer function during delayed_work initialization
together with other fields.
This ensures the timer function is always valid on an initialized
delayed_work.
Currently, queue/schedule[_delayed]_work_on() are located below the
counterpart without the _on postifx even though the latter is usually
implemented using the former. Swap them.
This is cleanup and doesn't cause any functional difference.
Signed-off-by: Tejun Heo
---
On Sat, Jul 28, 2012 at 01:32:50AM +0200, Linus Walleij wrote:
> On Wed, Jul 25, 2012 at 4:49 AM, Colin Cross wrote:
>
> > Many clocks that are used to provide sched_clock will reset during
> > suspend. If read_sched_clock returns 0 after suspend, sched_clock will
> > appear to jump forward.
On Wed, Jul 25, 2012 at 4:49 AM, Colin Cross wrote:
> Many clocks that are used to provide sched_clock will reset during
> suspend. If read_sched_clock returns 0 after suspend, sched_clock will
> appear to jump forward. This patch resets cd.epoch_cyc to the current
> value of read_sched_clock
Hi Michael,
> Bus 002 Device 003: ID 0a5c:21f1 Broadcom Corp.
> Device Descriptor:
> bLength18
> bDescriptorType 1
> bcdUSB 2.00
> bDeviceClass 255 Vendor Specific Class
> bDeviceSubClass 1
> bDeviceProtocol 1
>
On Tue, Jul 24, 2012 at 8:50 AM, John Crispin wrote:
> Implement support for pinctrl on lantiq/falcon socs. The FALCON has 5 banks
> of up to 32 pins.
>
> Signed-off-by: John Crispin
> Signed-off-by: Thomas Langer
> Cc: Linus Walleij
> Cc: devicetree-disc...@lists.ozlabs.org
> Cc:
On Tue, Jul 24, 2012 at 8:50 AM, John Crispin wrote:
> Implement support for pinctrl on lantiq/xway socs. The IO core found on these
> socs has the registers for pinctrl, pinconf and gpio mixed up in the same
> register range. As the gpio_chip handling is only a few lines, the driver also
>
Acked-by: Sean MacLennan
Worked for me ;)
Cheers,
Sean
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On 7/27/12, Jiri Kosina wrote:
...
>
> So, what is the alternative?
>
> The only thing I know is that it works at least in basic mode (haven't
> tested performance at all).
The driver for your card is a closed source driver called 'megasr'.
Here is a link to the LSI download page for this
On Sat, Jul 21, 2012 at 10:37 AM, Devendra Naga
wrote:
> the allocated memory will be destroyed at the driver unload time,
> automatically if driver uses the devm_ functions, so no need of
> doing devm_kfree at the error path
>
> Signed-off-by: Devendra Naga
Applied.
Thanks!
Linus Walleij
--
On Fri, Jul 20, 2012 at 10:58 PM, Sean Paul wrote:
> Move gpc4 to the end of the automatically processed gpio controllers so
> we don't taint the automatic offset calculation.
>
> This bug caused all controllers coming after gpc4 to map to the
> incorrect address. The result is < 0 0 0 0> would
On Wed, Jul 18, 2012 at 11:20 AM, Peter Ujfalusi wrote:
> TWL6040 provides GPO lines to be used for controlling external devices.The
> number
> of lines different between versions: twl6040 have 3 GPO while TWL6041 have 1.
>
> Signed-off-by: Sergio Aguirre
> Signed-off-by: Peter Ujfalusi
This
On Wed, Jul 18, 2012 at 11:20 AM, Peter Ujfalusi wrote:
I think you need to CC DT bindings to devicetree-discuss.
> diff --git a/Documentation/devicetree/bindings/mfd/twl6040.txt
> b/Documentation/devicetree/bindings/mfd/twl6040.txt
> index c855240..2a3d55c 100644
> ---
Hi Paul,
Unfortunately, your commit
commit ca5481c68e9fbcea62bb3c78ae6cccf99ca8fb73
Author: Paul Mundt
Date: Tue Jul 10 12:08:14 2012 +0900
sh: pfc: Rudimentary pinctrl-backed GPIO support.
breaks system suspend on the Mackerel board (.config attached). The system
simply doesn't
On Wed, Jul 18, 2012 at 11:20 AM, Peter Ujfalusi wrote:
> #define TWL6040_GPO1 0x01
> #define TWL6040_GPO2 0x02
> -#define TWL6040_GPO3 0x03
> +#define TWL6040_GPO3 0x04
Maybe a stupid question but does these register
From: Len Brown
The APM idle feature to call into the BIOS
is known to break some machines, and it has dubious benefit
on the (decades old) machines it doesn't break.
After this patch, systems running in APM mode will
simply run default_idle() and HALT, rather than calling
into the BIOS from
On Wed, Jul 18, 2012 at 11:20 AM, Peter Ujfalusi wrote:
> Linus, Grant, Samuel: Would it be possible to queue this series via the MFD
> tree
> to avoid merge issues? It applies cleanly on top of gpio-next I believe it
> will
> not cause problems via MFD.
Sure, as soon as you have mine or
From: Len Brown
Remove warning that perplex users about removal of CONFIG_APM_CPU_IDLE in 2012.
This allows applying the original removal patch cleanly.
In retrospect, adding this warning was a mistake.
We should have shipped the removal patch 16 months ago.
cc: x...@kernel.org
cc: Jiri Kosina
From: Len Brown
default_idle() was public and exported to modules
for the benefit of APM. But APM no longer touches
default_idle(), so default_idle() can now be private.
Cc: x...@kernel.org
Signed-off-by: Len Brown
---
arch/x86/include/asm/processor.h | 1 -
arch/x86/kernel/process.c
The 1st three patches in this series are specific to x86.
With an ack from the x86 crew (the main patch still has Ingo's ack
from 16 months ago) I think they could be 3.6-rc1 cleanup candidates.
The 4th patch is enabled by the first 3 -- removing pm_idle() from pm.h
touches 10 architectures.
On Sat, Jul 28, 2012 at 12:23:05AM +0200, Linus Walleij wrote:
> On Tue, Jul 24, 2012 at 11:16 AM, Bedia, Vaibhav wrote:
>
> >> > A connecting theme is that of being avle to flag clock sources as
> >> > sched_clock providers. If all clocksources were tagged with
> >> > rating, and only
On Thu, Jul 26, 2012 at 10:58 PM, Linus Torvalds
wrote:
> On Wed, Jul 25, 2012 at 3:48 PM, Linus Walleij
> wrote:
>>
>> in Grants absence, these are my queued and -next-tested changes
>> for v3.6, please pull them in. Grants "merge" branch prior to his
>> absence was merged in as a base for
On 06/13/2012 01:43 AM, Johannes Berg wrote:
> From: Johannes Berg
>
> Prior to
> commit 4266129964b8238526936d723de65b419d8069c6
> Author: Mauro Carvalho Chehab
> Date: Tue May 31 16:27:44 2011 -0300
>
> [media] DocBook: Move all media docbook stuff into its own directory
>
> it was
On Fri, 2012-07-27 at 12:03 +0900, Yasuaki Ishimatsu wrote:
> Even if a device has _SUN method, there is no way to know the slot unique-ID.
> Thus the patch creates "sun" file in sysfs so that we can recognize it.
Hi Yasuaki,
Thanks for the update. This version looks good to me.
Did you forget
Hello
Get this on first write made ( by deliver sending mail to inform of the
restart of services )
Home partition (the one receiving the mail) is based on ocfs2 created
from drbd block device in primary/primary mode
These drbd devices are based on lvm.
system is running linux-3.5.0, identical
On Tue, Jul 24, 2012 at 11:16 AM, Bedia, Vaibhav wrote:
>> > A connecting theme is that of being avle to flag clock sources as
>> > sched_clock providers. If all clocksources were tagged with
>> > rating, and only clocksources were used for sched_clock(), the
>> > kernel could select the
On Fri, 2012-07-27 at 16:58 -0500, Kumar Gala wrote:
> On Jul 20, 2012, at 7:47 AM, Zhao Chenhui wrote:
>
> > During suspend, all interrupts including IPI will be disabled. In this case,
> > the suspend process will hang in SMP. To prevent this, pass the flag
> > IRQF_NO_SUSPEND when requesting
On 07/27/2012 01:30 PM, Kent Yoder wrote:
> +
> + do {
> + tpm_cmd.header.in = tpm_getrandom_header;
> + tpm_cmd.params.getrandom_in.num_bytes = cpu_to_be32(num_bytes);
> +
> + err = transmit_cmd(chip, _cmd,
> +
First off, drivers/sh/pfc/pinctrl.c doesn't build after commit
5d589b0 (pinctrl: remove pinctrl_remove_gpio_range), because
sh_pfc_pinctrl_remove() uses the function that has been removed by
that commit. Fix this by removing the pinctrl_remove_gpio_range()
call, which is not necessary any more,
On Jul 20, 2012, at 7:47 AM, Zhao Chenhui wrote:
> During suspend, all interrupts including IPI will be disabled. In this case,
> the suspend process will hang in SMP. To prevent this, pass the flag
> IRQF_NO_SUSPEND when requesting IPI irq.
>
> Signed-off-by: Zhao Chenhui
> Signed-off-by: Li
On Fri, Jul 27, 2012 at 1:04 PM, Peter Zijlstra wrote:
> On Fri, 2012-07-20 at 05:31 -0700, Michel Lespinasse wrote:
>> +static void augment_rotate(struct rb_node *rb_old, struct rb_node *rb_new)
>> +{
>> + struct test_node *old = rb_entry(rb_old, struct test_node, rb);
>> + struct
On Wed, Jul 25, 2012 at 04:55:45PM +0400, Stanislav Kinsbursky wrote:
> Bruce, I feel this patch set is ready for inclusion.
>
> v2:
> 1) Rebase on Bruce's "for-3.6" branch.
>
> This patch set makes grace period and hosts reclaiming network namespace
> aware.
On a quick skim--yes, that looks
On Wed, Jul 25, 2012 at 04:56:58PM +0400, Stanislav Kinsbursky wrote:
> Signed-off-by: Stanislav Kinsbursky
> ---
> fs/nfsd/netns.h |2 ++
> fs/nfsd/nfs4state.c | 32 +++-
> 2 files changed, 21 insertions(+), 13 deletions(-)
>
> diff --git a/fs/nfsd/netns.h
On 07/27/2012 12:08 PM, Bill Davidsen wrote:
Have you set the io scheduler to deadline on all members of the array?
That's kind of "job one" on older kernels.
I have not, thanks for the tip, I'll look into that now.
Thanks!
-- Kevin
--
To unsubscribe from this list: send the line
> From: Konrad Rzeszutek Wilk [mailto:kon...@darnok.org]
> Sent: Friday, July 27, 2012 3:00 PM
> Subject: Re: [PATCH 0/4] promote zcache from staging
>
> On Fri, Jul 27, 2012 at 12:21:50PM -0700, Dan Magenheimer wrote:
> > > From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> > > Subject:
On Fri, Jul 27, 2012 at 12:26 PM, Peter Zijlstra wrote:
> On Fri, 2012-07-20 at 05:31 -0700, Michel Lespinasse wrote:
>> --- a/lib/rbtree.c
>> +++ b/lib/rbtree.c
>> @@ -88,7 +88,8 @@ __rb_rotate_set_parents(struct rb_node *old, struct
>> rb_node *new,
>> root->rb_node = new;
>>
> > As I mentioned in a previous mail, backporting e70acc100 by itself is
> > not a good idea, but together with this patch it should be ok.
> >
> I think the patches should mature a bit in mainline. We can decide in a month
> or so if we want to backport them to previous releases.
Yes, sorry,
On Jul 26, 2012, at 10:14 PM, Li Yang wrote:
> On Fri, Jul 27, 2012 at 1:29 AM, Kumar Gala wrote:
>>
>> On Jul 26, 2012, at 9:02 AM, Li Yang wrote:
>>
>>> On Fri, Jul 20, 2012 at 8:42 PM, Zhao Chenhui
>>> wrote:
Changes for v8:
* Separated the cpu hotplug patch into three patches,
From: "John W. Linville"
Date: Fri, 27 Jul 2012 11:58:06 -0400
> These fixes are intended for the 3.6 stream.
>
> Hauke Mehrtens provides a pair of bcma fixes, one to fix a build
> regression on mips and another to correct a pair of missing iounmap
> calls.
>
> Thomas Huehn offers a
here is an untested prototype of what I was talking about. This should
handle multiple data chunks.
-vlad
---
include/net/sctp/command.h |1 +
net/sctp/sm_sideeffect.c | 22 ++
net/sctp/sm_statefuns.c| 18 ++
3 files changed, 33
Bus 002 Device 003: ID 0a5c:21f1 Broadcom Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize064
idVendor
Seth Forshee reported that his system was reporting that the EFI framebuffer
stretched from 0x9001-0xb001 despite the GPU's BAR only covering
0x9000-0x9ff. It's safer to calculate this value from the pixel
stride and screen height (values we already depend on) rather than face
Hi Henrik,
On Fri, Jul 27, 2012 at 08:12:46PM +0200, Henrik Rydberg wrote:
> The behavior of the SMC has changed several times over the years,
> causing read failures in the driver. It seems the problem can be
> explained by a shift in SMC speed combined with improper action on
> status codes.
>
On Fri, Jul 27, 2012 at 12:21:50PM -0700, Dan Magenheimer wrote:
> > From: Seth Jennings [mailto:sjenn...@linux.vnet.ibm.com]
> > Subject: [PATCH 0/4] promote zcache from staging
> >
> > zcache is the remaining piece of code required to support in-kernel
> > memory compression. The other two
1 - 100 of 958 matches
Mail list logo
