guest_enter() doesn't call context_tracking_enabled() before calling
context_tracking_enabled_this_cpu(). Therefore the guest code doesn't
benefit from the static key on the fast path.
Just make sure that context_tracking_enabled_*cpu() functions check
the static key by themselves to propagate
In order to compute the kcpustat delta on a nohz CPU, we'll need to
fetch the task running on that target. Checking that its vtime
state snapshot actually refers to the relevant target involves recording
that CPU under the seqcount locked on task switch.
This is a step toward making kcpustat
Record guest as a VTIME state instead of guessing it from VTIME_SYS and
PF_VCPU. This is going to simplify the cputime read side especially as
its state machine is going to further expand in order to fully support
kcpustat on nohz_full.
Signed-off-by: Frederic Weisbecker
Cc: Yauheni Kaliuta
Cc:
Remove the superfluous "is" in the middle of the name. We want to
standardize the naming so that it can be expanded through suffixes:
context_tracking_enabled()
context_tracking_enabled_cpu()
context_tracking_enabled_this_cpu()
Signed-off-by: Frederic Weisbecker
Cc:
Record idle as a VTIME state instead of guessing it from VTIME_SYS and
is_idle_task(). This is going to simplify the cputime read side
especially as its state machine is going to further expand in order to
fully support kcpustat on nohz_full.
Signed-off-by: Frederic Weisbecker
Cc: Yauheni
Thanks to the recent patches that have brought a sensible rq->curr RCU
lifecycle, here comes a simplified rework of
"[PATCH 00/25] sched/nohz: Make kcpustat vtime aware"
See for the record and a summary:
https://lore.kernel.org/lkml/1542163569-20047-1-git-send-email-frede...@kernel.org/
Add a device tree binding doc for AD7292 monitor and control system.
Signed-off-by: Marcelo Schmitt
---
.../bindings/iio/adc/adi,ad7292.yaml | 107 ++
MAINTAINERS | 1 +
2 files changed, 108 insertions(+)
create mode 100644
The AD7292 is a 10-bit monitor and control system with ADC, DACs,
temperature sensor, and GPIOs.
Configure AD7292 devices in direct access mode, enabling single-ended
ADC readings.
Datasheet:
Link:
https://www.analog.com/media/en/technical-documentation/data-sheets/ad7292.pdf
Signed-off-by:
This patchset adds a basic driver for the AD7292 ADC/DAC system along
with device tree binding documentation.
Changelog V2:
- made SPI rx/tx buffers separated fields in the state struct
- adjusted spi_transfer tx_buf pointer
- at probe, stored vref supply for later reference
- removed
Hi Ben,
> From: Ben Dooks (Codethink), Sent: Wednesday, October 16, 2019 12:51 AM
>
> Fix the warnings generated by casting to/from __le16 without
> using the correct functions.
>
> Fixes the following sparse warnings:
>
> drivers/usb/renesas_usbhs/common.c:165:25: warning: incorrect type in
Some drivers just call phy_ethtool_ksettings_set() to set the
links, for those phy drivers that use genphy_read_status(), if
autoneg is on, and the link is up, than execute "ethtool -s
ethx autoneg on" will cause "link partner" information disappear.
The call trace is
Hi Ben,
> From: Ben Dooks (Codethink), Sent: Wednesday, October 16, 2019 12:30 AM
>
> Fix the type of buf in __usbhsg_recip_send_status to
> be __le16 to avoid the following sparse warning:
>
> drivers/usb/renesas_usbhs/mod_gadget.c:335:14: warning: incorrect type in
> assignment (different
On 2019/10/16 4:02, Heiner Kallweit wrote:
> On 14.10.2019 14:56, Yonglong Liu wrote:
>> Some drivers just call phy_ethtool_ksettings_set() to set the
>> links, for those phy drivers that use genphy_read_status(), if
>> autoneg is on, and the link is up, than execute "ethtool -s
>> ethx autoneg
On 10/16/2019 02:53 AM, Paul Burton wrote:
Hi Tiezhu & Huacai,
On Tue, Oct 15, 2019 at 12:00:25PM +0800, Tiezhu Yang wrote:
On 10/15/2019 11:36 AM, Huacai Chen wrote:
On Tue, Oct 15, 2019 at 10:12 AM Tiezhu Yang wrote:
When I update kernel with loongson3_defconfig based on the Loongson
On 10/15/19 6:36 PM, Bhaskar Chowdhury wrote:
> On 16:03 Tue 15 Oct 2019, Randy Dunlap wrote:
>> Subject: s/prunning/pruning/
>> Subject: s/:scripts:/scripts:/
>>
>> On 10/15/19 7:55 AM, Bhaskar Chowdhury wrote:
>>> This patch will remove old kernels from system selective way.
>>
>>
usdhc's clock rate is different according to different devices
connected, so clock rate assignment should be placed in board
DT according to different devices connected on each usdhc port.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mn-ddr4-evk.dts | 4
usdhc's clock rate is different according to different devices
connected, so clock rate assignment should be placed in board
DT according to different devices connected on each usdhc port.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mm-evk.dts | 4
usdhc's clock rate is different according to different devices
connected, so clock rate assignment should be placed in board
DT according to different devices connected on each usdhc port.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7ulp-evk.dts | 2 ++
arch/arm/boot/dts/imx7ulp.dtsi
usdhc's clock rate is different according to different devices
connected, so clock rate assignment should be placed in board
DT according to different devices connected on each usdhc port.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8qxp-ai_ml.dts | 4
usdhc's clock rate is different according to different devices
connected, so clock rate assignment should be placed in board
DT according to different devices connected on each usdhc port.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8mq-evk.dts| 4
On Tue, Oct 15, 2019 at 5:41 PM Christian Brauner
wrote:
>
> Hey everyone,
>
> In v5.4-rc2 we added two new helpers check_zeroed_user() and
> copy_struct_from_user() including selftests (cf. [1]). It is a generic
> interface designed to copy a struct from userspace. The helpers will be
>
Because period and duty cycle are defined as ints with units of
nanoseconds, the maximum time duration that can be set is limited to
~2.147 seconds. Change their definitions to u64 so that higher durations
may be set.
Signed-off-by: Guru Das Srinagesh
---
drivers/pwm/core.c | 4 ++--
Reworked the change pushed upstream earlier [1] so as to not add an extension
to an obsolete API. With this change, pwm_ops->apply() can be used to set
pwm_state parameters as usual.
[1] https://lore.kernel.org/lkml/20190916140048.GB7488@ulmo/
Guru Das Srinagesh (1):
pwm: Convert period and
On Tue, 3 Sep 2019, Christoph Hellwig wrote:
> Many of the privileged CSRs exist in a supervisor and machine version
> that are used very similarly. Provide a new X-naming layer so that
> we don't have to ifdef everywhere for M-mode Linux support.
>
> Contains contributions from Damien Le Moal
On Wed, 16 Oct 2019 09:03:17 +0800
Zhu Lingshan wrote:
> + IFC_INFO(>dev, "PCI capability mapping:\n"
> + "common cfg: %p\n"
> + "notify base: %p\n"
> + "isr cfg: %p\n"
> + "device
On Wed, 16 Oct 2019 09:03:17 +0800
Zhu Lingshan wrote:
> +int ifcvf_init_hw(struct ifcvf_hw *hw, struct pci_dev *dev)
> +{
> + int ret;
> + u8 pos;
> + struct virtio_pci_cap cap;
> + u32 i;
> + u16 notify_off;
For network code, the preferred declaration style is
reverse
Hi Shuah,
I know this has been merged already, so this is just FYI and in case it
helps anyone else who's tracking down build failures.
Sorry I didn't reply before you merged it, I was on leave.
Shuah Khan writes:
> Add kselftest-all target to build tests from the top level
> Makefile. This is
The RTL8723BU has problems connecting to AP after each warm reboot.
Sometimes it returns no scan result, and in most cases, it fails
the authentication for unknown reason. However, it works totally
fine after cold reboot.
Compare the value of register SYS_CR and SYS_CLK_MAC_CLK_ENABLE
for cold
On 10/15/2019 5:28 PM, Paolo Bonzini wrote:
On 14/10/19 18:58, Vitaly Kuznetsov wrote:
Xiaoyao Li writes:
They are duplicated codes to create vcpu.arch.{user,guest}_fpu in VMX
and SVM. Make them common functions.
No functional change intended.
Would it rather make sense to move this code
On Tue, Oct 15, 2019 at 3:06 AM Kirill A. Shutemov wrote:
>
> On Tue, Oct 08, 2019 at 11:37:11AM +0200, Thomas Hellström (VMware) wrote:
> > From: Thomas Hellstrom
> >
> > A huge pud page can theoretically be faulted in racing with pmd_alloc()
> > in __handle_mm_fault(). That will lead to
GD5FxGQ4xA didn't follow the SPI spec to keep MISO low while slave is
reading, and instead MISO is kept high. As a result, the first byte
of id becomes 0xFF.
Since the first byte isn't supposed to be checked at all, this patch
just removed that check.
While at it, redo the comment above to better
On 16:03 Tue 15 Oct 2019, Randy Dunlap wrote:
Subject: s/prunning/pruning/
Subject: s/:scripts:/scripts:/
On 10/15/19 7:55 AM, Bhaskar Chowdhury wrote:
This patch will remove old kernels from system selective way.
in a selective way.
failed to send to kvm list, resend, sorry for the inconvenience.
THanks,
BR
Zhu Lingshan
On 10/16/2019 9:30 AM, Zhu Lingshan wrote:
Hi all:
This series intends to introduce Intel IFC VF NIC driver for Vhost
Data Plane Acceleration.
Here comes two main parts, one is ifcvf_base layer,
Hi,
On Tue, 15 Oct 2019 at 22:22, YueHaibing wrote:
>
> Use devm_platform_ioremap_resource() to simplify the code a bit.
> This is detected by coccinelle.
>
> Signed-off-by: YueHaibing
We already posted a patch to do this, thanks anyway.
https://lore.kernel.org/patchwork/patch/1136894/
> ---
This commit introduced IFC VF operations for vdpa, which complys to
vhost_mdev interfaces, handles IFC VF initialization,
configuration and removal.
Signed-off-by: Zhu Lingshan
---
drivers/vhost/ifcvf/ifcvf_main.c | 541 +++
1 file changed, 541 insertions(+)
This commit introduced ifcvf_base layer, which handles IFC VF NIC
hardware operations and configurations.
Signed-off-by: Zhu Lingshan
---
drivers/vhost/ifcvf/ifcvf_base.c | 390 +++
drivers/vhost/ifcvf/ifcvf_base.h | 137 ++
2 files changed, 527
Hi all:
This series intends to introduce Intel IFC VF NIC driver for Vhost
Data Plane Acceleration.
Here comes two main parts, one is ifcvf_base layer, which handles
hardware operations. The other is ifcvf_main layer handles VF
initialization, configuration and removal, which depends on
and
On 10/16/2019 8:40 AM, Krish Sadhukhan wrote:
On 10/15/2019 09:40 AM, Xiaoyao Li wrote:
Move the MSR bitmap setup codes to vmx_vmcs_setup() and only setup them
when hardware has msr_bitmap capability.
Signed-off-by: Xiaoyao Li
---
arch/x86/kvm/vmx/vmx.c | 39
On 10/16/2019 6:05 AM, Krish Sadhukhan wrote:
On 10/15/2019 09:40 AM, Xiaoyao Li wrote:
Rename {vmx,nested_vmx}_vcpu_setup to {vmx,nested_vmx}_vmcs_setup,
to match what they really do.
No functional change.
Signed-off-by: Xiaoyao Li
---
arch/x86/kvm/vmx/nested.c | 2 +-
Hi all,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/usb/generic-ehci.yaml
between commit:
3aa3c66aedef ("dt-bindings: usb: Bring back phy-names")
from Linus' tree and commit:
02ceb12c20f5 ("dt-bindings: usb: generic-ehci: Add
From: Juergen Gross
Date: Mon, 14 Oct 2019 11:09:08 +0200
> One bugfix (patch 1) I stumbled over while doing a cleanup (patch 2)
> of the xen-netback init/deinit code.
Please do not mix cleanups and genuine bug fixes.
Submit the bug fix targetting the 'net' GIT tree, and once that eventually
From: Alexander Lobakin
Date: Mon, 14 Oct 2019 11:00:33 +0300
> Commit 323ebb61e32b4 ("net: use listified RX for handling GRO_NORMAL
> skbs") made use of listified skb processing for the users of
> napi_gro_frags().
> The same technique can be used in a way more common napi_gro_receive()
> to
On Tue, 15 Oct 2019 20:41:20 -0400
Joel Fernandes wrote:
> > +static const struct file_operations tracing_max_lat_fops;
> > +
> > +#if (defined(CONFIG_TRACER_MAX_TRACE) || defined(CONFIG_HWLAT_TRACER)) && \
> > + defined(CONFIG_FSNOTIFY)
>
> Something bothers me. If you dropped support for
This commit introduced ifcvf_base layer, which handles IFC VF NIC
hardware operations and configurations.
Signed-off-by: Zhu Lingshan
---
drivers/vhost/ifcvf/ifcvf_base.c | 390 +++
drivers/vhost/ifcvf/ifcvf_base.h | 137 ++
2 files changed, 527
Hi all:
This series intends to introduce Intel IFC VF NIC driver for Vhost
Data Plane Acceleration.
Here comes two main parts, one is ifcvf_base layer, which handles
hardware operations. The other is ifcvf_main layer handles VF
initialization, configuration and removal, which depends on
and
This commit introduced IFC VF operations for vdpa, which complys to
vhost_mdev interfaces, handles IFC VF initialization,
configuration and removal.
Signed-off-by: Zhu Lingshan
---
drivers/vhost/ifcvf/ifcvf_main.c | 541 +++
1 file changed, 541 insertions(+)
This patch adds support for the input capture function in the
i.MX GPT. Output compare and input capture functions are mixed
in the same register block, so we need to modify the irq ack/enable/
disable primitives to not stomp on the other function.
The input capture API is modelled after
Add pin group bindings to support input capture function of the i.MX
GPT.
Signed-off-by: Steve Longerbeam
---
.../devicetree/bindings/timer/fsl,imxgpt.txt | 28 +++
1 file changed, 28 insertions(+)
diff --git a/Documentation/devicetree/bindings/timer/fsl,imxgpt.txt
This commit introduced ifcvf_base layer, which handles IFC VF NIC
hardware operations and configurations.
Signed-off-by: Zhu Lingshan
---
drivers/vhost/ifcvf/ifcvf_base.c | 390 +++
drivers/vhost/ifcvf/ifcvf_base.h | 137 ++
2 files changed, 527
This commit introduced IFC VF operations for vdpa, which complys to
vhost_mdev interfaces, handles IFC VF initialization,
configuration and removal.
Signed-off-by: Zhu Lingshan
---
drivers/vhost/ifcvf/ifcvf_main.c | 541 +++
1 file changed, 541 insertions(+)
From: MarkLee
Date: Mon, 14 Oct 2019 15:15:16 +0800
> This patch set has two goals :
> 1. Fix mt7629 GMII mode issue after apply mediatek
> PHYLINK support patch.
> 2. Update mt7629 dts to reflect the latest dt-binding
> with PHYLINK support.
Series applied, thank
Hi all:
This series intends to introduce Intel IFC VF NIC driver for Vhost
Data Plane Acceleration.
Here comes two main parts, one is ifcvf_base layer, which handles
hardware operations. The other is ifcvf_main layer handles VF
initialization, configuration and removal, which depends on
and
Hi trond,
Because My mail system cant receive nfs mail list’s mails, I reply your patch
here.
I have some question for the patch.
>No. Basic O_DIRECT does not guarantee atomicity of requests, which is
>why we do not have generic locking at the VFS level when reading and
>writing. The only
On 10/15/2019 5:14 PM, Jiri Olsa wrote:
On Tue, Oct 15, 2019 at 10:53:57AM +0800, Jin Yao wrote:
There are some deprecated events listed by perf list. But we can't remove
them from perf list with ease because some old scripts may use them.
Deprecated events are old names of renamed events.
kindly ping.
On 2019/10/9 9:47, Mao Wenan wrote:
> If CONFIG_TYPEC_HD3SS3220=y, CONFIG_USB_ROLE_SWITCH=m, below errors
> can be found:
> drivers/usb/typec/hd3ss3220.o: In function `hd3ss3220_remove':
> hd3ss3220.c:(.text+0x64): undefined reference to `usb_role_switch_put'
>
On Wed, Jul 10, 2019 at 01:31:13AM +0100, Al Viro wrote:
> On Tue, Jul 09, 2019 at 04:00:29PM -0700, Eric Biggers wrote:
>
> > > index 49a058c73e4c..26f74e092bd9 100644
> > > --- a/fs/pnode.h
> > > +++ b/fs/pnode.h
> > > @@ -44,7 +44,7 @@ int propagate_mount_busy(struct mount *, int);
> > > void
On Fri, Oct 11, 2019 at 05:26:05PM +0200, Benjamin Tissoires wrote:
> Hi Kai-Heng,
>
> On Tue, Oct 1, 2019 at 9:09 AM Kai-Heng Feng
> wrote:
> >
> > This reverts commit 883a2a80f79ca5c0c105605fafabd1f3df99b34c.
> >
> > Apparently use dmi_get_bios_year() as manufacturing date isn't accurate
> >
Hi Sebastian,
On 16/10/19 5:17 am, Sebastian Andrzej Siewior wrote:
From: Thomas Gleixner
CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_RT.
Both PREEMPT and PREEMPT_RT require the same functionality which today
depends on CONFIG_PREEMPT.
Switch the entry code over to
On Wed, Oct 16, 2019 at 02:41:35AM +0200, Christian Brauner wrote:
> Hey everyone,
>
> In v5.4-rc2 we added two new helpers check_zeroed_user() and
> copy_struct_from_user() including selftests (cf. [1]). It is a generic
> interface designed to copy a struct from userspace. The helpers will be
>
On 10/15/2019 11:11 PM, Arnaldo Carvalho de Melo wrote:
Em Tue, Oct 15, 2019 at 09:57:33AM +0800, Jin, Yao escreveu:
On 10/15/2019 12:23 AM, Arnaldo Carvalho de Melo wrote:
Em Mon, Oct 14, 2019 at 04:42:08PM +0200, Jiri Olsa escreveu:
On Fri, Oct 11, 2019 at 01:05:45PM +0800, Jin Yao
On 10/15/2019 09:40 AM, Xiaoyao Li wrote:
Move the MSR bitmap setup codes to vmx_vmcs_setup() and only setup them
when hardware has msr_bitmap capability.
Signed-off-by: Xiaoyao Li
---
arch/x86/kvm/vmx/vmx.c | 39 ---
1 file changed, 20 insertions(+),
In v5.4-rc2 we added a new helper (cf. [1]) copy_struct_from_user().
This helper is intended for all codepaths that copy structs from
userspace that are versioned by size. The bpf() syscall does exactly
what copy_struct_from_user() is doing.
Note that copy_struct_from_user() is calling min()
In v5.4-rc2 we added a new helper (cf. [1]) copy_struct_from_user().
This helper is intended for all codepaths that copy structs from
userspace that are versioned by size. bpf_prog_get_info_by_fd() does
exactly what copy_struct_from_user() is doing.
Note that copy_struct_from_user() is calling
In v5.4-rc2 we added a new helper (cf. [1]) check_zeroed_user() which
does what bpf_check_uarg_tail_zero() is doing generically. We're slowly
switching such codepaths over to use check_zeroed_user() instead of
using their own hand-rolled version.
[1]: f5a1a536fa14 ("lib: introduce
Hey everyone,
In v5.4-rc2 we added two new helpers check_zeroed_user() and
copy_struct_from_user() including selftests (cf. [1]). It is a generic
interface designed to copy a struct from userspace. The helpers will be
especially useful for structs versioned by size of which we have quite a
few.
On Tue, Oct 15, 2019 at 01:19:07PM +0200, Viktor Rosendahl (BMW) wrote:
> This patch implements the feature that the tracing_max_latency file,
> e.g. /sys/kernel/debug/tracing/tracing_max_latency will receive
> notifications through the fsnotify framework when a new latency is
> available.
>
>
On 10/15/19 5:27 PM, tim.b...@sony.com wrote:
-Original Message-
From: Shuah Khan on Monday, October 14, 2019 3:45 PM
Fix O= and KBUILD_OUTPUT handling for relative paths.
export KBUILD_OUTPUT=../kselftest_size
make TARGETS=size kselftest-all
or
make O=../kselftest_size TARGETS=size
> > diff --git a/include/uapi/linux/perf_event.h
> > b/include/uapi/linux/perf_event.h
> > index bb7b271397a6..2af95f937a5b 100644
> > --- a/include/uapi/linux/perf_event.h
> > +++ b/include/uapi/linux/perf_event.h
> > @@ -427,6 +427,15 @@ struct perf_event_attr {
> > __u16 __reserved_2;
Hi all,
Today's linux-next merge of the sound-asoc tree got a conflict in:
sound/soc/intel/boards/Kconfig
between commit:
82e8d723e9e6 ("sound: Fix Kconfig indentation")
from the sound tree and commit:
47cbea216281 ("ASoC: Intel: eve: Enable mclk and ssp sclk early")
from the
From: Michael Kelley
Date: Sun, 13 Oct 2019 00:30:21 +
> From: Himadri Pandya
>
> Current code assumes PAGE_SIZE (the guest page size) is equal
> to the page size used to communicate with Hyper-V (which is
> always 4K). While this assumption is true on x86, it may not
> be true for Hyper-V
From: Alexandre Belloni
Date: Thu, 10 Oct 2019 22:45:30 +0200
> When connected to a micrel phy, phy_find_first doesn't work properly
> because the first phy found is on address 0, the broadcast address but, the
> first thing the phy driver is doing is disabling this broadcast address.
> The phy
On Tue, Oct 15, 2019 at 10:30:08AM +0200, Peter Zijlstra wrote:
> On Mon, Oct 14, 2019 at 01:03:08PM -0400, Joel Fernandes (Google) wrote:
> > In current mainline, the degree of access to perf_event_open(2) system
> > call depends on the perf_event_paranoid sysctl. This has a number of
> >
When allocating tx ring buffers failed, should free tx buffers, not rx buffers.
Signed-off-by: Zhang Lixu
Acked-by: Srinivas Pandruvada
---
drivers/hid/intel-ish-hid/ishtp/client-buffers.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Add a drgn-based tool to display slab information for a given memcg.
Can replace cgroup v1 memory.kmem.slabinfo interface on cgroup v2,
but in a more flexiable way.
Currently supports only SLUB configuration, but SLAB can be trivially
added later.
Output example:
$ sudo
On Mon, Oct 14, 2019 at 05:29:53PM +0200, Jiri Olsa wrote:
> On Tue, Oct 08, 2019 at 08:35:54PM +0800, Changbin Du wrote:
> > When in TUI mode, it is impossible to show all the debug messages to
> > console. This make it hard to debug perf issues using debug messages.
> > This patch adds support
From: Jakub Kicinski
Date: Tue, 15 Oct 2019 15:39:55 -0700
> On Tue, 15 Oct 2019 15:32:28 -0700, Scott Branden wrote:
>> > @@ -3482,7 +3476,12 @@ static int bcmgenet_probe(struct platform_device
>> > *pdev)
>> >
>> >SET_NETDEV_DEV(dev, >dev);
>> >dev_set_drvdata(>dev, dev);
>> > -
On Sat, 12 Oct 2019, Daniel Colascione wrote:
> Documentation/admin-guide/sysctl/vm.rst | 19 +-
> fs/anon_inodes.c| 89 +
> fs/userfaultfd.c| 47 +++--
> include/linux/anon_inodes.h | 27 ++--
>
On Wed, Oct 16, 2019 at 12:22:31AM +0200, Paolo Bonzini wrote:
> Oh come on. 0.9 is not 12-years old. virtio 1.0 is 3.5 years old
> (March 2016). Anything older than 2017 is going to use 0.9.
Sorry if I got the date wrong, but still I don't see the point in
optimizing for legacy virtio. I
On 10/15/19 3:50 AM, Michal Hocko wrote:
> On Tue 15-10-19 11:01:12, Piotr Sarna wrote:
>> With hugetlbfs, a common pattern for mapping anonymous huge pages
>> is to create a temporary file first.
>
> Really? I though that this is normally done by shmget(SHM_HUGETLB) or
> mmap(MAP_HUGETLB). Or
Hi all,
This is now a conflict between the net and net-next trees.
On Mon, 14 Oct 2019 10:32:32 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/lib/bpf/Makefile
>
> between commit:
>
> 1bd63524593b ("libbpf: handle symbol
Could CONFIG_PREEMPT_RT be supported in csky ? Any arch backend porting ?
On Wed, Oct 16, 2019 at 3:18 AM Sebastian Andrzej Siewior
wrote:
>
> From: Thomas Gleixner
>
> CONFIG_PREEMPTION is selected by CONFIG_PREEMPT and by CONFIG_PREEMPT_RT.
> Both PREEMPT and PREEMPT_RT require the same
Hi all,
This is now a conflict between the net and net-next trees.
On Wed, 9 Oct 2019 09:47:25 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/lib/bpf/Makefile
>
> between commit:
>
> 1bd63524593b ("libbpf: handle symbol
Hi all,
This is now a conflict between the net and net-next trees.
On Tue, 8 Oct 2019 09:48:40 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the bpf-next tree got a conflict in:
>
> tools/lib/bpf/Makefile
>
> between commit:
>
> 1bd63524593b ("libbpf: handle symbol
> -Original Message-
> From: Shuah Khan on Monday, October 14, 2019 3:45 PM
>
> Fix O= and KBUILD_OUTPUT handling for relative paths.
>
> export KBUILD_OUTPUT=../kselftest_size
> make TARGETS=size kselftest-all
>
> or
>
> make O=../kselftest_size TARGETS=size kselftest-all
>
> In
On Fri, Oct 4, 2019 at 2:31 PM Guillaume La Roque wrote:
>
> Add minimal thermal zone for two temperature sensor
> One is located close to the DDR and the other one is
> located close to the PLLs (between the CPU and GPU)
>
> Acked-by: Martin Blumenstingl
> Reviewed-by: Neil Armstrong
>
On Wed, 14 Aug 2019 10:55:27 -0700
Divya Indi wrote:
> Adding 2 new functions -
> 1) trace_array_lookup : Look up and return a trace array, given its
> name.
> 2) trace_array_set_clr_event : Enable/disable event recording to the
> given trace array.
>
> NOTE: trace_array_lookup returns a trace
Currently, in order to enable interrupt-only mode, one must set
polling-delay-passive and polling-delay properties in the DT to 0,
otherwise the thermal framework will continue to setup a periodic timers
to monitor the thermal zones.
Change the behaviour, so that on DT-based systems, we no longer
Add space betwen operator to fix check warning.
Issue detected by checkpatch tool.
Signed-off-by: Jules Irenge
---
drivers/staging/vc04_services/interface/vchi/vchi_cfg.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue Oct 15, 2019 at 4:02 PM Alexei Starovoitov wrote:
> On Tue, Oct 15, 2019 at 3:55 PM Christian Brauner
> wrote:
> >
> > On Tue, Oct 15, 2019 at 03:45:54PM -0700, Alexei Starovoitov wrote:
> > > On Thu, Oct 10, 2019 at 2:26 AM Christian Brauner
> > > wrote:
> > > >
> > > > On Wed, Oct 09,
Sorry for taking so long to getting to these patches.
On Wed, 14 Aug 2019 10:55:26 -0700
Divya Indi wrote:
> For functions returning a trace array Eg: trace_array_create(), we need to
> increment the reference counter associated with the trace array to ensure it
> does not get freed when in
Subject: s/prunning/pruning/
Subject: s/:scripts:/scripts:/
On 10/15/19 7:55 AM, Bhaskar Chowdhury wrote:
> This patch will remove old kernels from system selective way.
in a selective way.
>
> Signed-off-by: Bhaskar Chowdhury
> ---
>
On Tue, Oct 15, 2019 at 3:55 PM Christian Brauner
wrote:
>
> On Tue, Oct 15, 2019 at 03:45:54PM -0700, Alexei Starovoitov wrote:
> > On Thu, Oct 10, 2019 at 2:26 AM Christian Brauner
> > wrote:
> > >
> > > On Wed, Oct 09, 2019 at 04:06:18PM -0700, Alexei Starovoitov wrote:
> > > > On Wed, Oct 9,
Fix line over 80 characters checks warning.
Issue detected by checkpatch tool.
Signed-off-by: Jules Irenge
---
.../vc04_services/interface/vchi/vchi_cfg.h | 150 ++
1 file changed, 88 insertions(+), 62 deletions(-)
diff --git
On Tue, Oct 15, 2019 at 03:45:54PM -0700, Alexei Starovoitov wrote:
> On Thu, Oct 10, 2019 at 2:26 AM Christian Brauner
> wrote:
> >
> > On Wed, Oct 09, 2019 at 04:06:18PM -0700, Alexei Starovoitov wrote:
> > > On Wed, Oct 9, 2019 at 9:09 AM Christian Brauner
> > > wrote:
> > > >
> > > > Hey
From: "Carlos E.C. Barbosa"
There is overlapping code over two distinct lists. This repurposes one
of vimc_pix_map for strictly mapping formats and remaps other calls to
the matching v4l2_format_info.
---
Change in v2:
- Change commit message
- Remove struct with mbus code and pointer to
RGMII connections are always troublesome because of the need to add
delays between the RX or TX clocks and data lines. This can lead to a
fair amount of breakage that upsets users.
Introduce a new sysfs write only attribute which can be set to 1 to
instruct the PHY library to attempt to probe
The standard way of putting a PHY device into loopback is most often
suitable for testing. This is going to be necessary in a subsequent
patch that adds RGII debugging capability using the loopback feature.
Signed-off-by: Florian Fainelli
---
drivers/net/phy/phy_device.c | 2 +-
1 file changed,
Hi all,
This patch series is primarily intended to reduce the amount of support
involved with bringing up RGMII connections with the PHY library (or
PHYLINK) for that matter. The idea consists in looping back a packet we
just crafted and check whether it did came back correctly, if that is
the
On Fri, 11 Oct 2019 14:50:21 +0200, Kamel Bouhara wrote:
> Document devicetree binding of SAMA5D27 Kizbox3 HS board from Overkiz
> SAS.
>
> Signed-off-by: Kamel Bouhara
> ---
> Documentation/devicetree/bindings/arm/atmel-at91.yaml | 7 +++
> 1 file changed, 7 insertions(+)
>
Reviewed-by:
On Fri, 11 Oct 2019 14:50:20 +0200, Kamel Bouhara wrote:
> Overkiz is a smarthome solutions provider, more information on:
> https://www.overkiz.com
>
> Signed-off-by: Kamel Bouhara
> ---
> Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
101 - 200 of 1039 matches
Mail list logo
