On 1 February 2013 13:03, Santosh Shilimkar santosh.shilim...@ti.com wrote:
I am not talking about just notifiers. This is for external users who
has subscribed for notifiers. The point is whether the core CPUFReq
gets updated without that flag for all affected CPU.
Yes, its safe. Follow this
Hi Stephane,
On Fri, 1 Feb 2013 00:51:51 +0100, Stephane Eranian wrote:
Hi,
Looks like perf annotate in pipe mode is totally broken nowadays.
I tried this from tip.git:
$ perf record -o - noploop 5 perf.data
$ perf annotate -i i perf.data
Core dump
Callstack looks as follows:
This patchset attempts to make the atmel fw update a bit more robust by.
Some highlights:
1) handle more errors during fw update
2) use the CHG (interrupt) line to detect state transitions (instead of open
waiting)
3) handle cases where the device is in bootloader at probe time
4) tear
A recent patch refactored i2c error handling in the register read/write
path. This adds similar handling to the other i2c paths used in fw_update
and bootloader state detection.
The generic i2c layer can return values indicating a partial transaction.
From the atmel_mxt driver's perspective,
From: Benson Leung ble...@chromium.org
The driver should not immediately read bootloader status when
in Application Update Mode. The CHG line will assert when the device
has made a state transition and is ready to report a new status
via i2c.
This change adds a wait for completion in
Hi,
Likewise, I expect with the final version vmci_transport is a
separate module (or moves into the vmci driver), correct?
When you say final, do you mean something that we have to do before
acceptance into mainline or something we can refine over time?
IMHO refining in-tree is fine.
Move input device initialization to its own helper function.
This is in preparation of a future patch that makes input device
conditional on the device not being in its bootloader.
Signed-off-by: Daniel Kurtz djku...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 91
After firmware update, the device may have a completely different object
table which corresponds to an input device with different properties.
So, destroy the old state before firmware update, and completely
reinitialize the driver afterward.
Two benefits of this:
1) Since there is no input
From: Benson Leung ble...@chromium.org
175ms is not enough time to update the firmware. Set to
500ms.
Signed-off-by: Benson Leung ble...@chromium.org
---
drivers/input/touchscreen/atmel_mxt_ts.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Benson Leung ble...@chromium.org
Rather than msleep for MXT_RESET_TIME and MXT_FWRESET_TIME
during the transition to bootloader mode and the transition
back from app, wait for the CHG assert to indicate that the
transition is done.
This change replaces the msleep with a wait for completion
From: Benson Leung ble...@chromium.org
Refactor bootloading into a three parts:
1) bl enter that only happens when device is not yet in bl.
bl enter frees old driver state and switches to BL i2c addr.
2) the actual fw_update
3) bl exit that only happens if fw update is successful.
bl
As soon as the irq is request, input event interrupts could occur that
the isr should handle. Similarly, if there are input events queued up
in the device output buffer, it will send them immediately when we
drain the message buffer with mxt_handle_messages.
Therefore, register the input device
If there are any (i2c) errors during fw update, abort the update, but
leave the i2c address assigned to the bootloader address.
Note that an error when trying to reset the device into the bootloader
will leave the i2c address assigned to the application address.
Signed-off-by: Benson Leung
In some cases it is possible for a device to be in its bootloader at
driver probe time. This is detected by the driver when probe() is called
with an i2c_client which has one of the Atmel Bootloader i2c addresses.
In this case, we should load enough driver functionality to still loading
new
On 2013-01-29 오후 8:43, Egon Alter wrote:
Am Dienstag, 29. Januar 2013, 10:15:49 schrieb Russell King - ARM Linux:
On Mon, Jan 28, 2013 at 02:25:10PM -0800, Andrew Morton wrote:
What's this with enabled unaligned memory access thing? You mean if
the arch supports
Hi Stephen,
On Wednesday 30 January 2013 02:14 AM, Stephen Rothwell wrote:
Hi Vineet,
On Mon, 28 Jan 2013 12:40:24 +0530 Vineet Gupta vineet.gup...@synopsys.com
wrote:
Stephen, can you please add the following branch (rebased off 3.8-rc5) to
linux-next
On Sun, 2013-01-27 at 19:28 -0800, Amit Daniel Kachhap wrote:
This patch adds support to set the emulated temperature method in
thermal zone (sensor). After setting this feature thermal zone may
report this temperature and not the actual temperature. The emulation
implementation may be based
The input fuzz algorithm does a pretty good job filtering out small
jitter on input samples.
However, there is a subtle problem when fuzz is used with mt drivers that
also use input_mt_report_pointer_emulation() to report legacy single
touch coordinates. The reported single touch coordinates are
Investigating the following gesture highlighted two slight implementation
errors with choosing which slots to report in which slot when multiple
contacts are present:
Action SGM AGM (MTB slot:Contact)
1. Touch contact 0(0:0)
2. Touch contact 1(0:0, 1:1)
3. Lift contact 0
2013/02/01 12:07, Ming Lei wrote:
Currently, sizeof(struct parsed_partitions) may be 64KB in 32bit arch,
so it is easy to trigger page allocation failure by check_partition,
especially in hotplug block device situation(such as, USB mass storage,
MMC card, ...), and Felipe Balbi has observed
Hi, Stephane
On Thu, 31 Jan 2013 14:54:37 +0100, Stephane Eranian wrote:
This patchset adds a new command to perf: perf uncore.
It is used to measure processor socket-level metrics
on a system-wide basis and at all priv levels.
The command comes with a set of predefined key metrics
which
On Fri, Feb 1, 2013 at 9:21 AM, Sedat Dilek sedat.di...@gmail.com wrote:
people having the fbcon-locking-fixes [1] in their local GIT tree can
revert this change?
Yeah, if you have all the fixes reverting this is fine and appreciated
to increase testing. Dave will probably push the revert
On Fri 01-02-13 01:11:56, Johannes Weiner wrote:
An inactive file list is considered low when the its active
counter-part is bigger, regardless of whether it is a global zone LRU
list or a memcg zone LRU list. The only difference is in how the LRU
size is assessed.
get_lru_size() does the
-Original Message-
From: Zhang, Rui
Sent: Friday, February 01, 2013 11:14 AM
To: Amit Daniel Kachhap
Cc: linux...@vger.kernel.org; linux-kernel@vger.kernel.org; R, Durgadoss
Subject: Re: [PATCH] Thermal: Fix to use read critical temperature when
required
On Tue, 2013-01-08 at
On 02/01/2013 05:11 AM, Len Brown wrote:
From: Len Brown len.br...@intel.com
The commit, 4202735e8ab6ecfb0381631a0d0b58fefe0bd4e2
(cpuidle: Split cpuidle_state structure and move per-cpu statistics fields)
observed that the MWAIT flags for Cn on every processor to date were the
same, and
Just a nitpick. But maybe I shows it can be done with perf stat. :)
On Thu, 31 Jan 2013 14:54:39 +0100, Stephane Eranian wrote:
diff --git a/tools/perf/builtin-uncore.c b/tools/perf/builtin-uncore.c
new file mode 100644
index 000..b050712
--- /dev/null
+++ b/tools/perf/builtin-uncore.c
On 2013/1/31 23:59, Yinghai Lu wrote:
On Thu, Jan 31, 2013 at 7:37 AM, Jiang Liu liu...@gmail.com wrote:
So I think the code in handle_hotplug_event_bridge() to handle P2P
hot-addition
is dead. Yijing has helped to test the code by faking ACPI CUSTOM_METHOD,
and it
does work as expected.
On Friday 01 February 2013 01:32 PM, Viresh Kumar wrote:
On 1 February 2013 13:03, Santosh Shilimkar santosh.shilim...@ti.com wrote:
I am not talking about just notifiers. This is for external users who
has subscribed for notifiers. The point is whether the core CPUFReq
gets updated without
On Fri, Feb 01, 2013 at 11:54:01AM +0530, Vivek Gautam wrote:
Hi Balbi,
On Fri, Feb 1, 2013 at 11:52 AM, Vivek Gautam gautamvivek1...@gmail.com
wrote:
Hi Kishon,
On Fri, Feb 1, 2013 at 10:51 AM, kishon kis...@ti.com wrote:
Hi,
On Thursday 31 January 2013 09:08 PM, Felipe
Hi Michael,
On Thu, 31 Jan 2013 16:57:49 +0800, Michael Wang wrote:
On 01/31/2013 04:45 PM, Michael Wang wrote:
On 01/31/2013 04:24 PM, Michael Wang wrote:
On 01/31/2013 03:40 PM, Namhyung Kim wrote:
On Thu, 31 Jan 2013 15:30:02 +0800, Michael Wang wrote:
On 01/31/2013 02:58 PM, Namhyung Kim
On Fri, Feb 1, 2013 at 2:20 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Feb 01, 2013 at 11:54:01AM +0530, Vivek Gautam wrote:
Hi Balbi,
On Fri, Feb 1, 2013 at 11:52 AM, Vivek Gautam gautamvivek1...@gmail.com
wrote:
Hi Kishon,
On Fri, Feb 1, 2013 at 10:51 AM, kishon kis...@ti.com
At present, the value of timeout for freezing is 20s, which is
meaningless in case that one thread is frozen with mutex locked
and another thread is trying to lock the mutex, as this time of
freezing will fail unavoidably.
And if there is no new wakeup event registered, the system will
waste at
Hi All,
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4) will hang
forever and we will get something in /var/log/messages like below.
It seems to me that the io sent to the scsi layer is never returned back
On Tue, Jan 29, 2013 at 5:03 PM, Bernd Schubert
bernd.schub...@itwm.fraunhofer.de wrote:
Do not run with verbosity on/off depending on the ONLINE variable,
which gets set with C=1 or C=2, but allow the user to set the
verbosity using kernel default make V= paramemter.
Verbosity is off by
Viresh,
On Friday 01 February 2013 02:22 PM, Santosh Shilimkar wrote:
On Friday 01 February 2013 01:32 PM, Viresh Kumar wrote:
On 1 February 2013 13:03, Santosh Shilimkar santosh.shilim...@ti.com
wrote:
I am not talking about just notifiers. This is for external users who
has subscribed for
On Tue, Jan 29, 2013 at 5:03 PM, Bernd Schubert
bernd.schub...@itwm.fraunhofer.de wrote:
On my system one of the tests failed with
Fatal error: exception Failure(No OCaml compiler found! Install either
ocamlopt or ocamlopt.opt).
Investigating such issues is easier if the executed command
On 02/01/2013 03:54 PM, Bart Van Assche wrote:
On 02/01/13 07:13, Tao Ma wrote:
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4) will
hang forever and we will get something in /var/log/messages like below.
On Fri, Feb 1, 2013 at 9:42 AM, Daniel Vetter daniel.vet...@ffwll.ch wrote:
On Fri, Feb 1, 2013 at 9:21 AM, Sedat Dilek sedat.di...@gmail.com wrote:
people having the fbcon-locking-fixes [1] in their local GIT tree can
revert this change?
Yeah, if you have all the fixes reverting this is fine
Hi Stephen,
Not sure if you have already noticed this but,
I did try this patch on my 3.8, and it looks like the intermediate dts
file replaces all instances of linux with 1 because of predefined macros
in gcc.
As a result
linux,stdout-path = /soc/stm-asc2;
is changed to.
1,stdout-path =
On 02/01/2013 04:50 PM, Jack Wang wrote:
Hi All,
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4) will hang
forever and we will get something in /var/log/messages like below.
It seems to me that the io
On 02/01/2013 04:50 PM, Jack Wang wrote:
Hi All,
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4)
will hang forever and we will get something in /var/log/messages like
below.
It seems to me that the
Hello, please CC me directly if possible, I simply can't withstand the
firehose of subscribing to the full LKML but per the MAINTIANERS file this
was where this patch should go for open discussion.
If I should have posted it as two parts, I'll go do that straight away:
1) It's removing a +1 from
On Tue, Jan 29, 2013 at 3:53 PM, Andreas Larsson andr...@gaisler.com wrote:
This lets of_gpio_named_count return an errno on errors by being able to
distinguish between reaching the end of the phandle list and getting some
other
error from of_parse_phandle_with_args.
Return error from
On Sat, Jan 26, 2013 at 3:36 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
The Allwinner A10 has 9 banks of 32 GPIOs available, so it doesn't fit
in the usual 256 limit set by gpio.h. Increase this number to 288.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Patch
Hi,
On Fri, Feb 01, 2013 at 02:23:28PM +0530, Vivek Gautam wrote:
On Thu, Jan 31, 2013 at 08:53:27PM +0530, Vivek Gautam wrote:
Moreover, SoCs having multiple dwc3 controllers will have multiple
PHYs, which eventually be added using usb_add_phy_dev(), and not
using usb_add_phy().
On Sat, Jan 26, 2013 at 3:36 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
---
drivers/pinctrl/pinctrl-sunxi.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
Applied to my allwinner branch.
Thanks,
On Sat, Jan 26, 2013 at 3:36 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Since the Allwinner SoCs variants don't have the same set of pins to
handle, we need to declare the pin ranges available.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Applied to my
From: Garrick He g...@calpoly.edu
Fix all 'please, no space before tabs' warning found by checkpatch.pl
Signed-off-by: Garrick He garric...@gmail.com
---
drivers/staging/wlan-ng/hfa384x.h | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git
On Sat, Jan 26, 2013 at 3:36 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Applied to my allwinner branch.
Thanks,
Linus Walleij
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Sat, Jan 26, 2013 at 3:36 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
Applied to my allwinner branch.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On 1 February 2013 09:54, Stephen Warren swar...@wwwdotorg.org wrote:
The entire series is merged in Greg's driver-core tree [1] and I
presume all other associated patches would also be picked up by him.
Isn't it Greg?
[1] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
On 02/01/2013 07:54 AM, Bart Van Assche wrote:
* proc_scsi_write - handle writes to /proc/scsi/scsi
* @file: not used
* @buf: buffer to write
* @length: length of buf, at most PAGE_SIZE
* @ppos: not used
*
* Description: this provides a legacy mechanism to add or remove
* devices
On Tue, Jan 29, 2013 at 11:54 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Le 29/01/2013 23:41, Linus Walleij a écrit :
On Sun, Jan 27, 2013 at 8:02 PM, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Since the pin controller of sunxi chips is represented as a single bank
On 02/01/2013 05:24 PM, Jack Wang wrote:
On 02/01/2013 04:50 PM, Jack Wang wrote:
Hi All,
In our product system, we have several sata disks attached to one
machine. So when one of the disk fails, the jbd2(yes, we use ext4)
will hang forever and we will get something in
* Sasha Levin sasha.le...@oracle.com wrote:
These headers provide the same API as their pthread mutex counterparts.
The design here is to allow to easily switch to liblock lock validation
just by adding a liblock_ to pthread_mutex_*() calls, which means that
it's easy to integrate liblock
On Wed, Jan 30, 2013 at 12:27 PM, Thierry Reding
thierry.red...@avionic-design.de wrote:
__devinit, __devexit and __devexit_p have been removed and should no
longer be used.
Signed-off-by: Thierry Reding thierry.red...@avionic-design.de
Hm I think I removed these just the other day ... may
On 02/01/2013 05:52 PM, Bryn M. Reeves wrote:
On 02/01/2013 07:54 AM, Bart Van Assche wrote:
* proc_scsi_write - handle writes to /proc/scsi/scsi
* @file: not used
* @buf: buffer to write
* @length: length of buf, at most PAGE_SIZE
* @ppos: not used
*
* Description: this
On Fri, Feb 01, 2013 at 10:14:20AM +0900, Yasuaki Ishimatsu wrote:
2013/02/01 9:53, Yasuaki Ishimatsu wrote:
2013/02/01 9:50, Yasuaki Ishimatsu wrote:
2013/01/31 19:03, Daniel Vetter wrote:
On Thu, Jan 31, 2013 at 12:27:26PM +0900, Yasuaki Ishimatsu wrote:
I forgot to change subject. So I
On 02/01/2013 09:59 AM, Tao Ma wrote:
yes, but the result is the same. It will do some IO first which will
cause this command hang.
You seem to have a problem with either the device/adapter or in the
driver. The backtrace you posted shows that jbd2 (ext4) is still waiting
on IO that's been
On Tue, Jan 29, 2013 at 11:56:01AM -0500, Vince Weaver wrote:
On Tue, 29 Jan 2013, Jiri Olsa wrote:
ok, there's been perf fixies wrt enable events groups, but they
landed in 3.8-rc1.. until that point all the group members are
specifically enabled, so that's why your perf is working and
* Andi Kleen a...@firstfloor.org wrote:
From: Andi Kleen a...@linux.intel.com
Implement the TSX transaction and checkpointed transaction qualifiers for
Haswell. This allows e.g. to profile the number of cycles in transactions.
The checkpointed qualifier requires forcing the event to
Use the newly introduced devm_ioremap_resource() instead of
devm_request_and_ioremap() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages; so all explicit
error messages can be removed from the failure code paths.
Signed-off-by: Sachin Kamat
Use the newly introduced devm_ioremap_resource() instead of
devm_request_and_ioremap() which provides more consistent error handling.
devm_ioremap_resource() provides its own error messages; so all explicit
error messages can be removed from the failure code paths.
Signed-off-by: Sachin Kamat
This is the fifth version of the Tegra114 clockframework. It is based on the
for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git and
http://www.spinics.net/lists/arm-kernel/msg220452.html.
It has been boottested on Pluto.
Changes from v4:
* Split the new PLL
* Arnaldo Carvalho de Melo a...@infradead.org wrote:
Hi Ingo,
Please consider pulling,
- Arnaldo
The following changes since commit 152fefa921535665f95840c08062844ab2f5593e:
Merge tag 'perf-core-for-mingo' of
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into
On Fri, Feb 01, 2013 at 02:32:03PM +0800, zergmk2 wrote:
I've verified your patch and spi bus worked properly on PXA910 platform.
I used a debug tool to send data on spi bus, and I connected spi out pin
and spi in pin.
So when I read data from spi bus, it should be what I sent from spi bus.
This is the fifth version of the Tegra114 clockframework. It is based on the
for-next branch of
git://git.kernel.org/pub/scm/linux/kernel/git/swarren/linux-tegra.git and
http://www.spinics.net/lists/arm-kernel/msg220452.html.
It has been boottested on Pluto.
Changes from v4:
* Split the new PLL
Refactor the PLL programming code to make it useable by the new PLL types
introduced by Tegra114.
The following changes were done:
* Split programming the PLL into updating m,n,p and updating cpcon
* Move locking from _update_pll_cpcon() to clk_pll_set_rate()
* Introduce _get_pll_mnp() helper
*
On Thu 2013-01-31 23:38:27, Phil Turmel wrote:
On 01/31/2013 10:13 PM, paul.sz...@sydney.edu.au wrote:
[trim /] Does not that prove that PAE is broken?
Please, Paul, take *yes* for an answer. It is broken. You've received
multiple dissertations on why it is going to stay that way. Unless
Not all PLLs in Tegra114 have a bypass bit. Adapt the common code to only use
this bit when available.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
drivers/clk/tegra/clk-pll.c | 15 ++-
drivers/clk/tegra/clk.h |8 +---
2 files changed, 15 insertions(+),
Some PLLs in Tegra114 don't use a power of 2 mapping for the post divider.
Introduce a table based approach and switch PLLU to it.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
drivers/clk/tegra/clk-pll.c | 38 --
Tegra114 introduces new PLL types. This requires new clocktypes as well
as some new fields in the pll structure.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
drivers/clk/tegra/clk-pll.c | 719 +++
drivers/clk/tegra/clk.h | 47 +++
2
We will need some tegra peripheral clocks with the CLK_IGNORE_UNUSED flag,
most notably mselect, which is a bridge between AXI and most peripherals.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
drivers/clk/tegra/clk-periph.c | 11 ++-
drivers/clk/tegra/clk-tegra20.c |
hi,
this fix is related to following discussion:
http://thread.gmane.org/gmane.linux.kernel.perf.user/1144
The fix is straightforward, but I think we could have
same issue in perf_pmu_migrate_context function as well,
which is used so far only by uncore bits.
I think the perf_pmu_migrate_context
Workaround a hardware bug in MSENC during clock enable.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
drivers/clk/tegra/clk-periph-gate.c |9 +
drivers/clk/tegra/clk.h |1 +
2 files changed, 10 insertions(+), 0 deletions(-)
diff --git
The device tree binding models Tegra114 CAR (Clock And Reset) as a single
monolithic clock provider.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
.../bindings/clock/nvidia,tegra114-car.txt | 311
1 files changed, 311 insertions(+), 0 deletions(-)
On Fri 2013-02-01 11:20:44, Pavel Machek wrote:
On Thu 2013-01-31 23:38:27, Phil Turmel wrote:
On 01/31/2013 10:13 PM, paul.sz...@sydney.edu.au wrote:
[trim /] Does not that prove that PAE is broken?
Please, Paul, take *yes* for an answer. It is broken. You've received
multiple
Add references to tegra_car clocks for the basic device nodes.
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
arch/arm/boot/dts/tegra114.dtsi |7 ++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/arch/arm/boot/dts/tegra114.dtsi
* Arnaldo Carvalho de Melo a...@infradead.org wrote:
From: Sukadev Bhattiprolu suka...@linux.vnet.ibm.com
Rename EVENT_ATTR() to PMU_EVENT_ATTR() and make it global so it is
available to all architectures.
Further to allow architectures flexibility, have PMU_EVENT_ATTR() pass
in the
Signed-off-by: Peter De Schrijver pdeschrij...@nvidia.com
---
drivers/clk/tegra/clk.c |1 +
drivers/clk/tegra/clk.h |7 +++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/clk/tegra/clk.c b/drivers/clk/tegra/clk.c
index a603b9a..a328365 100644
---
These patches try to support context tracking for Power arch, beginning with
64-bit pSeries. The codes are ported from that of the x86_64, and in each
patch, I listed the corresponding patch for x86.
Would you please help review and give your comments?
Thanks, Zhong
Li Zhong (5):
powerpc:
This patch allows RCU usage in do_notify_resume, e.g. signal handling.
It corresponds to
[PATCH] x86: Exit RCU extended QS on notify resume
commit edf55fda35c7dc7f2d9241c3abaddaf759b457c6
Signed-off-by: Li Zhong zh...@linux.vnet.ibm.com
---
arch/powerpc/kernel/signal.c |5 +
1 file
Start context tracking support from pSeries.
Signed-off-by: Li Zhong zh...@linux.vnet.ibm.com
---
arch/powerpc/platforms/pseries/Kconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/platforms/pseries/Kconfig
b/arch/powerpc/platforms/pseries/Kconfig
index 837cf49..a9570fe
This is the exception hooks for context tracking subsystem, including
data access, program check, single step, instruction breakpoint, machine check,
alignment, fp unavailable, altivec assist, unknown exception, whose handlers
might use RCU.
This patch corresponds to
[PATCH] x86: Exception hooks
This patch corresponds to
[PATCH] x86: Use the new schedule_user API on userspace preemption
commit 0430499ce9d78691f3985962021b16bf8f8a8048
Signed-off-by: Li Zhong zh...@linux.vnet.ibm.com
---
arch/powerpc/include/asm/context_tracking.h | 11 +++
arch/powerpc/kernel/entry_64.S
This is the syscall slow path hooks for context tracking subsystem,
corresponding to
[PATCH] x86: Syscall hooks for userspace RCU extended QS
commit bf5a3c13b939813d28ce26c01425054c740d6731
TIF_MEMDIE is moved to the second 16-bits (with value 17), as it seems there
is no asm code using it.
Commit-ID: 11859e821761e9738c4d8a0e7d6ca1cc2e0d37e8
Gitweb: http://git.kernel.org/tip/11859e821761e9738c4d8a0e7d6ca1cc2e0d37e8
Author: Arnaldo Carvalho de Melo a...@redhat.com
AuthorDate: Wed, 30 Jan 2013 13:25:53 -0300
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu,
Hello Nicolas,
thanks for your review!
Cheers,
Bernd
--
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
Commit-ID: 0de233b9c4f8c83b2cb655bfdbec306c8da81199
Gitweb: http://git.kernel.org/tip/0de233b9c4f8c83b2cb655bfdbec306c8da81199
Author: Arnaldo Carvalho de Melo a...@redhat.com
AuthorDate: Wed, 30 Jan 2013 14:01:20 -0300
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu,
Commit-ID: 97f63e4a2cf88e9d7bc086a1c3f10fa41c9174df
Gitweb: http://git.kernel.org/tip/97f63e4a2cf88e9d7bc086a1c3f10fa41c9174df
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:29 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: 8d7d8474d7b04dc89aa653d67425b61d3ff5c6f0
Gitweb: http://git.kernel.org/tip/8d7d8474d7b04dc89aa653d67425b61d3ff5c6f0
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:30 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: a8bb559bd4eff5c71601e2e61a4bd1deef44a03c
Gitweb: http://git.kernel.org/tip/a8bb559bd4eff5c71601e2e61a4bd1deef44a03c
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:31 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: 6e1f601a10cbaa5cda869f844292dd81c519a8e7
Gitweb: http://git.kernel.org/tip/6e1f601a10cbaa5cda869f844292dd81c519a8e7
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:32 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Commit-ID: 29d720ed5f897d7e26f6b36c12c7704dc200d107
Gitweb: http://git.kernel.org/tip/29d720ed5f897d7e26f6b36c12c7704dc200d107
Author: Namhyung Kim namhyung@lge.com
AuthorDate: Tue, 22 Jan 2013 18:09:33 +0900
Committer: Arnaldo Carvalho de Melo a...@redhat.com
CommitDate: Thu, 31 Jan
Hi,
This set of patches are aimed to allow truncate_inode_pages_range() handle
ranges which are not aligned at the end of the page. Currently it will
hit BUG_ON() when the end of the range is not aligned. Punch hole feature
however can benefit from this ability saving file systems some work not
-invalidatepage() aop now accepts range to invalidate so we can make
use of it in all ext4 invalidatepage routines.
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/ext4/inode.c | 47 ++
include/trace/events/ext4.h | 22
The discard_partial_page_buffers is no longer used anywhere so we can
simply remove it including the *_no_lock variant and
EXT4_DISCARD_PARTIAL_PG_ZERO_UNMAPPED define.
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/ext4/ext4.h |8 --
fs/ext4/inode.c | 206
Currently punch hole is disabled in file systems with bigalloc
feature enabled. However the recent changes in punch hole patch should
make it easier to support punching holes on bigalloc enabled file
systems.
This commit changes partial_cluster handling in ext4_remove_blocks(),
ext4_ext_rm_leaf()
In commits 5f95d21fb6f2aaa52830e5b7fb405f6c71d3ab85 and
30bc2ec9598a1b156ad75217f2e7d4560efdeeab we've reworked punch_hole
implementation and there is noting holding us back from using punch hole
on file system with bigalloc feature enabled.
This has been tested with fsx and xfstests.
Add end variable.
Signed-off-by: Lukas Czerner lczer...@redhat.com
---
fs/ext4/extents.c |6 +++---
include/trace/events/ext4.h | 21 ++---
2 files changed, 17 insertions(+), 10 deletions(-)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index
1 - 100 of 1300 matches
Mail list logo
