With bpf_program__get_prog_info_linear, we can simplify the logic that
synthesizes bpf events.
This patch doesn't change the behavior of the code.
Signed-off-by: Song Liu
---
tools/perf/util/bpf-event.c | 118
1 file changed, 40 insertions(+), 78
bpf_prog_info contains information necessary to annotate bpf programs.
This patch saves bpf_prog_info for bpf programs loaded in the system.
Signed-off-by: Song Liu
---
tools/perf/builtin-record.c | 2 +-
tools/perf/builtin-top.c| 2 +-
tools/perf/util/bpf-event.c | 35 +--
bpf events should be tracked by default for perf-top. This patch makes it
on by default, and adds option to disable bpf events.
Signed-off-by: Song Liu
---
tools/perf/builtin-top.c | 3 +++
tools/perf/util/top.h| 1 +
2 files changed, 4 insertions(+)
diff --git a/tools/perf/builtin-top.c
btf contains information necessary to annotate bpf programs. This patch
saves btf for bpf programs loaded in the system.
Signed-off-by: Song Liu
---
tools/perf/util/bpf-event.c | 24 ++
tools/perf/util/bpf-event.h | 7
tools/perf/util/env.c | 65
To annotate bpf programs in perf, it is necessary to save information in
bpf_prog_info and btf. For short living bpf program, it is necessary to
save these information before it is unloaded.
This patch saves these information in a separate thread. This thread
creates its own evlist, that only
On Fri 2019-02-15 13:50:10, Stefan Mavrodiev wrote:
> Teres-I and A64-OLinuXino commes with populated LED connected
> to AXP803. So to be used as battery indication, pass the LED control
> to the charger itself in mode 0 ( FULL while charging, OFF no battery
> or completed).
>
> Signed-off-by:
> On Feb 15, 2019, at 10:20 AM, Arnaldo Carvalho de Melo
> wrote:
>
> Em Fri, Feb 15, 2019 at 05:47:58PM +, Song Liu escreveu:
>>
>>
>>> On Feb 15, 2019, at 9:40 AM, Arnaldo Carvalho de Melo
>>> wrote:
>>>
>>> Em Fri, Feb 15, 2019 at 05:25:01PM +, Song Liu escreveu:
> On Feb
Events with bpf_event should be considered as side-band event, as they
carry information about BPF programs.
Fixes: 6ee52e2a3fe4 ("perf, bpf: Introduce PERF_RECORD_BPF_EVENT")
Signed-off-by: Song Liu
---
kernel/events/core.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
This patch enables the annotation of bpf program.
A new dso type DSO_BINARY_TYPE__BPF_PROG_INFO is introduced to for BPF
programs. In symbol__disassemble(), DSO_BINARY_TYPE__BPF_PROG_INFO dso
calls into a new function symbol__disassemble_bpf(), where annotation
line information is filled based
Fix the following warnings by adding the proper missing breaks:
drivers/scsi/mpt3sas/mpt3sas_base.c: In function ‘_base_display_OEMs_branding’:
drivers/scsi/mpt3sas/mpt3sas_base.c:3548:4: warning: this statement may fall
through [-Wimplicit-fallthrough=]
switch (ioc->pdev->subsystem_device)
Changes v2 to v3:
1. Remove unnecessary include in header files;
2. Improved error handling;
3. Better naming of functions, variables, etc.;
4. Enable bpf events by default for perf-top.
Changes v1 to v2:
1. Fix compilation error with different feature-disassembler-four-args;
2. Fix a segfault in
container_of simply does pointer arithmetic; it's not going to spit out NULL, so
this BUG_ON is unneeded.
Signed-off-by: Sultan Alsawaf
---
drivers/char/random.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/char/random.c b/drivers/char/random.c
index
On Fri, Feb 15, 2019 at 10:43:25AM -0800, Andrew Morton wrote:
> On Fri, 15 Feb 2019 10:20:10 -0800 (PST) "kernelci.org bot"
> wrote:
> > Details:https://kernelci.org/boot/id/5c666ea959b514b017fe6017
> > Plain log:
> > https://storage.kernelci.
Hi Linus,
The following changes since commit 8fc75bed96bb94e23ca51bd9be4daf65c57697bf:
NFS: Fix up return value on fatal errors in nfs_page_async_flush()
(2019-01-29
16:33:24 -0500)
are available in the Git repository at:
git://git.linux-nfs.org/projects/anna/linux-nfs.git
On Thu, Feb 14, 2019 at 06:39:59PM -0700, Nathan Chancellor wrote:
> After commit cc9f8349cb33 ("arm64: crypto: add NEON accelerated XOR
> implementation"), Clang builds for arm64 started failing with the
> following error message.
>
> arch/arm64/lib/xor-neon.c:58:28: error: incompatible pointer
On 14/02/2019 20:14, Alex Williamson wrote:
>> This patch series extends both IOMMU and vfio components to support
>> mdev device passing through when it could be isolated and protected
>> by the IOMMU units. The first part of this series (PATCH 1/09~6/09)
>> adds the interfaces and implementation
t; * found. No manual investigation has been done to verify it, *
> * and the root cause of the problem may be somewhere else. *
> * Hope this helps! *
> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
>
> next
Explicitly cancel/sync the irq_work delayed work, otherwise
there's a chance that it will run after the device is removed,
which would result in a use-after-free.
Note that cancel/sync should happen:
- after irq's have been disabled, as the isr re-schedules the work
- before the power supply is
[+Cc linux-fscrypt]
Hi David,
On Fri, Feb 15, 2019 at 04:10:45PM +, David Howells wrote:
> Allow a container manager to attach keyrings to a container such that the
> keys contained therein are searched by request_key() in addition to a
> process's normal keyrings. This allows the manager
Hi Yauhen,
On 2/15/19 8:27 AM, Yauhen Kharuzhy wrote:
On Fri, Feb 15, 2019 at 12:03:07AM +0100, Pavel Machek wrote:
Hi!
I suggest that we deal with this special case by adding 3 custom
sysfs attributes:
1) "mode" which when read, prints, e.g. :
manual [on-when-charging]
While this allows
Add missing break statement and fix identation issue.
This bug was found thanks to the ongoing efforts to enable
-Wimplicit-fallthrough.
Fixes: 9cb62fa24e0d ("aacraid: Log firmware AIF messages")
Cc: sta...@vger.kernel.org
Signed-off-by: Gustavo A. R. Silva
---
drivers/scsi/aacraid/commsup.c |
Call order on probe():
- max14656_hw_init() enables interrupts on the chip
- devm_request_irq() starts processing interrupts, isr
could be called immediately
-isr: schedules delayed work (irq_work)
-irq_work: calls power_supply_changed()
- devm_power_supply_register() registers the power
On Fri, Feb 15, 2019 at 03:31:26PM +, Colin King wrote:
> From: Colin Ian King
>
> The phrasing in two dev_err messages is using fallbacking which
> os less understandable than "falling back", so fix this up.
>
> Signed-off-by: Colin Ian King
Applied to for-next, thanks!
signature.asc
Hi all,
On 2/15/19 12:27 PM, Hans de Goede wrote:
Hi,
On 15-02-19 00:03, Pavel Machek wrote:
Hi!
I suggest that we deal with this special case by adding 3 custom
sysfs attributes:
1) "mode" which when read, prints, e.g. :
manual [on-when-charging]
While this allows _user on console_ to
Hi Pavel,
On 2/14/19 1:28 PM, Pavel Machek wrote:
Hi!
Jacek, could we get you to comment here? I'd prefer "hardware" trigger...
What prevents use from using pattern trigger with its hw_pattern file?
Do you remember drivers/leds/leds-sc27xx-bltc.c and its breathing mode,
for which pattern
The pull request you sent on Fri, 15 Feb 2019 11:17:11 -0800:
> git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git scsi-fixes
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5ded5871030eb75017639148da0a58931dfbfc25
Thank you!
--
Deet-doot-dot, I am a bot.
On 2/15/2019 2:29 PM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-15 11:29:26)
On 2/15/2019 11:47 AM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-11 08:09:00)
On 1/28/2019 11:10 PM, Stephen Boyd wrote:
+static int clk_init_parent(struct clk_core *core)
+{
+ core->parent =
Quoting Jeffrey Hugo (2019-02-15 11:29:26)
> On 2/15/2019 11:47 AM, Stephen Boyd wrote:
> > Quoting Jeffrey Hugo (2019-02-11 08:09:00)
> >> On 1/28/2019 11:10 PM, Stephen Boyd wrote:
> >>
> >>> +static int clk_init_parent(struct clk_core *core)
> >>> +{
> >>> + core->parent =
Quoting Brian Masney (2019-02-15 05:47:33)
> On Thu, Feb 14, 2019 at 09:51:26PM -0800, Stephen Boyd wrote:
> > > diff --git a/drivers/mfd/qcom-pm8xxx.c b/drivers/mfd/qcom-pm8xxx.c
> > > index 8eb2528793f9..2f99a98ccee5 100644
> > > --- a/drivers/mfd/qcom-pm8xxx.c
> > > +++
This is still an issue in the latest kernel version.
Sultan
On Mon, Apr 30, 2018 at 8:12 AM Sultan Alsawaf wrote:
>
> From a872cf4f0bb57a7bb3c95ea557082fb7733344f8 Mon Sep 17 00:00:00 2001
> From: Sultan Alsawaf
> Date: Sun, 29 Apr 2018 20:04:35 -0700
> Subject: [PATCH] random: remove unused
If mv643xx_eth_shared_of_probe() fails, mv643xx_eth_shared_probe()
leaves clk undisabled.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/net/ethernet/marvell/mv643xx_eth.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
On Fri, Feb 15, 2019 at 09:17:51AM +, Mehta, Sanju wrote:
> From: Sanjay R Mehta
>
> Add bug fix for ntb_perf and ntb_hw_amd
>
> Sanjay R Mehta (4):
> NTB: ntb_perf: Increased the number of message retries to 1000
> NTB: ntb_perf: Disable NTB link after clearing peer XLAT registers
>
On Fri, Feb 15, 2019 at 12:20:57PM -0800, Matthew Wilcox wrote:
> On Fri, Feb 15, 2019 at 01:41:15AM +0300, Kirill A. Shutemov wrote:
> > - __delete_from_swap_cache() will blow up on
> >
> > VM_BUG_ON_PAGE(entry != page + i, entry);
>
> Right.
Thanks. I think this is the last one I found.
Quoting Lina Iyer (2019-01-24 12:21:59)
> Add new bus token to describe domains that are wakeup capable.
>
> Suggested-by: Stephen Boyd
> Signed-off-by: Lina Iyer
> ---
> include/linux/irqdomain.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/include/linux/irqdomain.h
On Fri, Feb 15, 2019 at 12:52 PM Andrew F. Davis wrote:
> On 2/15/19 1:58 PM, John Stultz wrote:
> > So yea, I don't think we should tie our hands in reworking the
> > interfaces, but it would be nice to avoid having subtle ABI changes
> > that don't have clear ways for userland to detect which
On Thu, 2019-02-14 at 18:43 -0600, Bjorn Helgaas wrote:
> Hi Lyude,
>
> On Tue, Feb 12, 2019 at 05:02:30PM -0500, Lyude Paul wrote:
> > On a very specific subset of ThinkPad P50 SKUs, particularly ones that
> > come with a Quadro M1000M chip instead of the M2000M variant, the BIOS
> > seems to
Quoting Jerome Brunet (2019-02-13 01:32:23)
> On Tue, 2019-01-29 at 10:56 -0800, Stephen Boyd wrote:
> > > > +/**
> > > > + * struct clk_parent_data - clk parent information
> > > > + * @hw: parent clk_hw pointer (used for clk providers with internal
> > > > clks)
> > > > + * @name: parent name
Quoting Brendan Higgins (2019-02-14 13:37:14)
> @@ -104,6 +167,7 @@ struct kunit {
> const char *name; /* Read only after initialization! */
> spinlock_t lock; /* Gaurds all mutable test state. */
> bool success; /* Protected by lock. */
> + struct list_head
Quoting Brendan Higgins (2019-02-14 13:37:22)
> diff --git a/kunit/test-test.c b/kunit/test-test.c
> index 0b4ad6690310d..bb34431398526 100644
> --- a/kunit/test-test.c
> +++ b/kunit/test-test.c
[...]
> +
> +#define KUNIT_RESOURCE_NUM 5
> +static void kunit_resource_test_cleanup_resources(struct
On 2/15/19 1:58 PM, John Stultz wrote:
> On Fri, Feb 15, 2019 at 11:22 AM Andrew F. Davis wrote:
>>
>> On 2/15/19 1:01 PM, John Stultz wrote:
>>> On Fri, Feb 15, 2019 at 2:51 AM Brian Starkey wrote:
On Thu, Feb 14, 2019 at 09:38:29AM -0800, John Stultz wrote:
> 2) For patches that cause
The rwsem_down_read_failed*() functions were relocted from above the
optimistic spinning section to below that section. This enables the
reader functions to use optimisitic spinning in future patches. There
is no code change.
Signed-off-by: Waiman Long
---
kernel/locking/rwsem-xadd.c | 172
Currently, the DEBUG_RWSEMS_WARN_ON() macro just dumps a stack trace
when the rwsem isn't in the right state. It does not show the actual
states of the rwsem. This may not be that helpful in the debugging
process.
Enhance the DEBUG_RWSEMS_WARN_ON() macro to also show the current
content of the
When rwsem_down_read_failed*() return, the read lock is acquired
indirectly by others. So debug checks are added in __down_read() and
__down_read_killable() to make sure the rwsem is really reader-owned.
The other debug check calls in kernel/locking/rwsem.c except the
one in up_read_non_owner()
On Fri, Feb 15, 2019 at 09:22:21AM -0800, Guenter Roeck wrote:
> On Fri, Feb 15, 2019 at 07:56:22AM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Feb 14, 2019 at 01:02:26PM -0800, Guenter Roeck wrote:
> > > On Wed, Feb 13, 2019 at 07:38:05PM +0100, Greg Kroah-Hartman wrote:
> > > > This is the
The atomic_long_cmpxchg_acquire() in rwsem_try_read_lock_unqueued() is
replaced by atomic_long_try_cmpxchg_acquire() to simpify the code and
generate slightly better assembly code. There is no functional change.
Signed-off-by: Waiman Long
---
kernel/locking/rwsem-xadd.c | 15 +--
1
Moves all the owner setting code closer to the rwsem-xadd fast paths
directly within rwsem.h file.
For __down_read() and __down_read_killable(), it is assumed that
rwsem will be marked as reader-owned when the functions return. That
is currently true except in the transient case that the waiter
The percpu event counts used by qspinlock code can be useful for
other locking code as well. So a new set of lockevent_* counting APIs
is introduced with the lock event names extracted out into the new
lock_events_list.h header file for easier addition in the future.
The existing qstat_inc()
The QUEUED_LOCK_STAT option to report queued spinlocks event counts
was previously allowed only on x86 architecture. To make the locking
event counting code more useful, it is now renamed to a more generic
LOCK_EVENT_COUNTS config option. This new option will be available to
all the architectures
On bare metail, the pvqspinlock event counts will always be 0. So there
is no point in showing their corresponding debugfs files. So they are
skipped in this case.
Signed-off-by: Waiman Long
---
kernel/locking/lock_events.c | 28 +++-
1 file changed, 27 insertions(+), 1
v2:
- Sync up to v4 of the part 0 patch.
- Remove the rwsem.h->rwsem-xadd.h renaming patch & change patches
to modify rwsem.h instead of rwsem-xadd.h.
- Add a new patch to micro-optimize rwsem_try_read_lock_unqueued().
This is part 1 of a 3-part (0/1/2) series to rearchitect the
Add lock event counting calls so that we can track the number of lock
events happening in the rwsem code.
With CONFIG_LOCK_EVENT_COUNTS on and booting a 4-socket 112-thread x86-64
system, the rwsem counts after system bootup were as follows:
rwsem_opt_fail=261
rwsem_opt_wlock=50636
We don't need to expose rwsem internal functions which are not supposed
to be called directly from other kernel code.
Signed-off-by: Waiman Long
---
include/linux/rwsem.h | 7 ---
kernel/locking/rwsem.h | 7 +++
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git
Am Freitag, 15. Februar 2019, 13:08:16 CET schrieb agajjar:
> On 2/15/2019 2:48 PM, Heiko Stübner wrote:
> > Am Mittwoch, 13. Februar 2019, 18:06:38 CET schrieb Akash Gajjar:
> >> lcd panel pinmux and vcc1v8_s3 regulator is redundant and has a no
> >> impact,
> >> so removing it.
> >>
> >>
On Fri, Feb 15, 2019 at 12:37:57AM +0800, John Garry wrote:
> The sysfs phy_identifier attribute for a sas_end_device comes
> from the rphy phy_identifier value.
>
> Currently this is not being set for rphys with an end device attached,
> so we see incorrect symlinks from systemd disk/by-path:
>
On Thu, Feb 14, 2019 at 01:35:37PM +0300, Kirill Tkhai wrote:
> +static unsigned noinline_for_stack move_pages_to_lru(struct lruvec *lruvec,
> + struct list_head *list)
> {
> struct pglist_data *pgdat = lruvec_pgdat(lruvec);
> + int
Kieran,
> This commit was pipped to the post by a similar patch [0] from Felipe Balbi
No problem! I probably should watch the LKML closer.
Go with the patch from Felipe, but like you men there is definitely no need
for the `include linux/fs.h` now.
Thanks for the tip on the Fixes tag. As a
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of Kai-Heng Feng
> Sent: Saturday, February 2, 2019 9:40 AM
> To: Kirsher, Jeffrey T
> Cc: net...@vger.kernel.org; Kai-Heng Feng
> ; intel-wired-...@lists.osuosl.org; linux-
> ker...@vger.kernel.org
> Subject:
Add missing break statement in order to prevent the code from falling
through to case CB_TARGET_MASK.
This bug was found thanks to the ongoing efforts to enable
-Wimplicit-fallthrough.
Fixes: dd220a00e8bd ("drm/radeon/kms: add support for streamout v7")
Cc: sta...@vger.kernel.org
Signed-off-by:
On Fri, Feb 15, 2019 at 01:29:44AM +0300, Kirill A. Shutemov wrote:
> On Thu, Feb 14, 2019 at 04:30:04PM +0300, Kirill A. Shutemov wrote:
> > On Tue, Feb 12, 2019 at 10:34:54AM -0800, Matthew Wilcox wrote:
> > > Transparent Huge Pages are currently stored in i_pages as pointers to
> > >
Hi Felipe,
Thank you for the patch,
On 15/02/2019 11:29, Felipe Balbi wrote:
> Since commit e262e32d6bde0f77fb0c95d977482fc872c51996 "vfs: Suppress
> MS_* flag defs within the kernel unless explicitly enabled", the
> generated gdb scripts can't be used anymore. That commit moved the
> definition
Hi Dan,
Thank you for the patch,
On 15/02/2019 19:17, Dan Robertson wrote:
> The linux constants MS_RDONLY, MS_SYNCHRONOUS, MS_MANDLOCK, MS_DIRSYNC,
> MS_NOATIME, and MS_NODIRATIME were previously defined in linux/fs.h.
> Following e262e32d6bde0f77fb0c95d977482fc872c51996 the constants are
> now
On Fri, Feb 15, 2019 at 01:41:15AM +0300, Kirill A. Shutemov wrote:
> - __delete_from_swap_cache() will blow up on
>
> VM_BUG_ON_PAGE(entry != page + i, entry);
Right.
@@ -167,7 +167,7 @@ void __delete_from_swap_cache(struct page *page,
swp_entry_t entry)
for (i = 0; i < nr;
On Fri, Feb 15, 2019 at 11:38:20AM +0200, Mika Westerberg wrote:
> On Thu, Feb 14, 2019 at 03:26:19PM -0600, Bjorn Helgaas wrote:
> > On Thu, Jan 31, 2019 at 08:07:44PM +0300, Mika Westerberg wrote:
> > > Hi all,
> > >
> > > Heiner reported [1] that runtime PME generation of his network card does
The function prototype used to call JITed eBPF code (ie. the type of the
struct bpf_prog bpf_func field) returns an unsigned int. The MIPS n64
ABI that MIPS64 kernels target defines that 32 bit integers should
always be sign extended when passed in registers as either arguments or
return values.
YueHaibing writes:
> Since commit 1c459de1e645 ("ARM: pxa: ssp: use devm_ functions")
> kfree, iounmap, clk_put etc no need do any more in remove path.
>
> Fixes: 1c459de1e645 ("ARM: pxa: ssp: use devm_ functions")
> Signed-off-by: YueHaibing
Sorry for the late reply, I had forgotten to answer.
REG_32BIT_ZERO_EX and REG_64BIT are always handled in exactly the same
way, and reg_val_propagate_range() never actually sets any register to
type REG_32BIT_ZERO_EX.
Remove the redundant & unused REG_32BIT_ZERO_EX.
Signed-off-by: Paul Burton
---
arch/mips/net/ebpf_jit.c | 17 +++--
чт, 14 февр. 2019 г. в 18:40, Sasha Levin :
>
> From: Pavel Shilovsky
>
> [ Upstream commit 0fd1d37b0501efc6e295f56ab55cdaff784aa50c ]
>
> If we don't receive a response we can't assume that the server
> granted one credit. Assume zero credits in such cases.
>
> Signed-off-by: Pavel Shilovsky
>
On Tue, Feb 12, 2019 at 3:50 PM Andy Shevchenko
wrote:
> On Tue, Feb 12, 2019 at 2:12 PM David Engraf wrote:
> > On 12.02.19 at 11:43, Andy Shevchenko wrote:
> > > On Mon, Feb 11, 2019 at 2:40 PM David Engraf
> > > wrote:
> > >> On 11.02.19 at 12:40, Andy Shevchenko wrote:
>
> > >> Ok got it.
* Faiz Abbas [190215 19:18]:
> From: Chunyan Zhang
>
> sdhci-omap can support both external dma controller via dmaengine
> framework as well as ADMA which standard SD host controller
> provides.
Care to describe here also how to configure things for ADMA and
instead of DMA? Just leave out dmas
On Sat, Feb 9, 2019 at 5:40 PM Pali Rohár wrote:
>
> On Tuesday 08 January 2019 17:32:55 Andy Shevchenko wrote:
> > On Fri, Dec 28, 2018 at 12:18 AM Pali Rohár wrote:
> > > On Monday 17 December 2018 10:50:04 Pali Rohár wrote:
> > > > On Wednesday 12 December 2018 14:57:36 Pali Rohár wrote:
> >
The addresses within a single page are always contiguous, so it's
not so necessary to always allocate one single page from CMA area.
Since the CMA area has a limited predefined size of space, it may
run out of space in heavy use cases, where there might be quite a
lot CMA pages being allocated for
* Faiz Abbas [190215 19:17]:
> The following add driver patches for porting TI's am335x and am437x
> devices to the sdhci-omap driver.
>
> This involves adding external DMA support to sdhci (first 3 patches from
> Chunyan) plus some miscellaneous patches to take care of deviations of
> the
On Fri, Feb 15, 2019 at 11:22 AM Andrew F. Davis wrote:
>
> On 2/15/19 1:01 PM, John Stultz wrote:
> > On Fri, Feb 15, 2019 at 2:51 AM Brian Starkey wrote:
> >> On Thu, Feb 14, 2019 at 09:38:29AM -0800, John Stultz wrote:
> >>> 2) For patches that cause ABI breaks, it might be good to make it
>
From: Alexander Duyck
Date: Fri, 15 Feb 2019 10:35:18 -0800
> I'll take care of it. I'm kind of annoyed that you resubmitted this to
> netdev before anyone had a chance to even provide review comments
> though.
He was only following instructions from Andrew Morton.
4.22 has never existed and this change was actually added to 4.21
hence fix the numbering.
Signed-off-by: Tomasz Duszynski
---
Documentation/ABI/testing/sysfs-bus-iio-sps30 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio-sps30
On Wed, Feb 13, 2019 at 5:56 AM Stuart Hayes wrote:
>
>
>
> On 2/11/2019 7:09 AM, Christoph Hellwig wrote:
> > We need to ensure rbu_data.lock is always held on return.
> >
Pushed to my review and testing queue, thanks!
> > Fixes: 289790a3ea94 ("platform/x86: dell_rbu: stop abusing the DMA
If query-ARS reports that ARS has stopped and requires continuation
attempt to retrieve short-ARS results before continuing the long
operation.
Reported-by: Krzysztof Rusocki
Signed-off-by: Dan Williams
---
drivers/acpi/nfit/core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Changes since v1: [1]
* Fix the root poll interval support to avoid a infinite loop condition
when the polling is faster than the ARS completion.
* Move the introduction of scrub_flags earlier in the series and
introduce ARS_POLL to fix the above issue.
[1]:
Gate ARS result consumption on whether the OS issued start-ARS since the
previous consumption. The BIOS may only clear its result buffers after a
successful start-ARS.
Reported-by: Krzysztof Rusocki
Reported-by: Vishal Verma
Signed-off-by: Dan Williams
---
drivers/acpi/nfit/core.c | 17
In preparation for introducing new flags to gate whether ARS results are
stale, or poll the completion state, convert the existing flags to an
unsigned long with enumerated values. This conversion allows the flags
to be atomically updated outside of ->init_mutex.
Signed-off-by: Dan Williams
---
The ARS implementation implements exponential back-off on the poll
interval to prevent high-frequency access to the DIMM / platform
interface. Depending on when the ARS completes the poll interval may
exceed the completion event by minutes. Allow root to reset the timeout
each time it probes the
The ars_start_flags property of 'struct acpi_nfit_desc' is no longer
used since ARS_REQ_SHORT and ARS_REQ_LONG were added.
Cc: Toshi Kani
Signed-off-by: Dan Williams
---
drivers/acpi/nfit/core.c | 10 +-
drivers/acpi/nfit/nfit.h |1 -
2 files changed, 5 insertions(+), 6
The no_init_ars option is meant to prevent long-ARS, but short-ARS
should be allowed to grab any immediate results.
Reported-by: Erwin Tsaur
Signed-off-by: Dan Williams
---
drivers/acpi/nfit/core.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git
On Fri, Feb 15, 2019 at 3:49 AM Brendan Higgins
wrote:
>
> On Thu, Feb 14, 2019 at 6:48 PM Frank Rowand wrote:
> >
> > On 2/14/19 5:26 PM, Brendan Higgins wrote:
> > > On Thu, Feb 14, 2019 at 4:10 PM Frank Rowand
> > > wrote:
> > >>
> > >> On 2/12/19 10:53 AM, Brendan Higgins wrote:
> > >>>
On Fri, 15 Feb 2019 at 20:43, Nick Desaulniers wrote:
>
> On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
> wrote:
> >
> > On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers
> > wrote:
> > >
> > > On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> > > wrote:
> > > > Provided that we stop sending
On Fri, Feb 15, 2019 at 11:28 AM Ard Biesheuvel
wrote:
>
> On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers
> wrote:
> >
> > On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> > wrote:
> > > Provided that we stop sending Clang enablement patches to -stable:
> >
> > What does that mean? We're
Before this change, recordmcount thought that there were zero sections
in an ELF that has more than 64K sections. It did nothing and exited
with exit status 0.
This change is needed so that CONFIG_DYNAMIC_FTRACE continues working
with special compilation flags that put each function in its own
On Fri, Feb 15, 2019 at 12:56 AM Jagan Teki wrote:
>
> Vertical video start delay is computed by excluding vertical porch
> value from total vertical timings, but the current driver excluding
> vertical porch along with vertical sync values from total vertical
> timings resulting wrong start
Hi,
Would you be interested in targeting Cybersecurity Users across the globe
for your Q1 marketing strategy?
Here is how we can help you:
Security users by vendor: Cisco, Juniper, Check Point, Aruba Networks,
Symantec and many others.
Security users by security solution: Email, SIEM,
Hello,
/proc/sys/kernel/sched_domain/ seems to be somewhat broken when kernel
is configured without CONFIG_CPUMASK_OFFSTACK and booting with
isolcpus= option.
Example with 8x CPU.
With CONFIG_CPUMASK_OFFSTACK=y and "isolcpus=2":
# uname -r
5.0.0-0.rc3.git0.1.fc30.x86_64
# ls
On Fri, 15 Feb 2019 at 20:25, Nick Desaulniers wrote:
>
> On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
> wrote:
> > Provided that we stop sending Clang enablement patches to -stable:
>
> What does that mean? We're trying to provide clang support back to
> 4.4 LTS branches. (so 4.4, 4.9,
On 2/13/19 2:33 PM, Stefan Wahren wrote:
>
>> Eric Anholt hat am 13. Februar 2019 um 19:28 geschrieben:
>>
>>
>> Stefan Wahren writes:
>>
>>> Hi Eric,
>>>
>>> Am 13.02.19 um 01:33 schrieb Eric Anholt:
The clock driver may probe after ours and so we need to pass the
-EPROBE_DEFER out.
On 2/15/2019 11:47 AM, Stephen Boyd wrote:
Quoting Jeffrey Hugo (2019-02-11 08:09:00)
On 1/28/2019 11:10 PM, Stephen Boyd wrote:
+static int clk_init_parent(struct clk_core *core)
+{
+ core->parent = __clk_init_parent(core, true);
+ if (IS_ERR(core->parent))
+ return
On Fri, Feb 15, 2019 at 11:20 AM Ard Biesheuvel
wrote:
> Provided that we stop sending Clang enablement patches to -stable:
What does that mean? We're trying to provide clang support back to
4.4 LTS branches. (so 4.4, 4.9, 4.14, 4.19).
--
Thanks,
~Nick Desaulniers
Hi Linus,
Please pull this small fix for a potential user-after-free on module
unload.
It has been sitting in -next for some days.
Cheers,
Miguel
The following changes since commit 8834f5600cf3c8db365e18a3d5cac2c2780c81e5:
Linux 5.0-rc5 (2019-02-03 13:48:04 -0800)
are available in the Git
On 2/15/19 1:01 PM, John Stultz wrote:
> On Fri, Feb 15, 2019 at 2:51 AM Brian Starkey wrote:
>>
>> Hi John,
>>
>> On Thu, Feb 14, 2019 at 09:38:29AM -0800, John Stultz wrote:
>>>
>> [snip]
>>
>>> Some thoughts, as this ABI break has the potential to be pretty painful.
>>>
>>> 1) Unfortunately,
On Fri, 15 Feb 2019 at 19:50, Will Deacon wrote:
>
> On Thu, Feb 14, 2019 at 06:39:59PM -0700, Nathan Chancellor wrote:
> > After commit cc9f8349cb33 ("arm64: crypto: add NEON accelerated XOR
> > implementation"), Clang builds for arm64 started failing with the
> > following error message.
> >
>
Hi!
I watched fosdem talk about
nbdkit... https://www.youtube.com/watch?v=9E5A608xJG0 . Nice. But word
of warning: I'm not sure using it read-write on localhost is safe.
In particular, user application could create a lot of dirty data
quickly. If there's not enough memory for nbdkit (or
On 09/02/2019 20:53, Andreas Kemnade wrote:
On Mon, 21 Jan 2019 11:58:03 -0800
Tony Lindgren wrote:
* Andreas Kemnade [190116 14:04]:
On the gta04 with a dm3730 omap_hdq does not work properly when the
device enters lower power states. Idling uart1 and 2 is enough
to show up that problem,
Add a Quirk to disable DTO during an erase command.
Signed-off-by: Faiz Abbas
---
drivers/mmc/host/sdhci-omap.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mmc/host/sdhci-omap.c b/drivers/mmc/host/sdhci-omap.c
index 8a05e94fe612..ae9701d198d5 100644
---
201 - 300 of 987 matches
Mail list logo
