On 01/04/2016 06:46 AM, Will Deacon wrote:
> On Sun, Jan 03, 2016 at 05:05:57PM +0100, Ard Biesheuvel wrote:
>> Instead of using absolute addresses for both the exception location
>> and the fixup, use offsets relative to the exception table entry values.
>> Not only does this cut the size of the e
> May I humbly ask why the [Finnish] you don't use the equivalent of the
> x86 _ASM_EXTABLE() macro? In fact, why don't we make that one generic, too?
I'm messing with that right now (with help from Andy Lutomirski and Boris) to
add different classes of exception table (so I can tag some instruct
On Sat, Jan 2, 2016 at 11:21 PM, Wolfram Sang wrote:
> On Sun, Dec 27, 2015 at 04:57:48PM +0200, Andy Shevchenko wrote:
>> On Wed, Dec 23, 2015 at 9:18 PM, Akshay Bhat wrote:
>> > "at" is not a valid vendor prefix, correcting the same to "atmel"
>> >
>>
>> I'm afraid you can't just do this change
On Sun, Jan 03, 2016 at 07:09:06PM +0200, Jarkko Sakkinen wrote:
> On Thu, Dec 17, 2015 at 11:23:14AM -0700, Jason Gunthorpe wrote:
> > include/acpi/actbl2.h is the proper place for these definitions
> > and the needed TPM2 ones have been there since
> > commit 413d4a6defe0 ("ACPICA: Update TPM2 AC
On Mon, Dec 21, 2015 at 05:10:06PM +1100, NeilBrown wrote:
>
> hi,
> I became maintainer for md (Linux Software RAID) in late 2001 and on
> the whole it has been fun and a valuable experience. But I have been
> losing interest in recent years (https://lwn.net/Articles/511073/) and
> as was me
On Fri, Jan 01, 2016 at 09:56:01AM +0800, Daniel Kurtz wrote:
> On Fri, Jan 1, 2016 at 6:07 AM, Mark Brown wrote:
> > On Thu, Dec 31, 2015 at 09:45:51PM +0800, Daniel Kurtz wrote:
> >> Things are actively broken right now, in the sense that there are many
> >> needless probe deferrals on boot.
>
On Sun, Jan 03, 2016 at 07:20:40PM +0200, Jarkko Sakkinen wrote:
> On Thu, Dec 17, 2015 at 11:23:15AM -0700, Jason Gunthorpe wrote:
> > Instead of clearing the global interrupts flag when any device
> > does not have an interrupt just pass -1 through tpm_info.irq.
> >
> > The only thing that asks
On 20 December 2015 at 08:29, Rabin Vincent wrote:
> On Fri, Dec 18, 2015 at 01:58:58PM -0700, Mathieu Poirier wrote:
>> When using the Coresight framework from the sysFS interface a
>> tracer is always handling a single session and as such, a path
>> can be associated with a tracer. But when sup
On Wed, Dec 30, 2015 at 3:27 AM, Michał Kępień wrote:
>> > If you feel like I'm nit-picking and none of the above matters,
>> > please feel free to disregard my input and just follow your gut.
>>
>> It's ok. We just understand it quite differently. And in this case what
>> about changing commit me
Hi Heikki,
> These are used at least by Acer with BCM43241.
>
> Signed-off-by: Heikki Krogerus
> ---
> drivers/bluetooth/hci_bcm.c | 3 +++
> 1 file changed, 3 insertions(+)
patch has been applied to bluetooth-next tree.
Regards
Marcel
--
To unsubscribe from this list: send the line "unsubscr
Hi Heikki,
> The IDs should all be for Broadcom BCM43241 module, and
> hci_bcm is now the proper driver for them. This removes one
> of two different ways of handling PM with the module.
>
> Signed-off-by: Heikki Krogerus
> Cc: Johannes Berg
> ---
> drivers/bluetooth/hci_bcm.c | 4
> net/rf
On Sun, Jan 03, 2016 at 07:26:50PM +0200, Jarkko Sakkinen wrote:
> > @@ -695,8 +685,8 @@ static int tpm_tis_init(struct device *dev, struct
> > tpm_info *tpm_info,
> > #endif
> >
> > chip->vendor.iobase = devm_ioremap_resource(dev, &tpm_info->res);
> > - if (!chip->vendor.iobase)
> > -
On Mon, Jan 04, 2016 at 11:54:40AM +, Suzuki K. Poulose wrote:
> Instead of hard coding the period we program on the PMU
> counters, define a symbol.
>
> Cc: Mark Rutland
> Cc: Punit Agrawal
> Signed-off-by: Suzuki K. Poulose
> ---
> drivers/bus/arm-cci.c | 19 ++-
> 1 fi
On Sun, Jan 03, 2016 at 07:32:13PM +0200, Jarkko Sakkinen wrote:
> On Thu, Dec 17, 2015 at 11:23:20AM -0700, Jason Gunthorpe wrote:
> > To support the force mode in tpm_tis we need to use resource locking
> > in tpm_crb as well, via devm_ioremap_resource.
> >
> > The light restructuring better ali
Put read operations into a function.
This improves modularity and readability.
Signed-off-by: Joshua Clayton
---
drivers/rtc/rtc-pcf2123.c | 36 +++-
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/drivers/rtc/rtc-pcf2123.c b/drivers/rtc/rtc-pcf212
Alexandre,
this is the second version of apatch set to be able to adjust the
clock on a pcf2123, but with a big addition. I am also proposing
a couple of new rtc api functions and a new sysfs file.
Patches 1-5 are very much v2 patches that address All of the
concerns you had with v1. It is my hope
On Mon, Dec 21, 2015 at 7:10 AM, tip-bot for Andy Lutomirski
wrote:
> Commit-ID: 30bfa7b3488bfb1bb75c9f50a5fcac1832970c60
> Gitweb: http://git.kernel.org/tip/30bfa7b3488bfb1bb75c9f50a5fcac1832970c60
> Author: Andy Lutomirski
> AuthorDate: Wed, 16 Dec 2015 23:18:48 -0800
> Committer: Tho
pcf2123 data sheet recommends a software reset when the chip
is first powered on. This change avoids resetting the chip
every time the driver is loaded, which has some negative effects.
There are several registers including a clock rate adjustment that really
should survive a reload of the driver
pcf2123 has an offset register, which can be used to make minor
adjustments to the clock rate to compensate for temperature or
a crystal that is not exactly right.
Expose the offset register to sysfs
Signed-off-by: Joshua Clayton
---
drivers/rtc/rtc-pcf2123.c | 57 ++
The file is called "offset", and may be set and read in decimal.
For rtcs that do not have read_offset or set_offset implemented,
read always returns zero and write will return -EINVAL.
Signed-off-by: Joshua Clayton
---
drivers/rtc/interface.c | 2 +-
drivers/rtc/rtc-sysfs.c | 29 ++
On 01/04/2016 03:20 AM, Heiko Carstens wrote:
> On Sun, Jan 03, 2016 at 05:05:51PM +0100, Ard Biesheuvel wrote:
>> There are currently four architectures (x86, ia64, alpha and s390) whose
>> user-access exception tables are relative to the table entry address rather
>> than absolute. Each of these
On 01/04/2016 02:02 PM, Davidlohr Bueso wrote:
On Sat, 02 Jan 2016, Manfred Spraul wrote:
Commit 6d07b68ce16a ("ipc/sem.c: optimize sem_lock()") introduced a
race:
sem_lock has a fast path that allows parallel simple operations.
There are two reasons why a simple operation cannot run in paral
A number of rtc devices, such as the NXP pcf2123 include a facility
to adjust the clock in order to compensate for temperature or a
crystal, capacitor, etc, that results in the rtc clock not running
at exactly 32.768 kHz.
Data sheets I have seen refer to this as a clock offset, and measure it
in p
On Mon, Jan 04, 2016 at 11:24:42AM -0700, Jason Gunthorpe wrote:
> On Sun, Jan 03, 2016 at 07:20:40PM +0200, Jarkko Sakkinen wrote:
> > On Thu, Dec 17, 2015 at 11:23:15AM -0700, Jason Gunthorpe wrote:
> > > Instead of clearing the global interrupts flag when any device
> > > does not have an interr
Add new functions pcf2123_write(), and pcf2123_write_reg().
Use named defines for the values being written.
This improves modularity and readability, and reduces lines of code.
Signed-off-by: Joshua Clayton
---
drivers/rtc/rtc-pcf2123.c | 67 ++-
1 fi
Refactor chip reset items into its own function, isolating it from
the rest of the device probe.
Subsequent commits will avoid calling this code.
Signed-off-by: Joshua Clayton
---
drivers/rtc/rtc-pcf2123.c | 64 ++-
1 file changed, 36 insertions(+), 28
Add defines for all 16 registers in the pcf2123.
Add defines for useful bits from several registers
I've tried to document all the registers, and
as best as possible, all the special bits they employ
Use BIT() wherever possible in the bit definitions
Signed-off-by: Joshua Clayton
---
drivers/rt
On 12/29/2015 12:37 PM, Rob Herring wrote:
On Tue, Dec 22, 2015 at 03:43:52PM -0800, David Daney wrote:
From: David Daney
Some Cavium ThunderX processors require quirky access methods for the
config space of the PCIe bridge. Add a driver to provide these config
space accessor functions. The
Em Mon, Jan 04, 2016 at 10:31:27AM -0500, Steven Rostedt escreveu:
> On Wed, 23 Dec 2015 22:08:41 +0900
> Namhyung Kim wrote:
>
> > The print_event_field() and print_event_fields() are to print basic
> > information of a given field or event without the print format. They'll
> > be used by dynam
Normally, when a platform driver defines a .probe callback, the
result of dev_pm_domain_attach() is ignored unless it is EPROBE_DEFER.
However, when a .probe callback is not defined the result of
dev_pm_domain_attach() is propagated to the caller.
But dev_pm_domain_attach() can return -ENODEV for
On Mon, Jan 4, 2016 at 2:06 AM, Sinan Kaya wrote:
> The Qualcomm Technologies HIDMA device has been designed to support
> virtualization technology. The driver has been divided into two to follow
> the hardware design.
>
> 1. HIDMA Management driver
> 2. HIDMA Channel driver
>
> Each HIDMA HW cons
On Mon, Jan 04, 2016 at 05:36:01PM +0100, Julia Lawall wrote:
> The aem_rw_sensor_template and aem_ro_sensor_template structures are never
> modified, so declare them as const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
Applied.
Thanks,
Guenter
--
To unsubscribe from
On 2016-01-04 12:11, Greg KH wrote:
On Mon, Jan 04, 2016 at 11:57:33AM -0500, Austin S. Hemmelgarn wrote:
On 2016-01-04 10:43, Greg KH wrote:
On Mon, Jan 04, 2016 at 04:34:56PM +0100, Pierre Paul MINGOT wrote:
Hello,
In Linux there is no way to set the number of tty devices or console
to crea
On Mon, Jan 4, 2016 at 2:06 AM, Sinan Kaya wrote:
> This patch adds support for hidma engine. The driver consists of two
> logical blocks. The DMA engine interface and the low-level interface.
> The hardware only supports memcpy/memset and this driver only support
> memcpy interface. HW and driver
On Mon, Jan 04, 2016 at 11:18:00AM -0500, Mike Marshall wrote:
> Hi Julia... thanks for the patch... I've applied it to my github repo,
> so it will be in the next push to kernel.org.
>
> Orangefs is still out-of-tree (only temporarily I hope ;-) so I guess I
> don't belong in the MAINTAINERS file
Hi Chen,
[auto build test ERROR on v4.4-rc8]
[also build test ERROR on next-20160104]
[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/Chen-Feng/Add-Support-for-Hi6220-PMIC-Hi6553-MFD-Core
On 01/04/2016 01:05 PM, Christoph Lameter wrote:
> On Thu, 24 Dec 2015, Sasha Levin wrote:
>
>>> Also what workload triggers the BUG()?
>>
>> Fuzzing with trinity inside a KVM guest. I've attached my config.
>
> Ok build and bootup works fine after fix from Tetsuo to config. Does not
> like my in
>From include/asm-generic/sections.h:
/*
* Usage guidelines:
* _text, _data: architecture specific, don't use them in
* arch-independent code
* [_stext, _etext]: contains .text.* sections, may also contain
* .rodata.*
* and/or .init.* sections
_text is not guaranteed acros
On 01/04/2016 10:20 AM, Luck, Tony wrote:
>> May I humbly ask why the [Finnish] you don't use the equivalent of the
>> x86 _ASM_EXTABLE() macro? In fact, why don't we make that one generic, too?
>
> I'm messing with that right now (with help from Andy Lutomirski and Boris) to
> add different clas
On 01/04/2016 10:31 AM, Andy Lutomirski wrote:
> On Mon, Dec 21, 2015 at 7:10 AM, tip-bot for Andy Lutomirski
> wrote:
>> Commit-ID: 30bfa7b3488bfb1bb75c9f50a5fcac1832970c60
>> Gitweb:
>> http://git.kernel.org/tip/30bfa7b3488bfb1bb75c9f50a5fcac1832970c60
>> Author: Andy Lutomirski
>> Au
On Mon, Jan 04, 2016 at 11:23:17AM -0700, Jason Gunthorpe wrote:
> On Sun, Jan 03, 2016 at 07:09:06PM +0200, Jarkko Sakkinen wrote:
> > On Thu, Dec 17, 2015 at 11:23:14AM -0700, Jason Gunthorpe wrote:
> > > include/acpi/actbl2.h is the proper place for these definitions
> > > and the needed TPM2 on
Hi,
Here are the follow up commits proposed during last Johan review of the
new mxu11x0 driver. I also patched a memory leak on usb_serial private data.
In v2, I fixed the trivial issues reported by Johan in commits 1/4 and 4/4.
About commit 2/4, I was wrong in last cover-letter message.
The exac
The function mxu1_set_termios is called twice in open callback.
Only the first call is necessary.
Signed-off-by: Mathieu OTHACEHE
---
drivers/usb/serial/mxu11x0.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/usb/serial/mxu11x0.c b/drivers/usb/serial/mxu11x0.c
index 7ad2727..6326
Sending OPEN and START commands twice is not necessary for this driver.
Also send STOP command at close.
Signed-off-by: Mathieu OTHACEHE
---
Changes in v2:
* Only remove OPEN_PORT and START_PORT in open callback.
drivers/usb/serial/mxu11x0.c | 21 +++--
1 file changed, 7 insert
Move interrupt in endpoint test and firmware download to a new probe
callback. This avoids unnecessary memory allocations done by core
before port_probe callback is called.
If the device has to be reseted (firmware downloaded) or if the
interface is incorrect (no interrupt in endpoint), the probe
On nominal execution, private data allocated on port_probe and attach
are never freed. Add port_remove and release callbacks to free them
respectively.
Signed-off-by: Mathieu OTHACEHE
---
Changes in v2:
* Move release callback after attach callback
drivers/usb/serial/mxu11x0.c | 20 +++
On Fri, Dec 11, 2015 at 03:58:01PM -0800, Brian Norris wrote:
> Commit 807f16d4db95 ("mtd: core: set some defaults when dev.parent is
> set") attempted to provide some default settings for MTDs that
> (a) assign the parent device and
> (b) don't provide their own name or owner
>
> However, this
> - begin comment -
>
> The offset to the fixup is signed, and we're trying to use the high
> bits for a different purpose. In C, we could just do:
>
> u32 class_and_offset = ((target - here) & 0x3fff) | class;
>
> Then, to decode it, we'd mask off the class and sign-extend to recover
On Mon, Jan 4, 2016 at 2:06 AM, Sinan Kaya wrote:
> This patch implements the hardware hooks for the HIDMA channel driver.
>
> The main functions of interest are:
> - hidma_ll_init
> - hidma_ll_request
> - hidma_ll_queue_request
> - hidma_ll_hw_start
>
> OS layer calls the hidma_ll_init function d
On Mon, Jan 04, 2016 at 11:54:41AM +, Suzuki K. Poulose wrote:
> Refactor pmu_write_counter to add __pmu_write_counter() which
> will actually write to the counter once the event is validated.
> This can be used by hooks specific to CCI PMU model to program
> the counter, where the event is alr
On Mon, Jan 4, 2016 at 10:48 AM, H. Peter Anvin wrote:
> On 01/04/2016 10:31 AM, Andy Lutomirski wrote:
>> On Mon, Dec 21, 2015 at 7:10 AM, tip-bot for Andy Lutomirski
>> wrote:
>>> Commit-ID: 30bfa7b3488bfb1bb75c9f50a5fcac1832970c60
>>> Gitweb:
>>> http://git.kernel.org/tip/30bfa7b3488bfb1
On Mon, Jan 04, 2016 at 11:54:42AM +, Suzuki K. Poulose wrote:
> Add a helper to group the writes to PMU counter, this will be
> used to delay setting the event period to pmu::pmu_enable()
>
> Cc: Mark Rutland
> Cc: Punit Agrawal
> Signed-off-by: Suzuki K. Poulose
> ---
> drivers/bus/arm-c
On Mon, Jan 4, 2016 at 10:59 AM, Tony Luck wrote:
>> - begin comment -
>>
>> The offset to the fixup is signed, and we're trying to use the high
>> bits for a different purpose. In C, we could just do:
>>
>> u32 class_and_offset = ((target - here) & 0x3fff) | class;
>>
>> Then, to dec
On Mon, Jan 4, 2016 at 8:09 AM, Dominique Martinet
wrote:
> Peter Zijlstra wrote on Mon, Jan 04, 2016 at 04:59:15PM +0100:
>> On Tue, Dec 29, 2015 at 10:43:26PM -0800, Andy Lutomirski wrote:
>> > [add cc's]
>> >
>> > Hi scheduler people:
>> >
>> > This is relatively easy for me to reproduce. Any
Commits such as commit 853f1c58c4b2 ("mtd: nand: omap2: show parent
device structure in sysfs") attempt to rely on the core MTD code to set
the MTD name based on the parent device. However, nand_base tries to set
a different default name according to the flash name (e.g., extracted
from the ONFI pa
On Mon, Jan 4, 2016 at 10:48 AM, Laura Abbott wrote:
> From include/asm-generic/sections.h:
>
> /*
> * Usage guidelines:
> * _text, _data: architecture specific, don't use them in
> * arch-independent code
> * [_stext, _etext]: contains .text.* sections, may also contain
> * .rodata.*
> *
On Sat, Jan 02, 2016 at 06:54:37AM -0500, Tejun Heo wrote:
> On Fri, Jan 01, 2016 at 03:40:28PM -0800, Jeremiah Mahler wrote:
> > all,
> >
> > When running the latest linux-next (20151231) two of my machines
> > hang early in the boot sequence. The initial message is for a
> > NULL pointer derefe
tpm_tis.c already gets actbl2.h via linux/acpi.h -> acpi/acpi.h ->
acpi/actbl.h -> acpi/actbl2.h, so the direct include in tpm_tis.c
is not needed.
Signed-off-by: Jerry Snitselaar
---
Jarrko, this is a trivial thing I noticed while doing some work.
Not sure if you guys care, but thought I'd send
On Tue, Dec 22, 2015 at 9:48 PM, Ming Lei wrote:
> For one cloned bio, kernel shouldn't touch all segments of this
> bio via the helper, because the bvec table is shared among all
> related bios, so warn once for this usage.
>
> This change should catch recent memory corruption issue, which is
> f
On 01/04/2016 10:20 AM, Luck, Tony wrote:
>> May I humbly ask why the [Finnish] you don't use the equivalent of the
>> x86 _ASM_EXTABLE() macro? In fact, why don't we make that one generic, too?
>
> I'm messing with that right now (with help from Andy Lutomirski and Boris) to
> add different clas
The Kconfig currently controlling compilation of this code is:
drivers/bus/Kconfig:config UNIPHIER_SYSTEM_BUS
drivers/bus/Kconfig:bool "UniPhier System Bus driver"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned
On Mon, Jan 04, 2016 at 11:54:44AM +, Suzuki K. Poulose wrote:
> Delay setting the event periods for enabled events to pmu::pmu_enable().
> We mark the event.hw->state PERF_HES_ARCH for the events that we know
> have their counts recorded and have been started.
Please add a comment to the code
Happy new year, Serge.
On Mon, Jan 04, 2016 at 01:15:53PM -0600, Serge E. Hallyn wrote:
> an updated set is at
> https://git.kernel.org/cgit/linux/kernel/git/sergeh/linux-security.git/commit/?h=cgroupns.v9
> Would you like a new patchset send to the list, or is the github
> tree ok?
Please repos
On Tue, Dec 15, 2015 at 03:55:53PM -0600, Suravee Suthikulpanit wrote:
> Add device HID AMDI0510 to match the I2C controlers on AMD Seattle platform
>
> Signed-off-by: Suravee Suthikulpanit
Applied to for-next, thanks!
signature.asc
Description: Digital signature
On Mon, Jan 04, 2016 at 11:07:43AM -0800, Andy Lutomirski wrote:
> On Mon, Jan 4, 2016 at 8:09 AM, Dominique Martinet
> wrote:
> > Peter Zijlstra wrote on Mon, Jan 04, 2016 at 04:59:15PM +0100:
> >> On Tue, Dec 29, 2015 at 10:43:26PM -0800, Andy Lutomirski wrote:
> >> > [add cc's]
> >> >
> >> > Hi
On Mon, Jan 4, 2016 at 10:48 AM, H. Peter Anvin wrote:
>
> Linus has frequently stated that if it is something that is critical
> enough for stable, it is critical enough for final. Linus will decide
> if an additional -rc is needed for that reason.
So it would have been good to have it in an -r
On 4 January 2016 at 20:21, H. Peter Anvin wrote:
> On 01/04/2016 10:20 AM, Luck, Tony wrote:
>>> May I humbly ask why the [Finnish] you don't use the equivalent of the
>>> x86 _ASM_EXTABLE() macro? In fact, why don't we make that one generic, too?
>>
>> I'm messing with that right now (with help
This removes a Sparse warning.
Signed-off-by: Hugo Camboulive
---
drivers/staging/wilc1000/wilc_debugfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wilc1000/wilc_debugfs.c
b/drivers/staging/wilc1000/wilc_debugfs.c
index 27c653a..291e6fa 100644
--- a/dri
Add a driver to setup the USB phy on Mediatek/Ralink SoCs.
The driver is trivial and only sets up power and host mode.
Signed-off-by: John Crispin
---
Changes in V2
* remove refcounting
* drop empty functions
* dont use static globals
* use explicit compatible strings
.../devicetree/bindings/ph
It has been a couple of months since the v8 version of this patch,
since various other priorities came up at work. Since it's been
a while I will try to summarize where I think we got to on the
various issues that were raised with v8.
1. Andy Lutomirski raised the issue of whether it really made
In prepare_exit_to_usermode(), call task_isolation_ready()
when we are checking the thread-info flags, and after we've handled
the other work, call task_isolation_enter() unconditionally.
In syscall_trace_enter_phase1(), we add the necessary support for
strict-mode detection of syscalls.
We add s
This per-cpu check was being done in the loop in lru_add_drain_all(),
but having it be callable for a particular cpu is helpful for the
task-isolation patches.
Signed-off-by: Chris Metcalf
---
include/linux/swap.h | 1 +
mm/swap.c| 13 +
2 files changed, 10 insertions(+)
We add the necessary call to task_isolation_enter() in the
prepare_exit_to_usermode() routine. We already unconditionally
call into this routine if TIF_NOHZ is set, since that's where
we do the user_enter() call.
We add calls to task_isolation_check_exception() in places
where exceptions may not
The new "task_isolation_debug" flag simplifies debugging
of TASK_ISOLATION kernels when processes are running in
PR_TASK_ISOLATION_ENABLE mode. Such processes should get no
interrupts from the kernel, and if they do, when this boot flag is
specified a kernel stack dump on the console is generated.
When the schedule tick is disabled in tick_nohz_stop_sched_tick(),
we call hrtimer_cancel(), which eventually calls down into
__remove_hrtimer() and thus into hrtimer_force_reprogram().
That function's call to tick_program_event() detects that
we are trying to set the expiration to KTIME_MAX and ca
From: Christoph Lameter
quiet_vmstat() can be called in anticipation of a OS "quiet" period
where no tick processing should be triggered. quiet_vmstat() will fold
all pending differentials into the global counters and disable the
vmstat_worker processing.
Note that the shepherd thread will conti
This change is a prerequisite change for TASK_ISOLATION but also
stands on its own for readability and maintainability. The existing
arm64 do_notify_resume() is called in a loop from assembly on
the slow path; this change moves the loop into C code as well.
For the x86 version see commit c5c46f59e
On Sun, Jan 03, 2016 at 09:53:20PM -0500, Doug Ledford wrote:
> On 01/03/2016 08:44 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > On Thu, 31 Dec 2015 13:30:22 +1100 Stephen Rothwell
> > wrote:
> >>
> >> Hi Doug,
> >>
> >> Today's linux-next merge of the rdma tree got conflicts in a quite a
> >
We need to call task_isolation_enter() from prepare_exit_to_usermode(),
so that we can both ensure we do it last before returning to
userspace, and we also are able to re-run signal handling, etc.,
if something occurs while task_isolation_enter() has interrupts
enabled. To do this we add _TIF_NOHZ
> >> +static int rk3x_i2c_v0_calc_divs(unsigned long clk_rate, unsigned long
> >> scl_rate,
> >> +unsigned long scl_rise_ns,
> >> +unsigned long scl_fall_ns,
> >> +unsigned long sda_fall_ns,
>
> Wolfram
Hi Julia,
> The ieee802154_llsec_ops structure is never modified, so declare it as
> const.
>
> Done with the help of Coccinelle.
>
> Signed-off-by: Julia Lawall
>
> ---
> include/net/ieee802154_netdev.h |2 +-
> net/mac802154/mac_cmd.c |2 +-
> 2 files changed, 2 insertions(+),
On Mon, Jan 04, 2016 at 10:57:40AM -0700, Toshi Kani wrote:
> With this change, there will be no caller to walk_iomem_res(). Should we
> remove walk_iomem_res() altogether, or keep it for now as a deprecated func
> with the checkpatch check?
Yes, kill it on the spot so that people don't get crazy
This function checks to see if a vmstat worker is not running,
and the vmstat diffs don't require an update. The function is
called from the task-isolation code to see if we need to
actually do some work to quiet vmstat.
Acked-by: Christoph Lameter
Signed-off-by: Chris Metcalf
---
include/linu
On Mon, Jan 04, 2016 at 11:30:25AM -0700, Jason Gunthorpe wrote:
> On Sun, Jan 03, 2016 at 07:32:13PM +0200, Jarkko Sakkinen wrote:
> > On Thu, Dec 17, 2015 at 11:23:20AM -0700, Jason Gunthorpe wrote:
> > > To support the force mode in tpm_tis we need to use resource locking
> > > in tpm_crb as wel
On Mon, 2016-01-04 at 20:41 +0100, Borislav Petkov wrote:
> On Mon, Jan 04, 2016 at 10:57:40AM -0700, Toshi Kani wrote:
> > With this change, there will be no caller to walk_iomem_res(). Should
> > we remove walk_iomem_res() altogether, or keep it for now as a
> > deprecated func with the checkp
On 12/17/2015 11:24 AM, Lee Duncan wrote:
> On 12/14/2015 05:55 PM, Martin K. Petersen wrote:
>>> "Hannes" == Hannes Reinecke writes:
>>
I'm not opposed to having the module option if others (Martin?) feel
they need it, but generally I think it's better to keep things as
simple
On Mon, Jan 04, 2016 at 11:17:29AM -0600, Dinh Nguyen wrote:
> We tried to jam the L2 and OCRAM EDAC functionality in the same
> altr_edac.c file. It looks like it might be clean if we split out the L2
> and OCRAM functions into their appropriate files(altr_edac_l2.c and
> altr_edac_ocram.c). Do yo
On Mon, Jan 04, 2016 at 08:28:52PM +0100, Ard Biesheuvel wrote:
> On 4 January 2016 at 20:21, H. Peter Anvin wrote:
> > I suspect that means we will also need to go back to arch-specific
> > sorting for x86.
> >
>
> AFAICT, Tony's patches are not incompatible with mine. The fixup
> address is off
This ensures that we always notify context tracking that we
have exited from user space no matter how we enter the kernel.
It is similar to how arm64 handles context tracking, for example.
This allows the removal of all the exception_enter() calls that
were added in commit 49e4e15619cd ("tile: sup
ACKNOWLEDGMENT: The original correlated clock source and cross
timestamp code was developed by Thomas Gleixner
. It has changed considerably and any mistakes are
mine.
The precision with which events on multiple networked systems can be
synchronized using, as an example, PTP (IEEE 1588, 802.1AS) i
With task_isolation mode, the task is in principle guaranteed not to
be interrupted by the kernel, but only if it behaves. In particular,
if it enters the kernel via system call, page fault, or any of a
number of other synchronous traps, it may be unexpectedly exposed
to long latencies. Add a sim
This change is a prerequisite change for TASK_ISOLATION but also
stands on its own for readability and maintainability. The existing
tile do_work_pending() was called in a loop from assembly on
the slow path; this change moves the loop into C code as well.
For the x86 version see commit c5c46f59e4
Modern Intel systems supports cross timestamping of the network device
clock and Always Running Timer (ART) in hardware. This allows the
device time and system time to be precisely correlated. The timestamp
pair is returned through e1000e_phc_get_sync_devicetime() used by
get_device_system_crossts
Modern Intel hardware adds an Always Running Timer (ART) that allows the
network and audio device clocks to precisely cross timestamp the device
clock with the system clock. This allows a precise correlation of the
device time and system time.
This patchset adds interfaces to the timekeeping code
The existing nohz_full mode is designed as a "soft" isolation mode
that makes tradeoffs to minimize userspace interruptions while
still attempting to avoid overheads in the kernel entry/exit path,
to provide 100% kernel semantics, etc.
However, some applications require a "hard" commitment from th
Currently, network /system cross-timestamping is performed in the
PTP_SYS_OFFSET ioctl. The PTP clock driver reads gettimeofday() and
the gettime64() callback provided by the driver. The cross-timestamp
is best effort where the latency between the capture of system time
(getnstimeofday()) and the d
The code in ktime_get_snapshot() is a superset of the code in
ktime_get_raw_and_real() code. Changes the latter to call the former. A
side effect of this is that ktime_get_raw_and_real() returns two clock
times corresponding to the *exact* same clock tick. Previously, this
code read the underlying
Another representative use case of time sync and the correlated
clocksource (in addition to PTP noted above) is PTP synchronized
audio.
In a streaming application, as an example, samples will be sent and/or
received by multiple devices with a presentation time that is in terms
of the PTP master cl
On modern Intel systems TSC is derived from the new Always Running Timer
(ART). ART can be captured simultaneous to the capture of
audio and network device clocks, allowing a correlation between timebases
to be constructed. Upon capture, the driver converts the captured ART
value to the appropriate
From: Aditya Kali
CLONE_NEWCGROUP will be used to create new cgroup namespace.
Signed-off-by: Aditya Kali
Signed-off-by: Serge Hallyn
---
include/uapi/linux/sched.h |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/uapi/linux/sched.h b/include/uapi/linux/sched.h
401 - 500 of 824 matches
Mail list logo
