On Thu, Mar 26, 2015 at 02:56:04PM -0600, Azael Avalos wrote:
> These patches introduce three new functions, cleaning up the driver
> code, checking for errors and returning accordingly, and also fixes
> bug 93911.
>
Queued, thank you Azael.
--
Darren Hart
Intel Open Source Technology Center
--
On Thu, Mar 26, 2015 at 05:58:20PM +0100, Michael Wang wrote:
> The questions is just wondering how the transition method could be, but
> if we have to do the changes for vendor, that sounds like a tough job...
I would see changing how the information is represented in the struct
as a follow on i
On Thu, Mar 26, 2015 at 07:48:50PM +, Hanjun Guo wrote:
> On 2015年03月26日 23:15, Will Deacon wrote:
> > commit 8ef320319592693f4a6286d80df210fd47b3e356
> > Author: Will Deacon
> > Date: Thu Mar 26 15:09:20 2015 +
> >
> > ARM64 / ACPI: fix usage of acpi_map_gic_cpu_interface
> >
> >
An early preview release Git v2.4.0-rc0 is now available for testing
at the usual places. This cycle is turning out to be a "product
excellence" release---majority of the changes are bugfixes, about
one-third of which are also already in the v2.3.x maintenance track.
The tarballs are found at:
On Wed, Mar 25, 2015 at 01:55:44PM -0600, David Ahern wrote:
> >Hmm, I am not entirely sure this is correct. You made an optimization that
> >hides the negative impact your patch does. I would prefer you split this
> >patch into two pieces. One with the read loop optimization (which I think
> >i
On Thu, 2015-03-26 at 22:01 +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 26, 2015 at 12:59:05PM -0700, Jesse Barnes wrote:
> > On 12/16/2014 09:42 AM, Daniel Vetter wrote:
> > > On Tue, Dec 16, 2014 at 6:15 PM, Peter Hurley
> > > wrote:
> > >> On 12/16/2014 11:22 AM, Imre Deak wrote:
> > >>> On
On Thu, Mar 26, 2015 at 1:20 PM, Liang, Kan wrote:
>
>
>> Subject: Re: [PATCH 1/1] perf/x86: filter branches for PEBS event
>>
>> On Thu, Mar 26, 2015 at 11:13 AM, wrote:
>> > From: Kan Liang
>> >
>> > For supporting Intel LBR branches filtering, Intel LBR sharing logic
>> > mechanism is introd
On Thu, Mar 26, 2015 at 12:59:05PM -0700, Jesse Barnes wrote:
> On 12/16/2014 09:42 AM, Daniel Vetter wrote:
> > On Tue, Dec 16, 2014 at 6:15 PM, Peter Hurley
> > wrote:
> >> On 12/16/2014 11:22 AM, Imre Deak wrote:
> >>> On Tue, 2014-12-16 at 10:00 -0500, Peter Hurley wrote:
> Fine. Just an
Bug 93911 reported a broken handling of the BT device, causing the
driver to get stuck in a loop enabling/disabling the device whenever
the device is deactivated by the kill switch as follows:
1. The user activated the kill switch, causing the system to generate
a 0x90 (status change) event and
This patch cleans the toshiba_bluetooth_add function by using the
recently introduced function toshiba_bluetooth_present, simplifying
its code and returning appropriate error values.
Also, disables the BT device at the removal of the driver, by using
the function toshiba_bluetooth_disable.
Signed
This patch introduces three new functions, which are going to be used
by the next patches.
The functions introduced are toshiba_bluetooth_present,
toshiba_bluetooth_status and toshiba_bluetooth_disable, which queries
the presence of the device, queries the status and disables the
device respective
These patches introduce three new functions, cleaning up the driver
code, checking for errors and returning accordingly, and also fixes
bug 93911.
Changes since v2:
- Merged patches 2-3 into one
- Added a comment block explaining a bit why we added an extra check
to the status of the device
Cha
On Thu, 2015-03-26 at 17:43 +0100, Christoph Hellwig wrote:
> On Thu, Mar 26, 2015 at 05:49:38PM +0200, Boaz Harrosh wrote:
> > > +#define E820_PRAM12
> >
> > Why the PRAM Name. For one 2/3 of this patch say PMEM the Kconfig
> > to enable is _PMEM_, the driver stack that gets loaded is pme
On Thu, 2015-03-26 at 19:52 +0100, Greg KH wrote:
> On Thu, Mar 26, 2015 at 11:52:43PM +0530, Niranjan Dighe wrote:
> > Replace string directly in place of format string and remove pointer
> > variable which was used just once.
[]
> > diff --git a/drivers/staging/slicoss/slicoss.c
> > b/drivers/st
On 26 March 2015 at 18:53, Joe Perches wrote:
> On Thu, 2015-03-26 at 17:37 +0100, Mathias Krause wrote:
>> On 26 March 2015 at 17:13, Joe Perches wrote:
>> > On Thu, 2015-03-26 at 13:40 +0100, Mason wrote:
>> >> On 25/03/2015 19:01, Joe Perches wrote:
>> >> > On Wed, 2015-03-25 at 18:56 +0100, M
[+bjorn, pci list]
On Thu, Mar 26, 2015 at 9:51 AM, David Ahern wrote:
> Hi:
>
> Boot of an 8-socket T5 sparc system fails on top of tree. git bisect points
> to this commit:
>
> commit 904bf6bd150bdafb42ddbb3257ea8
> Author: Yinghai Lu
> Date: Thu Jan 15 16:21:51 2015 -0600
>
> sparc/PCI: Cl
If we encounter an uncorrectable ECC error while scanning for the fastmap
UBI must not fail hard. Instead fall back to scanning mode.
Reported-by: Alexander Block
Signed-off-by: Richard Weinberger
---
drivers/mtd/ubi/attach.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/d
On 03/26/2015 02:34 PM, Ming Lin-SSI wrote:
>> -Original Message-
>> From: Jens Axboe [mailto:ax...@fb.com]
>> Sent: Wednesday, March 25, 2015 8:08 AM
>> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org
>> Cc: Ming Lin-SSI; da...@fromorbit.com; Jens Axboe
>> Subject: [PATCH 7
2015-03-25 2:10 GMT+03:00 David Rientjes :
...
>
> +
> +static void check_element(mempool_t *pool, void *element)
> +{
> + /* Mempools backed by slab allocator */
> + if (pool->free == mempool_free_slab || pool->free == mempool_kfree)
> + __check_element(pool, element, ks
> -Original Message-
> From: Jens Axboe [mailto:ax...@fb.com]
> Sent: Wednesday, March 25, 2015 8:08 AM
> To: linux-kernel@vger.kernel.org; linux-fsde...@vger.kernel.org
> Cc: Ming Lin-SSI; da...@fromorbit.com; Jens Axboe
> Subject: [PATCH 7/7] ext4: add support for write stream IDs
>
> Si
On Wed, Mar 25, 2015 at 03:47:39PM -0400, Konrad Rzeszutek Wilk wrote:
> Ah nice. That could be spun out as a seperate patch to optimize the existing
> ticket locks I presume.
Yes I suppose we can do something similar for the ticket and patch in
the right increment. We'd need to restructure the co
> Subject: Re: [PATCH 1/1] perf/x86: filter branches for PEBS event
>
> On Thu, Mar 26, 2015 at 11:13 AM, wrote:
> > From: Kan Liang
> >
> > For supporting Intel LBR branches filtering, Intel LBR sharing logic
> > mechanism is introduced from commit b36817e88630 ("perf/x86: Add
> Intel
> > LB
Hi Daniel,
Thanks for the review. Please find my answers below.
2015-03-26 10:50 GMT+01:00 Daniel Lezcano :
> On 03/12/2015 10:55 PM, Maxime Coquelin wrote:
>>
>> From: Maxime Coquelin
>>
>> This patch adds clocksource support for ARMv7-M's System timer,
>> also known as SysTick.
>>
>> Signed-
On Thu, 26 Mar 2015 11:09:01 +0530 Viresh Kumar wrote:
> A delayed work to schedule vmstat_shepherd() is queued at periodic intervals
> for
> internal working of vmstat core. This work and its timer end up waking an idle
> cpu sometimes, as this always stays on CPU0.
>
> Because we re-queue the
On 03/26/2015 01:01 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 26, 2015 at 04:23:27PM +0100, Roger Pau Monné wrote:
>> El 26/03/15 a les 13.16, Bob Liu ha escrit:
>>> Commit c43cf3ea8385 ("xen-blkback: safely unmap grants in case they are
>>> still
>>> in use") use gnttab_unmap_refs_async() to
On Thu, 26 Mar 2015, Stephen Boyd wrote:
> From: Josh Cartwright
>
> The IPQ8064 also includes an RPM following the same message structure as
> other chips. In addition, it supports a few new resource types to
> support the NSS fabric clocks and the SMB208/SMB209 regulators found on
> the refer
On Thu, 26 Mar 2015, Stephen Boyd wrote:
> From: Josh Cartwright
>
> The IPQ8064 SoC has several RPM-controlled resources, an NSS fabrick
> clock and four regulator resources. Provide definitions for them.
>
> Signed-off-by: Josh Cartwright
> [sb...@codeaurora.org: Drop regulator part of bind
On Thu, 26 Mar 2015, Mark Brown wrote:
> On Thu, Mar 26, 2015 at 10:40:15AM +, Build bot for Mark Brown wrote:
>
> For the past couple of days -next has been failing to build an ARM
> allmodconfig due to the use of defines which don't appear anywhere in
> the kernel, introduced in f35ba5c9f60
On Wed, 25 Mar 2015, Johannes Weiner wrote:
> Setting oom_killer_disabled to false is atomic, there is no need for
> further synchronization with ongoing allocations trying to OOM-kill.
>
> Signed-off-by: Johannes Weiner
Acked-by: David Rientjes
--
To unsubscribe from this list: send the line
On Thu, 26 Mar 2015, Davide Libenzi wrote:
> > Yes, this munmap() behavior of lengths <= hugepage_size - PAGE_SIZE for a
> > hugetlb vma is long standing and there may be applications that break as a
> > result of changing the behavior: a database that reserves all allocated
> > hugetlb memory
On Wed, Mar 25, 2015 at 04:18:19PM -0600, Azael Avalos wrote:
> > That suggests to me the checks for rfkill, powered, and plugged states
> > should be
> > done in the _enable() function itself, rather than at all the call sites.
> >
> > So... would a better fix be to push these two additional test
On Thu, 2015-03-26 at 14:13 -0500, Suravee Suthikulpanit wrote:
> This patch series introduce ACPI support for AHCI platform driver.
> Existing ACPI support for AHCI assumes the device controller is a PCI device.
> Since there is no ACPI _CID for generic AHCI controller, the driver
> could not use
On Wed, Mar 25, 2015 at 02:17:04AM -0400, Johannes Weiner wrote:
> Hi everybody,
>
> in the recent past we've had several reports and discussions on how to
> deal with allocations hanging in the allocator upon OOM.
>
> The idea of this series is mainly to make the mechanism of detecting
> OOM sit
On 12/16/2014 09:42 AM, Daniel Vetter wrote:
> On Tue, Dec 16, 2014 at 6:15 PM, Peter Hurley
> wrote:
>> On 12/16/2014 11:22 AM, Imre Deak wrote:
>>> On Tue, 2014-12-16 at 10:00 -0500, Peter Hurley wrote:
Fine. Just another expedient fix piled on top of other expedient fixes
that go bac
On Thu, 26 Mar 2015, Johannes Weiner wrote:
> > > exit_oom_victim() already knows that TIF_MEMDIE is set, and nobody
> > > else can clear it concurrently. Use clear_thread_flag() directly.
> > >
> > > Signed-off-by: Johannes Weiner
> >
> > For the oom killer, that's true because of task_lock()
On 2015年03月26日 23:15, Will Deacon wrote:
On Wed, Mar 25, 2015 at 05:17:35PM +, Catalin Marinas wrote:
On Tue, Mar 24, 2015 at 10:02:45PM +0800, Hanjun Guo wrote:
+/**
+ * acpi_map_gic_cpu_interface - generates a logical cpu number
+ * and map to MPIDR represented by GICC structure
+ * @mpid
Am 26.03.2015 um 18:23 schrieb Christian Borntraeger:
> Am 26.03.2015 um 18:07 schrieb Peter Zijlstra:
>> On Thu, Mar 26, 2015 at 09:45:07AM -0700, Linus Torvalds wrote:
>>
>>> Stop this idiocy.
>>
>> Yeah, clearly I can type faster than I can think straight :/
>>
>>
>> In any case, I've the below
On Thu, Mar 26, 2015 at 11:13 AM, wrote:
> From: Kan Liang
>
> For supporting Intel LBR branches filtering, Intel LBR sharing logic
> mechanism is introduced from commit b36817e88630 ("perf/x86: Add Intel
> LBR sharing logic"). It modifies __intel_shared_reg_get_constraints to
> config lbr_sel,
On Thu, 26 Mar 2015, David Rientjes wrote:
> Yes, this munmap() behavior of lengths <= hugepage_size - PAGE_SIZE for a
> hugetlb vma is long standing and there may be applications that break as a
> result of changing the behavior: a database that reserves all allocated
> hugetlb memory with mma
On Thu, Mar 26, 2015 at 01:09:18PM -0400, Matthew Wilcox wrote:
> On Tue, Mar 24, 2015 at 11:50:47AM -0700, Matt Mullins wrote:
> > We're also developing a user of direct_access, and we ended up with some
> > questions about the sleeping guarantees of the direct_access API.
>
> That's a great ques
On Thu, 26 Mar 2015, Geert Uytterhoeven wrote:
> Hi Lee,
>
> On Thu, Mar 26, 2015 at 2:51 PM, Lee Jones wrote:
> > On Wed, 25 Mar 2015, Geert Uytterhoeven wrote:
> >> On Mon, Mar 9, 2015 at 10:28 AM, Lee Jones wrote:
> >> > On Fri, 06 Mar 2015, Mike Turquette wrote:
> >> >> This approach looks
On Thu, 26 Mar 2015, Michal Hocko wrote:
> I am wrong here! pagefault_out_of_memory takes the lock and so the whole
> mem_cgroup_out_of_memory is called under the same lock.
If all userspace processes are frozen by the time oom_killer_disable() is
called, then there shouldn't be any race with th
Ping? It's been over a month.
On Fri, Feb 20, 2015 at 5:04 PM, Andy Lutomirski wrote:
> It's currently impossible to mount devpts in a user namespace that
> has no root user, since ptmx can't be created. This adds options
> ptmx_uid and ptmx_gid that override the default uid and gid of 0.
>
> T
From: Daniel Thompson
Currently update_sched_clock() is marked as notrace but this function
is not called by ftrace. This is trivially fixed by removing the mark
up.
Cc: Russell King
Cc: Will Deacon
Cc: Catalin Marinas
Cc: Daniel Thompson
Cc: Thomas Gleixner
Cc: Stephen Boyd
Cc: Peter Zijl
On Thu, Mar 26, 2015 at 11:46 AM, Elliott, Robert (Server Storage)
wrote:
>
>
>> -Original Message-
>> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
>> ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
>> Sent: Thursday, March 26, 2015 11:43 AM
>> To: Boaz Harrosh
>> C
From: Daniel Thompson
Currently it is possible for an NMI (or FIQ on ARM) to come in and
read sched_clock() whilst update_sched_clock() has locked the seqcount
for writing. This results in the NMI handler locking up when it calls
raw_read_seqcount_begin().
This patch fixes the NMI safety issues
This patch series extends perf record/report/annotate to enable
profiling of jitted (just-in-time compiled) code. The current
perf tool provides very limited support for profiling jitted
code for some runtime environments. But the support is experimental
and cannot be used in complex environments.
From: Daniel Thompson
Currently cd.read_data.suspended is read by the hotpath function
sched_clock(). This variable need not be accessed on the hotpath. In
fact, once it is removed, we can remove the conditional branches from
sched_clock() and install a dummy read_sched_clock function to suspend
From: Daniel Thompson
Currently the scope of the raw_write_seqcount_begin/end in
sched_clock_register far exceeds the scope of the read section in
sched_clock. This gives the impression of safety during cursory review
but achieves little.
Note that this is likely to be a latent issue at present
From: Daniel Thompson
Currently sched_clock(), a very hot code path, is not optimized to
minimise its cache profile. In particular:
1. cd is not cacheline_aligned,
2. struct clock_data does not distinguish between hotpath and
coldpath data, reducing locality of reference in the hot
Ingo, Peter, Thomas,
(No real changes since last time, only rebased ontop of tip/timers/core
so as to avoid the collision caused by some of my patches there. Also
resent as patches instead of pull request, since Ingo asked)
The following patches from Daniel extend the arch-generic sched_clock
imp
This is a standalone JVMTI library to help profile Java jitted
code with perf record/perf report. The library is not installed
or compiled automatically by perf Makefile. It is not used
directly by perf. It is arch agnostic and has been tested on
X86 and ARM. It needs to be used with a Java runtim
This patch adds a --jit option to perf inject.
This options injects MMAP records into the perf.data
file to cover the jitted code mmaps. It also emits
ELF images for each function in the jidump file.
Those images are created where the jitdump file is.
The MMAP records point to that location as wel
Add Java function descriptor demangling support.
Something bfd cannot do.
Use the JAVA_DEMANGLE_NORET flag to avoid decoding the
return type of functions.
Signed-off-by: Stephane Eranian
---
tools/perf/util/Build | 1 +
tools/perf/util/demangle-java.c | 199 +
From: Pawel Moll
Until now, perf framework never defined the meaning of the timestamps
captured as PERF_SAMPLE_TIME sample type. The values were obtaining
from local (sched) clock, which is unavailable in userspace. This made
it impossible to correlate perf data with any other events. Other
traci
On Thu, 26 Mar 2015, Davide Libenzi wrote:
> > I looked at this thread at http://marc.info/?t=14139250881 since I
> > didn't have it in my mailbox, and I didn't get a chance to actually run
> > your test code.
> >
> > In short, I think what you're saying is that
> >
> > ptr = mmap(...,
Device drivers typically use ACPI _HIDs/_CIDs listed in struct device_driver
acpi_match_table to match devices. However, for generic drivers, we do not
want to list _HID for all supported devices. Also, certain classes of devices
do not have _CID (e.g. SATA, USB). Instead, we can leverage ACPI _CLS
ACPI Device configuration often contain _CLS object to suppy PCI-defined
class code for the device. This patch introduces logic to process the _CLS
object.
Acked-by: Mika Westerberg
Reviewed-by: Hanjun Guo
Signed-off-by: Suravee Suthikulpanit
---
drivers/acpi/acpica/acutils.h | 3 ++
drivers
This patch series introduce ACPI support for AHCI platform driver.
Existing ACPI support for AHCI assumes the device controller is a PCI device.
Since there is no ACPI _CID for generic AHCI controller, the driver
could not use it for matching devices. Therefore, this patch introduces
a mechanism fo
This patch adds ACPI supports for AHCI platform driver, which uses _CLS
method to match the device.
The following is an example of ASL structure in DSDT for a SATA controller,
which contains _CLS package to be matched by the ahci_platform driver:
Device (AHC0) // AHCI Controller
{
Name(_H
The code here is checking for IS_ERR() when request_mem_region() only
returns NULL on error and never an ERR_PTR.
Signed-off-by: Dan Carpenter
---
v2: same as before but rebased on top of latest linux-next
diff --git a/drivers/mcb/mcb-pci.c b/drivers/mcb/mcb-pci.c
index 0af7361..de36237 100644
-
On Thu, Mar 26, 2015 at 7:55 AM, Christoph Hellwig wrote:
>
> On Mon, Mar 16, 2015 at 02:27:10PM -0400, Milosz Tanski wrote:
> > This patchset introduces two new syscalls preadv2 and pwritev2. They are the
> > same syscalls as preadv and pwrite but with a flag argument. Additionally,
> > preadv2 i
On Wed, Mar 25, 2015 at 07:36:17PM +0100, Hector Marco-Gisbert wrote:
> A bug in Linux ASLR implementation which affects some AMD processors has been
> found. The issue affects to all Linux process even if they are not using
> shared libraries (statically compiled).
>
> The problem appears because
* Eduardo Valentin [150324 08:17]:
> On Mon, Mar 23, 2015 at 02:39:39PM -0500, Nishanth Menon wrote:
> > BeagleBoard-X15 has capability for a fan and has an onboard TMP102
> > temperature sensor as well. This allows us to create a new thermal
> > zone (called, un-imaginatively "board"), and allows
On Thu, Mar 26, 2015 at 08:16:01PM +0800, Bob Liu wrote:
> There are several place using gnttab async unmap and wait for
> completion, so move the common code to a function
> gnttab_unmap_refs_async_wait_completion().
>
> Signed-off-by: Bob Liu
Jens, and would you be OK if this patch went throug
On Thu, Mar 26, 2015 at 04:23:27PM +0100, Roger Pau Monné wrote:
> El 26/03/15 a les 13.16, Bob Liu ha escrit:
> > Commit c43cf3ea8385 ("xen-blkback: safely unmap grants in case they are
> > still
> > in use") use gnttab_unmap_refs_async() to wait until the mapped pages are no
> > longer in use be
On Wed, Mar 25, 2015 at 1:41 AM, Scott Branden wrote:
> Hi Rob,
>
> On 15-03-22 06:20 PM, Rob Herring wrote:
>>
>> On 03/20/2015 08:06 PM, Scott Branden wrote:
>>>
>>> This patchset attempts to standardize the naming of dt-bindings
>>> documents based on the Broadcom vendor prefix of brcm.
>>>
>>>
* Laurent Dufour wrote:
> +{
> + unsigned long vdso_end, vdso_start;
> +
> + if (!mm->context.vdso_base)
> + return;
> + vdso_start = mm->context.vdso_base;
> +
> +#ifdef CONFIG_PPC64
> + /* Calling is_32bit_task() implies that we are dealing with the
> + * curre
+Cc Amit who implemented the emulation code.
On Thu, Mar 26, 2015 at 02:13:47PM -0400, Carlos Hernandez wrote:
> On 03/26/2015 11:53 AM, Sascha Hauer wrote:
> >- The code should only accept an emulated temperature when the emulated
> > temperature is lower than the critical temperature. Instead
Hi!
Am 26.03.2015 um 17:24 schrieb Hajime Tazaki:
> thank you for your deep review on the source code !
>
>> feeling that "lib" is the wrong name.
>> It has not much do to with an architecture.
>
> could you care to elaborate your feeling more explicitly ?
>
> what is an architecture here and w
Am 26.03.2015 um 18:52 schrieb Linus Torvalds:
> On Thu, Mar 26, 2015 at 10:24 AM, Christian Borntraeger
> wrote:
>>
>> Oh I just added that check back then because some guy named
>> Linus suggested something like that ;-)
>
> Yes, my bad.
>
> In my defense, that was when we were talking about A
On Thu, Mar 26, 2015 at 11:52:43PM +0530, Niranjan Dighe wrote:
> Replace string directly in place of format string and remove pointer
> variable which was used just once.
>
> Signed-off-by: Niranjan Dighe
>
> diff --git a/drivers/staging/slicoss/slicoss.c
> b/drivers/staging/slicoss/slicoss.c
From: Kan Liang
For supporting Intel LBR branches filtering, Intel LBR sharing logic
mechanism is introduced from commit b36817e88630 ("perf/x86: Add Intel
LBR sharing logic"). It modifies __intel_shared_reg_get_constraints to
config lbr_sel, which is finally used to set LBR_SELECT.
However, the
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Christoph Hellwig
> Sent: Thursday, March 26, 2015 11:43 AM
> To: Boaz Harrosh
> Cc: Christoph Hellwig; Ingo Molnar; linux-nvd...@ml01.01.org; linux-
> fsde...@vger.
On Thu, Mar 26, 2015 at 5:42 AM, Denys Vlasenko wrote:
> This change makes the check exact (no more false positives
> on kernel addresses).
>
> It isn't really important to be fully correct here -
> almost all addresses we'll ever see will be userspace ones,
> but OTOH it looks to be cheap enough:
Cpu frequency can be throttled due to failures of components like OCC,
power supply and fan. It can also be throttled due to temperature and
power limit. We can detect the throttling by checking 1)if max frequency
is reduced, 2)if the core is put to safe frequency 3)if the SPR based
frequency manag
Hello Marcelo,
On Wed, 25 Mar 2015, Marcelo Tosatti wrote:
On Thu, Mar 12, 2015 at 04:16:07PM -0700, Vikas Shivappa wrote:
This patch adds a description of Cache allocation technology, overview
of kernel implementation and usage of CAT cgroup interface.
Signed-off-by: Vikas Shivappa
---
Do
On Thu, Mar 26, 2015 at 07:31:03PM +0200, Boaz Harrosh wrote:
> But I hope you are not ignoring my real problem. any two memmap= ranges
> will halt the boot. Specially if they are dis-contiguous.
not the case here, verified it in various cofigurations.
> Also I need the contiguous variant split i
And here's the patch, sorry:
diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
index 4bd525a..e7bf89e 100644
--- a/arch/x86/kernel/e820.c
+++ b/arch/x86/kernel/e820.c
@@ -346,7 +346,7 @@ int __init sanitize_e820_map(struct e820entry *biosmap, int
max_nr_map,
* continu
From: Dave Hansen
This event traces any time we go looking to unmap a bounds table
for a given virtual address range. This is useful to ensure
that the kernel actually "tried" to free a bounds table versus
times it succeeded.
It might try and fail if it realized that a table was shared
with an
From: Dave Hansen
The MPX registers (bndcsr/bndcfgu/bndstatus) are not directly
accessible via normal instructions. They essentially act as
if they were floating point registers and are saved/restored
along with those registers.
There are two main paths in the MPX code where we care about
the
From: Dave Hansen
When we allocate a bounds table, we call mmap(), then add a
"valid" bit to the value before storing it in to the bounds
directory.
If we fail along the way, we go and mask that valid bit
_back_ out. That seems a little silly, and this makes it
much more clear when we have a p
From: Dave Hansen
Bounds tables are a significant consumer of memory. It is important
to know when they are being allocated. Add a trace point to trace
whenever an allocation occurs and also its virtual address.
Signed-off-by: Dave Hansen
---
b/arch/x86/include/asm/trace/mpx.h | 16 +
On Thu, 26 Mar 2015, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the xen-tip tree got a conflict in
> drivers/xen/Kconfig between commit 94ccae47e02d ("XEN / ACPI: Make XEN
> ACPI depend on X86") from the arm64-acpi tree and commit 628c28eefd6f
> ("xen: unify foreign GFN map/
On Thu, Mar 26, 2015 at 11:52:43PM +0530, Niranjan Dighe wrote:
> Replace string directly in place of format string and remove pointer
> variable which was used just once.
>
> Signed-off-by: Niranjan Dighe
>
> diff --git a/drivers/staging/slicoss/slicoss.c
> b/drivers/staging/slicoss/slicoss.c
From: Dave Hansen
The uprobes code has a nice helper, is_64bit_mm(), that consults both
the runtime and compile-time flags for 32-bit support. Instead of
reinventing the wheel, pull it in to an x86 header so we can use it
for MPX.
I prefer passing the mm around to test_thread_flag(TIF_IA32) be
From: Dave Hansen
MPX has the _potential_ to cause some issues. Say part of your init
system tried to protect one of its components from buffer overflows
with MPX. If there were a false positive, it's possible that MPX
could keep a system from booting.
MPX could also potentially cause perform
From: Dave Hansen
There are two basic things that can happen as the result of
a bounds exception (#BR):
1. We allocate a new bounds table
2. We pass up a bounds exception to userspace.
This patch adds a trace points for the case where we are
passing the exception up to userspac
From: Dave Hansen
We are going to do some calculations in a moment that are based on the
size of the virtual address space. __VIRTUAL_MASK is currently unsafe
to use on 32-bit since it overflows an unsigned long with its shift.
The current version will emit a warning if used at all on 32-bit
k
From: Dave Hansen
The comment and code here are confusing. We do not currently
allocate the bounds directory in the kernel.
Signed-off-by: Dave Hansen
---
b/arch/x86/mm/mpx.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/x86/mm/mpx.c~x86-mpx-we-do-not-allocate
From: Dave Hansen
We explicitly disable allowing 32-bit binaries to enable
MPX on 64-bit kernels. Re-allow that.
Signed-off-by: Dave Hansen
---
b/arch/x86/mm/mpx.c |6 --
1 file changed, 6 deletions(-)
diff -puN arch/x86/mm/mpx.c~x86-mpx-allow-mixed-binaries-again arch/x86/mm/mpx.c
From: Dave Hansen
This is the first in a series of MPX tracing patches.
I've found these extremely useful in the process of
debugging applications and the kernel code itself.
This exception hooks in to the bounds (#BR) exception
very early and allows capturing the key registers which
would infl
From: Dave Hansen
user_atomic_cmpxchg_inatomic() actually looks at sizeof(*ptr) to
figure out how many bytes to copy. If we run it on a 64-bit
kernel with a 64-bit pointer, it will copy a 64-bit bounds
directory entry. That's fine, except when we have 32-bit
programs with 32-bit bounds directo
From: Dave Hansen
Currently, to get from a bounds directory entry to the virtual
address of a bounds table, we simply mask off a few low bits.
However, the set of bits we mask off is different for 32 and
64-bit binaries.
This breaks the operation out in to a helper function and also
adds a temp
On Mar 26, 2015 6:32 AM, "Boris Ostrovsky" wrote:
>
> On 03/06/2015 08:50 PM, Andy Lutomirski wrote:
>>
>> I broke 32-bit kernels. The implementation of sp0 was correct as
>> far as I can tell, but sp0 was much weirder on x86_32 than I
>> realized. It has the following issues:
>>
>> - Init's s
From: Dave Hansen
From: Qiaowei Ren
MPX_BNDCFG_ADDR_MASK is defined two times, so this patch removes
redundant one.
Signed-off-by: Qiaowei Ren
Signed-off-by: Dave Hansen
---
b/arch/x86/include/asm/mpx.h |1 -
1 file changed, 1 deletion(-)
diff -puN
arch/x86/include/asm/mpx.h~0001-x8
From: Dave Hansen
Right now, the kernel can only switch between 64-bit and 32-bit
binaries at compile time. This patch adds support for 32-bit
binaries on 64-bit kernels when we support ia32 emulation.
We essentially choose which set of table sizes to use when doing
arithmetic for the bounds ta
Hi x86 maintainers,
It appeared that my attempt to send this earlier this week
failed to reach at least some of the intended recipients.
I updated a few of the patch descriptions and am resending.
There are 4 basic things going on here:
1. Make FPU/xsave code preempt safe and work properly
2. Add
From: Dave Hansen
When MPX can not free an entire bounds table, it will instead
try to zap unused parts of a bounds table to free the backing
memory. This decreases Rss (resident set) without decreasing
the virtual space allocated for bounds tables.
Signed-off-by: Dave Hansen
---
b/arch/x86
From: Dave Hansen
The MPX code appears to be saving off the FPU in an unsafe
way. It does not disable preemption or ensure that the
FPU state has been allocated.
This patch introduces a new helper which will do both of
those things internally.
Note that this requires a patch from Oleg in ord
201 - 300 of 810 matches
Mail list logo
