This patch introduces a new set of vm event counters to keep track of
ballooned pages compaction activity.
Signed-off-by: Rafael Aquini
---
include/linux/balloon_compaction.h | 7 +++
include/linux/vm_event_item.h | 7 ++-
mm/balloon_compaction.c| 2 ++
mm/migrate.c
Memory fragmentation introduced by ballooning might reduce significantly
the number of 2MB contiguous memory blocks that can be used within a guest,
thus imposing performance penalties associated with the reduced number of
transparent huge pages that could be used by the guest workload.
This
Memory fragmentation introduced by ballooning might reduce significantly
the number of 2MB contiguous memory blocks that can be used within a guest,
thus imposing performance penalties associated with the reduced number of
transparent huge pages that could be used by the guest workload.
This
Memory fragmentation introduced by ballooning might reduce significantly
the number of 2MB contiguous memory blocks that can be used within a guest,
thus imposing performance penalties associated with the reduced number of
transparent huge pages that could be used by the guest workload.
Besides
Memory fragmentation introduced by ballooning might reduce significantly
the number of 2MB contiguous memory blocks that can be used within a guest,
thus imposing performance penalties associated with the reduced number of
transparent huge pages that could be used by the guest workload.
This
This patch introduces MIGRATEPAGE_SUCCESS as the default return code
for address_space_operations.migratepage() method and documents the
expected return code for the same method in failure cases.
Signed-off-by: Rafael Aquini
---
fs/hugetlbfs/inode.c| 4 ++--
include/linux/migrate.h | 7
On Sun, Nov 11, 2012 at 05:03:21PM +, David Woodhouse wrote:
> On Sun, 2012-11-11 at 17:12 +0100, Krzysztof Mazur wrote:
> > It would require using atomic ops because also pppoatm_pop() can
> > modify this word. I think it's better to add additional word instead
> > of using atomic ops.
>
>
Hi Alex
I apologise for the delay in replying .
On Wed, Nov 7, 2012 at 6:57 PM, Alex Shi wrote:
> On 11/07/2012 12:37 PM, Preeti Murthy wrote:
>> Hi Alex,
>>
>> What I am concerned about in this patchset as Peter also
>> mentioned in the previous discussion of your approach
>>
On Sat, Nov 10, 2012 at 12:50:27PM +0100, Robert Richter wrote:
> On 09.11.12 19:01:34, Jacob Shin wrote:
> > The following patchset enables 4 additional performance counters in
> > AMD family 15h processors that counts northbridge events -- such as
> > DRAM accesses.
> >
> > This patchset is
On Fri, Nov 9, 2012 at 6:16 PM, Stephen Warren wrote:
> [Me]
>> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>> + if (res) {
>> + npct->prcm_base = devm_ioremap(>dev, res->start,
>> +resource_size(res));
>> +
> > 1. Yes, I've got first hand proof of a GPL violation (in which case
> > we'll then move to seeing how we can remedy this) or
> > 2. A genuine public apology for the libel, which I'll do my best to
> > prevail on RTS to accept.
> >
> > Because any further discussion
More include's and more comments, no changes in code.
To remind, once/if I am sure you agree with this patch I'll send 2 additional
and simple patches:
1. lockdep annotations
2. CONFIG_PERCPU_RWSEM
It seems that we can do much more improvements to a) speedup the writers and
b)
On Fri, Nov 9, 2012 at 9:06 AM, Thierry Reding
wrote:
> On Wed, Oct 31, 2012 at 05:57:27PM +0200, Pantelis Antoniou wrote:
>> + pinctrl = devm_pinctrl_get_select_default(>dev);
>> + if (IS_ERR(pinctrl))
>> + dev_warn(>dev, "unable to select pin group\n");
>> +
>
> I just saw
On Sun, 2012-11-11 at 10:15 -0500, Bradley M. Kuhn wrote:
> James wrote:
> >> [I'd like to see] a genuine public apology for the libel...
> >> Because any further discussion of unsubstantiated allegations of
> this
> >> nature exposes us all to jeopardy of legal sanction.
Hey that's a complete
On Wed, Nov 7, 2012 at 5:10 PM, Axel Lin wrote:
> Both ltq_pinctrl_dt_node_to_map() and ltq_pinctrl_dt_free_map() are not
> referenced outside of this file. Make them static.
>
> Signed-off-by: Axel Lin
Applied with John's ACK.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the
On Wed, Nov 7, 2012 at 4:57 PM, Axel Lin wrote:
> Current code adds empty ltq_pmx_disable() because pinmux_check_ops() requires
> this callback to be defined.
>
> This is not required since commit 02b50ce4cb1
> "pinctrl: make pinmux disable function optional".
>
> Thus remove ltq_pmx_disable()
On Sat, Nov 10, 2012 at 12:50 PM, Robert Richter wrote:
> On 09.11.12 19:01:34, Jacob Shin wrote:
>> The following patchset enables 4 additional performance counters in
>> AMD family 15h processors that counts northbridge events -- such as
>> DRAM accesses.
>>
>> This patchset is based on
On Tue, Nov 6, 2012 at 4:28 PM, Axel Lin wrote:
> Set it once is enough.
>
> Signed-off-by: Axel Lin
Applied with Kyungmin's ACK, thanks!
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Wed, Nov 7, 2012 at 6:37 AM, Axel Lin wrote:
> They are not referenced outside respective driver.
>
> Signed-off-by: Axel Lin
> Cc: Jean-Christophe PLAGNIOL-VILLARD
> Cc: Simon Arlott
> Cc: John Crispin
> Cc: Dong Aisheng
> Cc: Shawn Guo
> Cc: Stephen Warren
OK I had to merge down all
On Sun, Nov 11, 2012 at 2:32 AM, Rob Herring wrote:
> On 11/09/2012 06:48 PM, Stepan Moskovchenko wrote:
>> Use the cell-index property to construct names for platform
>> devices, falling back on the existing scheme of using the
>> device register address if cell-index is not specified.
>>
>> The
On 11 November 2012 19:42, Rob Herring wrote:
> On 11/06/2012 10:22 PM, viresh kumar wrote:
>> cluster0: cluster@0 {
>> + data1 = <0x50 0x60 0x70>;
>> + data2 = <0x5000 0x6000 0x7000>;
>> + data3 = <0x5000
On Thu, Nov 08, 2012 at 07:38:57AM +0100, Marek Szyprowski wrote:
> dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag, regardless
> the flags provided by the caller. This causes excessive pruning of
> emergency memory pools without any good reason. This patch changes the code
> to
On Sun, 2012-11-11 at 17:12 +0100, Krzysztof Mazur wrote:
> It would require using atomic ops because also pppoatm_pop() can
> modify this word. I think it's better to add additional word instead
> of using atomic ops.
Or use the existing flags word, perhaps. Only one bit of which is
actually
On Wed, Nov 07, 2012 at 12:32:43PM -0600, Mark Langsdorf wrote:
> When collecting stats, if a frequency doesn't match the table, go through
> the table again with both the search frequency and table values shifted
> left by 10 bits.
Why would that second pass succeed?
And why is this in generic
On Sun, Nov 4, 2012 at 11:37 PM, Jiri Slaby wrote:
> On 11/04/2012 10:06 PM, Geert Uytterhoeven wrote:
>> On Fri, Oct 19, 2012 at 1:28 PM, Jiri Slaby wrote:
>>> + if ((quirks & MS_RDESC_3K) && *rsize == 106 &&
>>> + !memcmp((char []){ 0x19, 0x00, 0x29, 0xff },
>>> +
On Sun, Nov 11, 2012 at 03:26:41PM +, David Woodhouse wrote:
> On Sun, 2012-11-11 at 14:50 +0100, Krzysztof Mazur wrote:
> > Looks and works ok after:
> > + atmvcc->unlock_cb = pppoatm_unlock_cb;
>
> Heh, yeah. That would probably help :)
>
> Not sure if it's really necessary to
Namjae Jeon writes:
> In calling of __fat_write_inode(inode, wbc->sync_mode == WB_SYNC_ALL),
> expression "wbc->sync_mode == WB_SYNC_ALL" will always be equivalent to value
> of wbc->sync_mode. So, remove this additional compare condition from function
> arguments.
Current style is better. I.e.
Namjae Jeon writes:
> Correctly update modification and status change time in case of
> file/directory removal and creation.
This changelog just explain "what", and it doesn't explain "why". Please
explain why we need this change.
IIRC, timestamp handling in FAT driver is strange historically.
Michal, All,
On Thursday 25 October 2012 Michal Marek wrote:
> On 22.10.2012 21:38, Yann E. MORIN wrote:
> > On Sunday 21 October 2012 Benjamin Poirier wrote:
> >> Changes v1-v2:
> >> * integrate the patch/suggestion from Yann to fix problems related to the
> >> usage of list.h with xconfig/c++
On 11/09, Paul E. McKenney wrote:
>
> On Fri, Nov 09, 2012 at 07:10:48PM +0100, Oleg Nesterov wrote:
> >
> > static bool xxx(brw)
> > {
> > down_write(>rw_sem);
>
> down_write_trylock()
>
> As you noted in your later email. Presumably you return false if
> the
1. rename mei_me_cl_update_filext to mei_me_cl_link
2. rename mei_remove_client_from_file_list to mei_me_cl_unlink
Code style, documenation, and usage of both function is updated
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c |4 +-
drivers/misc/mei/init.c| 67
1. Rename mei_cb_major_types to more understandable mei_cb_file_ops
2. Rename member struct mei_cl_cb of this type to simple 'fop_type'
3. Add kernel doc for the type
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c|2 +-
drivers/misc/mei/init.c |2 +-
We can use correct type 'struct mei_cl' instead of
'void *' for file_private in the struct mei_cb
as there is no other type assigned to this member of the structure
We rename the member from file_private to cl
Remove about 10 lines of declarations of temporary variables
used for type casting
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c | 19 +++
drivers/misc/mei/main.c| 10 +-
drivers/misc/mei/mei_dev.h |6 +-
3 files changed, 25 insertions(+), 10 deletions(-)
diff --git a/drivers/misc/mei/amthif.c b/drivers/misc/mei/amthif.c
structs hbm_client_connect_request and hbm_client_disconnect_request
have the same layout so we can drop the later
Add kdoc for the request and response structure so it is clear
they can be used for both purposes
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/hw.h| 22
Move amthif code part into separate function
mei_amthif_release.
Also helper functions mei_clear_list and mei_clear_lists
are moved along
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c | 114
drivers/misc/mei/main.c| 178
amthif cb list were prefixed with amthi_ instead
if amthif.
Signed-off-by: Tomas Winkler
---
drivers/misc/mei/amthif.c| 10 +-
drivers/misc/mei/init.c |8
drivers/misc/mei/interrupt.c |6 ++
drivers/misc/mei/main.c |5 ++---
On Sun, 2012-11-11 at 14:50 +0100, Krzysztof Mazur wrote:
> Looks and works ok after:
> + atmvcc->unlock_cb = pppoatm_unlock_cb;
Heh, yeah. That would probably help :)
Not sure if it's really necessary to optimise out the unneeded wakeups —
I don't think that code path gets exercised very
On Thu, 2012-11-08 at 18:18 -0800, Joseph Gasparakis wrote:
>
> if (skb->ip_summed == CHECKSUM_PARTIAL &&
> skb_checksum_help(skb))
> @@ -902,6 +903,17 @@ static netdev_tx_t ipgre_tunnel_xmit(struct sk_buff
> *skb, struct net_device *dev
> tunnel->err_count
> On Sun, Nov 11, 2012 at 09:34:16AM +, James Bottomley wrote:
>> Anybody who does enforcement will tell you that you begin with first
>> hand proof of a violation. That means obtain the product and make
>> sure it's been modified and that a request for corresponding source
>> fails.
I agree
Add regulator driver for Texas Instrument TPS80031/TPS80032 device.
TPS80031/ TPS80032 Fully Integrated Power Management with Power
Path and Battery Charger. It has 5 configurable step-down
converters, 11 general purpose LDOs, VBUS generator and digital
output to control regulators.
TPS80031/ TPS80032 Fully Integrated Power Management with Power
Path and Battery Charger. The device provides five configurable
step-down converters, 11 general purpose LDOs, USB OTG Module,
ADC, RTC, 2 PWM, System Voltage Regulator/Battery Charger with
Power Path from USB, 32K clock generator.
This patch series supports mfd core and regulator driver for the
Texas Instruments TPS80031/ TPS80032 Fully Integrated Power
Management with Power Path and Battery Charger. The device
provides five configurable step-down converters, 11 general
purpose LDOs, USB OTG Module, ADC, RTC, 2 PWM, System
On Sat, 2012-11-10 at 14:52 -0700, Bjorn Helgaas wrote:
> On Wed, Nov 7, 2012 at 7:55 PM, Peter Hurley wrote:
> > An incorrectly specified host bridge window may prevent
> > other devices from claiming assigned resources. For example,
> > this flawed _CRS resource descriptor from a Dell T5400:
>
On Sat, Nov 10, 2012 at 10:01:18PM +0100, Thierry Reding wrote:
> On Fri, Nov 09, 2012 at 05:00:54PM +0100, Christian König wrote:
> > On 09.11.2012 16:45, Rafał Miłecki wrote:
> > >2012/11/9 Thierry Reding :
> > >>+/* all fields little endian */
> > >>+struct hdmi_audio_infoframe {
> > >>+
Current perf_event__synthesize_mmap_events() only deals with
executable mappings. With recently added memory access sampling,
non-executable data mappings are needed also.
Cc: Stephane Eranian
Signed-off-by: Namhyung Kim
---
tools/perf/util/event.c | 10 +++---
1 file changed, 7
Use sscanf for parsing /proc/pic/maps file. It makes the code shorter
and cleaner IMHO.
Cc: Stephane Eranian
Signed-off-by: Namhyung Kim
---
tools/perf/util/event.c | 74 ---
1 file changed, 31 insertions(+), 43 deletions(-)
diff --git
On 11/06/2012 10:22 PM, viresh kumar wrote:
> On Tue, Nov 6, 2012 at 7:48 PM, Rob Herring wrote:
>>> +#define of_property_read_array(_np, _pname, _out, _sz)
>>> \
>
>>> + while (_sz--) \
>>> + *_out++ =
In calling of __fat_write_inode(inode, wbc->sync_mode == WB_SYNC_ALL),
expression "wbc->sync_mode == WB_SYNC_ALL" will always be equivalent to value
of wbc->sync_mode. So, remove this additional compare condition from function
arguments.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
Correctly update modification and status change time in case of
file/directory removal and creation.
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
---
fs/fat/dir.c|2 +-
fs/fat/namei_vfat.c |6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
FAT also notify warning message about discard support
as ext4(http://patchwork.ozlabs.org/patch/192668/)
Signed-off-by: Namjae Jeon
Signed-off-by: Amit Sahrawat
Acked-by: OGAWA Hirofumi
---
fs/fat/inode.c |9 +
1 file changed, 9 insertions(+)
diff --git a/fs/fat/inode.c
On Sun, Nov 11, 2012 at 11:39:53AM +, David Woodhouse wrote:
>
> Right. Something like this then, instead of my previous patch 8/7?
>
> Only addresses the sock_owned_by_user() case and not ATM_VF_RELEASED,
> ATM_VF_CLOSE or !ATM_VF_READY, but your amended patch 6 fixes that I
> think.
>
Move the code checking valid config to dove_audio1_ctrl_set(), this ensures we
always set valid config. And then dove_audio1_ctrl_get() always returns correct
config.
Signed-off-by: Axel Lin
---
drivers/pinctrl/mvebu/pinctrl-dove.c | 13 +++--
1 file changed, 7 insertions(+), 6
Current implementation in dove_audio1_ctrl_set() does not clear corresponding
register bit if BIT(0|1|2|3) of config is clear. Fix it.
Signed-off-by: Axel Lin
---
Hi,
I don't have this hardware.
I'd appreciate if someone can review and test this patch.
This resend also CC Sebastian Hesselbarth
It's been another week (modulo timezone differences), so -rc5 is out there.
This is quite a small -rc, I'm happy to say. -rc4 was already fairly
calm, and -rc5 has fewer commits still. And more importantly, apart
from one revert, and a pinctl driver update, it's not just a fairly
small number of
On Sun, Nov 11, 2012 at 09:34:16AM +, James Bottomley wrote:
> Anybody who does enforcement will tell you that you begin with first
> hand proof of a violation. That means obtain the product and make sure
> it's been modified and that a request for corresponding source fails.
> In this case,
Register IRQ domains through Device Tree for the internal and external
interrupt controllers. Register the same IRQ ranges as previously to
provide backward compatibility for non-DT drivers.
Signed-off-by: Jonas Gorski
---
.../devicetree/bindings/mips/bcm63xx/epic.txt | 20
Add support for loading DTBs embedded into the kernel. Iterate through
all embedded ones until a match is found and use that.
Use the NVRAM provided board name for constructing the compatible
property for selecting the appropriate in-kernel DTB.
Signed-off-by: Jonas Gorski
---
Use proper clk_prepare/unprepare calls in preparation for switching
to the generic clock framework.
Signed-off-by: Jonas Gorski
---
drivers/spi/spi-bcm63xx.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/spi/spi-bcm63xx.c b/drivers/spi/spi-bcm63xx.c
index
Use proper clk_prepare/unprepare calls in preparation for switching to
the generic clock framework.
Signed-off-by: Jonas Gorski
---
drivers/char/hw_random/bcm63xx-rng.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/char/hw_random/bcm63xx-rng.c
On Sun, Nov 11, 2012 at 1:52 PM, Stefan Hajnoczi wrote:
> Daniel Mack suggested the dyndbg mechanism which allows
> dev_dbg() messages to be enabled/disabled at run-time. This is more powerful
> than the compile-time CONFIG_LINE6_USB_DEBUG option.
>
> This patch series converts debug messages
The dyndbg feature allows dev_dbg() calls to be enabled/disabled at
runtime and is therefore more convenient than static debug log messages.
Use dev_dbg() instead of the line6-specific DEBUG_MESSAGES() macro.
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/driver.c | 6 ++---
The CONFIG_LINE6_USB_DEBUG option is no longer relevant since dyndbg
dev_dbg() is now used instead of a compile-time decision whether to
enable debug messages or not.
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/Kconfig | 8
1 file changed, 8 deletions(-)
diff --git
The DEBUG_MESSAGES() macro is no longer needed since dev_dbg() is now
used for debug messages.
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/driver.h | 6 --
1 file changed, 6 deletions(-)
diff --git a/drivers/staging/line6/driver.h b/drivers/staging/line6/driver.h
index
Daniel Mack suggested the dyndbg mechanism which allows
dev_dbg() messages to be enabled/disabled at run-time. This is more powerful
than the compile-time CONFIG_LINE6_USB_DEBUG option.
This patch series converts debug messages to dev_dbg() and drops the obsolete
CONFIG_LINE6_USB_DEBUG option.
bcm63xx_clk.h does not need to be included anymore as clk.h already
provides all required prototypes.
Signed-off-by: Jonas Gorski
---
drivers/tty/serial/bcm63xx_uart.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/tty/serial/bcm63xx_uart.c
Add simple Device Tree include files for all currently supported SoCs.
These will be populated with device definitions as driver support
gets added.
Signed-off-by: Jonas Gorski
---
arch/mips/bcm63xx/dts/bcm6328.dtsi | 30 ++
arch/mips/bcm63xx/dts/bcm6338.dtsi |
Register the GPIO controller through Device Tree and add the
appropriate values in the include files.
Since we can't register a platform driver at this early stage move the
direct call to bcm63xx_gpio_init from prom_init to an arch initcall.
Signed-off-by: Jonas Gorski
---
Add the serial block to the Device Tree includes for all SoCs.
Signed-off-by: Jonas Gorski
---
arch/mips/bcm63xx/dts/bcm6328.dtsi | 14 ++
arch/mips/bcm63xx/dts/bcm6338.dtsi |7 +++
arch/mips/bcm63xx/dts/bcm6345.dtsi |8
arch/mips/bcm63xx/dts/bcm6348.dtsi |
Enable serial through Device Tree board files instead of legacy
board files.
Signed-off-by: Jonas Gorski
---
arch/mips/bcm63xx/boards/board_bcm963xx.c | 15 ---
arch/mips/bcm63xx/dts/96328avng.dts |3 +++
arch/mips/bcm63xx/dts/96338gw.dts |3 +++
Add empty board files for all boards supported by the legacy board
support.
Signed-off-by: Jonas Gorski
---
arch/mips/bcm63xx/dts/96328avng.dts | 22 +++
arch/mips/bcm63xx/dts/96338gw.dts | 22 +++
arch/mips/bcm63xx/dts/96338w.dts | 22 +++
Add support for probing the serial ports through Device Tree.
Signed-off-by: Jonas Gorski
---
.../bindings/tty/serial/bcm63xx-uart.txt | 17 +
drivers/tty/serial/bcm63xx_uart.c | 35 ++--
2 files changed, 42 insertions(+), 10 deletions(-)
Add definitions for the clocks found and used in all supported SoCs.
Signed-off-by: Jonas Gorski
---
arch/mips/bcm63xx/dts/bcm6328.dtsi | 90 ++
arch/mips/bcm63xx/dts/bcm6338.dtsi | 47 +
arch/mips/bcm63xx/dts/bcm6345.dtsi | 33 ++
Switch BCM63XX to the common clock framework and use clkdev for
providing clock name lookups for non-DT devices.
Clocks can have a frequency and gate-bit, or none, in case they
are just provided for drivers expecting them to be present.
Signed-off-by: Jonas Gorski
---
Use proper clk_prepare/unprepare calls in preparation for switching to
the generic clock framework.
Signed-off-by: Jonas Gorski
---
drivers/net/ethernet/broadcom/bcm63xx_enet.c | 12 ++--
1 files changed, 6 insertions(+), 6 deletions(-)
diff --git
This patch series adds initial Device Tree support to BCM63XX by adding
bindings for interrupts, GPIOs and clocks to Device Tree. Finally it adds
one "real" user, the serial driver, to the device tree boards.
The main intention of this patch series is to make the transition to
device tree as
Add generic fallback device trees to load if there is no specific
device tree for the board available. This ensures that always present
devices like interrupt controllers are always available.
Signed-off-by: Jonas Gorski
---
arch/mips/bcm63xx/dts/Makefile |8
On Fri, Nov 09, 2012 at 07:06:40AM +0100, Manuel Traut wrote:
> If uio_pdrv[_genirq] is used, the uio maps have currently no name set.
> This patch sets the uio_mem name to the name of the memory resource.
Looks fine to me. I added the driver's authors to Cc.
Signed-off-by: "Hans J. Koch"
>
This patch introduces PF_MEMALLOC_NOIO on process flag('flags' field of
'struct task_struct'), so that the flag can be set by one task
to avoid doing I/O inside memory allocation in the task's context.
The patch trys to solve one deadlock problem caused by block device,
and the problem may happen
On Sun, Nov 11, 2012 at 8:34 PM, Ming Lei wrote:
> +/* GFP_NOIO isn't allowed if PF_MEMALLOC_NOIO is set in current->flags */
> +static inline gfp_t memalloc_noio_flags(gfp_t flags)
> +{
> + if (unlikely(current->flags & PF_MEMALLOC_NOIO))
> + flags &= ~GFP_NOIO;
> +
If one storage interface or usb network interface(iSCSI case)
exists in current configuration, memory allocation with
GFP_KERNEL during usb_device_reset() might trigger I/O transfer
on the storage interface itself and cause deadlock because
the 'us->dev_mutex' is held in .pre_reset() and the
This patch applies the introduced memalloc_noio_save() and
memalloc_noio_restore() to force memory allocation with no I/O
during runtime_resume/runtime_suspend callback on device with
the flag of 'memalloc_noio' set.
Cc: Alan Stern
Cc: Oliver Neukum
Cc: Rafael J. Wysocki
Signed-off-by: Ming
Deadlock might be caused by allocating memory with GFP_KERNEL in
runtime_resume and runtime_suspend callback of network devices in
iSCSI situation, so mark network devices and its ancestor as
'memalloc_noio' with the introduced pm_runtime_set_memalloc_noio().
Cc: "David S. Miller"
Cc: Eric
The patch introduces the flag of memalloc_noio in 'struct dev_pm_info'
to help PM core to teach mm not allocating memory with GFP_KERNEL
flag for avoiding probable deadlock.
As explained in the comment, any GFP_KERNEL allocation inside
runtime_resume() or runtime_suspend() on any one of device in
This patch applyes the introduced pm_runtime_set_memalloc_noio on
block device so that PM core will teach mm to not allocate memory with
GFP_IOFS when calling the runtime_resume and runtime_suspend callback
for block devices and its ancestors.
Cc: Jens Axboe
Signed-off-by: Ming Lei
---
v5:
This patch introduces PF_MEMALLOC_NOIO on process flag('flags' field of
'struct task_struct'), so that the flag can be set by one task
to avoid doing I/O inside memory allocation in the task's context.
The patch trys to solve one deadlock problem caused by block device,
and the problem may happen
This patchset try to solve one deadlock problem which might be caused
by memory allocation with block I/O during runtime PM and block device
error handling path. Traditionly, the problem is addressed by passing
GFP_NOIO statically to mm, but that is not a effective solution, see
detailed
On Thu, Nov 1, 2012 at 3:01 PM, Linus Walleij wrote:
> On Thu, Nov 1, 2012 at 1:07 PM, Mark Brown
> wrote:
>> On Thu, Nov 01, 2012 at 09:54:00AM +0100, Linus Walleij wrote:
>
>> For the pin hogging I'd actually been thinking separately that we should
>> just have the device core do a
Hi,
there is a bug in the emulation of the lapic time counter. In particular
what we are seeing is that the time counter of a periodic lapic timer
in the guest reads as zero 99% of the time. The patch below fixes that.
The emulation of the lapic timer is done with the help of a hires
timer that
Checkpatch warns when quoted strings are split across lines. The
rationale is that quoted strings should be left on a single line so that
grep works. (The 80 character line limit does not apply to quoted
strings.)
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/midibuf.c | 6 +++---
There are a few instances of 80+ character lines in playback.c. Two
instances are just because of a useless comment "this is somewhat
paranoid", so drop the comment. Other instances are straightforward
line wrapping.
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/playback.c | 17
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/pcm.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/line6/pcm.h b/drivers/staging/line6/pcm.h
index 5210ec8..6aa0d46 100644
--- a/drivers/staging/line6/pcm.h
+++ b/drivers/staging/line6/pcm.h
@@ -167,7
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/capture.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/staging/line6/capture.c b/drivers/staging/line6/capture.c
index c85c5b6..389c41f 100644
--- a/drivers/staging/line6/capture.c
+++
The LED value is an int, so replace strict_strtol() with kstrtoint().
It's safe to pass in the actual variable instead of a local temporary
because strto*() doesn't write to the result unless the function returns
success.
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/toneport.c | 8
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/usbdefs.h | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/line6/usbdefs.h b/drivers/staging/line6/usbdefs.h
index 353d59d..43eb540 100644
--- a/drivers/staging/line6/usbdefs.h
+++
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/variax.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/staging/line6/variax.c b/drivers/staging/line6/variax.c
index f97416b..1b85ecc 100644
--- a/drivers/staging/line6/variax.c
+++
Signed-off-by: Stefan Hajnoczi
---
drivers/staging/line6/pcm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/line6/pcm.c b/drivers/staging/line6/pcm.c
index 7fe44a6..6c1e313 100644
--- a/drivers/staging/line6/pcm.c
+++ b/drivers/staging/line6/pcm.c
@@
This series addresses a number of checkpatch.pl warnings, mostly exceeding the
80 character line limit.
Some checkpatch.pl warnings remain in the line6 driver but they are either more
difficult to resolve or I intend to drop that code entirely. So expect a
little more time before the driver
Did you do the "request-pull" *after* you had done all the above?
The ..BRANCH.NOT.VERIFIED.. implies that the request-pull couldn't
find the particular tag.
Also, if you have an older version of git, you need to tell
request-pull explicitly that it is a tag, by saying "tags/for-linus"
rather
From: Linus Walleij
This makes the pinctrl subsystem auto-grab the pinctrl handle and
set the "default" (PINCTRL_STATE_DEFAULT) state for every device
that is present on the platform or AMBA (PrimeCell) bus right
before probe. This will account for the lion's share of embedded
silicon devcies.
101 - 200 of 460 matches
Mail list logo
