Guenter,
On Mon, Jan 25, 2016 at 6:53 PM, Guenter Roeck
wrote:
> From: Guenter Roeck
>
> Convert driver to use watchdog infrastructure. This includes
> infrastructure support to handle watchdog keepalive if the watchdog
> is running while the watchdog device is closed.
>
> Signed-off-by: Guenter
On 01/29/2016 09:35 AM, Sudeep Holla wrote:
The vexpress hwmon implementation is currently just called vexpress.
This is a problem because it clashes with another module with the same
name in regulators.
This patch renames the vexpress hwmon implementation to vexpress-hwmon
so that there will be
Hi Bjorn,
On 1/29/2016 9:30 AM, Bjorn Helgaas wrote:
Hi Ray,
On Thu, Jan 28, 2016 at 03:37:20PM -0800, Ray Jui wrote:
This patch removes the conditional check that limits the number of
functions to be supported by the internally emulated endpoint device
connected to PAXC. Investigation shows t
On Fri, Jan 29, 2016 at 9:46 AM, Jens Axboe wrote:
> On 01/29/2016 08:18 AM, Dan Williams wrote:
>>
>> +unsigned char *read_dev_sector(struct block_device *bdev, sector_t n,
>> Sector *p)
>> +{
>> struct page *page;
>>
>> - page = read_mapping_page(mapping, (pgoff_t)(n >>
>> (PAGE_CA
On Fri, Jan 29, 2016 at 07:18:41AM -0800, Dan Williams wrote:
> Dynamically enabling DAX requires that the page cache first be flushed
> and invalidated. This must occur atomically with the change of DAX mode
> otherwise we confuse the fsync/msync tracking and violate data
> durability guarantees.
On Fri, Jan 29, 2016 at 02:10:52PM +, Nalla, Ravikanth wrote:
> Hi Mike, Hannes, Ben
> > This seems like a problem that has already been solved with path groups.
> > If the path(s) in your preferred path group are there, multipath will use
> > them. If not, then it will use your less preferre
Cache thrash detection (see a528910e12ec "mm: thrash detection-based
file cache sizing" for details) currently only works on the system
level, not inside cgroups. Worse, as the refaults are compared to the
global number of active cache, cgroups might wrongfully get all their
refaults activated when
On Fri, Jan 29, 2016 at 11:01:00AM +, Felipe F. Tonello wrote:
> add cs4271 and cs42727 support for fsl-asoc-card
>
> Signed-off-by: Felipe F. Tonello
Acked-by: Nicolin Chen
> ---
> Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 9 +
> sound/soc/fsl/Kconfig
Hi,
this is v2 of the per-cgroup thrash detection patches, incorporating
Vladimir's feedback and review tags.
These patches tag the page cache radix tree eviction entries with the
memcg an evicted page belonged to, thus making per-cgroup LRU reclaim
work properly and be as adaptive to new cache w
So far the only sites that needed to exclude charge migration to
stabilize page->mem_cgroup have been per-cgroup page statistics, hence
the name mem_cgroup_begin_page_stat(). But per-cgroup thrash detection
will add another site that needs to ensure page->mem_cgroup lifetime.
Rename these locking
This is a compile-time constant, no need to calculate it on refault.
Signed-off-by: Johannes Weiner
Reviewed-by: Vladimir Davydov
---
mm/workingset.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/mm/workingset.c b/mm/workingset.c
index 61ead9e..3ef92f6 100644
--
On Fri, Jan 29, 2016 at 12:40:14PM -0500, Steven Rostedt wrote:
> [ Added Rusty, as he's still maintainer of the module code ]
>
> On Fri, 29 Jan 2016 11:30:10 -0600
> Josh Poimboeuf wrote:
>
> > On Fri, Jan 29, 2016 at 05:30:46PM +0100, Miroslav Benes wrote:
> > > Otherwise than that it looks g
On 29 January 2016 at 18:18, Javier Martinez Canillas
wrote:
> Hello Michal,
>
> On 01/29/2016 02:07 PM, Michal Suchanek wrote:
>>
>> Hello,
>>
>> after commit a9fa852886fd5a7ccec3b7e9eff75f85072f009c
>>
>> display no longer works on the Snow board. The built-in panel is no
>> longer probed.
>>
>
For per-cgroup thrash detection, we need to store the memcg ID inside
the radix tree cookie as well. However, on 32 bit that doesn't leave
enough bits for the eviction timestamp to cover the necessary range of
recently evicted pages. The radix tree entry would look like this:
[ RADIX_TREE_EXCEPTIO
Per-cgroup thrash detection will need to derive a live memcg from the
eviction cookie, and doing that inside unpack_shadow() will get nasty
with the reference handling spread over two functions.
In preparation, make unpack_shadow() clearly about extracting static
data, and let workingset_refault()
On Sat, Jan 16, 2016 at 05:14:36PM +0100, Alexander Koch wrote:
> Extract integration times as #define constants. This prepares using them
> for delay/timeout length determination.
>
> Signed-off-by: Alexander Koch
> Signed-off-by: Michael Hornung
Tested-by: Andreas Dannenberg
Thanks for the
Bhaktipriya Shridhar writes:
> This patch fixes checkpatch.pl warning in rtw_mlme_ext.c file.
> WARNING: void function return statements are not generally useful
>
> Signed-off-by: Bhaktipriya Shridhar
> ---
> drivers/staging/rtl8723au/core/rtw_mlme_ext.c | 10 --
> 1 file changed, 10 de
On Sat, Jan 16, 2016 at 05:14:37PM +0100, Alexander Koch wrote:
> Change variable type of struct opt3001 members 'ok_to_ignore_lock' and
> 'result_ready' uint16-bitfield of length one to bool.
>
> They are used as bool, let the compiler do the optimization.
>
> Signed-off-by: Alexander Koch
> Si
Hi Tejun,
Can ata_sff_hsm_move grab the lock and save off the task_state,
like this patch?
Thanks,
David
On Fri, Jan 29, 2016 at 02:40:33PM +0100, Dmitry Vyukov wrote:
> On Fri, Jan 29, 2016 at 2:18 PM, Dmitry Vyukov wrote:
> > On Fri, Jan 29, 2016 at 1:23 PM, Tejun Heo wrote:
> >> Hello, Dmi
On Sat, Jan 16, 2016 at 05:14:38PM +0100, Alexander Koch wrote:
> Enable operation of the TI OPT3001 light sensor without having an
> interrupt line available to connect the INT pin to.
>
> In this operation mode, we issue a conversion request and simply wait
> for the conversion time available as
On Fri, Jan 29, 2016 at 11:01:01AM +, Felipe F. Tonello wrote:
> Signed-off-by: Felipe F. Tonello
> ---
> Documentation/devicetree/bindings/sound/fsl-asoc-card.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/sound/fsl-asoc-card.t
Hello.
On 01/29/2016 07:18 PM, Krzysztof Hałasa wrote:
The unclear part here is for IXP4xx, which supports both big-endian
and little-endian configurations. So far, the driver has done
no byteswap in either case. I suspect that is wrong and it would
actually need to swap in one or the other cas
On Sat, Jan 16, 2016 at 05:14:35PM +0100, Alexander Koch wrote:
> This patch series aims at enabling IRQ-less operation for the TI OPT3001 light
> sensor.
Jon,
I was checking to see if the DT bindings have been updated to reflect
the interrupt-less operation however I can't seem to find it in the
From: Dave Hansen
I don't have a strong opinion on whether we need a Kconfig prompt
or not. Protection Keys has relatively little code associated
with it, and it is not a heavyweight feature to keep enabled.
However, I can imagine that folks would still appreciate being
able to disable it.
Not
Memory Protection Keys for User pages is a CPU feature which will
first appear on Skylake Servers, but will also be supported on
future non-server parts (there is also a QEMU implementation). It
provides a mechanism for enforcing page-based protections, but
without requiring modification of the pa
From: Dave Hansen
calc_vm_prot_bits() takes PROT_{READ,WRITE,EXECUTE} bits and
turns them in to the vma->vm_flags/VM_* bits. We need to do a
similar thing for protection keys.
We take a protection key (4 bits) and encode it in to the 4
VM_PKEY_* bits.
Note: this code is not new. It was simpl
From: Dave Hansen
We might not strictly have to make modifictions to
access_error() to check the VMA here.
If we do not, we will do this:
1. app sets VMA pkey to K
2. app touches a !present page
3. do_page_fault(), allocates and maps page, sets pte.pkey=K
4. return to userspace
5. touch instruc
From: Dave Hansen
vma->vm_flags is an 'unsigned long', so has space for 32 flags
on 32-bit architectures. The high 32 bits are unused on 64-bit
platforms. We've steered away from using the unused high VMA
bits for things because we would have difficulty supporting it
on 32-bit.
Protection Key
From: Dave Hansen
We want to modify the Protection Key rights inside the kernel, so
we need to change PKRU's contents. But, if we do a plain
'wrpkru', when we return to userspace we might do an XRSTOR and
wipe out the kernel's 'wrpkru'. So, we need to go after PKRU in
the xsave buffer.
We do
From: Dave Hansen
The syscall-level code is passed a protection key and need to
return an appropriate error code if the protection key is bogus.
We will be using this in subsequent patches.
Note that this also begins a series of arch-specific calls that
we need to expose in otherwise arch-indep
From: Dave Hansen
The Protection Key Rights for User memory (PKRU) is a 32-bit
user-accessible register. It contains two bits for each
protection key: one to write-disable (WD) access to memory
covered by the key and another to access-disable (AD).
Userspace can read/write the register with th
From: Dave Hansen
Protection keys provide new page-based protection in hardware.
But, they have an interesting attribute: they only affect data
accesses and never affect instruction fetches. That means that
if we set up some memory which is set as "access-disabled" via
protection keys, we can s
On 01/27/2016 07:28 PM, Frederic Weisbecker wrote:
On Tue, Jan 19, 2016 at 03:45:04PM -0500, Chris Metcalf wrote:
You asked what happens if nohz_full= is given as well, which is a very
good question. Perhaps the right answer is to have an early_initcall
that suppresses task isolation on any cor
If a breakpoint is triggered under x86 with an int3 that
kdb does not know about, it will report it as a catastrophic
error rather than just assuming it was told to enter the debugger.
The macro that defines the kgdb breakpoint also needs to
conform to the newer gas format without the numbers.
Si
This patch series adds a config option which can be set during compile to
direct the compiler to output a breakpoint instruction anywhere a BUG()
macro has been placed in the kernel to trigger the system to enter a
debugger if a bug is detected by the system. Use of this compile time
option also a
From: Dave Hansen
The arch-specific mm_context_t is a great place to put
protection-key allocation state.
But, we need to initialize the allocation state because pkey 0 is
always "allocated". All of the runtime initialization of
mm_context_t is done in *_ldt() manipulation functions. This
ren
This patch series adds a config option which can be set during compile to
direct the compiler to output a breakpoint instruction anywhere a BUG()
macro has been placed in the kernel to trigger the system to enter a
debugger if a bug is detected by the system. Use of this compile time
option also a
From: Dave Hansen
As discussed earlier, we attempt to enforce protection keys in
software.
However, the code checks all faults to ensure that they are not
violating protection key permissions. It was assumed that all
faults are either write faults where we check PKRU[key].WD (write
disable) or
From: Dave Hansen
This sets the bit in 'cr4' to actually enable the protection
keys feature. We also include a boot-time disable for the
feature "nopku".
Seting X86_CR4_PKE will cause the X86_FEATURE_OSPKE cpuid
bit to appear set. At this point in boot, identify_cpu()
has already run the actu
From: Dave Hansen
This plumbs a protection key through calc_vm_flag_bits(). We
could have done this in calc_vm_prot_bits(), but I did not feel
super strongly which way to go. It was pretty arbitrary which
one to use.
Signed-off-by: Dave Hansen
Cc: linux-...@vger.kernel.org
Cc: linux-a...@vge
From: Dave Hansen
The protection key can now be just as important as read/write
permissions on a VMA. We need some debug mechanism to help
figure out if it is in play. smaps seems like a logical
place to expose it.
arch/x86/kernel/setup.c is a bit of a weirdo place to put
this code, but it al
From: Dave Hansen
I don't have a strong opinion on whether we need this or not.
Protection Keys has relatively little code associated with it,
and it is not a heavyweight feature to keep enabled. However,
I can imagine that folks would still appreciate being able to
disable it.
Here's the opti
Gilad is no longer working for Qualcomm, so I'm taking over (as best as
I can) this driver. Let's just say it's going to be a learning experience.
Rob Herring wrote:
diff --git a/Documentation/devicetree/bindings/net/qcom-emac.txt
b/Documentation/devicetree/bindings/net/qcom-emac.txt
new file
From: Dave Hansen
We try to enforce protection keys in software the same way that we
do in hardware. (See long example below).
But, we only want to do this when accessing our *own* process's
memory. If GDB set PKRU[6].AD=1 (disable access to PKEY 6), then
tried to PTRACE_POKE a target process
From: Dave Hansen
Lots of things seem to do:
vma->vm_page_prot = vm_get_page_prot(flags);
and the ptes get created right from things we pull out
of ->vm_page_prot. So it is very convenient if we can
store the protection key in flags and vm_page_prot, just
like the existing permission
From: Dave Hansen
Today, for normal faults and page table walks, we check the VMA
and/or PTE to ensure that it is compatible with the action. For
instance, if we get a write fault on a non-writeable VMA, we
SIGSEGV.
We try to do the same thing for protection keys. Basically, we
try to make su
From: Dave Hansen
This code matches a fault condition up with the VMA and ensures
that the VMA allows the fault to be handled instead of just
erroring out.
We will be extending this in a moment to comprehend protection
keys.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
b/mm/
From: Dave Hansen
The current get_user_pages() code is a wee bit more complicated
than it needs to be for pte bit checking. Currently, it establishes
a mask of required pte _PAGE_* bits and ensures that the pte it
goes after has all those bits.
This consolidates the three identical copies of t
From: Dave Hansen
This adds the raw instruction to access PKRU as well as some
accessor functions that correctly handle when the CPU does not
support the instruction. We don't use it here, but we will use
read_pkru() in the next patch.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
From: Dave Hansen
Previous documentation has referred to these 4 bits as "ignored".
That means that software could have made use of them. But, as
far as I know, the kernel never used them.
They are still ignored when protection keys is not enabled, so
they could theoretically still get used fo
Hi Doug,
On 01/29/2016 09:52 AM, Doug Anderson wrote:
Guenter,
On Mon, Jan 25, 2016 at 6:53 PM, Guenter Roeck
wrote:
From: Guenter Roeck
Convert driver to use watchdog infrastructure. This includes
infrastructure support to handle watchdog keepalive if the watchdog
is running while the watc
From: Dave Hansen
A protection key fault is very similar to any other access error.
There must be a VMA, etc... We even want to take the same action
(SIGSEGV) that we do with a normal access fault.
However, we do need to let userspace know that something is
different. We do this the same way
From: Dave Hansen
This fills in the new siginfo field: si_pkey to indicate to
userspace which protection key was set on the PTE that we faulted
on.
Note though that *ALL* protection key faults have to be generated
by a valid, present PTE at some point. But this code does no PTE
lookups which s
From: Dave Hansen
Note: "PK" is how the Intel SDM refers to this bit, so we also
use that nomenclature.
This only defines the bit, it does not plumb it anywhere to be
handled.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
b/arch/x86/mm/fault.c |8
1 file changed,
From: Dave Hansen
During a page fault, we look up the VMA to ensure that the fault
is in a region with a valid mapping. But, in the top-level page
fault code we don't need the VMA for much else. Once we have
decided that an access is bad, we are going to send a signal no
matter what and do not
Hi Ard,
On Tue, Jan 26, 2016 at 06:10:27PM +0100, Ard Biesheuvel wrote:
> Code can be found here:
> git://git.linaro.org/people/ard.biesheuvel/linux-arm.git arm64-kaslr-v4a
> https://git.linaro.org/people/ard.biesheuvel/linux-arm.git/shortlog/refs/heads/arm64-kaslr-v4a
The overall series looks fi
From: Dave Hansen
Protection Keys never affect kernel mappings. But, they can
affect whether the kernel will fault when it touches a user
mapping. The kernel doesn't touch user mappings without some
careful choreography and these accesses don't generally result in
oopses. But, if one does, we
From: Dave Hansen
There are two CPUID bits for protection keys. One is for whether
the CPU contains the feature, and the other will appear set once
the OS enables protection keys. Specifically:
Bit 04: OSPKE. If 1, OS has set CR4.PKE to enable
Protection keys (and the RDPKRU/W
From: Dave Hansen
The protection keys register (PKRU) is saved and restored using
xsave. Define the data structure that we will use to access it
inside the xsave buffer.
Note that we also have to widen the printk of the xsave feature
masks since this is feature 0x200 and we only did two charac
This patch series adds a config option which can be set during compile to
direct the compiler to output a breakpoint instruction anywhere a BUG()
macro has been placed in the kernel to trigger the system to enter a
debugger if a bug is detected by the system. Use of this compile time
option also a
On Fri, Jan 29, 2016 at 09:35:22AM -0800, Andy Lutomirski wrote:
> I'll fiddle with that benchmark a little bit. Maybe I can make it
> suck less. If anyone knows a good non-micro benchmark for this, let
> me know.
Yeah, I don't know of a good one. The TLB and all those intermediary
walker caches
From: Dave Hansen
There is a new bit in CR4 for enabling protection keys. We
will actually enable it later in the series.
Signed-off-by: Dave Hansen
Reviewed-by: Thomas Gleixner
---
b/arch/x86/include/uapi/asm/processor-flags.h |2 ++
1 file changed, 2 insertions(+)
diff -puN arch/x86
OK, so I've fixed up my build process to _actually_ build the
nommu code.
One of Vlastimil's comments made me go dig back in to the uprobes
code's use of get_user_pages(). I decided to change both of them
to be "foreign" accesses.
This also fixes the nommu breakage that Vlastimil noted last tim
On Thu, Jan 28, 2016 at 01:38:58PM -0800, Christoph Hellwig wrote:
> On Thu, Jan 28, 2016 at 12:35:04PM -0700, Ross Zwisler wrote:
> > There are a number of places in dax.c that look up the struct block_device
> > associated with an inode. Previously this was done by just using
> > inode->i_sb->s_
Hey, Peter.
On Fri, Jan 29, 2016 at 04:17:39PM +0100, Peter Zijlstra wrote:
> On Fri, Jan 29, 2016 at 06:09:41AM -0500, Tejun Heo wrote:
> > I posted a patch to disable
> > disable flush dependency checks on those workqueues and there's a
> > outreachy project to weed out the users of the old int
From: Dave Hansen
There is an XSAVE state component for Intel Processor Trace (PT).
But, we do not currently use it.
We add a placeholder in the code for it so it is not a mystery and
also so we do not need an explicit enum initialization for Protection
Keys in a moment.
Why don't we use it?
On 01/29/2016 12:01 PM, Steven Rostedt wrote:
> On Thu, Jan 28, 2016 at 02:13:04PM -0600, Corey Minyard wrote:
>> Tomeu, you added that check in
>>
>> [989561de9b5112999475b406557d9c7e9e59c041] PM / Domains: add setter for
>> dev.pm_domain
>>
>> and either something is wrong in the platform device
On 01/29, Robin Murphy wrote:
> So far, we have been blindly assuming that if a memory-mapped timer
> frame exists, then we have access to it. Whilst it's the firmware's
> job to give us non-secure access to frames in the first place, we
> should not rely on it always being generous enough to also
On 01/29, Arnd Bergmann wrote:
> We should not dereference registers as pointers, so use readl/writel
> instead for these registers.
>
> The clock registers are accessed in multiple files, so we have to
> change them all at once.
>
> I stumbled over these registers while looking at something unre
On Fri, Jan 29, 2016 at 05:59:46AM -0500, Tejun Heo wrote:
> fca839c00a12 ("workqueue: warn if memory reclaim tries to flush
> !WQ_MEM_RECLAIM workqueue") implemented flush dependency warning which
> triggers if a PF_MEMALLOC task or WQ_MEM_RECLAIM workqueue tries to
> flush a !WQ_MEM_RECLAIM workq
Hi Jeffrey,
[auto build test ERROR on v4.5-rc1]
[also build test ERROR on next-20160129]
[cannot apply to tip/x86/core]
[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/Jeffrey-Merkey/Add-BUG
On Fri, 2016-01-29 at 23:08 +0530, Sudip Mukherjee wrote:
> On Fri, Jan 22, 2016 at 03:44:16PM +0200, Andy Shevchenko wrote:
> > On Fri, Jan 22, 2016 at 12:53 PM, Sudip Mukherjee
> > wrote:
> > > On Wed, Jan 20, 2016 at 04:24:36PM +0800, Peter Hung wrote:
> > > > Hi Sudip,
> > > >
> > > > Sudip M
On Wed, 27 Jan 2016, Hugh Dickins wrote:
+*
+* The RCU read lock is taken as the inode is finally freed
+* under RCU. If the mapping still matches expectations then the
+* mapping->host can be safely accessed as being a valid inode.
Hi Florian,
thanks for your review!
On mer., janv. 27 2016, Florian Fainelli wrote:
> On 12/01/16 11:10, Gregory CLEMENT wrote:
>> This basic implementation allows to share code between driver using
>> hardware buffer management. As the code is hardware agnostic, there is
>> few helpers, most
Hi Linus,
We have some fixes queued up in my for-linus-4.5 branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
for-linus-4.5
Dave had a small collection of fixes to the new free space tree code,
one of which was keeping our sysfs files more up to date with feature
bits a
On Fri, 29 Jan 2016, Davidlohr Bueso wrote:
> On Wed, 27 Jan 2016, Hugh Dickins wrote:
>
> > > + *
> > > + * The RCU read lock is taken as the inode is finally freed
> > > + * under RCU. If the mapping still matches expectations then
> > > the
> > > + * mapping-
giOn 29 January 2016 at 19:26, Catalin Marinas wrote:
> Hi Ard,
>
> On Tue, Jan 26, 2016 at 06:10:27PM +0100, Ard Biesheuvel wrote:
>> Code can be found here:
>> git://git.linaro.org/people/ard.biesheuvel/linux-arm.git arm64-kaslr-v4a
>> https://git.linaro.org/people/ard.biesheuvel/linux-arm.git/s
[Re: [PATCH tip v6 2/5] kbuild: Add option to turn incompatible pointer check
into error] On 29/01/2016 (Fri 13:17) Daniel Wagner wrote:
> On 01/28/2016 03:44 PM, Daniel Wagner wrote:
> > +# enforce correct pointer usage
> > +KBUILD_CFLAGS += $(call cc-option,-Werror=incompatible-pointer-types)
>
On Fri, 2016-01-29 at 18:37 +0800, Yongji Xie wrote:
> On 2016/1/29 6:46, Alex Williamson wrote:
> > On Fri, 2016-01-15 at 15:06 +0800, Yongji Xie wrote:
> > > When vfio passthrough a PCI device of which MMIO BARs
> > > are smaller than PAGE_SIZE, guest will not handle the
> > > mmio accesses to th
- Original Message -
> On 2016/1/29 6:46, Alex Williamson wrote:
> > On Fri, 2016-01-15 at 15:06 +0800, Yongji Xie wrote:
> >> MSI-X tables are not allowed to be mmapped in vfio-pci
> >> driver in case that user get to touch this directly.
> >> This will cause some performance issues when
Hi!
On Fri, Jan 29, 2016 at 3:54 AM, Rusty Russell wrote:
> Lucas De Marchi writes:
>> Hi!
>>
>> CC'ing Rusty and mailing lists
>
> Thanks.
>
>> Rusty and ohers: it looks like both CONFIG_CRC32 and
>> CONFIG_CRYPTO_CRC32 can be compiled as module, and they generate
>> modules with the same name,
The policy wrt exports right now is "put it next to the definition
of object being exported, unless it's in assembler". The reasons for having
an export near the definition are obvious - it's easier to keep things
in sync that way, the fact that function can be called by modules is
obvious
From: Al Viro
Collect the symbols exported by anything that goes into lib.a and
add an empty object (lib-exports.o) with explicit undefs for each
of those to obj-y.
That allows to relax the rules regarding the use of exports in
lib-* objects - right now an object with export can be in lib-*
only
From: Al Viro
unreachable code, unused macros...
Signed-off-by: Al Viro
---
arch/sparc/lib/memcpy.S | 79 -
1 file changed, 79 deletions(-)
diff --git a/arch/sparc/lib/memcpy.S b/arch/sparc/lib/memcpy.S
index d3626cd..8913fea 100644
--- a/arch/s
From: Al Viro
Add asm-usable variants of EXPORT_SYMBOL/EXPORT_SYMBOL_GPL. This
commit just adds the default implementation; most of the architectures
can simply add export.h to asm/Kbuild and start using
from assembler. The area where the things might diverge from default
is the alignment; nor
From: Al Viro
Signed-off-by: Al Viro
---
arch/sparc/include/asm/string.h| 34 +++
arch/sparc/include/asm/string_32.h | 56 --
arch/sparc/include/asm/string_64.h | 44 --
arch/sparc/lib/memcpy.S|
From: Al Viro
Signed-off-by: Al Viro
---
arch/ia64/include/asm/Kbuild | 1 +
arch/ia64/kernel/entry.S | 3 ++
arch/ia64/kernel/esi_stub.S | 2 +
arch/ia64/kernel/head.S | 3 ++
arch/ia64/kernel/ia64_ksyms.c | 94 +--
arch
From: Al Viro
Signed-off-by: Al Viro
---
arch/sparc/include/asm/Kbuild | 1 +
arch/sparc/kernel/Makefile | 2 +-
arch/sparc/kernel/entry.S | 3 +
arch/sparc/kernel/head_32.S| 3 +
arch/sparc/kernel/head_64.S| 7 +-
arch/sparc/kernel/helpers.S
From: Al Viro
Signed-off-by: Al Viro
---
arch/arm/include/asm/Kbuild | 1 +
arch/arm/kernel/Makefile | 2 +-
arch/arm/kernel/armksyms.c| 183 --
arch/arm/kernel/entry-ftrace.S| 3 +
arch/arm/kernel/head.S
From: Al Viro
Signed-off-by: Al Viro
---
arch/powerpc/include/asm/Kbuild | 1 +
arch/powerpc/kernel/Makefile | 4 ---
arch/powerpc/kernel/entry_32.S | 2 ++
arch/powerpc/kernel/entry_64.S | 3 ++
arch/powerpc/kernel/epapr_hcalls.S | 2 ++
arch/powerpc/kernel/fpu.
From: Al Viro
Signed-off-by: Al Viro
---
arch/alpha/include/asm/Kbuild| 1 +
arch/alpha/kernel/Makefile | 2 +-
arch/alpha/kernel/alpha_ksyms.c | 102 ---
arch/alpha/kernel/machvec_impl.h | 6 ++-
arch/alpha/kernel/setup.c
From: Al Viro
the rest of architectures should just use generic-y += export.h in
asm/Kbuild
Signed-off-by: Al Viro
---
arch/m68k/include/asm/export.h | 3 +++
arch/m68k/kernel/Makefile | 2 +-
arch/m68k/kernel/m68k_ksyms.c | 32
arch/m68k/lib/ashldi3.c
From: Al Viro
Signed-off-by: Al Viro
---
arch/x86/entry/entry_32.S| 2 +
arch/x86/entry/entry_64.S| 2 +
arch/x86/entry/thunk_32.S| 3 ++
arch/x86/entry/thunk_64.S| 3 ++
arch/x86/include/asm/export.h| 4 ++
arch/x86/kernel/Makefile | 4 +-
arch
From: Al Viro
Signed-off-by: Al Viro
---
arch/s390/include/asm/Kbuild | 1 +
arch/s390/kernel/Makefile | 2 +-
arch/s390/kernel/entry.S | 6 ++
arch/s390/kernel/mcount.S | 3 +++
arch/s390/kernel/s390_ksyms.c | 15 ---
arch/s390/lib/mem.S | 3 +++
6
The patchset tries to avoid external fragmentation related to migration
fallback. The symptom of this external fragmentation is that there are
lots of allocation failures of order-2 and order-3 pages and many
threads enter allocation slowpath to compact and direct reclaim pages.
This will degrade s
On Fri, Jan 29, 2016 at 07:18:46AM -0800, Dan Williams wrote:
> Avoid populating pagecache when the block device is in DAX mode.
> Otherwise these page cache entries collide with the fsync/msync
> implementation and break data durability guarantees.
>
> Cc: Jan Kara
> Cc: Jeff Moyer
> Cc: Christ
On Fri, Jan 29, 2016 at 10:22:34AM -0300, Ezequiel Garcia wrote:
> On 28 January 2016 at 16:48, Brian Norris wrote:
> > On Thu, Jan 28, 2016 at 04:24:50PM -0300, Ezequiel Garcia wrote:
> >> How about this:
> >>
> >> 1) ioctl(MEMLOCK) the entire flash (SR_SRWD is set)
> >> 2) ioctl(MEMUNLOCK) parti
On Fri, 29 Jan 2016, Josh Poimboeuf wrote:
> On Fri, Jan 29, 2016 at 12:40:14PM -0500, Steven Rostedt wrote:
> > [ Added Rusty, as he's still maintainer of the module code ]
> >
> > On Fri, 29 Jan 2016 11:30:10 -0600
> > Josh Poimboeuf wrote:
> >
> > > On Fri, Jan 29, 2016 at 05:30:46PM +0100,
This helper function only factors out the code flow within each order
during fallback. There is no function change.
Signed-off-by: ChengYi He
---
mm/page_alloc.c | 79 +
1 file changed, 46 insertions(+), 33 deletions(-)
diff --git a/mm/pag
While buddy system fallbacks to allocate different migration type pages,
it prefers the largest feasible pages and might split the chosen page
into smalller ones. If the largest feasible pages are less than or equal
to orde-3 and migration fallback happens frequently, then order-2 and
order-3 pages
401 - 500 of 769 matches
Mail list logo
