The cacheinfo structures are alloced/freed by cpu online/offline
callbacks. Originally these were only used by sysfs to expose the
cache topology to user space. Without any in-kernel dependencies
CPUHP_AP_ONLINE_DYN was an appropriate choice.
resctrl has started using these structures to identify
On Mon, 24 Jun 2019, Catalin Marinas wrote:
> On Tue, Jun 11, 2019 at 03:56:27PM +0100, Sudeep Holla wrote:
> > The usage of emulated and _TIF_SYSCALL_EMU flags in syscall_trace_enter
> > is more complicated than required.
> >
> > Cc: Andy Lutomirski
> > Cc: Ingo Molnar
> > Cc: Borislav Petkov
On Sat, 2019-06-22 at 12:13 -0700, Paul E. McKenney wrote:
> On Fri, Jun 21, 2019 at 05:26:06PM -0700, Paul E. McKenney wrote:
> > On Thu, Jun 20, 2019 at 06:08:19PM -0500, Scott Wood wrote:
> > > On Thu, 2019-06-20 at 15:25 -0700, Paul E. McKenney wrote:
> > > > On Thu, Jun 20, 2019 at 04:59:30PM
This patch adds support for the i.MX6UL variant of the Variscite DART-6UL
SoM Carrier-Board
Signed-off-by: Oliver Graute
---
.../boot/dts/imx6ul-imx6ull-var-dart-common.dtsi | 458 +
1 file changed, 458 insertions(+)
create mode 100644 arch/arm/boot/dts/imx6ul-imx6ull-var-
This patch adds DeviceTree Source for the i.MX6 UltraLite DART NAND/WIFI
Signed-off-by: Oliver Graute
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx6ul-var-6ulcustomboard.dts | 203
2 files changed, 204 insertions(+)
create mode 10064
Need feedback to the following patches which adds support for a DART-6UL Board
Need feedback howto document propertys and compatible the right way
Product Page: https://www.variscite.com/product/evaluation-kits/dart-6ul-kits
Oliver Graute (2):
ARM: dts: imx6ul: Add Variscite DART-6UL SoM suppo
Hello, Patrick.
On Mon, Jun 24, 2019 at 06:34:05PM +0100, Patrick Bellasi wrote:
> > On Fri, Jun 21, 2019 at 09:42:14AM +0100, Patrick Bellasi wrote:
> > > Since it can be interesting for userspace, e.g. system management
> > > software, to know exactly what the currently propagated/enforced
> > >
From: Jordan Hand
For TPM2-based systems, retrieve the TCG log from the TPM2 ACPI table.
The TPM2 ACPI table is defined in section 7.3 of the TCG ACPI
Specification (see link).
The TPM2 table is used primarily by legacy BIOS in place of the TCPA table
when the system's TPM is version 2.0 to deno
- On Jun 24, 2019, at 11:52 AM, Joel Fernandes, Google
j...@joelfernandes.org wrote:
> On Mon, Jun 24, 2019 at 10:01:04AM -0400, Mathieu Desnoyers wrote:
>> - On Jun 24, 2019, at 5:18 AM, Peter Zijlstra pet...@infradead.org wrote:
>>
>> > While auditing all module notifiers I noticed a w
On Mon, Jun 24, 2019 at 04:32:53PM +0200, Andrey Konovalov wrote:
> This patch is a part of a series that extends kernel ABI to allow to pass
> tagged user pointers (with the top byte set to something else other than
> 0x00) as syscall arguments.
>
> userfaultfd code use provided user pointers for
Hey, Patrick.
On Mon, Jun 24, 2019 at 06:29:06PM +0100, Patrick Bellasi wrote:
> > I kinda wonder whether the term bandwidth is a bit confusing because
> > it's also used for cpu.max/min. Would just calling it frequency be
> > clearer?
>
> Maybe I should find a better way to express the concept
On Mon, Jun 24, 2019 at 05:55:32PM +0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.1.15 release.
> There are 121 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
Stephen,
can you replace Conny with
Janosch Frank
as contact fot kvms390-next?
Thanks
Christian
On 21.06.19 07:43, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the kvms390 tree got a conflict in:
>
> tools/testing/selftests/kvm/Makefile
>
> between commit:
>
> 61
On Tue, 2019-06-18 at 22:51 -0700, Dan Williams wrote:
> In preparation for sub-section hotplug, track whether a given section
> was created during early memory initialization, or later via memory
> hotplug. This distinction is needed to maintain the coarse
> expectation
> that pfn_valid() returns
Hi Tudor,
On Sat, 2019-06-22 at 10:18 +, tudor.amba...@microchip.com wrote:
> Hi, Eugeniy,
>
> On 06/07/2019 06:43 PM, Eugeniy Paltsev wrote:
> > External E-Mail
> >
> >
> > This commit adds support for the SST sst26wf016 and sst26wf032
> > flash memory IC.
>
> Please specify if you tested
On Tue, 2019-06-18 at 22:51 -0700, Dan Williams wrote:
> Prepare for hot{plug,remove} of sub-ranges of a section by tracking a
> sub-section active bitmask, each bit representing a PMD_SIZE span of
> the
> architecture's memory hotplug section size.
>
> The implications of a partially populated se
For testing coverage and improved defense in depth, enable KASLR by
default.
Acked-by: Ard Biesheuvel
Acked-by: Will Deacon
Reviewed-by: Kees Cook
Suggested-by: Arnd Bergmann
Suggested-by: Olof Johansson
Signed-off-by: Nick Desaulniers
---
Changes v1 -> v2:
* drop other hunks as per Olof and
On Sun, Jun 23, 2019 at 5:29 PM Shawn Guo wrote:
>
> On Mon, Jun 17, 2019 at 08:30:24AM -0700, Andrey Smirnov wrote:
> > Add support for ZII's i.MX7 based Remote Modem Unit 2 (RMU2) board.
> >
> > Signed-off-by: Andrey Smirnov
> > Cc: Shawn Guo
> > Cc: Rob Herring
> > Cc: Chris Healy
> > Cc: L
On Tue, 2019-06-18 at 22:52 -0700, Dan Williams wrote:
> Allow sub-section sized ranges to be added to the memmap.
> populate_section_memmap() takes an explict pfn range rather than
> assuming a full section, and those parameters are plumbed all the way
> through to vmmemap_populate(). There should
On Mon, Jun 24, 2019 at 05:56:18PM +0800, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.130 release.
> There are 51 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 kno
On Tue, 2019-06-18 at 22:52 -0700, Dan Williams wrote:
> Prepare the memory hot-{add,remove} paths for handling sub-section
> ranges by plumbing the starting page frame and number of pages being
> handled through arch_{add,remove}_memory() to
> sparse_{add,remove}_one_section().
>
> This is simply
Hi,
On Thu, Jun 20, 2019 at 7:41 PM Gwendal Grignou wrote:
>
> To allow cros_ec iio core library to be used with legacy device, add a
> vector to rotate sensor data if necessary: legacy devices are not
> reporting data in HTML5/Android sensor referential.
>
> On veyron minnie, check chrome detect
On Mon, Jun 24, 2019 at 09:46:17AM -0700, Andi Kleen wrote:
> > > The other hypervisors are relatively obscure, but eventually
> > > someone will hit problems.
> >
> > any idea if there's any other flag/way we could use to detect those?
>
> I'm not aware of a generic way to detect any hypervisor
Hi David,
On 6/24/2019 6:55 AM, David Laight wrote:
> From: Reinette Chatre
>> Sent: 19 June 2019 21:27
>>
>> While the DOC at the beginning of lib/bitmap.c explicitly states that
>> "The number of valid bits in a given bitmap does _not_ need to be an
>> exact multiple of BITS_PER_LONG.", some of
- On Jun 24, 2019, at 1:24 PM, Will Deacon will.dea...@arm.com wrote:
> On Mon, Jun 17, 2019 at 05:23:04PM +0200, Mathieu Desnoyers wrote:
>> This reverts commit 2b845d4b4acd9422bbb668989db8dc36dfc8f438.
>>
>> That commit introduces build issues for programs compiled in Thumb mode.
>> Rather
The ADF4372 is part of the same family with ADF4371, the main difference
is that it has only 3 channels instead of 4, as the frequency quadrupler
is missing. As a result, the ADF4372 allows frequencies from 62.5 MHz to
16 GHz to be generated.
Datasheet:
Link:
https://www.analog.com/media/en/techn
On 24.06.19 12:46, Bartosz Golaszewski wrote:
>> The patch seems pretty trivial and doesn't change any actual code, so
>> I don't see hard resons for rejecting it.
>>
>
> In its current form it makes the code even less readable. The #ifdef
> should actually be one line lower and touch the comment
On Sun, Jun 23, 2019 at 12:42:03PM -0400, Yangtao Li wrote:
> H3 has extra clock, so introduce something in ths_thermal_chip/ths_device
> and adds the process of the clock.
>
> This is pre-work for supprt it.
>
> Signed-off-by: Yangtao Li
> ---
> drivers/thermal/sun8i_thermal.c | 17 +
On Sun, Jun 23, 2019 at 5:59 PM Rong Chen wrote:
>
> On 6/22/19 6:27 AM, Stanislav Fomichev wrote:
> > On 06/21, Andrii Nakryiko wrote:
> >> )
> >>
> >> On Fri, Jun 21, 2019 at 9:11 AM Stanislav Fomichev
> >> wrote:
> >>> On 06/21, kernel test robot wrote:
> FYI, we noticed the following co
On 24/06/2019 18:24:31+0200, Andrew Lunn wrote:
> On Mon, Jun 24, 2019 at 05:23:45PM +0200, Allan W. Nielsen wrote:
> > Hi Andrew,
> >
> > The 06/24/2019 16:26, Andrew Lunn wrote:
> > > > > Yeah, there are 2 ethernet controller ports (managed by the enetc
> > > > > driver)
> > > > > connected in
Add support for ZII i.MX7 RMU2 board.
Signed-off-by: Andrey Smirnov
Reviewed-by: Fabio Estevam
Reviewed-by: Rob Herring
Cc: Shawn Guo
Cc: Chris Healy
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Bob Langer
Cc: Liang Pan
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kernel@vger.kernel.org
--
Add support for ZII's i.MX7 based Remote Modem Unit 2 (RMU2) board.
Signed-off-by: Andrey Smirnov
Reviewed-by: Fabio Estevam
Cc: Shawn Guo
Cc: Rob Herring
Cc: Chris Healy
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Bob Langer
Cc: Liang Pan
Cc: linux-arm-ker...@lists.infradead.org
Cc: linux-kern
On Fri, Jun 21, 2019 at 9:17 AM Dan Rue wrote:
>
> On Thu, Jun 20, 2019 at 10:17:04PM -0700, Andrii Nakryiko wrote:
> > On Thu, Jun 20, 2019 at 1:08 AM Naresh Kamboju
> > wrote:
> > >
> > > selftests: bpf test_libbpf.sh failed running Linux -next kernel
> > > 20190618 and 20190619.
> > >
> > > He
Currently hmat.c lives under an "hmat" directory which does not enhance
the description of the file. The initial motivation for giving hmat.c
its own directory was to delineate it as mm functionality in contrast to
ACPI device driver functionality.
As ACPI continues to play an increasing role in c
UEFI 2.8 defines an EFI_MEMORY_SP attribute bit to augment the
interpretation of the EFI Memory Types as "reserved for a specific
purpose".
The proposed Linux behavior for specific purpose memory is that it is
reserved for direct-access (device-dax) by default and not available for
any kernel usag
UEFI 2.8 defines an EFI_MEMORY_SP attribute bit to augment the
interpretation of the EFI Memory Types as "reserved for a specific
purpose". The intent of this bit is to allow the OS to identify precious
or scarce memory resources and optionally manage it separately from
EfiConventionalMemory. As de
Changes since v3 [1]:
- Clarify in the changelog that the policy decision of how to treat
specific-purpose memory is x86 only until other archs grow a
translation to IORES_DESC_APPLICATION_RESERVED. The EFI spec does not
mandate a behavior for the EFI_MEMORY_SP attribute so the decision is
There are multiple scenarios where the HMAT may contain information
about proximity domains that are not currently online. Rather than fail
to report any HMAT data just elide those offline domains.
If and when those domains are later onlined they can be added to the
HMEM reporting at that point.
In preparation for adding another EFI_MEMMAP dependent call that needs
to occur before e820__memblock_setup() fixup the existing efi calls to
check for EFI_MEMMAP internally. This is cleaner than checking
EFI_MEMMAP multiple times in setup_arch().
Cc:
Cc: Ingo Molnar
Cc: "H. Peter Anvin"
Cc: An
Given that EFI_MEMORY_SP is platform BIOS policy descision for marking
memory ranges as "reserved for a specific purpose" there will inevitably
be scenarios where the BIOS omits the attribute in situations where it
is desired. Unlike other attributes if the OS wants to reserve this
memory from the
In preparation for registering device-dax instances for accessing EFI
specific-purpose memory, arrange for the HMAT registration to occur
later in the init process. Critically HMAT initialization needs to occur
after e820__reserve_resources_late() which is the point at which the
iomem resource tree
Memory that has been tagged EFI_MEMORY_SP, and has performance
properties described by the ACPI HMAT is expected to have an application
specific consumer.
Those consumers may want 100% of the memory capacity to be reserved from
any usage by the kernel. By default, with this enabling, a platform
de
In preparation for handling platform differentiated memory types beyond
persistent memory, uplevel the "region" identifier to a global number
space. This enables a device-dax instance to be registered to any memory
type with guaranteed unique names.
Given this is a general identifier for persisten
Platform firmware like EFI/ACPI may publish "hmem" platform devices.
Such a device is a performance differentiated memory range likely
reserved for an application specific use case. The driver gives access
to 100% of the capacity via a device-dax mmap instance by default.
However, if over-subscrip
> Tom, plz correctme if I'm wrongm but AFAIK because the LBR tracing is
> enabled during the boot the lbr_from/lbr_to registers will fail the
> check_msr 'val_new != val_tmp' check
Ok this should be handleable. It should be enough to check
the ctrl register, if that working likely we don't need
to
Em Wed, Jun 19, 2019 at 09:44:28AM +0300, Adrian Hunter escreveu:
> Commit f08046cb3082 ("perf thread-stack: Represent jmps to the start of a
> different symbol") had the side-effect of introducing more stack entries
> before return from kernel space. When user space is also traced, those
> entries
Hello,
On Mon, Jun 24, 2019 at 02:34:24AM +0200, Thomas Gleixner wrote:
> I did not merge the ARM and MIPS parts as they lack any form of
> acknowlegment from their maintainers. Please talk to those folks. If they
> ack/review the changes then I can pick them up and they go into 5.3 or they
> have
On 07.06.19 17:59, Mark Brown wrote:
> On Fri, Jun 07, 2019 at 05:56:31PM +0200, Paul Cercueil wrote:
>> This allows the probe function to be dropped after the kernel finished
>> its initialization, in the case where the driver was not compiled as a
>> module.
>
> Hopefully not since we might prob
Chnages since v5:
Use shifts/masks for SMC response fields.
Add limit check for dimm_per_mc read from firmware.
Make use of offset_in_page() call.
Shravan Kumar Ramani (1):
EDAC, mellanox: Add ECC support for BlueField DDR4
MAINTAINERS | 5 +
drivers/edac/Kconfig |
Add ECC support for Mellanox BlueField SoC DDR controller.
This requires SMC to the running Arm Trusted Firmware to report
what is the current memory configuration.
Reviewed-by: James Morse
Signed-off-by: Shravan Kumar Ramani
---
MAINTAINERS | 5 +
drivers/edac/Kconfig
On 24/06/19 17:12, David Laight wrote:
> From: Fenghua Yu
>> Sent: 18 June 2019 23:41
>> From: Peter Zijlstra
>>
>> A bit in pwol_mask is set in b44_magic_pattern() by atomic set_bit().
>> But since pwol_mask is local and never exposed to concurrency, there is
>> no need to set bit in pwol_mask at
Em Wed, Jun 19, 2019 at 09:44:27AM +0300, Adrian Hunter escreveu:
> Hi
>
> Here is one non-urgent fix and a subsequent tidy-up.
Thanks, both applied.
- Arnaldo
>
> Adrian Hunter (2):
> perf thread-stack: Fix thread stack return from kernel for kernel-only
> case
> perf thread-sta
struct pid's count is an atomic_t field used as a refcount. Use
refcount_t for it which is basically atomic_t but does additional
checking to prevent use-after-free bugs.
For memory ordering, the only change is with the following:
- if ((atomic_read(&pid->count) == 1) ||
- atomic_
On Mon, Jun 24, 2019 at 11:38:06AM -0700, Andi Kleen wrote:
> > Tom, plz correctme if I'm wrongm but AFAIK because the LBR tracing is
> > enabled during the boot the lbr_from/lbr_to registers will fail the
> > check_msr 'val_new != val_tmp' check
>
> Ok this should be handleable. It should be enou
Em Thu, Jun 20, 2019 at 02:36:30PM -0500, Kyle Meyer escreveu:
> From: Kyle Meyer
>
> Attempting to profile 1024 or more CPUs with perf causes two errors:
>
> perf record -a
> [ perf record: Woken up X times to write data ]
> way too many cpu caches..
> [ perf record: Captured and wrote X MB per
On Mon, Jun 24, 2019 at 02:45:34PM -0400, Joel Fernandes (Google) wrote:
> struct pid's count is an atomic_t field used as a refcount. Use
> refcount_t for it which is basically atomic_t but does additional
> checking to prevent use-after-free bugs.
>
> For memory ordering, the only change is with
Em Sat, Jun 22, 2019 at 12:32:41PM +0300, Adrian Hunter escreveu:
> Hi
>
> Here are some improvements for the handling of core-to-bus ratio (CBR),
> including exporting it.
Thanks, applied.
>
> Adrian Hunter (7):
> perf intel-pt: Decoder to output CBR changes immediately
> perf int
Em Thu, Jun 20, 2019 at 08:58:29AM +0800, Leo Yan escreveu:
> Hi Mathieu,
>
> On Wed, Jun 19, 2019 at 11:49:44AM -0600, Mathieu Poirier wrote:
>
> [...]
>
> > > diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config
> > > index 51dd00f65709..4776c2c1fb6d 100644
> > > --- a/tools/pe
Dt-schema can be used for clock-names property.
Signed-off-by: Stefan Popa
---
Documentation/devicetree/bindings/iio/frequency/adf4371.yaml | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/iio/frequency/adf4371.yaml
b/Documentation/devic
When copying an event to userspace failed, the event queue
lock was never released. This fixes that.
Reported-by: Dan Carpenter
Signed-off-by: Nick Crews
---
drivers/platform/chrome/wilco_ec/event.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/chrome/wilc
The current implementation of the event queue both
wastes space using a doubly linked list and isn't super
obvious in how it behaves. This converts the queue to an
actual circular buffer. The size of the queue is a
tunable module parameter. This also fixes a few other things:
- A memory leak that
Em Mon, Jun 17, 2019 at 10:58:08AM +0800, Haiyan Song escreveu:
> Add a Intel event file for perf.
Applying: perf vendor events: Add Icelake V1.00 event file
error: corrupt patch at line 2558
Patch failed at 0001 perf vendor events: Add Icelake V1.00 event file
Can you check?
- Arnaldo
> Signe
On Mon, Jun 24, 2019 at 03:50:58PM -0300, Arnaldo Carvalho de Melo wrote:
SNIP
> > diff --git a/samples/bpf/map_perf_test_user.c
> > b/samples/bpf/map_perf_test_user.c
> > index fe5564bff39b..da3c101ca776 100644
> > --- a/samples/bpf/map_perf_test_user.c
> > +++ b/samples/bpf/map_perf_test_user.
On Mon, 24 Jun 2019 03:50:12 +, Xue Chaojing wrote:
> diff --git a/drivers/net/ethernet/huawei/hinic/hinic_ethtool.c
> b/drivers/net/ethernet/huawei/hinic/hinic_ethtool.c
> index be28a9a7f033..8d98f37c88a8 100644
> --- a/drivers/net/ethernet/huawei/hinic/hinic_ethtool.c
> +++ b/drivers/net/eth
On Mon, Jun 24, 2019 at 8:52 PM Joel Fernandes wrote:
> On Mon, Jun 24, 2019 at 02:45:34PM -0400, Joel Fernandes (Google) wrote:
> > struct pid's count is an atomic_t field used as a refcount. Use
> > refcount_t for it which is basically atomic_t but does additional
> > checking to prevent use-aft
Arnd,
We're getting into MMIO and barriers again, sigh. Cc-ing people recently
involved then.
On Fri, 21 Jun 2019, Arnd Bergmann wrote:
> > > > > The other property of packet memory and similar things is that you
> > > > > basically want memcpy()-behavior with no byteswaps. This is one
> > >
Hi Christoph,
Yep I've reviewed and tested it for both cases:
- coherent/noncoherent dma
- allocation from atomic_pool/regular allocation
everything works fine for ARC.
So,
Reviewed-by: Evgeniy Paltsev
Tested-by: Evgeniy Paltsev
for both
[PATCH 2/7] arc: remove the partial DMA_ATTR_NON_CONSI
On Mon, Jun 24, 2019 at 11:19:13AM -0500, Gustavo A. R. Silva wrote:
> In preparation to enabling -Wimplicit-fallthrough, mark switch
> cases where we are expecting to fall through.
>
> This patch fixes the following warnings:
>
> arch/x86/events/intel/core.c: In function ‘intel_pmu_init’:
> arch
From: Andi Kleen
After setting up metric groups through the event parser,
the metricgroup code looks them up again in the event list.
Make sure we only look up events that haven't been used
by some other metric. The data structures currently cannot
handle more than one metric per event. This avo
Fix some bugs and regressions in perf stat --metrics support.
Also available in
git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc perf/metric-fixes-1
From: Andi Kleen
Event merging is mainly to collapse similar events in lots of
different duplicated PMUs.
It can break metric displaying. It's possible for two metrics
to have the same event, and when the two events happen in a row
the second wouldn't be displayed. This would also not
show the
On 2019-06-24 12:54 p.m., Jason Gunthorpe wrote:
> On Mon, Jun 24, 2019 at 12:28:33PM -0600, Logan Gunthorpe wrote:
>
>>> Sounded like this series does generate the dma_addr for the correct
>>> device..
>>
>> This series doesn't generate any DMA addresses with dma_map(). The
>> current p2pdma c
From: Andi Kleen
Since 8c5421c016a4 ("perf pmu: Display pmu name when printing ...")
using --no-merge adds the PMU name to the evsel name. This breaks
the metric value lookup because the parser doesn't know about this.
Remove the extra postfixes for the metric evaluation.
Fixes: 8c5421c016a4 ("
From: Andi Kleen
The metric group code tries to find a group it added earlier
in the evlist. Fix the lookup to handle groups with partially
overlaps correctly. When a sub string match fails and we reset
the match, we have to compare the first element again.
I also renamed the find_evsel function
On Mon, Jun 24, 2019 at 10:34 PM Lee Jones wrote:
>
> Hopefully this is more to your liking.
I would actually have preferred you to throw the old buggy "fix" away,
and just do the final state.
But the end result looks sane, so I pulled it.
Linus
On 6/24/19 1:45 AM, kernel test robot wrote:
> Greeting,
>
> FYI, we noticed a -37.0% regression of reaim.jobs_per_min due to commit:
>
>
> commit: 4f23dbc1e657951e5d94c60369bc1db065961fb3 ("locking/rwsem: Implement
> lock handoff to prevent lock starvation")
> https://git.kernel.org/cgit/linux/ke
On Mon, 2019-06-24 at 21:31 +0200, Peter Zijlstra wrote:
> On Mon, Jun 24, 2019 at 11:19:13AM -0500, Gustavo A. R. Silva wrote:
> > In preparation to enabling -Wimplicit-fallthrough, mark switch
> > cases where we are expecting to fall through.
> >
> > This patch fixes the following warnings:
> >
On 6/24/19 7:29 AM, Christian Brauner wrote:
> Tools such as vpnc try to flush routes when run inside network
> namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This
> currently does not work because flush is not enabled in non-initial
> network namespaces.
> Since routes are per networ
From: "Andrew F. Davis"
This framework allows a unified userspace interface for dma-buf
exporters, allowing userland to allocate specific types of memory
for use in dma-buf sharing.
Each heap is given its own device node, which a user can allocate
a dma-buf fd from using the DMA_HEAP_IOC_ALLOC.
On Tue, Jun 25, 2019 at 1:08 AM Octavio Alvarez wrote:
>
> If I boot regularly (disable_msi not set) and then do modprobe -r sky2;
> modprobe sky2 disable_msi=1, the problem stays (when back from
> hibernation, the NIC does not work).
Side note: some distros end up unloading and reloading modules
Add very trivial allocation and import test for dma-heaps,
utilizing the vgem driver as a test importer.
A good chunk of this code taken from:
tools/testing/selftests/android/ion/ionmap_test.c
Originally by Laura Abbott
Cc: Benjamin Gaignard
Cc: Sumit Semwal
Cc: Liam Mark
Cc: Pratik Patel
On Mon, Jun 24, 2019 at 11:32:25AM -0700, Andrii Nakryiko wrote:
> On Fri, Jun 21, 2019 at 9:17 AM Dan Rue wrote:
> >
> > On Thu, Jun 20, 2019 at 10:17:04PM -0700, Andrii Nakryiko wrote:
> > > On Thu, Jun 20, 2019 at 1:08 AM Naresh Kamboju
> > > wrote:
> > > >
> > > > selftests: bpf test_libbpf.s
On Mon, Jun 24, 2019 at 8:37 AM Daniel Borkmann wrote:
>
> On 06/22/2019 02:03 AM, Matthew Garrett wrote:
> > From: David Howells
> >
> > There are some bpf functions can be used to read kernel memory:
>
> Nit: that
Fixed.
> > bpf_probe_read, bpf_probe_write_user and bpf_trace_printk. These al
On Mon, 2019-06-24 at 11:30 -0500, Alex Elder wrote:
> OK I want to try to organize a little more concisely some of the
> discussion on this, because there is a very large amount of volume
> to date and I think we need to try to narrow the focus back down
> again.
>
> I'm going to use a few terms
On Mon, 2019-06-24 at 14:42 -0400, Shravan Kumar Ramani wrote:
> Add ECC support for Mellanox BlueField SoC DDR controller.
> This requires SMC to the running Arm Trusted Firmware to report
> what is the current memory configuration.
[]
> diff --git a/drivers/edac/bluefield_edac.c b/drivers/edac/bl
On 21/06/2019 11:51:26+1000, Finn Thain wrote:
> Some machines store local time in the Real Time Clock. The hard-coded
> "UTC" string is wrong on those machines so just omit that string.
> Update the log parser so it doesn't require the string "UTC".
>
I don't agree, hctossys will always think th
On Mon, Jun 24, 2019 at 12:53 PM Dan Rue wrote:
>
> I would say if it's not possible to check at runtime, and it requires
> clang 9.0, that this test should not be enabled by default.
The latest clang is the requirement.
If environment has old clang or no clang at all these tests will be failing.
On June 24, 2019 9:49:33 PM GMT+02:00, David Ahern wrote:
>On 6/24/19 7:29 AM, Christian Brauner wrote:
>> Tools such as vpnc try to flush routes when run inside network
>> namespaces by writing 1 into /proc/sys/net/ipv4/route/flush. This
>> currently does not work because flush is not enabled in
Sakari Ailus writes:
> On Thu, Jun 20, 2019 at 01:17:17PM +0300, Sakari Ailus wrote:
>> diff --git a/drivers/media/i2c/mt9m111.c b/drivers/media/i2c/mt9m111.c
>> index bd3a51c3b081..9761a6105407 100644
>> --- a/drivers/media/i2c/mt9m111.c
>> +++ b/drivers/media/i2c/mt9m111.c
>> @@ -1263,9 +1263,1
The pull request you sent on Mon, 17 Jun 2019 11:00:54 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git tags/mfd-fixes-5.2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/63b2de12b7eeacfb2edbe005f5c3cff17a2a02e2
Thank you!
--
Deet-doot-dot, I am a b
The pull request you sent on Mon, 24 Jun 2019 15:34:11 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git mfd-fixes-5.2-1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c88e40e07cd967dcdf37321a63ab6e8b0d881100
Thank you!
--
Deet-doot-dot, I am a bot.
On Sun, Jun 23, 2019 at 10:45 PM Björn Töpel wrote:
>
> From: Björn Töpel
>
> Jonathan Lemon has volunteered as an official AF_XDP reviewer. Thank
> you, Jonathan!
Thanks Jonathan! Please reply with your Acked-by.
Thanks,
Song
>
> Signed-off-by: Björn Töpel
> ---
> MAINTAINERS | 1 +
> 1 fil
On Mon, Jun 24, 2019 at 12:54 PM Matthew Garrett wrote:
>
> On Mon, Jun 24, 2019 at 8:37 AM Daniel Borkmann wrote:
> >
> > On 06/22/2019 02:03 AM, Matthew Garrett wrote:
> > > From: David Howells
> > >
> > > There are some bpf functions can be used to read kernel memory:
> >
> > Nit: that
>
> Fi
On Mon, Jun 17, 2019 at 7:03 PM Nathan Chancellor
wrote:
>
> clang warns:
>
> arch/arm/mach-iop13xx/pci.c:292:7: warning: logical not is only applied
> to the left hand side of this comparison [-Wlogical-not-parentheses]
> if (!iop13xx_atux_pci_status(1) == 0)
>
On Mon, Jun 24, 2019 at 1:09 PM Andy Lutomirski wrote:
> I'm confused. I understand why we're restricting bpf_probe_read().
> Why are we restricting bpf_probe_write_user() and bpf_trace_printk(),
> though?
Hmm. I think the thinking here was around exfiltration mechanisms, but
if the read is blo
On 6/24/19 12:40 PM, Paolo Valente wrote:
> Hi Jens,
> this series, based against for-5.3/block, contains:
> 1) The improvements to recover the throughput loss reported by
>Srivatsa [1] (first five patches)
> 2) A preemption improvement to reduce I/O latency
> 3) A fix of a subtle bug causing l
On Tue, Jun 25, 2019 at 02:33:06AM +0530, Ajay Kaher wrote:
coredump: fix race condition between mmget_not_zero()/get_task_mm()
and core dumping
[PATCH v4 1/3]:
Backporting of commit 04f5866e41fb70690e28397487d8bd8eea7d712a upstream.
[PATCH v4 2/3]:
Extension of commit 04f5866e41fb to fix the r
On Mon, Jun 24, 2019 at 07:27:47AM -0700, Joe Perches wrote:
> On Mon, 2019-06-24 at 15:33 +0200, Peter Zijlstra wrote:
> > On Mon, Jun 24, 2019 at 03:03:23PM +0200, Sebastian Andrzej Siewior wrote:
> > > The --cc adds a Cc: prefix infront of the email address so it can be
> > > used by other Scrip
On Mon, Jun 24, 2019 at 07:47:28AM +0200, Christoph Hellwig wrote:
> No one is using this header anymore.
>
> Signed-off-by: Christoph Hellwig
> Acked-by: Arnd Bergmann
> Acked-by: Oleg Nesterov
> ---
> MAINTAINERS| 1 -
> arch/mips/include/asm/ptrace.h | 5 ---
> include
A recent fix to the cbm_ensure_valid() function left
some coding style issues that are now addressed:
- Follow reverse fir tree ordering of variable declarations
- Use if (!val) instead of if (val == 0)
- Return a value instead of using a function parameter as input and
output
Suggested-by: Borisl
901 - 1000 of 1256 matches
Mail list logo
