On Tue, Jun 5, 2018 at 6:18 PM, Sudeep Holla wrote:
>
>
> On 05/06/18 17:12, Rafael J. Wysocki wrote:
>> On Tue, Jun 5, 2018 at 5:33 PM, Sudeep Holla wrote:
>>>
>>>
>>> On 05/06/18 16:00, Rafael J. Wysocki wrote:
On Tue, Jun 5, 2018 at 4:35 PM, Sudeep Holla wrote:
> Though
Em Tue, Jun 05, 2018 at 02:14:16PM +0200, Jiri Olsa escreveu:
> Currently all the event parsing fails end up
> in the event_pmu rule, and display misleading
> help like:
>
> $ perf stat -e inst kill
> event syntax error: 'inst'
>\___ Cannot find PMU `inst'. Missing
On Tue, 5 Jun 2018 15:10:11 +0200
Pierre Morel wrote:
> On 05/06/2018 13:38, Cornelia Huck wrote:
> > On Fri, 25 May 2018 12:21:14 +0200
> > Pierre Morel wrote:
> >
> >> We use mutex around the FSM function call to make the FSM
> >> event handling and state change atomic.
> > I'm still not
On Tue, May 29, 2018 at 4:09 PM, Ricardo Ribalda Delgado
wrote:
> Describe which hardware is supported by the current driver.
> +static struct serdev_device_id nokia_bluetooth_serdev_id[] = {
> + { "hp4-bluetooth", },
> + {},
Terminator line better w/o comma.
> +};
--
With
Hi Sudeep,
On Tue, Jun 5, 2018 at 3:55 PM, Sudeep Holla wrote:
> This reverts commit 37c3ec2d810f87eac73822f76b30391a83bded19.
>
> Currently on ARM64 platforms, we don't update the CPU topology masks
> on each hotplug operation. However, the updates to cpu_coregroup_mask
I would add
On Tuesday 05 Jun 2018 at 15:55:43 (+0200), Vincent Guittot wrote:
> On 5 June 2018 at 15:52, Quentin Perret wrote:
> > On Tuesday 05 Jun 2018 at 15:18:38 (+0200), Vincent Guittot wrote:
> >> On 5 June 2018 at 15:12, Quentin Perret wrote:
> >> I would say no because when one will decrease the
On 05/06/18 16:41, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jun 05, 2018 at 10:30:00AM +0300, Adrian Hunter escreveu:
>> Fix object code reading and the "Object code reading" test for PTI entry
>> trampolines.
>>
>> perf tools uses map__rip_2objdump() to calculate objdump virtual addresses.
>>
On Tue, Jun 05, 2018 at 11:35:15AM +, Arnd Bergmann wrote:
> When CONFIG_OPTIMIZE_INLINING is enabled, the function native_set_p4d()
> may not be fully inlined into the caller, resulting in a false-positive
> warning about an access to the __pgtable_l5_enabled variable from a
> non-__init
On Tue, Jun 05, 2018 at 01:46:59PM +, yang wrote:
> Fix compile warnings:
> CC kernel/sched/fair.o
> kernel/sched/fair.c:2461:6: warning: no previous prototype for
> ‘task_numa_work’ [-Wmissing-prototypes]
> void task_numa_work(struct callback_head *work)
> ^
>
On 05/06/2018 15:52, Cornelia Huck wrote:
On Tue, 5 Jun 2018 15:34:52 +0200
Pierre Morel wrote:
On 04/06/2018 15:52, Cornelia Huck wrote:
On Fri, 25 May 2018 12:21:09 +0200
Pierre Morel wrote:
Let's move the state change from the IRQ routine to the
workqueue callback.
Signed-off-by:
Hi Rudolf,
I have been investigating the status with the AMD release management, but I
have not been given approval to publish any other microcode. I have been
trying to track down why there might be a version in the wild that I have not
been given for public publishing. It might have come
On Tue, Jun 05, 2018 at 02:01:29AM +1000, James Morris wrote:
> On Sat, 2 Jun 2018, Jarkko Sakkinen wrote:
>
> > The following changes since commit 424eaf910c329ab06ad03a527ef45dcf6a328f00:
> >
> > tpm: reduce polling time to usecs for even finer granularity (2018-05-18
> > 10:00:01 +0300)
>
On 05/06/2018 12:39, Viresh Kumar wrote:
> On 05-06-18, 11:16, Daniel Lezcano wrote:
>> diff --git a/drivers/powercap/idle_injection.c
>> b/drivers/powercap/idle_injection.c
>> +/**
>> + * idle_injection_wakeup - Wake up all idle injection threads
>> + * @ii_dev: the idle injection device
>> + *
On Mon, 4 Jun 2018 at 20:18, Stephen Rothwell wrote:
>
> Hi Trond,
>
> After merging the nfs tree, today's linux-next build (arm
> multi_v7_defconfig) produced this warning:
>
> fs/nfs/nfs4proc.c:910:13: warning: 'nfs4_layoutget_release' defined but not
> used [-Wunused-function]
> static void
On Tue, Jun 05, 2018 at 04:43:04PM +0200, Peter Zijlstra wrote:
> I can make a proper patch, hold on.
---
Subject: atomic/tty: Fix up atomic abuse in ldsem
Mark found ldsem_cmpxchg() needed an (atomic_long_t *) cast to keep
working after making the atomic_long interface type safe.
Needing
On Wed, 30 May 2018 15:14:32 +0200
Frieder Schrempf wrote:
> +
> +static void fsl_qspi_read_ahb(struct fsl_qspi *q, const struct spi_mem_op
> *op)
> +{
> + static int seq;
> +
> + /*
> + * We want to avoid needing to invalidate the cache by issueing
> + * a reset to the AHB
On Tue, Jun 5, 2018 at 4:35 PM, Sudeep Holla wrote:
> Though CONFIG_ACPI_PPTT is selected by platforms and nor user visible,
> it may be useful to support the build with CONFIG_ACPI_PPTT disabled.
>
> This patch adds the missing dummy/boiler plate implementation to fix
> the build.
>
> Cc:
On 29/05/18 11:55, Suzuki K Poulose wrote:
This series adds support for counting PMU events using 64bit counters
for arm64 PMU.
The Arm v8 PMUv3 supports combining two adjacent 32bit counters
(low even and hig odd counters) to count a given "event" in 64bit mode.
This series adds the support
I have to admit that I didn't try to follow this discussion, somehow I thought
that the plan was to use set_special_state(PARKED)...
On 06/05, Kohli, Gaurav wrote:
>
> As last mentioned on mail, we are still seeing issue with the latest
> approach and below is the susceptible race as mentioned
On Tue, May 29, 2018 at 4:35 AM, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 786b71f5b754273ccef6d9462e52062b3e1f9877
> commit: 854e55ad289efe7991f0ada85d5846f5afb9 objtool, perf: Fix GCC 8
> -Wrestrict error
>
On 05/06/18 16:11, Patrick Bellasi wrote:
[...]
> If I run an experiment with your example above, while using the
> performance governor to rule out any possible scale invariance
> difference, here is what I measure:
>
>Task1 (40ms delayed by the following Task2):
>
On Tue, Jun 5, 2018 at 6:30 PM, Josh Poimboeuf wrote:
> On Tue, Jun 05, 2018 at 06:19:07PM +0300, Andy Shevchenko wrote:
>> On Tue, May 29, 2018 at 4:35 AM, kbuild test robot wrote:
>> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> > master
>> > head:
From: Kan Liang
Context switches with perf LBR call stack context are fairly expensive
because they do a lot of MSR writes. Currently we unconditionally do the
expensive operation when LBR call stack is enabled. It's not necessary
for some common cases, e.g task -> other kernel thread -> same
From: Kan Liang
LBR has a limited stack size. If a task has a deeper call stack than
LBR's stack size, only the overflowed part is reported. A complete call
stack may not be reconstructed by perf tool.
Current code doesn't access all LBR registers. It only read the ones
below the TOS. The LBR
Hi Olivier,
On 03/13/2018 05:27 PM, Olivier MOYSAN wrote:
> Add support of iec958 controls for STM32 SAI.
>
> Signed-off-by: Olivier Moysan
> ---
> sound/core/pcm_iec958.c | 1 +
> sound/soc/stm/Kconfig | 1 +
> sound/soc/stm/stm32_sai_sub.c | 101
>
On Tue, Jun 05, 2018 at 12:29:43PM -0300, Arnaldo Carvalho de Melo wrote:
> > Arnaldo has queued the tools patches, but there are still 3 kernel patches:
> >
> > kallsyms: Simplify update_iter_mod()
> > kallsyms, x86: Export addresses of syscall trampolines
That one needs a changelog.
>
At the moment, afs_break_callbacks calls afs_break_one_callback() for each
separate FID it was given, and the latter looks up the volume individually
for each one.
However, this is inefficient if two or more FIDs have the same vid as we
could reuse the volume. This is complicated by cell
On Mon, Jun 04, 2018 at 06:21:22PM +0200, Dmitry Vyukov wrote:
> On Tue, May 29, 2018 at 8:07 PM, Mark Rutland wrote:
> > While the diff stat looks like a huge addition, the scripting comes in
> > at ~800 lines in total, including the fallback definitions, so we're
> > removing ~1000 lines of
From: Josef Bacik
We don't really need to save this stuff in the core block code, we can
just pass the bio back into the helpers later on to derive the same
flags and update the rq->wbt_flags appropriately.
Signed-off-by: Josef Bacik
---
block/blk-core.c | 9 -
block/blk-mq.c |
Em Tue, Jun 05, 2018 at 10:30:00AM +0300, Adrian Hunter escreveu:
> Fix object code reading and the "Object code reading" test for PTI entry
> trampolines.
>
> perf tools uses map__rip_2objdump() to calculate objdump virtual addresses.
> map__rip_2objdump() needs to be amended to deal with PTI
From: Stefan Popa
To: ji...@kernel.org,
michael.henner...@analog.com,
l...@metafoo.de
Cc: knaac...@gmx.de,
pme...@pmeerw.net,
mche...@kernel.org,
da...@davemloft.net,
gre...@linuxfoundation.org,
a...@linux-foundation.org,
Hi Ricardo,
> Describe which hardware is supported by the current driver.
>
> Cc: Marcel Holtmann
> Cc: Johan Hedberg
> Cc: Rob Herring
> Cc: Johan Hovold
> Cc: linux-blueto...@vger.kernel.org
> Signed-off-by: Ricardo Ribalda Delgado
> ---
> drivers/bluetooth/hci_nokia.c | 6 ++
> 1 file
Signed-off-by: Stefan Popa
---
.../devicetree/bindings/iio/dac/ad5758.txt | 84 ++
MAINTAINERS| 1 +
2 files changed, 85 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/dac/ad5758.txt
diff --git
On Tue, 5 Jun 2018 15:34:52 +0200
Pierre Morel wrote:
> On 04/06/2018 15:52, Cornelia Huck wrote:
> > On Fri, 25 May 2018 12:21:09 +0200
> > Pierre Morel wrote:
> >
> >> Let's move the state change from the IRQ routine to the
> >> workqueue callback.
> >>
> >> Signed-off-by: Pierre Morel
>
On Tue, Jun 05, 2018 at 09:17:52AM +0200, Miroslav Benes wrote:
> On Mon, 4 Jun 2018, Josh Poimboeuf wrote:
>
> > On Mon, Jun 04, 2018 at 04:16:35PM +0200, Miroslav Benes wrote:
> > > An administrator may send a fake signal to all remaining blocking tasks
> > > of a running transition by writing
On Tue, Jun 05, 2018 at 03:56:16PM +0200, Peter Zijlstra wrote:
> On Tue, Jun 05, 2018 at 02:28:02PM +0100, Mark Rutland wrote:
> > On Tue, Jun 05, 2018 at 02:16:23PM +0200, Peter Zijlstra wrote:
> > > and simply using smp_mb__{before,after}_atomic for the full fence, its
> > > exactly what they
On 05/06/18 15:01, Quentin Perret wrote:
> On Tuesday 05 Jun 2018 at 15:15:18 (+0200), Juri Lelli wrote:
> > On 05/06/18 14:05, Quentin Perret wrote:
> > > On Tuesday 05 Jun 2018 at 14:11:53 (+0200), Juri Lelli wrote:
> > > > Hi Quentin,
> > > >
> > > > On 05/06/18 11:57, Quentin Perret wrote:
>
The following changes since commit 75bc37fefc4471e718ba8e651aa74673d4e0a9eb:
Linux 4.17-rc4 (2018-05-06 16:57:38 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
tags/ext4_for_linus
for you to fetch changes up to
On Tue, Jun 5, 2018 at 4:35 PM, Sudeep Holla wrote:
> Currently, ARM64 doesn't support updating the CPU topology masks on
> CPU hotplug operations. ACPI PPTT support rely on that missing feature
> which is technically not incorrect. Instead of reverting all the PPTT
> support, let's keep it
On 05/06/18 16:18, Peter Zijlstra wrote:
> On Mon, Jun 04, 2018 at 08:08:58PM +0200, Vincent Guittot wrote:
[...]
> > As you mentioned, scale_rt_capacity give the remaining capacity for
> > cfs and it will behave like cfs util_avg now that it uses PELT. So as
> > long as cfs util_avg <
On 05/06/18 16:00, Rafael J. Wysocki wrote:
> On Tue, Jun 5, 2018 at 4:35 PM, Sudeep Holla wrote:
>> Though CONFIG_ACPI_PPTT is selected by platforms and nor user visible,
>> it may be useful to support the build with CONFIG_ACPI_PPTT disabled.
>>
>> This patch adds the missing dummy/boiler
Em Tue, Jun 05, 2018 at 09:00:17AM +0300, Alexey Budankov escreveu:
> Hi,
> On 04.06.2018 22:16, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jun 04, 2018 at 06:22:43PM +0300, Alexey Budankov escreveu:
> >> On 04.06.2018 17:58, Arnaldo Carvalho de Melo wrote:
> >>> Em Mon, Jun 04, 2018 at
On Tue, Jun 05, 2018 at 12:51:24AM +0900, Masami Hiramatsu wrote:
> Remove arch dependent setjump/longjump functions
> and unused fields in kprobe_ctlblk for jprobes
> from arch/arm64.
>
> Signed-off-by: Masami Hiramatsu
> Cc: Catalin Marinas
> Cc: Will Deacon
> Cc:
Hello Thierry,
Can you please share your comments on the patch?
Thanks,
Shenwei
-Original Message-
From: Shenwei Wang
Sent: Wednesday, May 30, 2018 12:00 PM
To: thierry.red...@gmail.com
Cc: linux-...@vger.kernel.org; dl-linux-imx ;
linux-kernel@vger.kernel.org
Subject: RE: [PATCH 1/1]
Hello,
On Tue, Jun 05, 2018 at 10:31:36AM -0500, Eric W. Biederman wrote:
> What I have above is not the clearest, and in fact the logic could be
> better.
>
> The fundamental challenge is because hash collisions are possible a file
> offset does not hold complete position information in a
Hi Takashi,
On 04/17/2018 01:17 PM, Mark Brown wrote:
> On Tue, Apr 17, 2018 at 08:29:17AM +, Olivier MOYSAN wrote:
>
>> I guess the blocking patch in this patchset is the patch "add IEC958
>> channel status control helper". This patch has been reviewed several
>> times, but did not get a
Am Dienstag, 5. Juni 2018, 17:35:01 CEST schrieb Theodore Y. Ts'o:
> On Tue, Jun 05, 2018 at 05:13:35PM +0200, Richard Weinberger wrote:
> > > Add bunch of cleanups, and add support for the Speck128/256
> > > algorithms. Yes, Speck is contrversial, but the intention is to use
> > > them only for
On Mon, Jun 4, 2018 at 11:44 AM Josh Poimboeuf wrote:
>
> Linus, would you be willing to pick these up directly, or would you
> rather me route them through somebody else?
I took them directly.
That said, if you had a git tree, that would have fit my merge-window
workflow better. I've been very
On Mon, May 21, 2018 at 3:53 PM, Sudeep Holla wrote:
> of_property_read_u32 searches for a property in a device node and read
> a 32-bit value from it. Instead of using of_get_property to get the
> property and then read 32-bit value using of_read_number, we can
> simplify it by using
Em Tue, Jun 05, 2018 at 02:13:13PM +0200, Jiri Olsa escreveu:
> Adding the support to read rusage data once the
> workload is finished and display the system/user
> time values:
> Those times are the very same displayed by 'time' tool.
> They are returned by wait4 call via the getrusage struct
>
Though CONFIG_ACPI_PPTT is selected by platforms and nor user visible,
it may be useful to support the build with CONFIG_ACPI_PPTT disabled.
This patch adds the missing dummy/boiler plate implementation to fix
the build.
Cc: "Rafael J. Wysocki"
Signed-off-by: Sudeep Holla
---
On 05.06.2018 12:36, Dmitry Vyukov wrote:
> On Tue, Jun 5, 2018 at 11:03 AM, Kirill Tkhai wrote:
>> Hi, Dmirty!
>>
>> On 04.06.2018 18:22, Dmitry Vyukov wrote:
>>> On Mon, Jun 4, 2018 at 5:03 PM, syzbot
>>> wrote:
Hello,
syzbot found the following crash on:
HEAD commit:
On 05/06/2018 14:18, Cornelia Huck wrote:
On Fri, 25 May 2018 12:21:16 +0200
Pierre Morel wrote:
Two new events, VFIO_CCW_EVENT_ONLINE and VFIO_CCW_EVENT_OFFLINE
allow to handle the enabling and disabling of a Sub Channel and
the init, shutdown, quiesce and reset operations are changed
On Tue, Jun 05, 2018 at 04:20:51PM +0200, Greg Kroah-Hartman wrote:
> I think Peter Hurley was just trying to hid the atomic mess behind
> function calls, which is why he didn't open-code it like you did here.
No reason to then not use the right types though. I mean, you can still
use the helper
* Linus Torvalds wrote:
> On Mon, Jun 4, 2018 at 5:21 AM Ingo Molnar wrote:
> >
> > - __clear_user() micro-optimization (Alexey Dobriyan)
>
> Was this actually tested?
I'm not sure - Alexey?
> I think one reason people avoided the constant was that on some
> microarchitecture it ended up
On Mon, Jun 04, 2018 at 12:00:33PM +0200, Clément Péron wrote:
> From: Clément Peron
>
> Add devicetree binding document for NXP's i.MX SoC specific
> EPIT timer driver.
>
> Signed-off-by: Clément Peron
> ---
> .../devicetree/bindings/timer/fsl,imxepit.txt | 21 +++
> 1 file
On Tue, 5 Jun 2018 16:10:52 +0200
Pierre Morel wrote:
> On 05/06/2018 14:18, Cornelia Huck wrote:
> > On Fri, 25 May 2018 12:21:16 +0200
> > Pierre Morel wrote:
> >> +static int fsm_online(struct vfio_ccw_private *private)
> >> +{
> >> + struct subchannel *sch = private->sch;
> >> + int ret
On 05/06/18 16:02, Rafael J. Wysocki wrote:
> On Tue, Jun 5, 2018 at 4:35 PM, Sudeep Holla wrote:
>> Currently, ARM64 doesn't support updating the CPU topology masks on
>> CPU hotplug operations. ACPI PPTT support rely on that missing feature
>> which is technically not incorrect. Instead of
On Wed, May 23, 2018 at 5:06 PM, Pavel Machek wrote:
> On Thu 2018-05-17 06:59:49, H. Nikolaus Schaller wrote:
>> The register constants are so far defined in a way that they fit
>> for the pcal9555a when shifted by the number of banks, i.e. are
>> multiplied by 2 in the accessor function.
>>
>>
> +#ifdef CONFIG_X86_64
> +int arch_get_kallsym(unsigned int symnum, unsigned long *value, char *type,
> + char *name)
> +{
> + unsigned int cpu, ncpu;
> +
> + if (symnum >= num_possible_cpus())
> + return -EINVAL;
> +
> + for (cpu =
Em Tue, Jun 05, 2018 at 06:00:46PM +0200, Peter Zijlstra escreveu:
> On Tue, Jun 05, 2018 at 12:29:43PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Arnaldo has queued the tools patches, but there are still 3 kernel
> > > patches:
> > >
> > > kallsyms: Simplify update_iter_mod()
> > >
On Wed, May 23, 2018 at 10:47 AM, Yisheng Xie wrote:
> Hi Andy,
>
> On 2018/5/22 6:00, Andy Shevchenko wrote:
>> On Mon, May 21, 2018 at 2:57 PM, Yisheng Xie wrote:
>>> match_string() returns the index of an array for a matching string,
>>> which can be used intead of open coded variant.
>>
>>>
On 6/1/2018 9:59 AM, Konrad Rzeszutek Wilk wrote:
> Hi,
>
> I was reading the AMD whitepaper on SSBD and noticed that they have added
> two new bits in the 8000_0008 CPUID. EBX:
> 1) Bit[26] - similar to Intel's SSB_NO not needed anymore.
> 2) Bit[24] - use SPEC_CTRL MSR (0x48) instead of VIRT
On Tue, May 29, 2018 at 4:10 PM, Ricardo Ribalda Delgado
wrote:
> If a serdev ttyport controller does not have an acpi nor an of child,
> create a ttydev as a child of that controller.
>
> Doing this allows the removal, addition and replacement of ttydev devices
> at runtime.
> @@ -619,6 +619,27
On Tue, Jun 5, 2018 at 12:55 AM, Peter Hutterer
wrote:
> On Mon, Jun 04, 2018 at 02:19:44PM -0700, Dmitry Torokhov wrote:
>> On Mon, Jun 04, 2018 at 10:42:31PM +0200, Benjamin Tissoires wrote:
>> > On Mon, Jun 4, 2018 at 7:33 PM, Dmitry Torokhov
>> > wrote:
>> > > On Mon, Jun 04, 2018 at
On Tuesday 05 Jun 2018 at 15:15:18 (+0200), Juri Lelli wrote:
> On 05/06/18 14:05, Quentin Perret wrote:
> > On Tuesday 05 Jun 2018 at 14:11:53 (+0200), Juri Lelli wrote:
> > > Hi Quentin,
> > >
> > > On 05/06/18 11:57, Quentin Perret wrote:
> > >
> > > [...]
> > >
> > > > What about the diff
On Tue, Jun 05, 2018 at 02:00:22PM +0200, Peter Zijlstra wrote:
> On Tue, May 29, 2018 at 07:07:40PM +0100, Mark Rutland wrote:
> > In ldsem_cmpxchg a pointer to unsigned long is passed to
> > atomic_long_cmpxchg(), which expects a pointer to atomic_long_t.
>
> > - long tmp =
On 05/06/2018 15:35, Cornelia Huck wrote:
On Tue, 5 Jun 2018 15:10:11 +0200
Pierre Morel wrote:
On 05/06/2018 13:38, Cornelia Huck wrote:
On Fri, 25 May 2018 12:21:14 +0200
Pierre Morel wrote:
We use mutex around the FSM function call to make the FSM
event handling and state change
On Tue, Jun 05, 2018 at 08:22:22AM -0600, Jens Axboe wrote:
> > I fucked up majorly on the bioset/mempool conversion - I forgot to check
> > that
> > everything biosets/mempools were being embedded in was actually being
> > zeroed on
> > allocation. Device mapper currently explodes, you'll
On Tue, Jun 05 2018 at 10:22P -0400,
Jens Axboe wrote:
> On 6/5/18 3:26 AM, Kent Overstreet wrote:
> > mempool_init()/bioset_init() require that the mempools/biosets be zeroed
> > first; they probably should not _require_ this, but not allocating those
> > structs with kzalloc is a fairly
The following changes since commit 75bc37fefc4471e718ba8e651aa74673d4e0a9eb:
Linux 4.17-rc4 (2018-05-06 16:57:38 -1000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/fscrypt.git
tags/fscrypt_for_linus
for you to fetch changes up to
On 29/05/18 09:27, Manivannan Sadhasivam wrote:
> Hi Matthias,
>
> On Tue, May 29, 2018 at 08:38:27AM +0200, Matthias Brugger wrote:
>> Hi Manivannan,
>>
>> it's nice to see that someone at Linaro cares about upstreaming the 96 board.
>> From what I can see, your patches add the very same
On Tue, 5 Jun 2018 16:21:03 +0200
Pierre Morel wrote:
> On 05/06/2018 15:35, Cornelia Huck wrote:
> > On Tue, 5 Jun 2018 15:10:11 +0200
> > Pierre Morel wrote:
> >
> >> On 05/06/2018 13:38, Cornelia Huck wrote:
> >>> On Fri, 25 May 2018 12:21:14 +0200
> >>> Pierre Morel wrote:
> >>>
>
Em Tue, Jun 05, 2018 at 05:08:35PM +0300, Adrian Hunter escreveu:
> On 05/06/18 16:41, Arnaldo Carvalho de Melo wrote:
> > And this test fails way less often, but still does, for instance:
> > # while true ; do perf test -v object 2>out.txt ; grep -i fail out.txt &&
> > break ; done
> >
"Hatayama, Daisuke" writes:
>> >> +
>> >> + /* Is the saved position usable? */
>> >> + if (saved) {
>> >> + /* Proper parent and hash? */
>> >> + if ((parent != saved->parent) || (saved->hash != hash)) {
>> >> + saved = NULL;
>> >
>> > name is uninitialized in
Em Thu, May 31, 2018 at 01:23:41PM +0300, Adrian Hunter escreveu:
> Hi
>
> Here are some small non-urgent fixes for Intel PT.
Thanks, applied the kit,
- Arnaldo
>
> Adrian Hunter (4):
> perf intel-pt: Fix sync_switch INTEL_PT_SS_NOT_TRACING
> perf intel-pt: Fix decoding to accept
On 05-Jun 16:18, Peter Zijlstra wrote:
> On Mon, Jun 04, 2018 at 08:08:58PM +0200, Vincent Guittot wrote:
> > On 4 June 2018 at 18:50, Peter Zijlstra wrote:
>
> > > So this patch-set tracks the !cfs occupation using the same function,
> > > which is all good. But what, if instead of using that
The AFS filesystem depends at the moment on /proc for configuration and
also presents information that way - however, this causes a compilation
failure if procfs is disabled.
Fix it so that the procfs bits aren't compiled in if procfs is disabled.
This means that you can't configure the AFS
Alter the dynroot mount so that cells created by manipulation of
/proc/fs/afs/cells and /proc/fs/afs/rootcell and by specification of a root
cell as a module parameter will cause directories for those cells to be
created in the dynamic root superblock for the network namespace[*].
To this end:
Show all of a server's addresses in /proc/fs/afs/servers, placing the
second plus addresses on padded lines of their own. The current address is
marked with a star.
Signed-off-by: David Howells
---
fs/afs/proc.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git
Remove the restriction on DNS lookup upcalls that prevents ipv6 addresses
from being looked up.
Signed-off-by: David Howells
---
fs/afs/addr_list.c |2 +-
fs/afs/dynroot.c |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/afs/addr_list.c b/fs/afs/addr_list.c
On 5 June 2018 at 05:48, Arnd Bergmann wrote:
> The newly introduced code fails to build in some configurations
> unless we include the right headers:
>
> drivers/hwtracing/coresight/coresight-tmc-etr.c: In function
> 'tmc_free_table_pages':
>
Hi Al,
Here's a set of AFS patches, one fixes, but mostly development. The fix is:
(1) Fix AFS to build if CONFIG_PROC_FS=n.
and the development patches:
(1) Make AFS show all of a server's addresses in /proc/fs/afs/servers.
(2) Allow DNS upcalls to ask for IPv6 addresses.
(3) Add
On 05/06/18 17:12, Rafael J. Wysocki wrote:
> On Tue, Jun 5, 2018 at 5:33 PM, Sudeep Holla wrote:
>>
>>
>> On 05/06/18 16:00, Rafael J. Wysocki wrote:
>>> On Tue, Jun 5, 2018 at 4:35 PM, Sudeep Holla wrote:
Though CONFIG_ACPI_PPTT is selected by platforms and nor user visible,
it
Use CC_SET(z)/CC_OUT(z) instead of explicit setz instruction.
Using these two defines, the compiler that supports generation of
condition code outputs from inline assembly flags generates e.g.:
cmpxchg8b %fs:(%esi)
jne172255 <__kmalloc+0x65>
instead of
cmpxchg8b %fs:(%esi)
sete
On 05-Jun 17:31, Juri Lelli wrote:
> On 05/06/18 16:11, Patrick Bellasi wrote:
>
> [...]
>
> > If I run an experiment with your example above, while using the
> > performance governor to rule out any possible scale invariance
> > difference, here is what I measure:
> >
> >Task1 (40ms
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Tomas Winkler
commit 93fdd5ac64bbe80dac6416f048405362d7ef0945 upstream.
Pull device descriptor reading out of ufs quirk so it can be used also
for other purposes.
Revamp the fixup setup:
1.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Potomski, MichalX
commit a4b0e8a4e92b1baa860e744847fbdb84a50a5071 upstream.
Since in UFS 2.1 specification some of the descriptor lengths differs
from 2.0 specification and some devices, which
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream.
The recent LPM changes to setup_rfi_flush() are causing some section
mismatch warnings because we removed the __init
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mauricio Faria de Oliveira
commit 6232774f1599028a15418179d17f7df47ede770a upstream.
After migration the security feature flags might have changed (e.g.,
destination system with unpatched
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Tissoires
commit 40f7090bb1b4ec327ea1e1402ff5783af5b35195 upstream.
New ICs (like the one on the Lenovo T480s) answer to
ETP_SMBUS_IAP_VERSION_CMD 4 bytes instead of 3. This corrupts
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Greg Kroah-Hartman
This reverts commit 0bd77073e693e8f93ff6ddba65a9f426153221cb which is
commit a7aa75a2a7dba32594291a71c3704000a2fd7089 upstream.
There's been too many complaints about this.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Sachin Grover
commit efe3de79e0b52ca281ef6691480c8c68c82a4657 upstream.
Call trace:
[] dump_backtrace+0x0/0x428
[] show_stack+0x28/0x38
[] dump_stack+0xd4/0x124
[]
On Tue, Jun 05, 2018 at 03:50:15PM +0200, Benjamin Tissoires wrote:
> On Tue, Jun 5, 2018 at 12:55 AM, Peter Hutterer
> wrote:
> > On Mon, Jun 04, 2018 at 02:19:44PM -0700, Dmitry Torokhov wrote:
> >> On Mon, Jun 04, 2018 at 10:42:31PM +0200, Benjamin Tissoires wrote:
> >> > On Mon, Jun 4, 2018
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Ellerman
commit eb0a2d2620ae431c543963c8c7f08f597366fc60 upstream.
Some versions of firmware will have a setting that can be configured
to disable the RFI flush, add support for it.
This is the start of the stable review cycle for the 4.9.107 release.
There are 61 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Jun 7 17:00:59 UTC 2018.
Anything
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mimi Zohar
commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b upstream.
Userspace applications have been modified to write security xattrs,
but they are not context aware. In the case of
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit 90f779e565bdc18dd4f79d81cf11f43a7266010b upstream.
Signed-off-by: Wolfram Sang
Signed-off-by: Wolfram Sang
Signed-off-by: Fabrizio Castro
Reviewed-by: Chris Paterson
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wolfram Sang
commit ff2316b87a336bff940939cd9fc56287ed48e578 upstream.
After making sure to reinit the HW and clear interrupts in the timeout
case, we know that interrupts are always disabled
[Cc +dwmw2]
On Fri, 25 May 2018 14:54:08 -0600
Alex Williamson wrote:
> On Fri, 25 May 2018 08:45:36 +
> Shameerali Kolothum Thodi wrote:
>
> > Yes, the above changes related to list empty cases looks fine to me.
>
> Thanks Shameer, applied to my next branch with the discussed fixes
301 - 400 of 1606 matches
Mail list logo
