From: Namhyung Kim
The context menu in TUI hists browser checks corresponding sort keys
when creating the menu item. But hotkey actions lacks these checks so
it can filter using incorrect info.
For example, default sort key of 'perf top' doesn't contain 'comm' or
'pid' sort key so each hist ent
From: Namhyung Kim
It's not used anymore and the output format is accessed by the hpp_list
pointer instead when hierarchy is enabled. Let's get rid of it.
Signed-off-by: Namhyung Kim
Tested-by: Jiri Olsa
Cc: Andi Kleen
Cc: David Ahern
Cc: Peter Zijlstra
Cc: Stephane Eranian
Cc: Wang Nan
://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-20160310
for you to fetch changes up to 206cab651d07563d766c7f4cb73f858c5df3dec5:
perf stat: Add --metric-only support for -A (2016-03-10 16:50:47 -0300
From: Arnaldo Carvalho de Melo
While building on a Docker container for ubuntu and installing package
by package one ends up with:
MKDIR/tmp/build/util/
CC /tmp/build/util/genelf.o
util/genelf.c:22:19: fatal error: dwarf.h: No such file or directory
#include
On Wed, Mar 09, 2016 at 03:01:46PM +0100, Petr Mladek wrote:
> LivePatch framework deserves some documentation, definitely.
> This is an attempt to provide some basic info. I hope that
> it will be useful for both LivePatch producers and also
> potential developers of the framework itself.
>
> Sig
On Thu, Mar 10, 2016 at 01:24:11PM -0700, Toshi Kani wrote:
> I am not familiar with PPRO_FEATURES,
That's the feature bits of the "qemu32" model, and others, in qemu.
> but shouldn't 'flags' in /proc/cpuinfo show "pat" when X86_FEATURE_PAT is set?
static void early_init_intel(struct cpuinfo_x86
From: Jiri Olsa
Pass perf_hpp_list all the way through setup_sort_list so that the sort
entry can be added on the arbitrary list.
Signed-off-by: Jiri Olsa
Acked-by: Namhyung Kim
Cc: David Ahern
Cc: Jiri Olsa
Cc: Peter Zijlstra
Link: http://lkml.kernel.org/r/20160309100417.ga30...@krava.redh
From: Andi Kleen
Add metric only support for -A too. This requires a new print function
that prints the metrics in the right order.
v2: Fix manpage
v3: Simplify nrcpus computation
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Link:
http://lkml.kernel.org/r/1457049458-28956-7-git-send-email-a
Hi Piotr,
[auto build test WARNING on next-20160310]
[cannot apply to tip/x86/core v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Piotr-Henryk-Dabrowski
From: Andi Kleen
With all the recently added fields in the perf stat CSV output we should
finally document them in the man page. Do this here.
v2: Fix fields in documentation (Jiri)
v3: fix order of fields again (Jiri)
v4: Change order again.
v5: Document more fields (Jiri)
v6: Move time stamp f
From: Vivien Didelot
Date: Mon, 7 Mar 2016 18:24:17 -0500
> Apply a few non-functional changes on the port state setter:
>
> * add a dynamic debug message with state names to track changes
> * explicit states checking instead of assuming their numeric values
> * lock mutex only once when
From: Vivien Didelot
Date: Mon, 7 Mar 2016 18:24:39 -0500
> The port register 0x07 contains more options than just the default VID,
> even though they are not used yet. So prefer a read then write operation
> over a direct write.
>
> This also allows to keep track of the change through dynamic
From: Vivien Didelot
Date: Mon, 7 Mar 2016 18:24:52 -0500
> There is no need to change the 802.1Q port mode for the same value.
> Thus avoid such message:
>
> [ 401.954836] dsa dsa@0 lan0: 802.1Q Mode: Disabled (was Disabled)
>
> Signed-off-by: Vivien Didelot
Applied.
From: Nick Wang
Date: Tue, 8 Mar 2016 13:52:28 +0800
> File "inet_connection_sock.h" is a common share header that not can
> be use for one module, so use pr_devel instead of pr_debug is OK.
Not really, we only want these printks to do anything only when debug
printk's are enabled.
We don't w
From: Chunhao Lin
Date: Tue, 8 Mar 2016 16:51:05 +0800
> For pcie nic, after setting link speed and thers is no link driver does not
> need
> to do phy reset untill link up.
"there's", "until"
> For some pcie nics, to do this will also reset phy speed down counter and
> prevent
> phy from au
Hi Stefan,
[auto build test ERROR on shawnguo/for-next]
[also build test ERROR on v4.5-rc7]
[cannot apply to next-20160310]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Stefan-Agner/ARM
From: Neil Armstrong
Date: Tue, 8 Mar 2016 10:36:20 +0100
> The initial commit badly merged into the dsa_resume method instead
> of the dsa_remove_dst method.
> As consequence, the dst->master_netdev->dsa_ptr is not set to NULL on
> removal and re-bind of the dsa device fails with error -17.
>
From: John Crispin
Date: Tue, 8 Mar 2016 11:29:53 +0100
> This series adds support for the Mediatek ethernet core found on current ARM
> based SoCs. The driver works on MT2701 and MT7623 SoCs
>
> Instead of trying to upstream everything at once I decided to concentrate on
> the important parts
From: Fenghua Yu
A few new AVX-512 instruction groups/features are added in cpufeatures.h
for enuermation: AVX512DQ, AVX512BW, and AVX512VL.
The specification for latest AVX-512 including the features can be found at
https://software.intel.com/sites/default/files/managed/07/b7/319433-023.pdf
Si
LGTM. It's very late in the cycle so I'll queue all three for 4.6-rc1
and I tagged the first two patches (not this one) for -stable
backporting.
On 03/10/2016 04:23 PM, Fenghua Yu wrote:
> A few new AVX-512 instruction groups/features are added in cpufeatures.h
> for enuermation: AVX512DQ, AVX512BW, and AVX512VL.
>
> The specification for latest AVX-512 including the features can be found at
> https://software.intel.com/sites/default/files
On Wed, Mar 09, 2016 at 03:30:15PM -0700, Jonathan Corbet wrote:
> Applied to the docs tree, thanks.
Where can I find the docs tree on kernel.org?
Thanks
--
Philippe Loctaux
This patch was recently backported to 4.1.19, and when I merged it with -rt,
the following bug triggered:
===
[ INFO: suspicious RCU usage. ]
4.1.19-test-rt22+ #1 Not tainted
---
/work/rt/stable-rt.git/kernel/workqueue.c:608 sched RCU, wq->mu
Add a reset-controller driver for performing reset management of
various devices present on the SoC, with the reset registers shared
between devices in a common register memory space. This driver uses
the syscon/regmap frameworks to actually implement the various reset
functionalities needed by the
On Thu, Mar 10, 2016 at 10:33:49AM -0800, Linus Torvalds wrote:
> On Thu, Mar 10, 2016 at 6:58 AM, Ric Wheeler wrote:
> >
> > What was objectionable at the time this patch was raised years back (not
> > just to me, but to pretty much every fs developer at LSF/MM that year)
> > centered on the conc
Add syscon reset controller binding. This will hook to the reset
framework and use syscon/regmap to set reset bits. This allows
reset control of individual SoC subsytems and devices with
memory-mapped reset registers in a common register memory
space.
Signed-off-by: Andrew F. Davis
[s-a...@ti.com
Some SoCs contain reset controls for modules that are memory-mapped to
areas shared with other module configuration settings. This requires
synchronization across all drivers accessing this memory area. This
series adds a generic SYSCON reset driver to allow resets toggled
by bits in memory-mapped
On 10/03/16 20:56, Chris Boot wrote:
> On 05/03/16 09:33, Nicholas A. Bellinger wrote:
>> On Sat, 2016-03-05 at 08:45 +, Chris Boot wrote:
>>> Are these in linux-next or another branch somewhere I can easily clone
>>> them from?
>>
>> The patch series is in target-pending/for-next.
>
> Hi Nic,
> "Joseph" == Joseph CHANG writes:
> Enable chip's EP3 interrupt to get the link-up notify soon
> immediately.
Sorry, what do you mean about 'soon immediately'?
> +
> +/* Always return 8-bytes data to host per interrupt-interval */
> +dm_write_reg(dev, DM_USB_CT
On Sun, Mar 06 2016, Nicolai Stange wrote:
> + *
> + * Allow any ongoing concurrent call into debugfs_remove() or
> + * debugfs_remove_recursive() blocked by a former call to
> + * debugfs_use_file_start() to proceed and return to its caller.
> + */
> +static void debugfs_use_file_finish(int srcu
On Thursday, March 10, 2016 10:54:29 AM Lv Zheng wrote:
> It is reported that the following commit triggers regressions:
> Linux commit: efaed9be998b5ae0afb7458e057e5f4402b43fa0
> ACPICA commit: 31178590dde82368fdb0f6b0e466b6c0add96c57
> Subject: ACPICA: Events: Enhance acpi_ev_execute_reg_metho
From: Dave Hansen
Kirill Shutemov pointed this out to me.
The tip tree currently has commit:
dfb4a70f2 [x86/cpufeature, x86/mm/pkeys: Add protection keys related
CPUID definitions]
whioch added support for two new CPUID bits: X86_FEATURE_PKU and
X86_FEATURE_OSPKE. But, those bits we
On Thu, Mar 10, 2016 at 06:39:15PM +0200, Jarkko Sakkinen wrote:
> Some might want to use this in a way that the created virtual device
> is not closed when /dev/vtpmx is closed.
No, there is no reason to create an API like that - TPM's are
stateful, one cannot close the server side and re-connect
On Thursday, March 10, 2016 04:10:36 PM Richard Cochran wrote:
> The function, cpufreq_quick_get, accesses the global 'cpufreq_driver' and
> its fields without taking the associated lock, cpufreq_driver_lock.
>
> Without the locking, nothing guarantees that 'cpufreq_driver' remains
> consistent du
On Thu, Mar 10, 2016 at 01:30:34PM -0800, Andrew Morton wrote:
>
> LGTM. It's very late in the cycle so I'll queue all three for 4.6-rc1
> and I tagged the first two patches (not this one) for -stable
> backporting.
Sounds good, thank you.
On Thu, 2016-03-10 at 22:07 +0100, Borislav Petkov wrote:
> On Thu, Mar 10, 2016 at 01:24:11PM -0700, Toshi Kani wrote:
> > I am not familiar with PPRO_FEATURES,
>
> That's the feature bits of the "qemu32" model, and others, in qemu.
>
> > but shouldn't 'flags' in /proc/cpuinfo show "pat" when X8
On Thursday, March 10, 2016 11:56:14 AM Peter Zijlstra wrote:
> On Thu, Mar 10, 2016 at 11:30:08AM +0100, Peter Zijlstra wrote:
> > On Thu, Mar 10, 2016 at 05:23:54PM +0700, Vincent Guittot wrote:
> >
> > > > No, since its a compile time thing, we can simply do:
> > > >
> > > > #ifdef arch_scale_f
Hi Piotr,
[auto build test ERROR on next-20160310]
[cannot apply to tip/x86/core v4.5-rc7 v4.5-rc6 v4.5-rc5 v4.5-rc7]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Piotr-Henryk-Dabrowski/cpu
On Thu, 10 Mar 2016 01:16:57 +0100 Rasmus Villemoes
wrote:
> Commit 7bd3e239d6c6 ("locking: Remove atomicy checks from
> {READ,WRITE}_ONCE") removed said warning.
>
> Acked-by: Christian Borntraeger
> Signed-off-by: Rasmus Villemoes
> ---
> Andrew, can you pick this up please?
>
> include/l
On 06/03/2016 at 12:43:57 +0300, Alexander Kochetkov wrote :
> Year field must be in BCD format, according to
> hym8563 datasheet.
>
> Due to the bug year 2016 became 2010.
>
> Signed-off-by: Alexander Kochetkov
> ---
> drivers/rtc/rtc-hym8563.c |2 +-
> 1 file changed, 1 insertion(+), 1 de
On Wed, Mar 09, 2016 at 05:13:55PM -0500, Jessica Yu wrote:
> Put all actions in complete_formation() that are performed after
> module->state is set to MODULE_STATE_COMING into a separate function
> prepare_coming_module(). This split prepares for the removal of the
> livepatch module notifiers in
From: Rafael J. Wysocki
If the current value of MPERF or the current value of TSC is the
same as the previous one, respectively, intel_pstate_sample() bails
out early and skips the sample.
However, intel_pstate_adjust_busy_pstate() is still called in that
case which is not correct, so modify int
On Wed, Mar 09, 2016 at 05:13:57PM -0500, Jessica Yu wrote:
> Remove the livepatch module notifier in favor of directly enabling and
> disabling patches to modules in the module loader. Hard-coding the
> function calls ensures that ftrace_module_enable() is run before
> klp_module_coming() during m
On Thursday, March 10, 2016 10:32:04 AM Jarkko Nikula wrote:
> On 03/10/2016 01:34 PM, Xiangliang Yu wrote:
> > Add device HID AMDI0010 to match the AMD ACPI Vendor ID (AMDI) that
> > was registered in http://www.uefi.org/acpi_id_list, and the I2C
> > controller on future AMD paltform will use the
On Tue, 8 Mar 2016, Peter Zijlstra wrote:
On Mon, Mar 07, 2016 at 11:27:26PM +, Luck, Tony wrote:
+ bytes = mbm_current->interval_bytes * MSEC_PER_SEC;
+ do_div(bytes, diff_time);
+ mbm_current->bandwidth = bytes;
+ mbm_current->inte
On 07/03/2016 at 09:03:02 -0600, Josh Poimboeuf wrote :
> objtool reports the following warnings:
>
> drivers/rtc/rtc-ds1685.o: warning: objtool: ds1685_rtc_work_queue()+0x0:
> duplicate frame pointer save
> drivers/rtc/rtc-ds1685.o: warning: objtool: ds1685_rtc_work_queue()+0x3:
> duplicate
On Mon, 7 Mar 2016, Peter Zijlstra wrote:
On Tue, Mar 01, 2016 at 03:48:26PM -0800, Vikas Shivappa wrote:
Lot of the scheduling code was taken out from Tony's patch and a 3-4
lines of change were added in the intel_cqm_event_read. Since the timer
is no more added on every context switch this
On Tuesday, March 08, 2016 10:52:10 AM Joshua Hunt wrote:
> While investigating a possible memory leak using kmemleak I came across the
> following five leaks coming from APEI and ERST:
>
> unreferenced object 0x880402b6ee80 (size 32):
> comm "swapper/0", pid 1, jiffies 4294669373 (age 318.1
On Thu, 2016-03-10 at 23:45 +0100, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> If the current value of MPERF or the current value of TSC is the
> same as the previous one, respectively, intel_pstate_sample() bails
> out early and skips the sample.
>
> However, intel_pstate_adjust_busy
>> drivers/acpi/apei/apei-base.c |6 --
>> drivers/acpi/apei/erst.c |3 +++
>> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> Tony, Boris, should I apply these?
Rafael,
Yes please.
-Tony
On 10/03/16 21:52, Chris Boot wrote:
> On 10/03/16 20:56, Chris Boot wrote:
>> On 05/03/16 09:33, Nicholas A. Bellinger wrote:
>>> On Sat, 2016-03-05 at 08:45 +, Chris Boot wrote:
Are these in linux-next or another branch somewhere I can easily clone
them from?
>>>
>>> The patch serie
> Le 6 mars 2016 à 20:53, Andreas Färber a écrit :
>
> Signed-off-by: Andreas Färber
> ---
> v2 -> v3:
> * Adopted wakeup-source instead of gpio-key,wakeup (Julien)
> * Dropped gpio-keys #address-cells and #size-cells properties (Julien)
> * Dropped power button reg property (Julien)
> * Adopte
A release candidate Git v2.8.0-rc2 is now available for testing
at the usual places. It is comprised of 459 non-merge commits
since v2.7.0, contributed by 60 people, 19 of which are new faces.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following publ
The latest maintenance release Git v2.7.3 is now available at
the usual places. This is primarily to sync the maintenance track
with miscellaneous fixes that are scheduled to be part of upcoming
v2.8.0 release.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/
The foll
> Le 8 mars 2016 à 11:16, Andreas Färber a écrit :
>
> Am 08.03.2016 um 10:41 schrieb Julien Chauveau:
>> Le 8 mars 2016 à 09:54, Geert Uytterhoeven a écrit :
>>> On Mon, Mar 7, 2016 at 7:24 PM, Andreas Färber wrote:
Drop #address-cells and #size-cells, which are not required by the
> Le 8 mars 2016 à 11:09, Andreas Färber a écrit :
>
> Am 08.03.2016 um 09:54 schrieb Geert Uytterhoeven:
>> On Mon, Mar 7, 2016 at 7:24 PM, Andreas Färber wrote:
>>> Drop #address-cells and #size-cells, which are not required by the
>>> gpio-keys binding documentation, as button sub-nodes are
> Le 6 mars 2016 à 20:53, Andreas Färber a écrit :
>
> Signed-off-by: Andreas Färber
> ---
> v2 -> v3:
> * Adopted wakeup-source instead of gpio-key,wakeup (Julien)
> * Dropped gpio-keys #address-cells and #size-cells properties (Julien)
> * Dropped power button reg property (Julien)
> * Adopte
On Thursday, March 10, 2016 10:55:56 PM Luck, Tony wrote:
> >> drivers/acpi/apei/apei-base.c |6 --
> >> drivers/acpi/apei/erst.c |3 +++
> >> 2 files changed, 7 insertions(+), 2 deletions(-)
> >
> > Tony, Boris, should I apply these?
>
> Rafael,
>
> Yes please.
OK, applied.
T
On 03/10/2016 01:35 PM, Dave Hansen wrote:
> On 03/10/2016 04:23 PM, Fenghua Yu wrote:
>> A few new AVX-512 instruction groups/features are added in cpufeatures.h
>> for enuermation: AVX512DQ, AVX512BW, and AVX512VL.
>>
>> The specification for latest AVX-512 including the features can be found at
Quoting Rafael J. Wysocki (2016-03-09 15:41:34)
> On Wed, Mar 9, 2016 at 11:15 AM, Juri Lelli wrote:
> > Hi,
> >
> > sorry if I didn't reply yet. Trying to cope with jetlag and
> > talks/meetings these days :-). Let me see if I'm getting what you are
> > discussing, though.
> >
> > On 08/03/16 21:
Use the more normal kernel definition/declaration style.
Done via:
$ git ls-files arch/sparc | \
xargs ./scripts/checkpatch.pl -f --fix-inplace --types=unspecified_int
Signed-off-by: Joe Perches
---
Dunno if you want this, I was just testing an updated version of checkpatch.
Cross-compiled
On Thu, Mar 10, 2016 at 07:03:31PM +0100, Ingo Molnar wrote:
>
> * Rich Felker wrote:
>
> > > So instead of a sticky cancellation flag, we could introduce a sticky
> > > cancellation signal.
> > >
> > > A 'sticky signal' is not cleared from signal_pending() when the signal
> > > handler
> >
On Wednesday, February 10, 2016 03:23:27 PM Brian Norris wrote:
> From: Kaiyen Chang
>
> Silence the following checkpatch warning:
> WARNING: struct dev_pm_ops should normally be const.
>
> Signed-off-by: Kaiyen Chang
> Signed-off-by: Brian Norris
Applied, thanks!
Rafael
From: Tony Luck
Includes all the core infrastructure to measure the total_bytes and
bandwidth.
We have per socket counters for both total system wide L3 external bytes
and local socket memory-controller bytes. The OS does MSR writes to
MSR_IA32_QM_EVTSEL and MSR_IA32_QM_CTR to read the counters
On Sunday, February 28, 2016 08:31:49 PM Colin King wrote:
> From: Colin Ian King
>
> element is &package->package.elements[i] which can never be NULL
> so the check to see if it is NULL is redundant and can be removed.
>
> Detected with static analysis by CoverityScan
>
> Signed-off-by: Colin
On Monday, February 15, 2016 12:52:01 PM Chen Fan wrote:
> Per the x86-specific footnote to PCI spec r3.0, sec 6.2.4, the value 255 in
> the Interrupt Line register means "unknown" or "no connection."
> Previously, when we couldn't derive an IRQ from the _PRT, we fell back to
> using the value from
On Saturday, February 06, 2016 02:08:08 AM gr...@linuxhacker.ru wrote:
> From: Oleg Drokin
>
> In debugfs it's not enough to just set file mode to read-only to
> deny write access to a file, instead just don't provide
> the write method unless write access is really requested.
>
> Signed-off-by:
Currently cqm(cache quality of service monitoring) is grouping all
events belonging to same PID to use one RMID. However its not counting
all of these different events. Hence we end up with a count of zero for
all events other than the group leader. The patch tries to address the
issue by keeping a
RMID could be allocated or deallocated as part of RMID recycling.
When an RMID is allocated for mbm event, the mbm counter needs to be
initialized because next time we read the counter we need the previous
value to account for total bytes that went to the memory controller.
Similarly, when RMID is
This patch adds a per package timer which periodically updates the
Memory bandwidth counters for the events that are currently active.
Current patch has a periodic timer every 1s since the SDM guarantees
that the counter will not overflow in 1s but this time can be definitely
improved by calibratin
The MBM init patch enumerates the Intel (Memory b/w monitoring)MBM and
initializes the perf events and datastructures for monitoring the memory
b/w. Its based on original patch series by Tony Luck and Kanaka Juvva.
Memory bandwidth monitoring(MBM) provides OS/VMM a way to monitor
bandwidth from on
On Monday, February 15, 2016 10:40:04 PM Colin King wrote:
> From: Colin Ian King
>
> device_decode is now no longer used, so we may as well remove it.
> Fixes gcc 6 warning:
>
> drivers/acpi/acpi_video.c:221:19: warning: ‘device_decode’ defined
> but not used [-Wunused-const-variable]
> stati
Fixes the hotcpu notifier leak and other global variable memory leaks
during cqm(cache quality of service monitoring) initialization.
Reviewed-by: Tony Luck
Signed-off-by: Vikas Shivappa
---
arch/x86/kernel/cpu/perf_event_intel_cqm.c | 43 ++
1 file changed, 32 inser
The patch series has two preparatory patch for cqm and then 4 MBM
patches. Patches are based on tip perf/core.
Thanks to Thomas and PeterZ for feedback on V5 and have tried to
implement feedback in this version.
Memory bandwitdh monitoring(MBM) provides OS/VMM a way to monitor
bandwidth from one
On Tuesday, March 01, 2016 01:31:45 PM Timur Tabi wrote:
> From: Harb Abdulhamid
>
> An error message is printed for resources of type 19, which is a valid
> supported resource type. The Firmware Test Suite tool (fwts) reports
> this as a test failure. This change fixes the false test failures
Document and match the brcm,brcmnand-v6.2 compatible string, the controller has
a register layout identical to the v6.0 version and supports prefetch. Update
the
command shift logic to account for v6.2 controller which are the first ones to
use a shift of 0 (6.1 used a shift of 24).
Signed-off-by
On Wednesday, March 02, 2016 02:16:02 PM Lv Zheng wrote:
> This patchset improves initrd override mechanism.
>
> Lv Zheng (2):
> ACPI / OSL: Cleanup initrd table override code
> ACPI / OSL: Add support to install tables via initrd
>
> drivers/acpi/internal.h |1 +
> drivers/acpi/osl.c
On Wed, Feb 10, 2016 at 02:23:25PM -0800, Andrew Duggan wrote:
> Synaptics uses the Register Mapped Interface (RMI) protocol as a
> communications interface for their devices. This driver adds the core
> functionality needed to interface with RMI4 devices.
>
> RMI devices can be connected to the h
The mm-of-the-moment snapshot 2016-03-10-15-49 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 wi
From: Matthew Wilcox
ext4 needs to reserve enough space in the journal to allocate a PUD-sized
page.
Signed-off-by: Matthew Wilcox
---
fs/ext4/file.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/ext4/file.c b/fs/ext4/file.c
index a2f975e..b966b17 100644
--- a/fs/ext4/file.c
+++ b
From: Matthew Wilcox
The x86-specific code needed to support the PUD uses in the transparent
hugepages code.
Signed-off-by: Matthew Wilcox
---
arch/x86/Kconfig | 1 +
arch/x86/include/asm/paravirt.h | 11 +++
arch/x86/include/asm/paravirt_types.h | 2 +
arch/x86
On Thu, Mar 10, 2016 at 01:39:43PM +0100, Oliver Neukum wrote:
> On Tue, 2016-03-08 at 15:53 +0800, Lu Baolu wrote:
>
> > diff --git a/Documentation/ABI/testing/sysfs-bus-platform
> > b/Documentation/ABI/testing/sysfs-bus-platform
> > index 5172a61..a2261cb 100644
> > --- a/Documentation/ABI/test
I recently got the order of arguments to VM_BUG_ON_VMA the wrong way
around, which was only noticable when compiling with CONFIG_DEBUG_VM.
Prevent the next mistake of this kind by making the macros evaluate both
their arguments at compile time (this has no effect on the built kernel).
Signed-off-b
This patch updates the GPMC's DT DMA property to reflect the updated eDMA
bindings.
Fixes: cce1ee000187 ("ARM: DTS: am437x: Use the new DT bindings for the eDMA3")
Signed-off-by: Franklin S Cooper Jr
---
Version 4 changes:
Split into its own commit. Use proper Fixes syntax.
arch/arm/boot/dts/a
Now that the PMD and PUD fault handlers are passed pgoff, there's no
need to calculate it themselves.
Signed-off-by: Matthew Wilcox
---
fs/dax.c | 26 --
1 file changed, 12 insertions(+), 14 deletions(-)
diff --git a/fs/dax.c b/fs/dax.c
index c5d87be..5db3841 100644
---
Based on DMA documentation and testing using high memory buffer when
doing dma transfers can lead to various issues including kernel
panics.
To workaround this simply use cpu copy. The amount of high memory
buffers used are very uncommon so no noticeable performance hit should
be seen.
Signed-off
On Tue, Mar 08, 2016 at 01:01:09PM -0800, Joe Perches wrote:
> On Tue, 2016-03-08 at 21:40 +0100, Rasmus Villemoes wrote:
> > Passing overlapping source and destination is fragile, and in this
> > case we can even simplify the code and avoid the huge stack buffer by
> > using the %p extension for p
We have customer demand to use 1GB pages to map DAX files. Unlike the 2MB
page support, the Linux MM does not currently support PUD pages, so I have
attempted to add support for the necessary pieces for DAX huge PUD pages.
Filesystems still need work to allocate 1GB pages. With ext4, I can
only
When i_mmap_lock (or the page lock) was the only protection against
truncate, we checked i_size at the beginning of the fault handler,
then rechecked it after acquiring the lock. Since the fliesystems now
exclude truncate from racing with the fault handler, we no longer need
to recheck i_size. We
Add additional details to the GPMC NAND documentation to clarify
what is needed to enable NAND DMA prefetch.
Signed-off-by: Franklin S Cooper Jr
---
Documentation/devicetree/bindings/bus/ti-gpmc.txt | 7 ++-
Documentation/devicetree/bindings/mtd/gpmc-nand.txt | 2 +-
2 files changed, 7 ins
This patch updates the GPMC's DT DMA property to reflect the updated eDMA
bindings.
Fixes: b5e509066074 ("ARM: DTS: am33xx: Use the new DT bindings for the eDMA3")
Signed-off-by: Franklin S Cooper Jr
---
Version 4 changes:
Split in its own commit. Uses correct syntax for Fixes
arch/arm/boot/dt
The prefetch engine sends a dma request once a FIFO threshold has
been met. No other requests are received until the previous request
is handled.
Starting an edma transfer (dma_async_issue_pending) results in any
previous event for the dma channel to be cleared. Therefore, starting
the prefetch en
NAND DMA prefetch has been broken for awhile and seems to have only
worked for SDMA based devices
This patchset fixes DMA prefetch to work on both EDMA and SDMA devices
Test on:
am335x gp evm
am437x gp evm
am37x gp evm
This rev is pretty much the same as v2 which was blocked due to
dependencies
Switch from dma_request_channel to allow passing dma channel
information from DT rather than hardcoding a value.
Also provide a handle to the GPMC's dev so it can be used to parse the DMA
channel information within the GPMC's DT node.
Signed-off-by: Franklin S Cooper Jr
---
Version 4 changes:
Pa
The dma channel information is located within the GPMC node which is the
NAND's parent node. The NAND driver requires a handle to the GPMC's dev
to properly parse the DMA properties. Therefore, set the NAND's parent dev
to the GPMC's dev so it can be referenced within the driver.
Signed-off-by: Fr
From: Matthew Wilcox
In preparation for adding the ability to handle PUD pages, convert
->pmd_fault to ->huge_fault. huge_fault() takes a vm_fault structure
instead of separate (address, pmd, flags) parameters. The vm_fault
structure is extended to include a union of the different page table
po
x86_32 and x86_64 had diverged slightly in their implementations
of the non-SMP cases for native_ptep_get_and_clear() and
native_pmdp_get_and_clear(). Unify the non-SMP cases in pgtable.h,
leaving only the SMP cases in the other three files.
Signed-off-by: Matthew Wilcox
---
arch/x86/include/as
From: Matthew Wilcox
Spotted during PUD support review.
Reported-by: Kirill A. Shutemov
Signed-off-by: Matthew Wilcox
---
mm/memory.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/mm/memory.c b/mm/memory.c
index a975fd4..12fc10e 100644
--- a/mm/memory.c
+++ b/m
checkpatch whines about these whitespace issues. No code changes.
Signed-off-by: Matthew Wilcox
---
arch/x86/include/asm/pgtable-2level.h | 2 +-
arch/x86/include/asm/pgtable.h| 10 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/arch/x86/include/asm/pgtable-2
From: Matthew Wilcox
The DAX support for transparent huge PUD pages
Signed-off-by: Matthew Wilcox
---
fs/dax.c | 188 +++
1 file changed, 188 insertions(+)
diff --git a/fs/dax.c b/fs/dax.c
index ef46bd8..35f0709 100644
--- a/fs/dax.c
501 - 600 of 794 matches
Mail list logo
